Cross-communication failure
Precisely one of the 2 possibilities apply:
A) The SDC is the cross-communication master and switches to isolated operation, i.e. it no longer participates in the cross-communication.
B) The SDC is the cross-communication slave and switches to isolated operation, i.e. it no longer participates in the cross-communication.
Note: Error 513 is only generated if cross communication is desired, i.e. if:
ID1102 "VL-Mode", Bit5 = 1 and
ID1109 "VL-Inter_Section" = 1
Signal to primary control by:
Setting the error bit in VL status
Output of the error number
Source and Remedy
Cause of A)
Incorrect parameterization
Identifier
ID1102 "VL-Mode", Bit0 set from 1 to 0 or
ID1050 "SIM-Command[Axle= 2]" set from 1 to 0 or
ID1114 "VL-DRR-Protocol" changed or
ID1115 "VL-ISR-Protocol" changed Reset and prevent incorrect parameterization .
Cause of A)
The ISR bit was deleted at a cross-communication slave.
Identifier
Check ID1102 "VL-Mode" at all slaves;
at one slave Bit5 = 0. Set and save Bit 5 to 1 for the slave concerned ID1102 "VL-Mode"
Cause of A)
The cross-communication ring has collapsed.
Identifier
ID1055 "SIM phase[Axle = 2]" < 402 Find the cause of the ring collapse.
Either the cross-communication master independently arrives back into phase 4, there e.g. the following is possible:
ID1058 "SIM-Slave-Number[Axle= 2]" was overwritten.
Reset or short-term voltage failure at two adjacent cross-communication slaves
Or the cross-communication master does not succeed in achieving phase start, then the following causes of error 511 are possible.
Cause of B)
Incorrect parameterization
Identifier
ID1102 "VL-Mode", Bit0 set from 0 to 1 or
ID1000 "SIS Command[Axle= 2]" set from 1 to 0 or
ID1114 "VL-DRR-Protocol" changed or
ID1115 "VL-ISR-Protocol" changed Reset and prevent incorrect parameterization .
Cause of B)
The ISR bit was deleted at another cross-communication slave.
Identifier
Check ID1102 "VL-Mode" at all slaves other; at one slave Bit5 = 0. Set and save Bit 5 to 1 for the slave concerned ID1102 "VL-Mode"
Cause of B)
The cross-communications ring has collapsed
Identifier
ID1005 "SIS-Phase[Axle= 2]" < 400
and with SDC 3.02 as master:
ID1055 "SIM-Phase[Axle = 2]" <402
or with MLC 3.02 as master:
ID2431 "SIMx Phase[Axle = Ring-No.] < 402 Find the cause of the ring collapse.
Either the cross-communication master independently arrives back into phase 4, there e.g. the following is possible:
Reset or short-term voltage failure at the cross-communication master
Restart the phase start at the cross-communication master
Reset or short-term voltage failure at two adjacent cross-communication slaves
Or the cross-communication master does not succeed in achieving phase start, then the following causes of error 511 are possible.
Cause of B)
The SDC is itself the 1st cross-communications slave in the ring and its 1st fibre optic input is faulty.
Identifier
ID1005 "SIS-Phase[Axle= 2]" = 0 and
ID257 "fibre optic distortion[Axle = 2]" > 0% and
LED "ERR" lights up.
At SDC 3.02 as master:
ID1055 "SIM-Phase[Axle = 2]" = 402
At MLC 3.02 as master:
ID2431 "SIMx Phase[Axle = Ring-No.] = 402 Check of own fibre optic receiver "IN1", the fibre optic cable at "IN1" and the fibre optic transmitter "OUT1" at the master. Replace defective hardware.
Check the transmitter power for "OUT1" at the master:
At SDC 3.02 as master:
Correct and save ID251 "1.LWL transmitter [Axle = 2]".
At MLC 3.02 as master:
Correct and save ID251 "1.fibre optic transmitter [Axle = ring number]".
Restart the cross-communication, i.e.:
At SDC 3.02 as master:
Overwrite ID1058 "SIM-Slave-Number[Axle= 2]" with the same value.
At MLC 3.02 as master:
Describe ID2533 "ML Ring-command[Axle= Ring No.]" with the value 1.
Cause of B)
At an SDC in the ring both the 1st and the 2nd fibre optic input is faulty.
The following are possible:
the cross-communication master,
the 2nd, 3rd ... and last cross-communication slave in the ring.
At all the slaves
ID1005 "SIS-Phase[Axle = 2]" = 400
Several SDC constantly switch backwards and forwards between "IN1" and "IN2".
The LED "ERR" lights up at almost all SDCs.
One of the possible SDCs displays both for "IN1" and for "IN2"
ID257 "fibre optic distortion[Axle = 2]" > 0%. Check "IN1" and "IN2" of the SDCs concerned, the fibre optic cable at "IN1" and "IN2" and the corresponding fibre optic transmitter. Replace defective hardware.
Check the transmitter powers set:
At SDC 3.02 as predecessor:
Correct and save ID251 "1. fibre optic transmitter [Axle = 2]".
At MLC 3.02 as predecessor:
Correct and save ID251 "1.fibre optic transmitter [Axle = ring number]".
At SDC 3.02 as predecessor:
Correct and save ID252 "2. fibre optic transmitter [Axle = 2]".
At MLC 3.02 as predecessor:
Correct and save ID252 "2.fibre optic transmitter [Axle = ring number]".
Restart the cross-communication, i.e.:
At SDC 3.02 as master:
Overwrite ID1058 "SIM-Slave-Number[Axle= 2]" with the same value.
At MLC 3.02 as master:
Describe ID2533 "ML Ring-command[Axle= Ring No.]" with the value 1.
Cause of B)
1. fibre optic output faulty
Identifier
ID1024 "SIS-Watchdog[Axle = 2]" displays the Max value 15 and
ID1005 "SIS-Phase[Axle = 2]" = 400 and
the successor has switched over to input "IN2", i.e.:
At SDC 3.02 as predecessor:
ID258 "optical fibre input [Axle = 2]" = 1
With MLC 3.02 as master:
ID258 "optical fibre input [Axle = Ring No.]" = 1 Pull off the optical fibre connection at "IN2" of the successor, in this way "IN1" automatically becomes active again.
Check of own fibre optic transmitter "OUT1", the fibre optic cable at "OUT1" and the fibre optic receiver "IN1" at the successor. Replace defective hardware.
Correct the ID251 "1.optic fibre transmitter [Axle= 2]" the following applies up to the receiver:
At SDC 3.02 as receiver:
ID257 "optical fibre distortion [Axle = 2]" = 1
With MLC 3.02 as Receiver:
ID257 "optical fibre distortion [Axle = Ring No.]" = 0%Save corrected transmitter power Reinstate the optical fibre link to "IN2" of the successor.
Restart the cross-communication, i.e.:
At SDC 3.02 as master:
Overwrite ID1058 "SIM-Slave-Number[Axle= 2]" with the same value.
At MLC 3.02 as master:
Describe ID2533 "ML Ring-command[Axle= Ring No.]" with the value 1.
Cause of B)
Older software version loaded onto cross-communication master
Identifier
ID1024 "SIS-Watchdog[Axle = 2]" displays the Max value 15 and the error occurs during putting into service. Load compatible software