To Next PageTo Next PageTo Previous PageTo Previous Page
Loading...
Need help?Do you have a question about the Omron NX-SID800 and is the answer not in the manual?
General| Model | NX-SID800 |
|---|---|
| Input Voltage | 24 VDC |
| Number of Input Points | 8 |
| Number of Output Points | 0 |
| Number of I/O Points | 8 |
| Safety Standard | IEC 61508 SIL3, ISO 13849-1 PLe |
| Connection Method | Removable terminal block |
| Safety Category | 4 |
Emphasizes early risk assessment in design to identify dangers and optimize product selection.
Ensures correct unit connection, safety signature verification, and confirms destination before data transfer.
Introduces the NX-series Safety Control Units, their features, system configuration, and application procedures.
Explains system configuration for safety controls on EtherCAT and EtherNet/IP networks.
Outlines the step-by-step procedure to build a safety system, divided into standard and safety control stages.
Lists the available models for Safety CPU Units, Safety Input Units, and Safety Output Units.
Lists the PFH values for NX-SL3300 and NX-SL3500 Safety CPU Units.
Lists the PFH values for NX-SID800 and NX-SIH400 Safety Input Units.
Lists the PFH values for NX-SOD400 and NX-SOH200 Safety Output Units.
Details the parts and names of the Safety CPU Unit, including marker attachment locations and indicators.
Identifies the parts of the NX-SL3300 or NX-SL3500 Safety CPU Unit and their functions.
Details the parts and names of Safety I/O Units, including terminal blocks and indicators.
Identifies the parts of NX-SIH400, NX-SID800, NX-SOD400, and NX-SOH200 Safety I/O Units.
Explains various safety I/O functions, including connectable input devices and self-diagnosis features.
Details safety input functions, including connectable input devices, their types, and parameters.
Explains safety output functions, including connectable output devices and connection methods for I/O power supply.
Describes how to calculate safety reaction times for Safety Control Units, including response times of components.
Defines safety reaction time as the time to turn OFF an output considering failures and breakdowns.
Explains the calculation of safety reaction time by summing sensor/switch response, I/O refresh, and actuator response times.
Describes the process of verifying calculated safety reaction times against required specifications.
Describes the safety task of the Safety CPU Unit and its effect on safety reaction times.
Explains the purpose of the safety task in assigning execution conditions for processes like data exchange and program execution.
Details the repetitive operations performed for the safety task, including input data processing and program execution.
Provides methods to find the minimum safety task period based on EtherCAT and EtherNet/IP network configurations.
Describes how to approximate the safety task period using formulas involving minimum safety task period and expansion communications monitoring time.
Explains FSoE watchdog timers used for timeouts in safety process data between Safety CPU Unit and Safety I/O Unit.
Defines FSoE watchdog timers as used for timeouts in safety process data between Safety CPU Unit and Safety I/O Unit.
Provides procedures to check FSoE watchdog timer values within Sysmac Studio.
Explains how to find set values for FSoE watchdog timers based on safety task periods.
Details procedures for changing FSoE watchdog timer values using Sysmac Studio.
Outlines the procedures for using Sysmac Studio to configure and set up the safety control system.
Describes configuration and setup procedures for Safety Control Units on EtherCAT and EtherNet/IP Slave Terminals.
Provides step-by-step instructions for creating controller configurations for Safety Control Units on EtherCAT Slave Terminals using Sysmac Studio.
Describes how to set and view settings for Safety CPU Units and Safety I/O Units, including device names and model numbers.
Explains how to view or change safety process data communications settings automatically set when adding a Safety Control Unit.
Describes how to set safety input and output functions of Safety I/O Units by assigning input and output devices in Sysmac Studio.
Details how to register device variables for I/O ports to access external devices from safety programs.
Explains POUs (Programs, Function Blocks, Functions) as building blocks for safety programs.
Defines POU as a unit in the IEC 61131-3 model, including local variables and algorithms.
Provides an overview of Programs, Function Blocks (FBs), and Functions (FUNs) as types of POUs.
Compares Programs, Function Blocks, and Functions in terms of type, execution method, and algorithm.
Describes program structure, including local variable tables, algorithms, and execution order.
Explains function block definitions, instances, parameters, and procedures for creating them.
Describes functions, their structures, instruction names, and the inability to create user-defined functions.
Defines instructions as the smallest processing elements, including FB and FUN instructions.
Describes variable designations in detail, including types, attributes, and data types used for I/O exchange and calculations.
Allows debugging programs without being connected online to a Safety CPU Unit using a Simulator.
Best practice to simulate safety programs on the computer to check operation logic and parameter settings.
Covers procedures before operating the Safety CPU Unit, including commissioning and data transfer.
Details the step-by-step procedure to start operating the Safety CPU Unit after writing safety programs.
Describes how to start communications and transfer configuration information from Sysmac Studio to the controller units.
Explains the necessity of transferring Slave Terminal settings before going online with the Safety CPU Unit.
Describes the operating modes of the Safety CPU Unit, state changes, and executable functions in each mode.
Explains how the Safety CPU Unit changes to PROGRAM or RUN mode after power ON based on program validation.
Describes how to place the Safety CPU Unit into DEBUG mode and transfer safety application data.
Describes functions in Sysmac Studio used to check the operation on the Safety CPU Unit, allowing control and debugging.
Lists functions for checking operation, including monitoring variables, controlling BOOL variables, and troubleshooting.
Explains debugging safety programs by controlling BOOL variables, changing present values, and using forced refreshing.
Describes the procedure for safety validation testing to confirm functions meet system specifications.
Details the process of performing safety validation after debugging programs, saving data to non-volatile memory.
Explains procedures to change the Safety CPU Unit to RUN mode after performing safety validation.
Describes the procedure to change the Safety CPU Unit from RUN mode to PROGRAM mode.
Describes methods to check for errors in Safety Control Units, including checking indicators and using Sysmac Studio.
Explains how to use TS and FS indicators to check NX Unit status and errors, and provides troubleshooting procedures.
Describes using Sysmac Studio to check error meanings and troubleshooting procedures based on error management methods.
Explains how to check current Controller errors and logs of past Controller errors using Sysmac Studio's Controller Error Tab Page.
Describes errors that can originate in the Safety CPU Unit and Safety I/O Units and how to correct them.
Lists errors (events) that can originate in the Safety CPU Unit and Safety I/O Units, including event codes and assumed causes.
Describes the information given for individual errors, including name, meaning, source, error attributes, effects, and cause/correction.
