i4SCADA Knowledge Base

i4SCADA Internal Signals

Abstract

In order to learn more about the i4SCADA Internal Signals check out this article that has been easily structured for a better understanding.

i4SCADA uses internal signals to pass data between different components. Some of this signals are available for the user and might be useful in certain situations.

Number of all previous unacknowledged alarms

WFSInternal_ActiveOrUnacknowledgedAlarmCount

Number of total alarms: No Gone or No Ack Timestamp.

Text in the viewer: "Total".

Number of all previous alarms

WFSInternal_ActiveAlarmCount

Active alarms: No Gone timestamp.

Text in the viewer: "Active".

Number of unacknowledged alarms

WFSInternal_UnacknowledgedAlarmCount

Unacknowledged Alarms: No Ack Timestamp.

Text in the viewer: "Unacknowledged".

Number of active unacknowledged alarms per signal

WFSInternal.Signal.AlarmCount.[SignalName]

Active Alarms: No Ack Timestamp.

Text in the viewer: "Active Unacknowledged".

Number of not gone alarms (active or acknowledged) per signal

WFSInternal.Signal.ActiveAlarmCount.[SignalName]

Alarms: No Gone Timestamp.

Text in the viewer: "No Gone".

Status of the signal

WFSInternal.Signal.Status.[SignalName]

Usage: dynamically switching on / off signal updates during runtime.

  • 0 -> signal is in Active mode, values are updated in the HTML page.

  • 1 -> signal is in Inactive mode, values are NOT updated in the HTML page.

  • 2 -> signal is in Inactive mode with a specified value when getting disabled. The special value must be written together with the command (separated by a |). Example: 2|999 - the signal will be turned to offline and the current value will be set to 999.

All state values can be read and written!

Examples:

  • writing a decimal 1 to WFSInternal.Signal.Status.[SignalName] will turn off the signal update.

  • writing a decimal 0 to WFSInternal.Signal.Status.[SignalName] will turn on the signal update.

  • writing a STRING 2|999 to WFSInternal.Signal.Status.[SignalName] will turn off the signal update and set the current value to 999.

OPC quality of the signal

WFSInternal.Signal.Quality.[SignalName]

  • 192 - Quality Good/Non Specific

  • 216 - Quality Good/Local Override

  • 255 - No Quality/No Value

  • 0 - Quality Bad/Non Specific

  • 4 - Quality Bad/Configuration Error

  • 8 - Quality Bad/Not Connected

  • 12 - Quality Bad/Device Failure

  • 16 - Quality Bad/Sensor Failure

  • 20 - Quality Bad/Last Known Value

  • 24 - Quality Bad/Comm Failure

  • 28 - Quality Bad/Out of Service

  • 64 - Quality Uncertain/Non Specific

  • 68 - Quality Uncertain/Last Usable Value

  • 80 - Quality Uncertain/Sensor Not Accurate

  • 84 - Quality Uncertain/EU Units Exceeded

  • 88 - Quality Uncertain/Sub Normal

  • 0 - Quality Limit Field/Not

  • 1 - Quality Limit Field/Low

  • 2 - Quality Limit Field/High

  • 3 - Quality Limit Field/Constant

Status of an Alarm/AlarmTag

WFSInternal.Alarm.Status.[SignalName].[AlarmTag]

  • 0 - inactive

  • 1 - active and not acknowledged

  • 2 - active and acknowledged

  • 3 - gone and not acknowledged

WEBfactory Server Status

WFSInternal_AliveStatus

  • 10 - Stopped

  • 11 - Stopping

  • 12 - Starting

  • 13 - Started

WEBfactory Server TimeStamp

WFSInternal_AliveTimeStamp

YYYY-MM-DD HH:MM:SS.mmm

WEBfactory Server

WFSInternal_LoggedOnUserCount

The number of currently logged users.

WEBfactory Logger Status

WFLInternal_AliveStatus

  • 10 - Stopped

  • 11 - Stopping

  • 12 - Starting

  • 13 - Started

WEBfactory Logger TimeStamp

WFLInternal_AliveTimeStamp

YYYY-MM-DD HH:MM:SS.mmm

WEBfactory Alarm Manager Status

WFAInternal_AliveStatus

  • 10 - Stopped

  • 11 - Stopping

  • 12 - Starting

  • 13 - Started

WEBfactory Alarm Manager TimeStamp

WFAInternal_AliveTimeStamp

YYYY-MM-DD HH:MM:SS.mmm