This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
software:openmonica [2011/08/05 04:26] Warren Hankey |
software:openmonica [2012/01/25 01:42] Jamie McCallum |
||
---|---|---|---|
Line 17: | Line 17: | ||
* GPIB: communicates to various GPIB devices, allowing monitoring and control of devices like the tick offset counters, and the reference oscillators. It is controlled by the service Monica.gpib and this creates a socket server listening on port 60006, which MoniCA connects to. | * GPIB: communicates to various GPIB devices, allowing monitoring and control of devices like the tick offset counters, and the reference oscillators. It is controlled by the service Monica.gpib and this creates a socket server listening on port 60006, which MoniCA connects to. | ||
* wthke: (only at Katherine) parses a website that describes the weather conditions at the Katherine site. It is controlled by the service Monica.gpib and this creates a socket server listening on port 60007, which MoniCA connects to. | * wthke: (only at Katherine) parses a website that describes the weather conditions at the Katherine site. It is controlled by the service Monica.gpib and this creates a socket server listening on port 60007, which MoniCA connects to. | ||
- | * | + | * weather: communicates with the anemometer at each site, allowing monitoring of wind speed and direction, and wind stow triggers. It is controlled by the service Monica.weather and this creates a socket server listening on port 6008, which MoniCA connects to. |
+ | At Hobart, MoniCA also connects to the MET3 sensor in the same way as the field system, and the site temperature, pressure and humidity comes from that sensor. | ||
+ | |||
+ | **Updating monitor points** | ||
+ | If the response from a monitor point changes (e.g, if additional variables are returned) Monica will ignore these until it is recompiled with the correct monitor-points.txt settings. For the servers (pcfshb, etc), the relevant file is ''/usr2/AuscopeUtils/monitoring/openMonica2/config/monitor-points.txt''. The format of the lines is fairly clear (described in detail [[http://code.google.com/p/open-monica/wiki/MonitorPointsFileFormat|here]]). For additional returned variables, use the current configuration as a guide. Once the ''monitor-points.txt'' file is correct, run the follwing commands to generate a new open-monica.jar file | ||
+ | |||
+ | ''/etc/init.d/Monica.monica stop''\\ | ||
+ | ''cd /usr2/AuscopeUtils/monitoring/openMonica2/''\\ | ||
+ | ''ant'' | ||
+ | |||
+ | If there are no reported errors, restart the monica server with ''/etc/init.d/Monica.monica start''. From here on, the new variables will be logged into the Monica database. | ||
+ | |||
+ | To be able to monitor the new variables, you will also need to edit the monitor points on ops-serv2. The relevant file on ops-serv2 is ''/usr2/AuscopeUtils/monitoring/oMonica/config.pcfshb/monitor-points.txt''. Stop any processes using open-monica.jar & rebuild it with | ||
+ | |||
+ | ''cd /usr2/AuscopeUtils/monitoring/oMonica/''\\ | ||
+ | ''ant'' | ||
+ | |||
+ | It should rebuild 4 jar files and exit cleanly. Start the Monica client & check that you can monitor the new variables. | ||
====== Below this line is the old information ====== | ====== Below this line is the old information ====== | ||