This post is part of the Temperature monitoring project.
After the first articles published, it’s now time to introduce some vocabulary and a global view before going into more details (should have been done first?).
The following picture shows how stuff is organized.
We have from bottom to top:
- Remote units installed into places we have to monitor, that receive temperatures (but it could be other variables) from sensors over radio transmission.
- Those units transmit measures to a central server acting as a data collector.
- End users are able to see all temperatures collected by connecting to the central server over the WEB.
Remote unit’s parameterization is done locally using a WEB interface through the local network. This means a micro-WEB server is implemented into the remote nodes, not meant to be accessed over internet as explained in Initial considerations article.
It could have been downloaded from the central server, but as the project started with Pachube, this was not possible (and too complex to implement). Another option envisioned was to upload from the local network a configuration file.
This parameterization includes:
- Enabling / disabling local sensors.
- Setting central server properties: DNS name (or IP address), URL parameters, authorization key, sending frequency.
- Setting local IP config.
And the WEB interface enables also to display a one page status.
I started a project to implement my own central server, but it will take time to go live…
Below are some screen shot of the local WEB interface.
Enabled channels ID are hardcoded from 1-3 for Oregon radio sensors, 4 for local to the remote unit temp sensor, and 5-7 for home made sensors.
Actual user friendly names that map to those ID are set into the central server.
Next article will start describing the exact implementation.