Select Page

Digital Outputs (DO) in Sensoft Multiline

 

Applies to

Sensoft Multiline 1.3.1 and later
For older versions see this page

 

Question

Can I get a digital output signal when an alarm is raised? Or when a fault is detected? Where would I connect the wires?

 

Answer

SenSystem does output a voltage when a warning or an alarm is raised. It does not output a voltage when a fault is detected, but you can set criteria to raise a warning at every fault, e.g. "Warning if lump > 100 µm".

Software settings

To configure digital outputs (DO) click on Configure... on page Settings and then change to the tab Digital Outputs, see Figure 1.

Figure 1: Settings for Digital Outputs. The field Distances from sensor to marker [m] is relevant only if Duration is Pulsed (25 ms), and is hidden in the other cases.

The field Digital Outputs on the left specifies the pins of the warning and alarm outputs. It is recommended not to change this field and use it only to identify the pins on the break-out (Figure 2). In the normal case there are two pins for each sensor connector on the Sensystem box, one for warnings and one for alarms. To see how they are ordered let's consider an example: A Sensystem Standard has four connectors C1, C2, C3, C4; the connectors C1 and C2 connected each to a sensor; the Digital Outputs field states Dev1/port2/line0:7. Then pin Dev1/port2/line0 or 2.0 as it is labeled on the break-out goes to +24 V when the sensor connected to C1 raises a warning. Pin 2.1 goes high (i.e. +24 V against any of the GND pins) when the sensor connected to C1 raises an alarm. Pin 2.2 goes high when the sensor connected to C2 raises a warning and so on. Which pins are GND and to what pin number (1 to 50) of the IDC-50 flat connector they correspond can be seen on the break-out (Figure 2).

Figure 2: Break-out with IDC-50 flat cable for Sensystem V4 (left) and W1 (right).

 

Figure 3: Rear of Sensystem Standard (left) and Compact (right).

 

Figure 4: Schematics of the opto-coupler used in the Sensystem.

By default the warning and alarm DOs stay high until no warning (resp. alarm) criterion is met, i.e. the wire is good again. You can change this with the field Duration, which has the following choices

  • Off - Deactivated.
  • Until wire good again - The DO signal is on until no Criteria is fulfilled (or more precisely: for alarm DO: no alarm criteria, for warning DO: no warning criteria). Typical use: Warning lamp or siren, signaling to the operator to control the process.
  • Until the end of the measurement - The DO signal is on until the end of the measurement (i.e. the end of the spool). Typical use: Warning lamp or siren, signaling to the operator to discard the spool.
  • Pulse (25 ms) - The DO signal is on for 25 ms. Typical use: Trigger a marker. The pulse is delayed until the defect arrives at the marker, see section Specifics of pulsed DOs below. The positions of the markers are specified by the field Distances from sensor to marker [m].

To make the change permanent save the settings.

Hardware connection

The signal comes out of connector B1 (ICD-50). The connector B1 is galvanically separated from the rest of the electronics so that no noise is transmitted to the sensitive electronics. This means that the 24 V voltage for connector B1 has to be supplied by an external power supply. The external 24 V power supply can be a switching power supply and should be connected to connector A1 on the rear panel of the Sensystem (see the specifications for the A1 connector). The output configuration is by default Emitter-Follower, see Figure 4. The drawn current must not exceed 50 mA (i.e. the load must have a impedance of over 470 Ω). For pulsed DOs, if the load has high impedance, you may want to shorten the fall-down time by adding a pull-down resistor of 10 kΩ in parallel (in Figure 4 between DOUT1 and DOUT1_GND).

Grouped or inactive sensors

