Omron E5ZN-DRT Operation Manual page 18

Devicenet communications unit for e5zn temperature controllers
Hide thumbs Also See for E5ZN-DRT:
Table of Contents

Advertisement

Features and System Configuration
Wide Range of Maintenance Functions
Copy Function (Uploading
or Downloading
Temperature Controller
Parameters)
Monitoring Network Power
Voltage
Monitoring the Unit
Conduction Time
Unit Comments
Setting Temperature
Controller Comments
Monitoring
Communications Error
History
Monitoring Temperature
Controller Power Status
Monitor Temperature
Controller Conduction
Time and RUN Time
Easy Expansion
Connecting Existing
Terminal Units
Internal Circuit Power
Supply for Slaves Not
Required
Parameters for all Temperature Controllers connected to the DeviceNet Com-
munications Unit can be uploaded or downloaded together. (The parameters
that have been read are stored in the DeviceNet Communications Unit.) When
Temperature Controllers are replaced, the new Controllers can be easily reset
onsite without using a Configurator.
The DeviceNet network communications power voltage values (present value,
peak value, and bottom value) can be stored in the DeviceNet Communica-
tions Unit, and the recorded voltages can be read from the Configurator. By
setting the voltage monitor value in the DeviceNet Communications Unit, noti-
fication will be sent to the master if the voltage level drops below the monitor
value.
The conduction time of the DeviceNet Communications Unit's internal circuit
power supply can be recorded. The recorded conduction time can be read
from the Configurator or using explicit messages. By setting a monitor value
for the conduction time in the DeviceNet Communications Unit, notification will
be sent to the master when the total time exceeds the monitor value.
Any name can be set for a DeviceNet Communications Unit and recorded in
the Unit. Specifying names enables the user to easily differentiate the applica-
tions of the DeviceNet Communications Units when setting and monitoring
them from the Configurator.
A name can be set for each Temperature Controller channel connected to the
DeviceNet Communications Unit and recorded in the DeviceNet Communica-
tions Unit. Specifying names enables the user to easily differentiate the func-
tion of each channel when setting and monitoring them from the Configurator.
The error status for the last four communications errors (the causes and com-
munications power voltage when the communications error occurred) can be
recorded in the DeviceNet Communications Unit. The recorded communica-
tions error history can be read from the Configurator.
The power supply to the Temperature Controllers can monitored to confirm
that power is ON and send notification of the status to the master. (The power
status can be checked for Temperature Controllers connected to the
DeviceNet Communications Unit only.) The power status of the Temperature
Controllers can be read from the Configurator or using explicit messages.
The conduction time of the Temperature Controller's internal circuit power
supply or the RUN time of the Temperature Controller can be totaled and
recorded. (Select whether to total the conduction time or RUN time by setting
the monitor mode.) The recorded total time can be read using the Configura-
tor or explicit messages. By setting a monitor value in the DeviceNet Commu-
nications Unit, notification will be sent to the master if the Unit conduction time
exceeds the monitor value.
DeviceNet Communications Units can be connected to the Terminal Units
used for previous (non-DeviceNet) E5ZN Temperature Controllers, so existing
Temperature Controllers can easily be connected to DeviceNet.
The internal circuit power of the DeviceNet Communications Unit is supplied
from the DeviceNet communications power supply. Therefore, power supply
wiring is not required for the DeviceNet Communications Unit. (The Tempera-
ture Controller power supply must be supplied separately.)
Section 1-1
3

Advertisement

Table of Contents
loading

Table of Contents