What I report here was observed in conjunction with the Radio RA2 v2 driver on my CQC install. It is not clear if this is due to the driver or my setup.
My single-server CQC server has no active clients, so user interference/change can be eliminated. The role of the server if to perform actions based on triggers received from the RA2 driver (and others).
Recently I have had a brief power outage. My server rack is on UPS, so the network and computers were not affected, but the power circuit where my RA2 main repeater is plugged in is not on back-up power and the main repeater was power-cycled. After the power was back the RA2 system restored itself and worked just fine, no devices are lost or missing and the core RA2 functionality is there. However, the conditional actions driven by CQC were missing.
I opened the CQC admin interface and the driver showed a connected status, and no errors in logs. The CQCEventDump did not show any events being received and also no errors. After I paused the RA2 driver and restarted it, the connection has been fully restored and everything worked again.
For now, it is not possible to put my RA2 main repeater on UPS, but will evaluate this possibility.
Is the behavior above expected? I speculate that after the RA2 main repeater came back online, it simply swallowed the commands from CQC with no error codes. Other drivers, like my Brultech ECM also lost power but came back alright.
Is there a housekeeping code/program to run from time to time to cause drivers to pause/reconnect? If so how frequently? Any examples?
I recall in the early days of programming my RA2 setup, a similar event, but back then I attributed this to my code, and for most my CQC complementing the RA2 has been solid. But I now have several important loads switched by CQC, and I will now be concerned whether the loads have been turned off as expected or not.
I am also concerned that the driver showed connected status, so most error checking or alerts would have failed.
My single-server CQC server has no active clients, so user interference/change can be eliminated. The role of the server if to perform actions based on triggers received from the RA2 driver (and others).
Recently I have had a brief power outage. My server rack is on UPS, so the network and computers were not affected, but the power circuit where my RA2 main repeater is plugged in is not on back-up power and the main repeater was power-cycled. After the power was back the RA2 system restored itself and worked just fine, no devices are lost or missing and the core RA2 functionality is there. However, the conditional actions driven by CQC were missing.
I opened the CQC admin interface and the driver showed a connected status, and no errors in logs. The CQCEventDump did not show any events being received and also no errors. After I paused the RA2 driver and restarted it, the connection has been fully restored and everything worked again.
For now, it is not possible to put my RA2 main repeater on UPS, but will evaluate this possibility.
Is the behavior above expected? I speculate that after the RA2 main repeater came back online, it simply swallowed the commands from CQC with no error codes. Other drivers, like my Brultech ECM also lost power but came back alright.
Is there a housekeeping code/program to run from time to time to cause drivers to pause/reconnect? If so how frequently? Any examples?
I recall in the early days of programming my RA2 setup, a similar event, but back then I attributed this to my code, and for most my CQC complementing the RA2 has been solid. But I now have several important loads switched by CQC, and I will now be concerned whether the loads have been turned off as expected or not.
I am also concerned that the driver showed connected status, so most error checking or alerts would have failed.
