User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
code:observatory_weather_blocking [2008/11/17 14:07]
code:observatory_weather_blocking [2009/12/14 21:22]
Line 1: Line 1:
 +====== State ======
 +Implemented and running fine.
 ====== Introduction ====== ====== Introduction ======
Line 51: Line 55:
 This procedure is implemented in order to not to close dome roof on RTS2 This procedure is implemented in order to not to close dome roof on RTS2
 restart. restart.
 +====== Solution ======
 +Following solution was implemented and runs successfully on all systems:
 +  - **weather state** each device have weather state. It can be either good or bad. This way any device may signal if weather is acceptable for observation or no.
 +  - **central server required device list** so central server know which devices must be presents in order to turn central weather to good. If some devices are missing, central weather state is set to off.
 +  - **list of failed devices** in central server, so user knows from monitor why central server is in bad weather state.
 +  - **mootd**, which allows to connect two or more central server, and signals to all central server off states. If at least one central server is in hard off, mootd signals bad weather on all connected central servers.
code/observatory_weather_blocking.txt ยท Last modified: 2009/12/14 00:00 (external edit)