A Force Control URCap program completed its first run but reported a Node Executor error on the second run. The available evidence identifies a software update—not a confirmed programming defect—as the supported first corrective action: update Robotiq Force Copilot to version 1.7.1 and repeat the execution test.
Observed Failure
The failure occurs when the same programmed sequence runs for a second time. The evidence does not include the exact error text, program file, controller version, URCap version currently installed, or node configuration, so it cannot establish that the program logic caused the fault.
Supported Root-Cause Assessment
| Item | Evidence-based status |
|---|---|
| Failure point | Second execution of the programmed sequence |
| Error category | Node Executor error |
| Confirmed program defect | Not established |
| Supported corrective release | Force Copilot 1.7.1 |
Robotiq states that Force Copilot 1.7.1 fixes most Node Executor errors. This supports treating the installed software version as the first diagnostic branch, but it does not prove that every Node Executor error has the same cause.
Update and Retest Procedure
- Record the currently installed Force Copilot version and preserve the existing program before changing the installation.
- Update Force Copilot to version 1.7.1 using the applicable Robotiq installation process.
- Run the same program once, then run it a second time under the same operating conditions.
- Confirm whether the Node Executor error returns on the second execution.
Verification and Escalation
If both executions complete without the error, document version 1.7.1 as the corrective change. If the error persists, retain the exact error display and the sequence location where execution stops, then provide those details and the program to Robotiq through an official support channel. The available evidence does not support additional node edits or controller changes.
FAQ
How do I fix a Force Copilot Node Executor error?
Update Robotiq Force Copilot to version 1.7.1, then execute the same program twice to verify whether the second-run error is resolved.
Does a Node Executor error prove my robot program is wrong?
No. The evidence does not confirm a programming defect, while Force Copilot 1.7.1 is specifically reported to fix most Node Executor errors.
What should I collect if Force Copilot 1.7.1 still fails?
Capture the exact error display, identify where the sequence stops, record the installed software version, and retain the program for review through an official Robotiq support channel.
