SRVO-481: Invalid payload number
The collaborative robot's current payload number is invalid - and here's the gotcha that catches nearly every new cobot install: the default payload number is 0, which is deliberately invalid.
What it means
The collaborative robot's current payload number is invalid - and here's the gotcha that catches nearly every new cobot install: the default payload number is 0, which is deliberately invalid. The robot refuses to run until you tell it what it's carrying, because a cobot's contact-stop sensitivity is only as good as its payload data.
Common causes
Ranked by what technicians most often find, most likely first.
- Payload number still at the factory default of 0 - nobody set it during commissioning.
- Program selecting a payload schedule that was never configured.
How to fix it
- Set the payload number to a configured schedule between 1 and 10 (and make sure that schedule's mass/CG data reflects the real tooling). This isn't bureaucracy - collaborative force limits are computed against this data.
Quick facts
- Category
- Servo
- Affected series
- R-30iB Plus / Mate Plus (collaborative CR/CRX systems)
- Alarm family
- SRVO