23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

45-10 Industrial Communication Systems<br />

45.5.9 Diagnostic Frame<br />

Diagnostic frames always carry transport layer data. There are two types, the master request frame<br />

(MRF) and the slave response frame (SRF). The transmitter is always the master. The MRF has the ID<br />

0x3C (60) and always has eight data bytes. It is the “go-to-sleep” command if the first byte carries 0x00,<br />

otherwise it carries a transport layer protocol. The SRF transfers the slave response of the transport layer<br />

protocol to the master. It has the ID 0x3D (61) and also has eight data bytes.<br />

45.6 Network and Status Management<br />

The network and the status management features are very simple. The network management feature<br />

supports only the “wake-up” and “go-to-sleep” signals. The corresponding slave state diagram is shown<br />

in Figure 45.9. The slave node enters the Initializing state after power-on, reset or wake-up. In the operational<br />

mode state that the slave node can transmit and receive frames. In the bus sleep mode state, the<br />

node is normally in power save mode. The bus line is set to the recessive level (logical 1). Any node can<br />

send a wake-up request for the cluster. Each slave node can detect the wake-up request and listen for bus<br />

commands for a short period. The master node can also wake-up and send frame headers to establish<br />

the cause of the wake-up.<br />

The slave nodes enter the bus sleep node if they receive the go-to-sleep command from the master or<br />

if the bus is inactive for a minimum of 4 s. Bus inactivity means no transitions between logical 0 and 1<br />

bit values and so covers the IDLE state and a short circuit condition with V SUP or GND.<br />

For status management each slave node monitors its <strong>communication</strong>. The slave provides two status<br />

bits for status management within its own node: error_in_response and successful_transfer. If it detects<br />

an error (bit error, framing error, or checksum error), it sets the response_error signal. This is carried<br />

as a one bit scalar signal in an unconditional frame to the master. The position in the frame is defined<br />

in the LDF. Based on this single bit, the master node can interpret the error states as listed in Table 45.4.<br />

Reset or power on<br />

Wake up<br />

signal<br />

Initializing<br />

Bus sleep<br />

mode<br />

Go-to-sleep<br />

command<br />

Operational<br />

mode<br />

FIGURE 45.9<br />

Slave node state diagram.<br />

Table 45.4 Interpretation of the Response_error<br />

Signal by the Master Node<br />

Response_error<br />

False<br />

True<br />

The slave node did not answer<br />

Interpretation<br />

The slave node is<br />

operating correctly<br />

The slave node has<br />

intermittent problems<br />

The slave node, bus,<br />

or master node has<br />

serious problems<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!