| |
|
 |
| |
DeviceNet
Introduction |
| |
DeviceNet™
Unplugged
A View “Under the Hood” for End Users |
| Page 21 of 21 | first
page | « previous page | next page
» | last page | home |
| DeviceNet Master Stack |
A DeviceNet Master Software stack is
the software the implements the DeviceNet and CIP Communication
protocol. A DeviceNet Master must be able to send messages
over the physical CAN network. To do that it must know
the particular register interface of a selected CAN controller.
A DeviceNet device developer that wants to implement a
DeviceNet Master must create the interface between the
DeviceNet Master and the CAN Controller selected by the
hardware designer. Sometimes, as in the case of DeviceNet
Master stacks provided by Real Time Automation, Inc., an interface
file for a particular CAN Controller is delivered as part
of the DeviceNet Master stack.
To implement a DeviceNet Master the application controls
the DeviceNet devices to allocate, the number of data
bytes to produce and consume and how often the DeviceNet
slave devices are polled. For more information on implementing
a DeviceNet Master application, contact Real Time Automation, Inc..
|
| DeviceNet Slave Stacks |
A DeviceNet Slave Software stack is
the software the implements the DeviceNet and CIP Communication
protocol. A DeviceNet Slave must be able to receive an
allocation message from a DeviceNet Master, consume outputs
generated by the Master and produce inputs. To do that
it must know the particular register interface of a selected
CAN controller just like the DeviceNet Master stack. A
DeviceNet device developer that wants to implement a DeviceNet
Slave must create the interface between the DeviceNet
Slave and the CAN Controller selected by the hardware
designer. Sometimes, as in the case of DeviceNet Slave
stacks provided by Real Time Automation, Inc., an interface
file for a particular CAN Controller is delivered as part
of the DeviceNet Slave stack.
To implement a DeviceNet Slave the application controls
the DeviceNet address, the number of data bytes to produce
and consume and the object structure of the device. Implementing
the object structure of the device in the DeviceNet slave
is one of the most important parts of implementing a DeviceNet
slave device. This structure is the structure seen by
the users of the device and must be implemented correctly
to meet their needs.
For more information on implementing a DeviceNet Slave
application, contact Real Time Automation, Inc.. |
| |
| REFERENCES |
| The ultimate reference for all DeviceNet
devices is the specification from ODVA: DeviceNet Specification
Release 2.0, Open DeviceNet Vendor Association
|
Real Time Automation, Inc. (RTA, Inc.) is an authorized
DeviceNet Developer, a member of the Profibus Trade Organization
(PTO) and the Open DeviceNet Vendor Association (ODVA).
DeviceNetis a trademark of the Open DeviceNet Vendor
Association (ODVA) |
|
 |
|
|
|
|
| Page 21 of 21 | first
page | « previous page | next page
» | last page | home |
top of page |
|
|
