Suggested Use Cases
What does LOGGER do? The LOGGER is a stand alone IoT device that reads sensors and stores the data. The LOGGER captures 256 bytes of data on up to 128 sensors every few seconds. The data is stored on an SD card and kept permanently. About 40 years of data taken once every ten seconds fit on a 64Gb card.
The LOGGER is a 'last mile' Internet of Things sensor system. It captures sensor data from sensors and logs the sensor history permanently in local memory. The LOGGER is a Web Server allowing direct obseration of the data that has been logged. The LOGGER can also control output pins. The LOGGER then reports to standard cloud based Internet of Things services uplinking the sensor data to the cloud.
The LOGGER was motivated by prior work monitoring environmental parameters using Mesh Networks at Wireless Sensors and by consumption/production monitoring systems like Solar Log. Another seed was the availability of the extreemly low cost WiFi enabled processor the ESP8266. LOGGER provides a more complete set of tools and hits a dramatically lower price point than our prior efforts. While today's price is $200 with high volume production the cost could be less than $50, possibly quite a bit less. LOGGER also has a more open software strategy suited to customer enhancements than the predecessor products.
This is a web page directly from the LOGGER device showing a temperature
Capturing sensor history is often important. Many sensor systems capture only the current state. Without sensor history many control problems are difficult or impossible, for example controlling a furnace from a thermostat is much easier with a few minutes of history to make sure the furnace is not turned on and off too frequently.
The LOGGER seeks to combine sensing, actuation, and usage monitoring on a single platform and to meld those with long term history logging. Often missing in prior solutions is long term data capture (so history is not lost), actuation of outputs, integration of a large variety of sensors in a single device and a more general purpose software and sensor strategy. The display of the data is often not available at the point of data collection nor in real time.
The LOGGER is a slow sample rate data logger and controller for multiple sensors. The long term goal is to provide a complete 'last mile' software system that connects the world of inexpensive embedded system I/O devices (i.e. I2C, SPI and OneWire) to the Internet of Things middleware solutions that are starting to become available. (i.e. Amazon AWS IOT and MQTT)
The LOGGER has a built in basic integration to MQTT which allows sensor data to be posted to the cloud. The LOGGER also had an integration with the now discontinued AT&T M2X service which supported time series data logging. A replacement for that service is being implemented by the LOGGER engineering staff. See LOGGER MQTT for a discussion of the LOGGER MQTT implementation.
The LOGGER offers a developers kit that uses a plug and play philosophy for sensors. A variety of simple inexpensive sensor modules are plugged in to a processor module to configure a data logging node targeted at a specific purpose.
The LOGGER acts as a web server, the data collected is displayed on web pages hosted by the LOGGER itself. This data is also available as XML making it available in machine readable form to computers on the internet.
Use Case: Temperature Alerts
The LOGGER keeps track of temperature over time. The base level processor module is capable of reporting temperature history and can send email alerts if the temperature is outside of a specified range.
Use Case: Temperature Tracking
Keep track of temperature over time. The history is a permanent record that can be used to make sure refrigeration is consistant or to watch a heating system. Track many locations and compare them. Report them to the cloud and combine many devices at different locations.
Use Case: Electric Usage/Production
LOGGER plots graphs of usage over
time on web pages.
A LOGGER manual specific to this task has been created: Electric Consumption Manual
Use Case: Water Usage
Connect a water meter to the LOGGER and the strategies used for electric consumption can monitor water consumption. Detecting a leaking toilet is no more than looking to see if intervals with no flow are absent. Sensors such as these can be directly connected with built in conversions to Gpm or Lpm.
Use Case: Controlled Environment
Medical supplies and foodstuffs have to be kept in controlled environments. Having a log of the environmental history can be critical to determining if the items are safe to use. A LOGGER manual specific to this task has been created: Food or Medical Manual
Use Case: Animal Cage
Research labs keep animals in carefully controlled environments. Typical research projects require knowlege that the environment was properly controlled throughout the experiment. The LOGGER can also be used to turn experimental systems on and off.
Use Case: Sensor Manufacturer
The maker of an embedded sensor typically makes a demonstration module to allow prospective users to experiment with the sensor and to see if the data measured suits their needs. The LOGGER allows a Sensor Manufacturer to build a trivial (wires only) adapter module and plug that into a LOGGER processor module. The same processor module can be used for all sensors made by that manufacturer.
I/O Expander Module
Using the I/O Expander Module the LOGGER is capable of counting pulses on a subset of the digital inputs. For each such input the total pulses observed to date are logged every second. To calculate usage for an interval read the count at a start time and the count at an end time and subtract. Graphs of usage are available as web pages.
The Humidity Module captures relative humidity and temperature every sample. The LOGGER supports one Humidity Module.
AC Power Module
Developers Kit I/O Module
Key LOGGER Goals
These are the basic ideas that motivate this project.
LOGGER pages copyright 2016-2021 by Dragonnorth Group (Michael Newman).|
Send comments and corrections to: