IV - 136
Appendix 7. Explanation of Alarms
Appendix 7.10 Multi CPU Errors (A)
A01 MULTI CPU ERROR 3015
Details
- In a multiple CPU system, the parameter settings are different between the modules.
Remedy
- Read the error details using a programming tool, check and correct the details of the
parameter that corresponds to the read value (parameter No. or CPU No.), as well as the
parameter of the target module.
A01 MULTI CPU ERROR 3100
Details
- The number of actually installed modules is different from that designated in the number of
modules setting parameter of MELSECNET/H.
- The head I/O number of actually installed modules is different from that designated in the
network parameter of MELSECNET/H.
- Some data in the parameters cannot be handled.
- The station type of MELSECNET/H has been changed while the power is ON.
(Reset and restart is required to change the station type.)
Remedy
- Check the network parameters and actual mounting status, and if they differ, make them
matched.
If any network parameter has been corrected, write it to the CPU module.
- Check the extension base unit stage No. setting.
- Check the connection status of the extension base units and extension cables.
When the GOT is bus-connected to the main base unit and extension base units, also
check the connection status.
- If the error occurs after the above checks, the possible cause is a hardware fault. Contact
your local service center.
Details
- In a multiple CPU system, the MELSECNET/H under control of another CPU is specified
as the head I/O number in the network setting parameter of the MELSECNET/H.
Remedy
- Delete the MELSECNET/H network parameter of the MELSECNET/H under control of
another CPU.
- Change the setting to the head I/O number of the MELSECNET/H under control of the
host CPU.
Details
- The network parameters of the MELSECNET/H operating as a normal station was
changed to the control station, or the network parameter of the MELSECNET/H operating
as a control station was changed to a normal station.
(The network parameter is updated on the module side by resetting.)
Remedy
- Reset the CPU module.