Trying to use a Devicenet Master Card to control Smart Motor.
With reference to manual(DeviceNetC5ManualRev1_010.pdf) from Animatics website.
Could not figure out how format the Messages document At Chapter 2.4,
The example below set the acceleration, which message group does it belong and what does every individual byte represent.
2.4.4.1 Set Accel:
Command Frame: [ 0x01, 0x00, 0x23, 0x21, 0x7D, 0x01, 0x00, 0x00 ] Axis 1 AT=100
Response Frame: [ 0x??, 0x00, 0x8?, 0x21, 0x00, 0x00, 0x00, 0x00 ] Axis 1 at Position 0
Hi KK. These bytes are for Polled I/O control. The bytes are referenced starting on page4 of the manual. The other way(easier to understand) to communicate is through Explicit Messaging. What type/brand of controller do you have? PLC.. or something else?
Tentatively using a Devicenet Master card plug onto a normal computer.
If using the method starting from Page 4, how does the message look like if I need to send the following command to Axis 1 of Smart Motor. Any example?
MV ADT=100 VT=50 G
Sorry, but the only examples are the ones in the manual. They reference the 8 input and 8 output bytes that the master uses to interface with the Smartmotor.
It's difficult to write an example that fits all DeviceNet masters. On the Allen Bradley PLC I have here, I use RSNetworx to read the .eds file and define where the 8 input and 8 output bytes appear in the PLC memory(it usually maps to the normal input and output registers).
All DeviceNet masters will allow some way to read in the .eds file. This is the only way they know what the device does, and how each Class, Attribute, and Instance effects the device. Documentation should be available for the card that you are evaluating. At the least, they should provide a .dll file or tools to commission your DeviceNet network. It is up to the master to know what it has at each MacID(node) on the network, so it will have some way to map(for example) that the device at Node1 is a 16-point input/output module, and Node2 is a Smartmotor.
Once the I/O location of the 8 input and 8 output bytes is known, the table on page 4 will represent these two groups of 8 bytes.