How the work is put together
Most control-system projects are described in adjectives. A proposal that says “accurate and reliable” cannot be built. One that says “±0.5 % at 25 kg, 600 bags per hour, three-stage cut-off” can be built, tested and rejected if it misses.
Every proposal here starts with the number. Mass, throughput, tolerance, cycle count — fixed before a component is named. The hardware then has to earn its place against that number.
The experience behind them is shop-floor before it is academic: transferring schematics into physical harnesses, then proving the assembly against the drawing. That is where tolerance, routing and traceability stop being theory — a harness either passes continuity and insulation tests or it does not.
It also sets the limit of what is claimed. Standards are treated as design targets, never as credentials. Client and employer names stay off this site. Working equipment and test equipment are described by what they do, not by whose badge is on them.
- Weighing
- Load cells, three-stage cut-off, in-flight compensation
- Control
- PLC (S7-1200 / S7-300), HMI, sequencing, interlocking
- Vision
- Camera sorting, classification, reject actuation
- Networks
- Modbus, CAN, MQTT, SCADA logging
- Assembly
- Schematic to harness, continuity and insulation testing
- Documentation
- Objectives, scope, method, schedule, acceptance criteria
Method
- Step 01Fix the numberMass, throughput and tolerance are agreed before any hardware is named.
- Step 02Draw the chainSensor, controller, actuator, reject — every element carries the value it has to hold.
- Step 03Build and measureThe prototype is judged against the number, not against how it looks.
- Step 04Record the evidenceResults, deviations and the test that produced them stay with the drawing.
What a proposal contains
Talk about a topic or a plant.
Proposals, supervision or a second opinion on an existing design.