Migatronic RCI2, User Manual

Page: 69 / 80

68 69
ERROR LIST
Error
code Problem Solution
E.33-00 CAN MigaOpen -
Device initialization timeout - Error in configuration file
- CAN bus error
- Check CAN connection to welding machine
E.33-01 CAN MigaOpen - Device response error - CAN bus error
- Check CAN connection to welding machine
E.33-02 CAN MigaOpen - Device watchdog One of the connected CAN controlled units has stopped sending Alive
signal. Exchange the defective unit.
- Check all connected units
E.33-03 CAN MigaOpen - Device status error This information is send to the Robot controller, because there is a “legal”
error on the welding machine or wire feeder. Like GAS or TEMP error
- Correct the error on the welding machine
E.33-04 CAN MigaOpen - Rule initialization timeout - Check the setup of RCI
2
- Exchange RCI
2
PCB 71617074
E.33-05 CAN MigaOpen -
Network initialization timeout Unable to connect to MIGANET,
- Check CAN connection to welding machine and all connected devices
E.33-20 Analog I/O - Rule initialization error - Error in configuration file
- Check/Reload configuration file
- Check connected devices
E.33-21 Analog I/O - Error on received output
message - Error in configuration file
- Check/Reload configuration file
- Check connected devices
E.33-22 Analog I/O - Task unknown state - Check the setup of RCI
2
E.33-40 Fieldbus- Anybus - module not present - A configuration file for an Anybus module is loaded in to RCI
2
but the
Anybus module is not mounted.
- Place the Anybus module in the socket
E.33-41 Fieldbus- Anybus - unsupported module
type - The installed software version does not support the mounted Anybus
module
E.33-42 Fieldbus- Anybus - Driver information - Anybus module is defective. See also next pages “Anybus – Error list
E.33-43 Fieldbus- Anybus - Driver warning - Anybus module is defective. See also next pages “Anybus – Error list
E.33-44 Fieldbus- Anybus - Driver fatal error - Anybus module is defective. See also next pages “Anybus – Error list
E.33-45 Fieldbus- Anybus -
Module communication timeout - Anybus module is defective. See also next pages “Anybus – Error list
E.33-46 Fieldbus- Anybus -
Network configuration error - Anybus module is defective. See also next pages “Anybus – Error list
E.33-47 Fieldbus- Anybus -
Process-data configuration error - Anybus module is defective. See also next pages “Anybus – Error list
E.33-48 Fieldbus- Anybus - Activation error - Anybus module is defective. See also next pages “Anybus – Error list
E.33-49 Fieldbus- Anybus - Module error - There is at least one serious network error.
- Check network cable
- Check robot/PLC setup
- Exchange the Anybus module if a restart is not solving the problem
See next page
E.33-50 Fieldbus- Anybus - Module exception - The Anybus module has ceased all network participation due to a host
application-related error. This state is unrecoverable, i.e. the module
must be restarted in order to be able to exchange network data.
- Exchange the Anybus module if a restart is not solving the problem
See next page
E.33-51 Fieldbus- Anybus - Too many listen objects - Error in configuration file
- Check/Reload configuration file
E.33-52 Fieldbus- Anybus - Task unknown state - Check the setup of RCI
2
E.34-00 CAN MigaOpen Network Error - Check IDs settings of connected devices.
E.80-00 Class A trap - Check the setup of RCI
2
E.80-01 Class B trap - Check the setup of RCI
2
E.80-02 Vector trap - Check the setup of RCI
2