FANUC CRX Cobot: Tablet Programming, Collaborative Mode, and Hand-Guidance Quirks That Trip Up Field Crews

The CRX shows up on a pallet, you unbox it, plug in the tablet, and try to apply what you learned on R-30iB cells. Nothing behaves the way you expect: block programming instead of TP, force sensing that caps speed without telling you, and hand guidance that only works when you press the right button on the wrist module. The CRX is a FANUC robot underneath, but the cockpit is genuinely different. At Probot Systems we deploy CRX-10iA and CRX-25iA cells alongside traditional FANUC arms, and the same surprises trip up customers every time.

This post is written for technicians and integrators commissioning their first CRX, or troubleshooting CRX-specific behaviour on a cell where the rest of the plant runs R-30iB cabinets. The cobot range covered is CRX-10i, CRX-10iA, CRX-25iA, and CRX-30iA. All of them share the tablet workflow and the collaborative-mode logic.

What this error actually means

CRX-specific surprises tend to surface as unexpected slow motion (the collaborative-mode speed cap kicked in), hand guidance refusing to engage, or alarms that look like R-30iB alarms but mean something slightly different on the CRX. The most common alarms in this family are SRVO-485 Hand Guidance overspeed, SRVO-486 Hand Guidance E-stop, SRVO-487 Hand Guidance Deadman switch, and SYST-212 Need to apply to DCS param, which appears after any safety zone or mastering change.

Per the FANUC error code manual on SRVO-485: “Operation speed by Hand Guidance exceeds limit. Remedy: Check limit speed setting of Hand Guidance.” On SRVO-487: “The DEADMAN switch of Hand Guidance device was not pressed. Remedy: Press the DEADMAN switch to release it, then press RESET. If you want to use with Collaborative robot, enable Contact stop.” Both alarms are clearly documented, but they only show up because somebody tried to use hand guidance the wrong way.

The shop floor reality: the CRX has force sensors in every joint, a tablet-based block programming environment, and a wrist module with two buttons. Collaborative mode is the default, and it automatically caps speed when force exceeds the configured threshold. To run at production speed, you have to switch modes. To hand-guide, you have to press the right button and hold the deadman.

Most common causes, in order of probability

1. Expecting the traditional TP workflow on the tablet pendant. The CRX tablet shows block programming by default. TP-style editing is available under the advanced settings, but you have to go looking for it (Reddit CRX tablet pendant thread).
2. Collaborative mode left on for full-speed work. The CRX runs slowly until you switch out of collaborative mode in the safety menu.
3. Hand guidance attempted without the wrist button. The wrist module has two buttons (green and yellow). Hand guidance requires the green one to be pressed and held. Pressing the tablet button alone does nothing.
4. Option file differences from R-30iB tutorials. A KAREL utility, an Ethernet/IP setup, or a custom HMI written for an R-30iB will not load identically on a CRX. The order file is different, and options that exist on the R-30iB may have a different code on the CRX. A Reddit thread titled “I’ve messed up our CRX10i” documents exactly the kind of cross-controller confusion that produces SYST-212 chains (reference).
5. Mastering or DCS changes not applied. Any safety zone or mastering change on the CRX puts you in SYST-212 territory, just like on an R-30iB. The fix is the same (F3 APPLY in the DCS menu), but the menu lives behind the legacy pendant view on the tablet.

How to diagnose in under 10 minutes

Step 1. Confirm the collaborative mode state. On the tablet, navigate to Settings > Safety > Robot Mode. The current mode is clearly displayed. If “Collaborative” is selected, the robot will cap speed when force exceeds the threshold. If “High Speed” or equivalent is selected, the robot runs at full TCP speed but requires perimeter guarding.

Step 2. Read the alarm log. The tablet has its own alarm view, but the legacy pendant view (Settings > Switch to TP view) shows the full FANUC alarm log, including the SRVO-48x family for hand guidance and the SYST-21x family for DCS.

Step 3. Test hand guidance. With the robot in T1 or collaborative mode, press and hold the green button on the wrist module while pressing the deadman on the tablet. The robot should move freely with low resistance. If it does not move, either the green button is not making contact (mechanical issue) or the hand-guidance option is not enabled in the safety configuration.

Step 4. Confirm that the tablet firmware matches the controller firmware: Settings > About on the tablet, and MENU > STATUS > Version ID in the legacy view. A mismatch causes intermittent block-to-TP translation issues.

