2: Corba error while loading the DeviceNet Layer. Either the software was incor-
rectly installed, or a driver has crashed. In this case, rebooting the PC is recommen-
ded, then trying again.
3: Internal error while establishing the DeviceNet connection. If this occurs, reboot
the PC and try again.
4: A Devicenet connection to the unit already exists. It may be that another pro-
gram (running in another window) established this connection. If unsure, please re-
boot the PC and try again to establish a connection.
5: A Connection to the Unit does not exist (Internal Error). This error normally occurs
as a result of bugs that exist in the software trying to access the unit.
6: Timeout while waiting for connection to the device. This error occurs when the
unit doesn't respond to a command sent via CAN-bus within the expected amount of
time. This occurs most often due to an error in the Devicenet allocation which occurs
at the program's start / initialization.
Other possible causes:
● CAN-Card is defective
● CAN cable connections are incorrect
● Incorrect IRQ of the CAN-card in the PC driver has been set, or the PC does
not support that IRQ (for example, because it has been disabled in the BIOS)
● The Unit is not turned on
● The Unit is defective and can't allocate resources. Note this error can also oc-
cur while the Unit is in operation. (For example, when the Unit "crashes")
7: Invalid response from the Unit.
8: Error message from the Unit. This error message will be seen when the program
receives an unexpected message or error from the Unit. In these situations, the fields
<Cmd>, <ErrCode>, and <FatalErr> can provide more information about the
nature of the problem.
HSA3500 / HSA3500 plus Power Supply 79
To Next Page
Loading...
Need help?
General
