Robot Remote Diagnostics
What remote diagnostics actually means
Your robot faulted at 2 a.m. The line is down and the morning shift starts in six hours. You do not need an engineer on a plane. You need someone to read the log tonight. That is what remote diagnostics is: your engineers stay on site with the robot, and we read the fault with you from wherever we are, using what the controller already tells you.
Send us the event-log export and a photo of the alarm screen, and we read the root cause with you the same day. No travel, no waiting for a visit window, just the log, a photo and a reply.
Diagnosis is free, there is no site visit, and we aim to quote within 24 hours. You only pay if you decide to order a part.
How remote diagnostics works
You send three things and we do the reading. It is deliberately light on your side, because the person on site is busy keeping the cell safe:
- The event log: exported from the controller (ABB: Event Log; FANUC: Alarm → History). The log shows the sequence of faults, not just the last red line, which is usually where the real cause hides.
- A photo of the alarm screen: including the code and any group/axis reference. One clear photo beats ten guesses.
- A short video (optional): If the fault is intermittent, a clip of the behaviour tells us more than a description.
From there we map the fault to the subsystem, name the likely failed part, and tell you the one check that confirms it before you spend a cent on hardware.
What we can read remotely
A controller is talkative if you know where to look. From the log and screen alone we can usually separate a real hardware failure from a setting, a safety input or a battery that simply ran out:
| What you see | What it often means | Confirmed remotely? |
|---|---|---|
| Repeated alarm code (e.g. ABB 38200 / FANUC SRVO-062) | Battery backup lost, position data at risk | Yes, and we tell you the save step |
| Overcurrent / OVC at one axis | Motor, cable or amplifier on that axis | Partly: the log narrows it to the axis |
| Communication lost with PLC | Fieldbus / I/O / safety input, not the robot | Yes: points at the bus, not the arm |
| Not mastered / pulse mismatch | Battery or encoder; re-master needed | Yes, and we give the sequence |
What we need from you
The single most useful thing is the robot serial number. That alone lets us pull the exact configuration and the compatible spare, so we are not guessing from a model family. If you have them, also send:
- Controller model and software version (ABB IRC5 / OmniCore + RobotWare; FANUC R-30iB Plus + V8/V9)
- The alarm code exactly as shown, with the group/axis reference
- The event-log export or a photo of the alarm history
You do not need to diagnose it yourself. Sending the serial and the alarm is enough to start. We do the reading.
No site visit required
Your engineers are the ones with hands on the robot; we support you remotely. That is the whole model: you stay in control of the cell, we give you the diagnosis and the part confirmation, and nobody books a flight. For most faults the fix is a confirmed part and a clear check you can run on site, which is also why we never pad a quote with a visit you did not need.
From diagnosis to the right part
Once we have read the log, we confirm the exact part number against your serial, not a "probably fits" guess. You order only what the fault actually calls for, and where a repair is the cheaper right answer we say so. That is the difference between a quote built on a photo and a quote built on a site guess: you buy the amplifier only when the fibre was not the only thing broken.
Send us the event log and the alarm photo and we will read the root cause with you remotely, then confirm the exact spare. You order only what the fault calls for.
FAQ
Which faults can you diagnose remotely?
Most: alarm codes, battery/position loss, overcurrent narrowed to an axis, fieldbus and PLC communication loss, and "not mastered" conditions. Where a fault needs a meter on a live winding we tell you the exact check to run on site and read the result with you.
What do I need to send?
The robot serial number is enough to start. Add the controller model, software version and a photo or export of the alarm, and we can name the part. You do not need to have diagnosed anything first.
Can I just ask a technical question without buying a part?
Yes. If the log shows the cause is a setting, a safety input or a battery you can handle, we tell you that directly. Getting your line running is the point, not selling a part you do not need.
What information do I need for a quote?
Serial number plus the alarm detail. We confirm the exact spare against your configuration and aim to return a quote within 24 hours. All parts carry 12 months cover, with extended cover available on request.
SongWei Robotics is an independent robot-parts supplier and is not affiliated with ABB, FANUC, KUKA or YASKAWA. All brand names, product numbers and trademarks are the property of their respective owners.
