<< return to blog entries
2010-11-29 08:08:38 (8002 views) The LVD testing survivors have arrived. One remote is damaged, two remotes and three receivers still stand (after two different tests, getting zapped with ESD and overheated and shorted in all possible ways!)
With these we're moving ahead and finishing up the last safety bits and we're also starting on the documentation.
Today a panic button was added that allows the male to reset the receiver and turn off leash/canine/timer and all other modes in case of emergency.
The administrator can disable this button from the DL Uplink's admin panel locally.
In the context of on-site male training the panic button will probably only be used when the parties are familiarizing themselves with the device and the DL2K-LINK is plugged into the male's own PC.
Remote managing users won't be able to disable this button, but if the male clicks it during a sessions, administrators will be notified.
Additionally, when the administrator enters the management session remotely the leash status (on or off) is now displayed. This prevents an administrator from thinking the leash mode is still active when the panic button has been used while they were offline.
Comments
Post new comment
|
If leash mode wasn't active when going off-line, would there be any sort of indication that the panic button was used? Couldn't that negate any timer functions?
> use regardless of whether or not she was on-line at the
> time?
And how? One could disconnect the internet connection, push panic and then shut down the application. Or if you make the internet connection compulsory to push the panic button then you lose much of the safety margin it provides.
> If leash mode wasn't active when going off-line, would
>there be any sort of indication that the panic button was
>used?
No
>Couldn't that negate any timer functions?
Feel free to propose a solution!
This is the only way I can think of to do it that would survive a full backup and restore before and after pressing the button on the host computer.
If the host program has not been continuously running since last connection, an inquisition can begin to determine if any unauthorized activity has taken place.
To be honest I really don't like the panic button idea. In the event of a emergency as long as tamper evident seals instead of a real lock are used the cb could be removed. So it isn't needed anyway.