...
Type - control the meaning of the signal value:
SIGNAL - a default value having no meaning, the signal can be used in rules to control the state of the machine
NOPROCESSING - makes the processing skip this signal, it’s value is not being tracked
COUNTER - is used as a good product count, its
Unit
field sets the machine production unit. Currently, only a single good counter per machine is allowedWASTE_COUNTER - defines a waste product count. There can be many waste counters on a single machine. Its
Unit
can be different than the one of theCOUNTER
- PackOS will make a conversion using an active packing structure.SHORT_PERFORMANCE - used to track current performance value. It's calculated automatically from the COUNTER. There should be only one signal of this type per machine and production line.
Unit
defines how the signal is being calculated (e.g. car/min) converting the production unit from the Counter unit using an active packing structure and appropriate time denominator.ENERGY_ACTIVE_COUNTER-electricity consumption counter(currently assumed to always be in kWh, if you need to convert units - please use pre-processing function). You can define multiple counters for a single machine / line.
ENERGY_CURRENT_POWER-current electricity demand (assumed to be in kW). Shown in a gauge.
KEEP_ALIVE-used to capture status messages from the edge. There should be exactly 1 for each machine. Its Source URI should be
KEEPALIVE
and Device ID corresponds to the name of the LogiX Gate.
Should Archive - decides if a history of signal values should be persisted. You can still use it in rules to determine machine state etc. But you won’t be able to analyse it’s historical values
Value type - currently not used
Source URI & Device ID - defines a data source for the signal.
Source URI
corresponds to the name of the OPC tag (theNodeId
from the message), andDevice ID
to the name of the input defined in the LogiX Gate (ApplicationUri
in the message)Unit - used for unit conversions of the COUNTER and WASTE_COUNTER signals
Min & Max - can be defined to display threshold lines in the signal history, and publish notifications about exceeded thresholds
...