User manual

DeviceNet 5-5

Run/Idle Mode

The BridgeWay has two modes of operation, Run and Idle. In both modes the

BridgeWay’s DeviceNet master maintains communication with slave devices in

its scan list.

In Run mode the BridgeWay sends output data to the slaves and receives input

data. Since it is actively sending output data affecting slave device operation, the

BridgeWay rejects attempts to alter its configuration and disrupt communications;

it must first be put in Idle mode.

In Idle mode the BridgeWay still receives input data from the slaves but it does

not send output data. In Idle mode the BridgeWay configuration can be changed.

The Run/Idle mode of the BridgeWay is controlled through the command regis-

ters at the front of the output data from the Ethernet scanner (See “Output Assem-

bly” on page 6-6). The module powers up in Idle mode.

The module automatically reverts to Idle mode when the Ethernet I/O messaging

stops. If the Ethernet protocol is EtherNet/IP, this is handled when the I/O connec-

tion closes. If the protocol is Modbus/TCP, this is handled when no requests are

received within the configured timeout period.

If no Ethernet I/O messaging is active, the Run/Idle mode of the BridgeWay is set

through an attribute of the Identity object. To change the Run/Idle mode, use a

DeviceNet messaging tool and send the following message:

Service: Set_Attribute_Single

Class: 1

Instance: 1

Attribute: 103 (67h)

Request Data: 00 for Idle, 01 for Run

Note: When the BridgeWay is reset or powered up, it begins operation in Idle

mode.