In this screen, statuses of the HS/FS can each be linked to one communication object. The communication objects entered here change their value to 1 or not equal to zero when the HS/FS assumes the status.
Internal or external (EIB) communication objects can be assigned.
When using the EIB communication objects, an implicit type conversion takes place.
The communication objects can then, for example, be processed further in the logic.
Status objects which document errors are reset to zero after successful elimination of errors.
Internal or external (EIB) communication objects can be assigned.
When using the EIB communication objects, an implicit type conversion takes place.
The communication objects can then, for example, be processed further in the logic.
Status objects which document errors are reset to zero after successful elimination of errors.
1.General
System start
The communication object assigned here assumes the value 1 after the end of the logic initialisation when starting up the HS/FS.
The value always remains set to 1 during operation.
See also the Logic startup behaviour documentation.
The value always remains set to 1 during operation.
See also the Logic startup behaviour documentation.
Portal use
The communication object assigned here assumes the value 1 when the HS/FS is successfully linked to the portal.
If the HS/FS is no longer linked to the portal, then the value is zero.
If the HS/FS is no longer linked to the portal, then the value is zero.
ISDN use
The communication object assigned here assumes the value 1 when the HS/FS is linked to the Internet via ISDN.
Memory capacity (assigned)
The communication object assigned here assumes a value between 0 and 100% and shows the assignment of the Retentive memory. If an error occurs in the flash while writing the retentive data, the communication object is set to -1.
Note: Update
This communication object is updated in or from the flash during every retentive data saving and reading operation.
If no retentively saved data is present, the communication object is not updated.
If no retentively saved data is present, the communication object is not updated.
Cleanings (number)
The communication object assigned here assumes a value greater than zero when the memory in the HS/FS is in danger of overflowing.
The value of the communication object specifies how often the HS/FS has already deleted archive data (cut off) to make enough space for saving.
The value of the communication object specifies how often the HS/FS has already deleted archive data (cut off) to make enough space for saving.
Important
This value should be connected with an alert and thus be monitored!
ISDN lock-out (With lock-out=1)
The communication object assigned here assumes the value 1 with the lock-out activated.
Load retentive memory
The communication object assigned here indicates whether the data was correctly read out of the flash memory.
- 1 = OK
- 2 = Error
Save retentive memory
The communication object assigned here indicates whether the data could be correctly written to the flash memory.
- 0 = Start of writing
- 1 = OK
- 2 = Error
Connections (internal)
The communication object (of the type 1-bit) assigned here specifies whether there is currently at least one client connection to a PC in the local network. Please bear in mind that disconnected connections are still detected as present up to the timeout. The connections are also visible in the Buddy list.
Connections (external)
The communication object (of the type 1-bit) assigned here specifies whether there is currently at least one client connection to a PC outside the local network. Please bear in mind that disconnected connections are still detected as present up to the timeout. The connections are also visible in the Buddy list.
NTP difference
The communication object (of the type 32-bit) assigned here contains the difference between battery-buffered system time and NTP time in seconds. The maximum value is a year expressed in seconds. In order to process these variables, a logic must be linked to the status object System (after start always 1).
EIB Scan
On completion of the scanning process, the communication object assigned here contains one of the following values:
- 0: All queried addresses have responded.
- 1: All queries have been sent. Not all queries were answered on completion of the scanning process.
- 2: The scanning process was cancelled. It was not possible to send all queries during the scanning process.
Certificate (days)
The communication object assigned here (type 32-bit) shows the difference (in days) between today and the expiry date of the validity of one of the certificates. The difference value is determined for both certificates. The lesser of the two values is displayed.
If the value is positive, it shows the days until validity expires.
If the value is negative, it shows the days since validity expired.
If the value is positive, it shows the days until validity expires.
If the value is negative, it shows the days since validity expired.
2.Connections
Important
The status objects do not supply information on whether it was possible to provide a service (e.g. the sending of an e-mail). They only provide information on whether the connection to the service provider was successfully established.
2.1.Successful connections
The communication objects for successful connections are entered in this column.
2.2.Failed connections
The communication objects for unsuccessful connections are entered in this column.
3.Telephone operation and call alerting
If a call is received, first the status object Calling number is set, then the status object Called number. The format of the number is dependent on which value the telephone system/the connection reports. So that the HS/FS fills both status objects, the phone number to be monitored must be configured as a "target number" in the telephone operation or as a PIN-query number or as a data communications direct dial-in.
4.Holidays & Public holiday
Holidays
This communication object is of the 1-bit type. It is designed to be connected by the user.
It does not show the status of the holiday calendar!
Setting to 1 and setting to 0 is permanent, i.e., the communication object remains in a selected status until it is set by the user to another status!
When executing an action with a timer, the communication object is "OR"-ed with the holiday calendar status for the current day, i.e. if either the current day is defined as a holiday in the holiday calendar, OR if this communication object is set to 1, the current day is considered a holiday for the timer.
This communication object is tested when an action (a timer) is waiting to be carried out.
It does not show the status of the holiday calendar!
Setting to 1 and setting to 0 is permanent, i.e., the communication object remains in a selected status until it is set by the user to another status!
When executing an action with a timer, the communication object is "OR"-ed with the holiday calendar status for the current day, i.e. if either the current day is defined as a holiday in the holiday calendar, OR if this communication object is set to 1, the current day is considered a holiday for the timer.
This communication object is tested when an action (a timer) is waiting to be carried out.
Public holiday
Functions exactly like holiday: only the calendar linked to this communication object is not the holiday, but rather the public holiday calendar.