Filter
Top Products
5-4 Software Setup
Device Net Configuration
The Device Net expansion board is a Device Net Group 2 Only Slave
device using the predefined master/slave connection set, as defined by
the ODVA. It is capable of explicit messaging, as well as polled and/or
COS/Cyclic I/O. The interface is based on the Baldor Binary Protocol
(BBP) command set.
This EDS file (Electronic Data Sheets) is used by Device Net equipment
to communicate with the BBP of the Baldor Device Net expansion
board. The Baldor EDS file is provided on a diskette that is shipped with
the expansion board. A Device Net configuration tool, such as
Allen-Bradley “Device Net Manager” software should be used to
configure the Device Net expansion board. The EDS file is also
available on the Baldor World Wide WEB page (www.baldor.com).
EXB I/O Instances
The input and output assembly instances are predefined I/O data
formats that can be selected based on your application. If an I/O
connection is being used, the selected I/O assembly instance
determines the size and format of the data. Only one input instance and
one output instance can be selected. The Input and Output instances
should be set using a Device Net configuration tool prior to connection
to a host device.
Note: Instances 105 and 155 are factory preset. These instances must
be properly set for your application.
Elements of an I/O instance can be 1 to 32 bits in length and can
reference any of the Baldor Binary Protocol (BBP) transactions
supported by the Device Net expansion board (see Section 6 of
this manual). Each assembly instance can contain no more than
8 bytes.
Tables 5-1 and 5-2 defines the format of the Input and Output Assembly
Instances.