Baumuller Error No. 512

Redundancy case in the cross-communication

The SDC has Phase 0 in the cross-communication ring and can receive master-sync telegrams.

Phase start is however, not possible as the cross-communication master is in Phase 4. Error 512 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. Acknowledge after error correction:

Source And Remedy

Reset or short-term voltage failure at the SDC
Identifier
ID1005 "SIS-Phase[Axle = 2]" = 0 and 
ID257 "optical fibre distortion[Axle = 2]" < 70%
With SDC 3.02 as master: 
ID1055 "SIM-Phase[Axle = 2]" = 402
At MLC 3.02 as master: 
ID2431 "SIMx Phase[Axle = Ring-No.] = 402 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. 
Wrong number of slaves

Identifier
At SDC 3.02 as master: 
Check the ID1055 "SIM-Phase[Axle = 2]" = 001
for MLC 3.02 as master: 
Check the ID2429 "SIMx SlaveNumber[Axle= Ring No.] 
The value does not equal the number of cross communication slaves. At SDC 3.02 as master: 
Correct and save ID1058 
with MLC 3.02 as master: 
Correct and save 
ID2501 "ML Member 1[Axle = Ring No.] to 
ID2532 "ML Member 32[Axle = Ring No.] 

Baumuller Error No. 132

Offset of the analog position differs by more than one sector

          The error message is triggered by the pick-up monitoring module if the offset monitoring of the analog position is active and the offset of the analog position has changed by more than one sector. Offset monitoring of the analog position is activated by bit 11 in the parameter ID280 "G-Mon.Command Ax" and can trigger a fatal error if bit 11 is also set in the parameter ID282 "G-Mon.error_mask".

          The positional information of a SINCOS rotary encoder is coded with the help of an analog sinus and an analog cosine track (a sine/cosine period equals one PPR). The angle within a stroke period is calculated as follows:
Angle = arc tan (measured sine value/measured cosine value).

          The track signals are used in the main processor (DSP) to continuously calculate the position. Positional information from the track signals is also formed in a register of the CPLD (A1) within the pick-up evaluation of the drive controller. The analog positions of the two separate pick-up signal evaluations are continuously compared with each other. As the CPLD register is reset to zero at the time a rotary encoder is activated, an offset arises between the analog position (i.e. the calculated position in the DSP) and the position value in the CPLD register, which depends on the current position on activation of the rotary encoder. This offset value is calculated on initialisation of the rotary encoder and is displayed in parameter ID2345 (“Analog Offset [Ax]“).

         The error is triggered if the offset changes by more than one sector, i.e. more than 90° related to a signal period. The error is fatal and leads to immediate shutoff of the drive controller. In this case the drive coasts to a standstill.
         Renewed release of the drive by the controller is prevented until the cause of the error has been corrected and the error has been acknowledged.
The error can be acknowledged from the control centre after the cause of the error has been corrected.

Source And Remedy 

If the error occurs repeatedly, 
the rotary encoder or the pick-up lead may be defective, 
the M drive may be defective 
Check the pick-up lead for correct plugged connections, intact signal leads and functioning shielding.
If necessary, replace the controller cassette or the rotary encoder.

Baumuller Error No. 7

Link/activate module error

A program module was found to be missing on starting the controller software program. This error is used for diagnosis during software development. The error does not occur during operation.

The controller software is not started correctly. The drive controller cannot be released.

Source and Remedy 
The controller software was wrongly generated or saved. Replace the controller software. 

Baumuller Error No. 6

 Link/activate module error

Initialisation of part of a program incorrectly terminated on starting the controller software program. This error is used for diagnosis during software development. The error does not occur during operation.

The controller software is not started correctly. The drive controller cannot be released.

Source and Remedy 
The controller software was wrongly generated or saved. Replace the controller software. 

Baumuller Error No. 566

Power section error auxiliary voltage supply

The auxiliary voltage supply is monitored and generates an error message if undervoltage occurs. The error is fatal and leads to immediate shutoff of the drive controller. In this case the drive coasts to a standstill. Renewed release of the drive by the controller is prevented until the cause of the error has been corrected and the error has been acknowledged. The error can be acknowledged at the control centre after the cause of the error has been corrected.

Source and Remedy 
Check the voltage supply of the auxiliary voltage

Baumuller Error No. 567

Power section overtemperature

The power section is blocked if the power section exceeds the switch-off temperature specified via the parameter ID1658 in the current controller. The error is fatal and leads to immediate shutoff of the drive controller. In this case the drive coasts to a standstill. Renewed release of the drive by the controller is prevented until the cause of the error has been corrected and the error has been acknowledged.
The error can be acknowledged at the control centre after the cause of the error has been corrected.

Source and Remedy 
Check function of power section fan.

Baumuller Error No. 26

EEPROM access error, wrong address

The error is triggered by the "data record management" module, if read or write access to the special parameter in emulated EEPROM is to take place on the flash card, but the access address lies outside the special parameter’s memory area.
Access to the special parameter occurs if the value entered for parameter ID21 „DSV-Mode“ is 0 or 2.. The required address is selected via the parameter ID25 "EEPROM address" and the value read or written with ID26 "EEPROM Date". The M0 Offset is e.g. a special parameter in the emulated EEPROM
The error is signalled to the primary control. If the primary control switches the drive controller off, renewed release of the drive controller is prevented until the cause of the error is corrected and the error acknowledged.
The error can be acknowledged at the control centre after the cause of the error has been corrected.

Source and Remedy 
Memory area for special parameter not found, wrong address Delete all parameters and special parameters on the flash card, load new data records and save. If this fails, replace flash card. 

Baumuller Error No. 5

Link module error

Creation of a parameter incorrectly terminated on starting the controller software program. This error is used for diagnosis during software development. The error does not occur during operation.

The controller software will not be started correctly. The drive controller cannot be released. Acknowledge after error correction:

Source and Remedy 
The controller software was wrongly generated or saved. Replace the controller software.