Omron NE1A Series Manual page 6

About NE1A-series Safety Network Controllers
1-1-5 Functions Improved in the Unit Version 1.0 Upgrade
Function
Logic operations
Logic operations
Function blocks
Specifying the reset condi-
tions for the Reset and
Restart function blocks
I/O control functions
Data usable in I/O tags
Contact Operation
Counter
Total ON Time Monitor
DeviceNet communications functions
Safety Master function
Specifying the safety I/O
communications status
after a communications
error occurs
Restarting I/O communi-
cations that were stopped
due to a communications
error
Remote I/O allocation
Functions supporting system startup and error recovery
Saving the error history
Added error history items
The following table outlines the changes made in the unit version 1.0 upgrade.
Up to 254 logic functions and function blocks can be used in program-
ming.
The following additional function blocks can be used:
Logic functions
• RS Flip-flop
• Comparator
Function blocks
• Muting
• Enable Switch
• Pulse Generator
• Counter
• Multi Connector
The following reset conditions can be selected:
• Low - High - Low ON pulse (Earlier versionís reset condition)
• Low - High rising edge
The following additional I/O tags can be used:
• Local I/O status
• General Unit status
The number of ON/OFF operations at an input or output can be counted
and stored internally.
The ON time of an input or output can be timed and stored internally.
Up to 32 connections can be used.
The user can specify one of the following conditions for safety I/O com-
munications after a communications error occurs.
• Automatic reset (earlier versionís function)
• Stop only the connection where the error occurred.
• Stop all connections
When safety I/O communications have been stopped due to a communi-
cations error, the I/O communications can be restarted from the Network
Configurator or the logic program.
When the Controller is operating as a Safety Slave or Standard Slave with
inputs, the following data can be attached to the send data.
• Local input monitor
• Local output monitor
The non-fatal error history is stored in non-volatile memory.
Errors occurring in function blocks are recorded in the error history.
Summary
Section 1-1
Reference
Section 6
Section 6
Section 6
6-1-2
5-1-3
5-1-4
4-4
4-4
4-4
4-3
10-3
10-4
7