You call or message
Fault code, machine make, and what it was doing right before it stopped — the more specific, the faster we can help.
The helpline is not a ticket queue. An engineer who has worked on drives and panels picks up, asks for the fault code, and tells you whether it needs a visit — before you've even finished explaining the problem.
Fault code, machine make, and what it was doing right before it stopped — the more specific, the faster we can help.
An engineer who has actually worked on drives and panels talks you through a first check — half of calls are resolved right here.
If it needs more, we connect remotely where a gateway exists, or dispatch an engineer within your plan's response window.
Root cause noted against the machine's history — so the third occurrence of the same fault gets a permanent fix, not another visit.
Three plans, built around how much downtime a line can actually absorb. Pricing depends on panel count, drive count and site distance — confirm with a survey before quoting a customer.
Response: within 48 hours
For lines with a spare or a backup process — support that keeps small faults from becoming big ones.
Response: same working day
For lines that can absorb a few hours of downtime but not a full shift — the plan most of our multi-line customers run.
Response: within 4 hours, on-site
For a line where an hour of downtime is a real number on someone's desk. Built around the customers this matters most to.
Where a gateway already exists from an IIoT install, we connect over the same secure link — never a port opened directly to the PLC.
Pulling the drive or PLC's live fault history to confirm the actual cause before dispatching anyone.
Walking your operator through a parameter check or a safe restart sequence, step by step.
If it does need a visit, the engineer arrives already knowing the fault code, the history, and what's been tried.
Tell us your panel and drive count, and which lines matter most. We'll recommend a plan — no obligation.