636 | OSM User Code File Error | |
The correct "usercode" file could not be found in the root folder of the SD card because the file is not present, or the existing file is corrupted or the wrong type file. | • Make sure the eccm.mod file is in the root folder of the SD card. Note: The usercode files are created with the User Setting Tool "IDissuer.exe". | |
641 | Engine-Controller Communication Error: Non-Response | |
There was no response to a frame sent from the controller board to the engine. | • Turn the machine power off/ on. | |
650 | Communication error of the remote service modem (Cumin-M) | |
651 | Incorrect dial up connection | |
669 | EEPROM Communication Error | |
The machine failed to detect a match between the read/write data for the EEPROM on the BCU after 3 attempts. | • EEPROM installed incorrectly • EEPROM defective. Turn the machine power off/on after replacing the EEPROM. • BCU defective. | |
670 | Engine response error | |
After powering on the machine, a response is not received from the engine within 30 seconds. | • BCU installed incorrectly • BCU defective • Controller board defective | |
672 | Controller-to-operation panel communication error at startup | |
After powering on the machine, the communication circuit between the controller and the operation panel is not opened, or communication with controller is interrupted after a normal startup. | • Controller stalled • Controller board installed incorrectly • Controller board defective • Operation panel connector loose or defective | |
687 | Memory address (PER) command error | |
The BCU did not receive a memory address command from the controller with the prescribed time once the paper reached the registration sensor. | • Harness connection at BCU, Controller board loose or broken • D |
OSM User Code File Error
نيمو تكنولجي
8:32 صشاهد أيضاً
random