TurboSam...
There may be something you can use conceptually, but my sense is that the driver is very specifc. The driver is part of an astronomical observatory control system which is built around the M1. It has all the standard controls and abilities (alarms, emails, voice, etc), but is tailored to the needs of a remote observatory like opening and closing roofs / dome shutters, controlling telescope piers, monitoring cloud sensors, etc. The issue I've been working on involves redundancies to protect equipment from rainfall. We use the system at a remote observatory called Deep Sky West at elevation (7,400 ft) in New Mexico.
The first line of defense against rain is an infrared cloud sensor which will trigger closure given a specific difference between the sky and ambient temperature that is indicative of excessive cloud cover. Closure occurs well before actual rainfall. If the cloud sensors fail we have 2nd and 3rd lines of rain defense automated via Hydreon optical rain sensors and a standard Rain Clik (a real last resort) -- each will trigger closure rules/tasks if needed. Only in testing has the 1st line ever failed. But there's a possibility of failure on the PC that monitors the equipment and sends signals to the M1. To guard against this the solution I implemented takes advantage of the periodic polling already in place between the driver and the M1. And of course, we have on- and near-site staff for true emergency situations.
The observatory is a large steel quonset hut (25x35 feet, 3,800 lbs). It is actuated by an electric motor. The entire building is on wheels and moves along tracks. It is fully autonomous. Each evening the M1 checks the status of the weather (cloud cover in particular), Internet and power. If all is well, the building is retracted and exposes 10 telescopes to the night sky. If at anytime the weather becomes unsafe, AC fails, or the WAN fails, closure is triggered automatically. Aside from that, shortly after sunrise the roof/building is moved back into place and the cycle starts over the next evening.
The telescopes inside are all set for long-expsoure astrophotography. They are themselves automated with the ability to point, focus, track, and take long-exposure images of multiple targets throughout the night. Our user / members are from all over the globe and operate their systems remotely. Some engage in research, but most of us just take "pretty pictures". The telescopes we host are "escapees" from urban light pollution and other locations with poor atmospheric conditions. We host and protect them...
You can see more about the observatory at
www.deepskywest.com.
Some "pretty pictures" all taken by me (all from about 2,000 miles away from the observatory):
http://www.astrobin.com/users/sixburg/
The driver is described at
www.backyardobservatories.com/m1oasys.htm.
Hope this helps.