View single post by Ingo

Posted: Sunday Jul 28th, 2013 11:24 am

Joined:	Sunday Jan 21st, 2007
Location:	South Africa
Posts:	591
Status:	Offline

I am thinking the complete opposite. A reset is just as the name suggests, it resets everything. If you now introduce some variables that are persistent then a reset is not something to start your system from scratch. If you persist certain variables then you have to introduce a new reset command that can either, like in the BGP Networking world, do a SoftReset, to perhaps retain your persistence and maybe even your TCP connection or a HardReset that starts from scratch without needing to power off/on the unit (for remote support).

Calculations based on data received should make provision if a system resets, it can either be an external reset, a software forced reset or power off/on reset. The connected system wouldn't know either way. When data is persistent then there needs to be some indicator that can be queried to indicate either a 'persist' reset occurred or it was a power on reset.

What if a Counter changes while Comfort is in a reset state? Hmm... Does the UCM also reset? Yes. Does a UCM do a full scan once back up again? Yes. (UCM/CBus referenced in my assumptions)

Just throwing some food for thought into the mix...

Ingo

Close Window