MOTN-176: Failed to enter slave mode
The robot could not be set as a slave.
What it means
The robot could not be set as a slave. The setup data or group mask in the program may be wrong, or the robot is still in motion when the slave assignment was attempted.
Common causes
Ranked by what technicians most often find, most likely first.
- Incorrect setup data in the program.
- Incorrect group mask in the program.
- The robot was still moving when slave mode was requested.
How to fix it
- Verify the setup data in the program is correct.
- Verify the group mask in the program is correct.
Quick facts
- Category
- Motion
- Affected series
- R-30iB; R-30iB Mate; R-30iB Plus; R-30iB Mate Plus
- Alarm family
- MOTN