|
HIM -> Drive
| Error Displayed | Possible Causes | Action |
| Error 1 | The HIM calculated a checksum for the file to be downloaded, then checked the EEPROM checksum of the download. The checksums did not match, indicating the file stored in the HIM is invalid and the download was not successful. | Upload a valid, uncorrupted file from the source drive and then repeat the download. |
| Error 2 | The number of parameters in the HIM file is different than the number of parameters in the drive file. The smaller of the two numbers is the number of parameters downloaded. The last downloaded parameter number is displayed. |
Verify that the correct file is being downloaded to the correct drive, then press the Enter key.
|
| Error 3 | The file in the HIM is for a different type of drive than the drive to which it is connected (i.e. 1336 PLUS file to 1336 IMPACT drive). Downloads can only occur between like drive types. | None - Download not allowed. |
Error 4 |
The value just transferred to the drive is an illegal value (out of range, too high or too low) for the parameter. | Record the parameter number displayed and then press the Enter key to continue the download. Manually reprogram all recorded parameters after the download is complete. |
| Error 5 | The download was attempted while the drive was running. | Stop the drive and repeat the download attempt. |
| Error 6 | The file in the HIM is for a different HP or voltage drive than the drive to which it is connected (i.e. 1336 PLUS 10 HP file to 1336 PLUS 15 HP drive). | If the download is desired, press the Enter key. If not desired, press the ESCape key to end the download |
Drive -> HIM
| Error Displayed | Possible Causes | Action |
| Error 1 | The HIM calculated a checksum as the file was uploaded and compared it to the HIM file checksum stored after the upload. The checksums did not match, indicating the upload was not successful and the HIM file is now corrupted. |
Repeat the Upload. |
The following were taken from the programming reference manual. These are hard coded errors from the CAN programming manual. These errors may not pertain to usage with a drive. These are provided for information ONLY!
Scanport Errors:
Network Error 0 - Service Failed Due to an internal reason the master could not perform.
Network Error 1 - Service Not Supported.
Network Error 2 - Class Not Supported.
Network Error 3 - Instance Not Supported.
Network Error 4 - Attribute Not Supported.
Network Error 5 - Data Value Out Of Range.
Network Error 6 - Object State Conflict. The Object Was In An Incorrect State to Perform the Request.
CAN Errors:
Network Error 7 - Bus Status Error. CAN read or write error counter reached 256, CAN bus goes to off state. The software then starts a request before the CAN tries to go back on-line.
Network Error 8 - Data Overrun Error. Both receive buffers were full and another message was received and lost.
Network Error 9 - Wake-Up Interrupt Set. The CAN went to sleep and then detected activity on the bus and woke up.
Other Errors:
PIN ID Error - The most usual cause of this error is a broken ScanPort wire or connection pin. On power-up, the PIN ID test is ran 2 times. The first time it is ran is at the start of the power up sequence to determine the adapter number. Once a valid adapter number is found, the HIM listens on the CAN bus, for 1 second, for any other devices using that adapter number. If no other devices are found to be using that adapter number, the HIM will verify the adapter number by running the PIN ID test again. If the adapter numbers are not the same from the first test to the second test, the PIN ID error will occur.