Most equipment projects do not fail on the shop floor. They fail much earlier, in the gap between a product idea and the first decision on how to build it. The questions arriving engineers face are rarely exotic: can this idea actually be made, what should the machine be built around, what will the first prototype cost, and where will it break. PLC and HMI integration sits at the centre of that gap, because it is the layer where the operator meets the machine and where every design assumption is finally exposed. The route from idea to prototype is a sequence of small, checkable steps, and it is shorter than most teams expect.
Start with the control architecture, not the panel
Teams that treat the control system as the last box on the drawing end up redesigning the machine around a panel that was never going to fit. A prototype is a control project as much as a mechanical one. Before anything is cut, the control tasks should be written down as a plain list: what has to run continuously, what has to be interlocked, what has to be protected against, what the operator must be able to see, and what has to stop the machine when something goes wrong.
That list drives everything downstream. It determines the number of inputs and outputs, the size of the cabinet, the safety devices, and the amount of code. It also fixes the boundary between the PLC and the HMI: the PLC owns logic, sequencing, alarms and protection; the HMI owns presentation, setpoints, and permission. Getting that boundary wrong is the single most common cause of rework on a first prototype.
Five steps from a concept to a testable machine
1. Fix the scope of the first build. A prototype exists to answer questions, not to be a product. Choose the three functions that carry the highest technical risk and build those; leave convenience features out. Everything else is deferred to a later iteration, which is why the build stays affordable.
2. Define the I/O before the structure. Count valves, motors, sensors, and safety devices. The count sets the PLC size and the cabinet layout, and the cabinet has to live somewhere inside the frame. Fixing the machine envelope first and looking for panel space afterwards is how projects get late, expensive surprises.
3. Write the control logic as states. Mode, step, permitted actions, and alarms. State-based logic reads like the machine behaves, which makes it testable and makes the HMI design almost automatic, because the screens simply report and command the same states.
4. Wire the protection layer first. Emergency stops, interlocks, dry-run and leakage protection, and safe shutdown are not extras to be added once the machine runs. They are the reason a prototype can be tested safely, and they are the first items a customer or an inspector will look for.
5. Prove it with a documented test. A prototype that was only observed running is not validated. Function tests, performance tests under real conditions, continuous-operation checks, and an electrical safety check produce a record that supports the decision to build the next version.
How PowerDe develops equipment from idea through prototype
Shenzhen PowerDe Automation Precision Equipment Co., Ltd. has built equipment since 2007, and its engineering services are organised around exactly this path. The product R&D accelerator is the entry point for a team that has a concept but no engineering package: the idea is assessed for feasibility, the mechanical, electrical, control and system modules are mapped out, an initial cost and cycle estimate is produced, and a prototype route is agreed before a large R&D budget is committed.
Once the direction is settled, product development services carry the project from drawings to hardware. PowerDe handles the mechanical structure, sheet-metal and enclosure work, the electrical schematics, the electrical cabinet, the control program, sensor and actuator integration, and the human-machine interface, then assembles the prototype, runs the debugging, and produces the test record. BOM, assembly process documentation, and inspection standards are prepared so the same machine can move into small-batch trial production without being reinvented.
Verification is a service in its own right rather than an afterthought. The hardware testing programme covers control panel and HMI function, actuator response, alarm and protection behaviour, pressure, temperature and flow performance, continuous and repeated start-stop running, and electrical safety checks such as leakage and emergency-stop response. The output is a problem list, a cause analysis, and an optimisation plan, which is what a decision to fund the next build should be based on.
A worked pattern: a steam cleaning machine prototype
PowerDe's own product line shows what this looks like in practice, because its machines combine heating, pumping, and vacuum functions with an operator interface. The fixed PowerDe HW02 steam cleaning machine switches between dry steam and wet steam, adds vacuum cleaning, and is fed from a tap-water inlet on a 220 V supply. That behaviour is not one big program; it is a set of control decisions that a PLC handles cleanly and an HMI makes usable.
Read those decisions as a checklist for any prototype in this class of equipment:
- Mode selection. Dry steam, wet steam, and vacuum modes require different valve and pump combinations. The PLC enforces which combinations are legal; the HMI only offers the modes the machine will actually permit.
- Process values as setpoints, not code. The HW02 page lists a steam temperature of 160°C and a vapour pressure of 0.8 MPa. In a prototype these belong in a parameter block that the HMI can adjust and the PLC enforces limits on, so tuning does not require rewriting logic.
- Protection as hard interlocks. Leakage, short-circuit, high-temperature, high-voltage and water-shortage protection are interlocks and safe-state behaviour, not pop-up messages. Water-shortage protection in particular must shut the heater down independently of whatever screen the operator is on.
- Alarms the operator can act on. The HMI should state which sensor or which circuit is at fault and what to do about it, and it should log the event so the same fault can be traced over a test campaign.
- Serviceability of the panel. Cabinet layout, cable routing and access matter as soon as the machine is being debugged; a panel that is hard to reach slows every test iteration.
Prototype or production-ready product
The practical question after the first build is not whether it ran, but whether the next build is the last one before customers see it. Two answers change the plan. If the project is still exploring whether the machine is worth building at all, a single prototype and a test report are the right investment, and nothing more should be committed. If the machine works and a brand or a market is behind it, then the work shifts to OEM and ODM territory: appearance and logo customisation, functional module selection, and production import. PowerDe supports both routes through its customised solutions, and through an integrated engineering team when the customer's own staff cannot cover mechanical, electrical, automation, test and manufacturing work at the same time.
What to decide before the first panel is quoted
Before a PLC and an HMI are bought, three decisions should be written down. First, which control tasks the machine must perform on its own and which the operator must be allowed to change. Second, the input and output count that follows from that split, with spare capacity kept for the iteration you have not thought of yet. Third, the pass or fail criteria for the prototype, agreed before it is built, so the test at the end produces a decision rather than a debate.
Teams that make these decisions up front spend most of their budget on the machine. Teams that do not spend most of it on rework. PowerDe's path from requirement definition through technical feasibility assessment, product architecture, prototype route design, and validation is built around making those decisions early, and it starts with a conversation about the idea rather than a quotation.
Have an equipment concept that needs a control architecture and a first prototype? Send your requirements to PowerDe Automation at sales@powerde.net, or call +86 13023198376 to discuss the technical route, prototype plan and cost range.
