Crown L1060 812 Alarm?

[travelingman]

The control is a OSP-U10L and the machine is a 2000 model.
We are getting a 812 P alarm at start up. All control lights are lit and there is no response from any control buttons.
Please help me figure out how to get it going. Thanks

[OkumaWiz]

Got this from the alarm book. Looks like you have a drive unit problem and communication can't be established. Look for drive unit error LED's and check for possible fiber optic failure if you have them. Check HEX code for further details on what is happening.

Best regards,


0812 MCS start
An error occurred in initialization of MCS when the power was supplied.
[Object] None or axis name
[Character-string] Varies with the code.
[Code] XXXXYYYY
XXXX: Kind of generated alarm YYYY: Further information on the alarm (Varies with XXXX.) XXXX FFFF...YYYY is 00UV. Where, U: Faulty channel number - 1 0= Channel 1 1= Channel 2 2= Channel 3 V: Cause of alarm (V=1 indicates that servo link mode has not been established.) FF01...Memory error occurred in read/write test of the servo link I/O buffer. YYYY= 0 (always) Character-string shows the address where the error occurred. FF00...Communication LSI caused an error in read/write test of the servo link I/O buffer. YYYY= Error status Character-string shows the address where the error occurred. F000...YYYY=bit 7:Same ID number used
bit 6:Improper ID number bit 5:Missing ID number bit 4:Too many CH4 controllers bit 3:Too many CH3 controllers bit 2:Too many CH2 controllers bit 1:Too many CH1 controllers bit 0:
With this error, connection data appears in the screen center. EF00...The servo link does not connect with all the required axes or connects with an improper axis. YYYY= ID number of required axis controller Character-string shows the problem axis name. With this alarm, connection data appears in the screen center. EE00...An error occurred in downloading an optional file.
High-order digit of YYYY shows the cause while low-order part is an error code. If high-order digit= 1: File is not in OSP format. 2: File attribute is not contiguous.
3: File opening error. Low-order part is an error code.
5232-E P-16
SECTION 2 ALARM P
4: Error in initial data reading. Low-order part is an error code. 5: File does not start with "MCS1". 6: File name is not followed by "OPFS". 7: The number of file sets is 0.
8: Data reading error. Low-order part is an error code. 9: File data has a sector length of 0. A: The number of bytes transferred is 0. B: File data has a sector length smaller than the number of bytes transferred. C: Data reading error. Low-order part is an error code.
ED00...An error occurred when manual mode is switched to auto mode. High-order digit of YYYY shows the cause while low- order part is an error code. High order digit=1: World clock does not start. EC01...Time difference occurred in setting CH1 timer. YYYY is the difference. EC02...Time difference occurred in setting CH2 timer. YYYY is the difference.
EC03...Time difference occurred in setting CH3 timer. YYYY is the difference. D001...In buffering the initial data in AT (auto) receive mode, the software synchronization bit does not come on within 3 seconds. YYYY is always 0. D002...In buffering the initial data in AT (auto) receive mode, the buffer A received a wrong format code. Two low-order characters of YYYY are the received format code. D003...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the first block. YYYY is the received format code. D004...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the second block. YYYY is the received format code. D005...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the third block. YYYY is the received format code. D006...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the fourth block. YYYY is the received format code. D007...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the fifth block. YYYY is the received format code. D008...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the sixth block. YYYY is the received format code. D009...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the seventh block. YYYY is the received format code. D00A...In buffering the initial data in AT (auto) receive mode, the buffer B received a wrong format code in the eighth block. YYYY is the received format code. D010...In buffering the initial data in AT (auto) receive mode, the received self-diagnostic data is not $55. YYYY is the received diagnostic data. D011...In buffering the initial data in AT (auto) receive mode, the buffer A received the bit data which is wrong at bit No. 0 and No. 1. YYYY is the received data. D012...In buffering the initial data in AT (auto) receive mode, the buffer A received the bit data which is wrong at bit No. 2 and No. 3. YYYY is the received data. D013...In buffering the initial data in AT (auto) receive mode, the buffer A received the bit data which is wrong at bit No. 4 and No. 5. YYYY is the received data. D080...Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 441C. YYYY is the received data. D081...Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 2428. D090...Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 4405. YYYY is the received data. D091...Initial data buffered in AT (auto) receive mode includes wrong data at ID data No. 4404. YYYY is the received data. D092...Initial data buffered in AT (auto) receive mode includes wrong offset data for compensating positioning points. YYYY is the received data.
[Probable Faulty Locations] • Invertor unit (Check the LED of the invertor unit.) • Improper ID number set in MCS • Specification code setting error • Erroneous connection with MCS

[old timer okuma]

The code on the alarm is important, but the status of the drive units can sometimes paint the best picture. If one of the drives is in alarm and the rest are still booting up you will get this alarm. Do you know the code or the drive unit status?