Skip to main content

System, alarm and session signals

YTCC provides three groups of signals without any configuration. System and Alarms signals are real signals of the project: they appear in the signal list, can be shown on screens, archived, used in alarms and read by scripts. They are read only. Session signals exist only in the browser of each operator station.

The names System, Alarms and Session are reserved; your own signals cannot start with them.

System​

SignalsTypeUpdatedContent
System.Time.Year, .Month, .Day, .Hour, .Minute, .SecondInt321 sLocal date and time
System.Time.Weekday, .WeekOfYear, .DayOfYearInt321 sWeekday (1 = Monday), ISO week, day of the year
System.Time.Date, .Clock, .DateTimeString1 sDate YYYY-MM-DD, time HH:MM:SS, both
System.Time.EpochMs, .UtcOffsetMinInt64, Int321 sMilliseconds since 1970, offset from UTC in minutes
System.Server.Name, .OsString5 sName and operating system of the server
System.Server.UptimeSInt645 sSeconds since the server started
System.Server.CpuPct, .MemPct, .DisksUsedPctFloat645 sProcessor, memory and disk use in %
System.Server.MemTotalMB, .MemUsedMBFloat645 sMemory in MB
System.Server.DisksTotalGB, .DisksFreeGBFloat645 sDisk space in GB
System.Server.Disks.<disk>.MountString5 sMount point of a disk (C on Windows; root, mnt_data … on Linux)
System.Server.Disks.<disk>.TotalGB, .FreeGB, .UsedPctFloat645 sSize, free space and use of the disk
System.Server.Disks.<disk>.LevelInt325 s0 normal, 1 warning, 2 high, 3 critical
System.Project.Slug, .StartTime, .WorkDir, .InstallDir, .VersionString5 sProject code, start time, folders and version
System.Project.UptimeSInt645 sSeconds since the project started
System.Processes.Total, .Running, .StoppedInt645 sNumber of processes of the project
System.Processes.<process>.RunningBool5 sThe process runs
System.Processes.<process>.StateString5 sState of the process
System.Processes.<process>.Pid, .Restarts, .UptimeS, .PortInt645 sProcess number, restarts, running time, port
System.Processes.<process>.CpuPct, .MemMBFloat645 sProcessor use and memory of the process
System.Drivers.<driver>.RunningBoolOn changeThe driver process runs
System.Drivers.<driver>.Equipments, .ConnectedInt64On changeNumber of devices and of connected devices
System.Drivers.<driver>.<device>.StateInt32On change0 not connected, 1 connected, 2 initial sync, 3 inactive
System.Drivers.<driver>.<device>.ConnectedBoolOn changeThe device communicates
System.Drivers.<driver>.<device>.SentFrames, .RcvFrames, .RejFramesInt64On changeFrames sent, received and rejected
System.Drivers.<driver>.<device>.RxPerSecFloat64On changeReceived frames per second
System.Drivers.<driver>.<device>.LastErrorStringOn changeLast error reported by the driver
System.Drivers.<driver>.<device>.Timeouts, .Retries, .ReconnectsInt64On changeResponse timeouts, retries and reconnects since the driver started; 0 when the driver does not measure them
System.Drivers.<driver>.<device>.RespAvgMs, .RespMaxMsFloat64On changeAverage and longest response time in ms since the last connection; 0 when not measured
System.Drivers.<driver>.<device>.ConnectedSinceStringOn changeLocal time of the last connection, YYYY-MM-DD hh:mm:ss; empty when not connected
System.Drivers.<driver>.<device>.CycleMs, .LoadPctFloat64On changeScan cycle in ms and scan load in % (above 100 the device cannot be read as often as configured); 0 when not measured
System.Historian.DiskUsedPct, .DiskFreeGB, .TotalSizeMB, .DbSizeMBFloat6430 sDisk and size of the history
System.Historian.DiskLevelInt3230 s0 normal to 3 critical
System.Historian.ValuesPaused, .EventsPaused, .ReservePresentBool30 sRecording of values or events paused, reserve file present
System.Historian.TablesInt3230 sNumber of archive tables
System.Historian.Tables.<table>.SizeMB, .MaxGB, .LimitUsedPctFloat6430 sSize and limit use of an archive table
System.Historian.Tables.<table>.Days, .OldestDay, .NewestDay, .ActiveInt32, String, Bool30 sDays held, oldest and newest day, table active

Process names are the process identifiers with . instead of /. Values are published when they change and refreshed every 30 seconds. Server scripts and the electrical topology add further signals under System.Scripts.<script> and System.Elec.<page>.<device>; see Server scripts and The live single-line diagram.

Alarms​

The alarm counters exist for the whole project (Alarms.Summary), for each alarm area (Alarms.Areas.<area>, sub-areas under .Sub.<sub-area>) and for each alarm group (Alarms.Groups.<group>, sub-groups under .Sub.<sub-group>). They are updated on change, at most four times a second.

SignalTypeContent
….ActiveInt32Active alarms
….UnackedInt32Alarms not yet acknowledged
….AckedInt32Acknowledged active alarms
….ReturnedUnackedInt32Returned alarms not yet acknowledged
….ShelvedInt32Shelved alarms (they count only here)
….OpenInt32Alarms in the list (active or not yet acknowledged)
….Critical, ….High, ….Medium, ….LowInt32Open alarms per priority
….HighestPriorityInt32Highest open priority: 0 none … 4 critical
….HasUnackedBoolAt least one alarm is not acknowledged

Alarms that are out of service or suppressed are not counted. System alarms without a definition, such as communication alarms and failed commands, count in Alarms.Summary only. Area and group names are written without special characters in the path, for example Ünite 1 as unite_1.

Session​

Session signals are calculated in the browser; each operator station sees its own values. They are not stored on the server and cannot be written, archived or used in server alarms.

SignalTypeContent
Session.User.Name, .IdStringSigned-in user
Session.User.RolesStringProfile identifiers of the user, separated by commas
Session.User.LoginTimeStringTime of the sign-in, local time
Session.User.LoggedInBoolA user is signed in
Session.User.IdleSIntSeconds since the last mouse, key or touch input
Session.Client.AddressStringName of the server the browser is connected to
Session.Client.LanguageStringLanguage of the interface
Session.Client.PageStringName of the current page
Session.Client.CommLostViewStringHow values are shown when communication is lost: last (last known value) or unknown