Banner XS/SC26 Security Controller Debugging and Troubleshooting

Application of Input/Output Wiring and EDM/AVM

3.1 Sink/Source Input Configuration

The 24V DC input group of XS/SC26 and SC10-2 can be switched to Sinking or Sourcing through the common terminal (COM) wiring method:

Sinking input: COM connected to 0V, suitable for PNP sensors (high level effective).

Sourcing: COM connected to+24V, suitable for NPN sensors (low level active).

Each group of inputs has independent COM terminals that can be configured in a mixed manner. Note that this option is not available for communication input (1764-24AWA base).

3.2 External Device Monitoring (EDM) and Adjustable Valve Monitoring (AVM)

To achieve Category 4/PL e, it is strongly recommended to enable EDM on safe output. EDM monitors the forced disconnection of NC contacts on external contactors or valves, and checks whether the contacts are truly disconnected after the safety output is closed. If no closure is detected within 250 ms, the controller enters a latch and displays fault 3.2.

AVM is suitable for monitoring devices that may slow down, such as single/double solenoid valves. The AVM input must become high within the set time (50 ms~5 s) after the safety output is turned off, otherwise an error of 2.25 will be reported. When using AVM, the output will not turn on until the AVM input meets the conditions - this will result in additional ON delay, which must be considered in the design.

3.3 Common Line Resistance and Latch Mistriggering

When the solid-state safety output is turned off, its terminal voltage must be lower than 1.7 V relative to the module's 0V terminal. If the 0V common line is too long or too thin, the load current will cause the voltage drop to increase, causing the controller to misjudge that the output is not turned off and trigger a latch. Countermeasure: Use thicker wires (above 14 AWG), shorten the distance, or use single point grounding (as shown in Figure 42 of the manual).

Troubleshooting of Industrial Ethernet Communication Malfunctions

XS/SC26 supports EtherNet/IP, Modbus TCP, and PROFINET starting from FID 2; Add EtherCAT (requiring XSeCAT gateway) for FID 6 and above. SC10-2 supports the above protocol from FID 1. In actual debugging, communication failures are mostly caused by the following reasons:

4.1 IP Address Conflict and Firewall

The factory default IP is 192.168.0.128/24. When using Ethernet for the first time, it is necessary to first connect via USB, select "Enable Network Interface" in the software, set a unique IP address, and send it to the controller. Important: If multiple controllers are connected to the network using the default IP, you can click the "Flash LED" button in the software (to make the corresponding controller LED flash) to identify the physical device.

The PC side must allow the Banner Safety Controller software to pass through the Windows Firewall (Domain/Private/Public three checkboxes). If the authorization is cancelled during the first startup, you need to manually add xs26.exe in the "allowed applications" section.

4.2 EDS files and Assembly instances

When adding banner devices in the Rockwell system, the correct EDS file must be selected based on the controller's FID (Feature ID) and date code. The manual provides a detailed comparison table (see the original document table "Which XS/SC26 EDS file..."). Common error: Used "VI Status/Fault" connection, but the controller does not support virtual input (FID 1); Or "VRCD plus ISD" was used, but the controller does not support ISD. At this time, the PLC will report a connection timeout or size mismatch.

The recommended minimum RPI (Request Packet Interval) is 100 ms. The data format must be INT and DINT cannot be used.

4.3 PROFINET device name and IP

PROFINET controllers (such as Siemens S7-1200/1500) are assigned IP addresses based on device names. Although the Banner controller has a default IP address of 192.168.0.128 when first powered on, the PROFINET bus may overwrite it with zero. Correct approach: First, enable the PROFINET protocol in the software and write the configuration via USB. Then, use PLC software (such as TIA Portal) to execute "Assign device name" and assign the target name to the MAC address of the controller. Afterwards, the IP is dynamically allocated by the PLC.

4.4 EtherCAT State Machine

XSeCAT gateway supports EtherCAT, but PDO allocation can be customized. If the PLC master station requires specific TxPDO/RXPDO, the required PDO (such as ISD chain status) can be checked through the "Industrial Ethernet" tab of the software. Please note that before downloading the configuration, the PLC should place the EtherCAT module in the Initiat or PREOP state, otherwise the module may enter an error state and require a power outage and restart.

Quick search for fault codes and system reset

When the safety controller detects input, output, or system faults, it will enter a lockout state and all affected outputs will be turned off. Fault codes can be read through the panel (with display model) or software Live Mode. The following are the most commonly encountered codes and solutions on site: