Output Specifications At Cpu Stop - Hitachi HIDIC EH-150 Applications Manual

Devicenet master module(eh-rmd)/ slave controller(eh-iocd)/ discrete i/o slave unit (rdx16d,rdy16tp,rdy16r)
Hide thumbs Also See for HIDIC EH-150:
Table of Contents

Advertisement

11.2 Output Specifications at CPU Stop

If the EH-150 CPU module is in the STOP status (the same in case it is stopped due to ERR), the EH-RMD is
put into the IDLE status and does not output data to the slaves.
The following lists the status of the output data of each slave:
Slave device
EH-IOCD
RDY16R,
RDY16TP
Other vendor's
slave
When connecting with the other vendor's DeviceNet master, EH-IOCD and Discrete I/O sometimes can not
detect IDLE status by the specification of the other vendor's DeviceNet master.
In this case, the DeviceNet master will send the Clear data or Hold data to all slaves.
When using an other vendor's DeviceNet master and Hitachi's slave, please use after sufficiently confirming.
Table 11.1 Output Specifications as CPU Stop
Output status
Clear/Hold
Clear
Depends on the vendor's
specification
Remark
It is possible to set this by the DIP switch.
See Section 6.4.
It is possible to specify either to clear or hold when
a communication error occurred.
See Section 7.6.
Normally, it is possible to specify either to clear or
hold when a communication error occurred.
Caution
11-2
Chapter 11 Precautions for Use

Advertisement

Table of Contents
loading

Table of Contents