In the field Digital Outputs include every possible physical sensor (i.e. every row in the Box and Sensors page of Figure 1) in the port list, even if the sensor is not attached, not activated or grouped with another one. This allows to activate and deactivate sensors without having to change the hardware wiring. The table below shows the total number of digital outputs of the different Sensystem models. If there are not enough digital outputs, you can assign a dummy port to the "unused" connectors. The "unused" connectors are those whose Line name does not appear as a line name in the main page of Sensoft Multiline, either because they are set as inactive in the Box and Sensors page, or because they are not the first sensor of a sensor group. E.g.: A Sensystem W1 has 8 mono-axial PXS sensors grouped into 4 bi-axial sensors (grouped are C1 with C2, C3 with C4, C5 with C6 and C7 with C8, and all connectors are connected). Although we will use only 8 DOs (one for warnings and one for alarms, for each of the 4 virtual sensors), we must specify 16 DOs (two for each of the 8 physical sensors). Since we only have 12 DOs available, we include some dummy DOs at the places of the "unused" C2, C4, C6 and C8. For C2 we choose to just repeat the DOs of C1, and so forth for the other connectors. The Digital Outputs field thus could read Dev1/port0/line0:1, Dev1/port0/line0:1, Dev1/port0/line2:3, Dev1/port0/line2:3, Dev1/port0/line4:5, Dev1/port0/line4:5, Dev1/port0/line6:7, Dev1/port0/line6:7 or the equivalent but slightly compacter Dev1/port0/line0:1, Dev1/port0/line0:3, Dev1/port0/line2:5, Dev1/port0/line4:7, Dev1/port0/line6:7 .

Table 1: Digital outputs available on each model of Sensystem.
Model Number of DOs DOs
Compact 4 port1/line0:3
V3 16 port1/line0:7, port2/line0:7
V4, V6 16 port0/line8:15,port2/line0:7
W1 12 port0/line0:7, port1/line0:3

 

 

 

 

 

 

Specifics of unpulsed DOs

There is a delay of about 1 s between the fault raising the alert passes the sensor and the switching of the DO.

Specifics of pulsed DOs

Pulsed DO are synchronized, i.e. they are emitted when the defect is at the marker. The wire velocity, abbreviated v, is expected not to drop too much (not below v/2) before the defect arrives to the marker. There is a minimum distance of the marker from the sensor and it depends on the wire velocity.

To determine if your marker is at a sufficient distance, there are two methods:

  1. The software warns you if the marker is too near.
    So just try. Set the alert Duration to Pulse (25 ms) and the distances of the markers, see Figure 1. Start a measurement: If you don't see a warning, it is ok. The warning would appear in the top right section of Sensoft Multiline and state "<Line name>: Warning: Marker too near for this wire speed". To force it to appear, try increasing the velocity on page Criteria by a factor 1000 and start a new measurement. The warning is triggered by really measuring how much time it takes your system to process the data.
  2. Use the following formula:
    d/v > 1/Update rate + 0.25 s
    Here d/v is the time it takes the defect to go to the marker, with the marker distance d and the wire velocity v. Thus d/v can be seen as the marker distance in seconds. On the right hand side we have the time required to schedule the DO pulse: the time to measure the data (1/Update rate [Hz], set on page Settings), the time to process the data (depends on many things, but is rarely over 0.1 s) plus some security.
    Note: Lag = 1/Update rate + Time to process the data is constantly monitored. If during testing time you really want to see the Lag statistics of your system, you can press Ctrl - D and look the graph on page Debug. Beware of clutter.

An example: With v = 30 m/min and Update rate = 4 Hz we get a minimum marker distance of 25 cm.

The following table details the behavior and the most important border cases.

Case Warning and Alarm DO
Typical precision  50 mm ± 0.5 mm * v [m/min]
Defect does not arrive at the marker, or much too late If the defect does not arrive at the marker within twice the expected time, the pulse is aborted, i.e. not emitted. In formulas: Abortion time = 2*d/v + 0.1 s.
Defect arrives at the marker after end of measurement Pulse not emitted
Defect arrives at marker too early (before DO is scheduled) DO pulse emitted as soon as possible. Solved by larger marker distance
Alerts are very near (e.g. 10 alerts in 100 ms) 2 pulses of 25 ms (all alerts within 50 ms are grouped into one pulse)
PC lags No problem. Tested with maximum stress-level of IntelBurnTest
Daylight saving time change No problem
System time changed (e.g. by daily time synchronization) No problem