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