IK360 -CAN
x
Date: 23.01.2017 Page 28 of 41 Art.no. 86089 Mod. Status 10/17
Unexpected module / Module missing / Wrong module
Problem:
Improper definition of node address or improper loading of EDS file.
Solution:
Reinitialize the CAN bus or re-install the EDS file.
Node state stopped upon loading and initialization
Problem:
Mostly because the bus transmission timeout is defined lesser than the IK360 transmission
time.
Solution:
Increase the bus timeout period (approximately 2-3 seconds).
Unable to change to another node number
If all nodes are found to be in operational mode, than follow the next few steps to set the
required node number to a selected device.
1. Calculate the required node number in hexadecimal. (IK360 is internally programmed to add
1 to any node number change fed to it, in order to avoid the node number 0)
2. For example: If we want a Node Number = 28 dec, we need to feed 27 decimal (27 + 1 =
28). So the Node Number 1B hex has to be fed in order to set the selected device to node
number 28.
3. Send a write telegram to the particular node, with 1B as data on the object 3000h.
4. Use 2300h to save the parameters with the reset.
5. A boot up message with the new node number pops us.
8
IK360 CANopen objects
8.1
Object 1000h: Device Type
The object at index 1000h describes the type of device and its functionality. It is composed of a
16-bit field, which describes the device profile, that is used, and a second 16-bit field, which
gives additional information about optional functionality of the device. The additional information
parameter is device profile specific.
Subindex
Description
Data Type
Default Value
Access
Restore after
BootUp
0
-
Unsigned 32
0X3019Ah*
0X4019Ah**
ro
no
*Singel Axis (IK360-1 axis)
**Dual Axis (IK360-2 axis)