03.08.2013 Views

OPERATION MANUAL CompoBus/S

OPERATION MANUAL CompoBus/S

OPERATION MANUAL CompoBus/S

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Checking Operations of CS-series and CJ-series Master Units Section 6-3<br />

6-3-4 Checking Normal Operations Using Ladder Programming<br />

This section provides information on how to write a ladder program to monitor<br />

the operation of the <strong>CompoBus</strong>/S System and prohibit using the I/O data of<br />

the Slaves in the system when an error occurs or the Slaves are not participating<br />

in the network correctly.<br />

Master Unit Settings<br />

The following table shows the Master Unit settings used in the programming<br />

example (when all Slaves OUT0 to OUT15 and IN0 to IN15 are connected).<br />

Master’s unit number 0<br />

Usable node numbers IN0 to IN15 and OUT0 to OUT15<br />

Example 1 Communications will be performed only when the Communications Error<br />

Flags of all Slaves are OFF, and the Active Node Flags correspond to the configuration<br />

of connected Slaves.<br />

Status Area<br />

(Refer to Status Flag Functions on page 97 and page 119 for details.)<br />

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bits<br />

CIO 2016<br />

Output Slave Communications Error Flags<br />

Slave 7 0<br />

Active Output Slave Flags<br />

Slave 7 0<br />

CIO 2017<br />

Input Slave Communications Error Flags<br />

Slave 7 0<br />

Active Input Slave Flags<br />

Slave 7 0<br />

CIO 2018<br />

Output Slave Communications Error Flags<br />

Slave 15 8<br />

Active Output Slave Flags<br />

Slave 15 8<br />

CIO 2019<br />

Input Slave Communications Error Flags<br />

Slave 15 8<br />

Active Input Slave Flags<br />

Slave 15 8<br />

Active Node Flags:<br />

Once a Slave joins the <strong>CompoBus</strong>/S network after the Slave is turned ON, the<br />

Active Node Flag corresponding to the Slave will be ON.<br />

Communications Error Flags:<br />

If a Slave in the network fails to communicate with the Master, the Communications<br />

Error Flag corresponding to the Slave will be ON. After the Communications<br />

Error Flag is ON, the previous input data from the input Slave will be<br />

kept on hold. While the Communications Error Flag is ON, the input data of<br />

the input Slave is not reliable. (The program will be executed with the previous<br />

data.)<br />

Operations<br />

The input conditions require the Input Slave and Output Slave Active Node<br />

Flags to match the network configuration and that the Output Slave or Input<br />

Slave Communications Error Flags are OFF.<br />

371

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

Saved successfully!

Ooh no, something went wrong!