When we woke this morning (in New Zealand so it's winter) our radiators were cold. As far as I can tell, the cortex PC restarted at 3.20 am, probably due to an automatic windows update, and one node (our outside LTH) faulted. The log message is "some nodes failed to reset" and led to a "network stop request". This seems to have caused the network not to start with the fault screen/node status screen displayed. When restarted, the node reset normally and everything was fine, but the house was a bit cold.
Sometimes a node will stop working in our system for no particular reason and when reset it is fine. The "fault node and stop communicating with it" setting in the network supervisor is set but doesn't seem to apply at network start (since the network doesn't start). The autoreflex program for the heating seemed to work when I tested it some time ago when I powered down the PC, but having partly started the network, the reflex programming seems not to have kicked in.
The IPD repower spur on fault was set to only operate between 0800 and 2200 (the default I think), though I have now changed this to "all the time." Will this then repower/reset the faulty node so the network can start - I suspect it probably wont and am looking for a way to get the network to automatically always start, so we don't lose all our heating in the middle of the night again.
Any ideas anyone?
Sometimes a node will stop working in our system for no particular reason and when reset it is fine. The "fault node and stop communicating with it" setting in the network supervisor is set but doesn't seem to apply at network start (since the network doesn't start). The autoreflex program for the heating seemed to work when I tested it some time ago when I powered down the PC, but having partly started the network, the reflex programming seems not to have kicked in.
The IPD repower spur on fault was set to only operate between 0800 and 2200 (the default I think), though I have now changed this to "all the time." Will this then repower/reset the faulty node so the network can start - I suspect it probably wont and am looking for a way to get the network to automatically always start, so we don't lose all our heating in the middle of the night again.
Any ideas anyone?
Comment