Step 5. Check the order file. In the legacy pendant view, go to MENU > STATUS > Version ID > F1 [ORDER FILE]. The CRX has its own option codes, and assuming an R-30iB tutorial applies because “it is still a FANUC” is how cells end up with options that do not load. The CRX experiences thread on Reddit collects multiple examples of this (reference).

How to fix it

For tablet vs. TP programming:

Use the tablet block view for simple sequences and operator-edited routines. For complex motion, IO logic, or anything that needs Mixed Logic / BG Logic, switch to the legacy pendant view. The tablet and TP code are the same underneath; the tablet is simply a higher-level editor.

For the collaborative-mode speed cap:

If you need full speed, switch out of collaborative mode in Settings > Safety. This requires a fenced cell or appropriate guarding. If you need to keep collaborative mode but want a specific zone to run faster, configure the DCS speed zones to allow higher speed only inside the production envelope. The DIY Robotics community thread on disabling CRX Contact Stop discusses exactly this trade-off (reference).

For failing hand guidance:

Confirm that the green button on the wrist module makes contact. A worn or dirty contact will register on the tablet but will not provide the hand-guidance enable. If the button is good and hand guidance still fails, check the safety option list (legacy MENU > STATUS > Version ID > Order File) for the hand-guidance option code. Not all CRX configurations ship with hand guidance enabled.

For option file differences:

Treat the CRX as a separate platform. Use CRX-specific tutorials and the FANUC CRX Maintenance and Operator Manuals, not the R-30iB equivalents. KAREL utilities must be recompiled against the CRX firmware. Ethernet/IP setups use the same EDS file format, but the CRX configuration menu is restructured.

For SYST-212 after a CRX change:

Switch to the legacy pendant view, go to MENU > 0 NEXT > 6 SYSTEM > DCS, press F3 APPLY, and enter the code. It is the same workflow as on the R-30iB, just hidden behind one extra step (switching views). The Reddit “messed up our CRX10i” thread documents how this caught users off guard (reference).

For SRVO-485 / 486 / 487 hand-guidance alarms:

SRVO-485 (overspeed) requires lowering the limit or guiding more slowly. SRVO-486 (E-stop on the hand-guidance device) means the deadman was released; reset and try again. SRVO-487 means the deadman was not pressed when the system expected it. If you do not want hand guidance at all, the manual remedy is: “Set Hand Guidance disable I/O to ON if you do not use Hand Guidance function then.”

When to call a specialist

Two situations are worth a service call:

You are commissioning your first CRX and want the safety zones, collaborative mode boundaries, and hand-guidance behaviour configured correctly for the planned application. This is a documented setup with a stopping-time validation (the CRX-25 stopping-time documentation referenced in the French DIY Robotics thread is part of the standard worksheet). Getting it right the first time is faster than iterating on the floor (reference).

You need to integrate the CRX with a PLC, a vision system, or KAREL utilities ported from R-30iB cells. The platform differences are real and are not documented in the marketing material. Mapping an SPI to a DO on the CRX is a workflow of its own (DIY Robotics community thread).

Contact us for CRX commissioning, or schedule a preventive maintenance visit so the collaborative-mode configuration is reviewed before each production batch.

Related errors to check

• SYST-212 Need to apply to DCS param: any DCS or mastering change. Same fix as on the R-30iB, but hidden behind the legacy view.
• SRVO-485 Hand Guidance overspeed: the speed limit during hand guidance was exceeded. Lower the limit or guide more slowly.
• SRVO-486 Hand Guidance E-stop: the deadman or E-stop on the hand-guidance device was released.
• SRVO-487 Hand Guidance Deadman switch: the deadman was not pressed when the system expected it.
• SRVO-378 SFDIxx status abnormal: dual-channel safety signal mismatch. Same fix as on R-30iB cabinets (check both channels, replace the E-stop board if needed).
• SYST-322 series and SYST-325: CRX-specific safety and collaborative-mode alarms.

Probot Systems is a FANUC integrator based in Lévis, Quebec, serving Canada and the US. We deploy CRX-10iA, CRX-25iA, and traditional R-30iB cells in the same plants, and we know the platform differences from working with them side by side. If your CRX behaves differently from the rest of your FANUC fleet and you cannot figure out why, that is a conversation worth having: contact us.