What happens when a device that SmartStruxure has COV subscriptions with goes OFFLINE for a while and then comes back ONLINE?
What is the limit on number of COV subscription AS/ES support.
There is no hard limits in the AS/ES for number of COV subscription, the server is limited only by resources.
How often does the Automation Server subscribe (sends the subscription requests) for the very first time to the other devices?
When the subscriptions are first established they are sent immediately to the devices, for example when you save a PE script program any COV created as a result of compiling the program are sent immediately to the device.
In the case that the other device (the gateway) restarts or goes OFFLINE, how does the Automation Server handle the sending of the re-subscription requests?
If a renewal fails due to device offline, it will be retried every minute indefinitely until it succeeds or the subscription is canceled.
So if the device goes offline for a while some of the re-subscriptions will fail and will be re-tried once a minute, when the device is back, within a minute all the failed re-subscriptions will be sent again.
Can the COVSubscriptionLifetime and the COVTimerPeriod be set in the AS? or is it only in the ES
They can be set in both the ES and the AS by editing the server.properties file in versions of SBO prior to 1.8.1
In SBO 1.8.1 and above, the settings can be accessed from the BACnet interface manager.
Where is the server.properties file located in the server file system?
AS: /opt/tac/etc (1.4.1 and below)
AS: /opt/sbo/etc (1.5.0 and above)
ES: "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\