Adrian Mitevski
A multifunctional and modular Firmware for Multitech's mDot based on ARM mBed provides a widerange of functionality for several Sensors such as MAX44009, BME280, MPU9250, SI1143 and uBlox. It allows you to quickly build a Sensornode that measures specific data with its sensors and sends it via LoRaWAN.
Dependencies: mDot_LoRa_Sensornode_Flowmeter_impl mbed-rtos mbed
LoRa-Sensornode Firmware for Multitech mDot
A multifunctional and modular Firmware for Multitech's mDot which provides a widerange of functionality for several Sensors. It allows you to quickly build a Sensornode that measures specific data with its sensors and sends it via LoRaWAN.
Supported Sensors
- MAX44009 (Lux Measurment) http://www.ebay.ie/itm/MAX44009-Ambient-Light-Sensor-Module-for-Arduino-with-4P-Pin-Header-/381676089124?hash=item58ddaaef24:g:-ecAAOSwzJ5XZm5E
- BME280 (Temperature, Pressure and Humdity Measurment) At the moment there are some known problem using this. https://www.adafruit.com/product/2652 https://www.amazon.com/Diymall-Pressure-Temperature-Sensor-Arduino/dp/B0118XCKTG
- MPU9250 (Acceleration, Gyroscope and Magnetometer) http://www.watterott.com/de/9-DOF-IMU-Module-With-MPU-9250
- Si1143 (Proximity up to 50cm) https://moderndevice.com/product/si1143-proximity-sensors/
- uBlox M8Q (GPS Position) http://www.dx.com/de/p/gygpsv3-m8n-u-blox-neo-m8n-001-flight-controller-gps-module-blue-394557#.V4lFW-uLRhE
Idea
The Firmware has some predefined Application Modes running different Tasks(Measurements). Each mode can be used in a different Scenario. Application_Modes define which sensors are used, how often they aquire data and how often the data has to be sent via LoRa. Lets say you just want to measure the Light then you choose an Application_Mode (or define one) that only runs TaskLight for light measurement. As a standard all measurements are taken every second and sent via LoRa but you can change that interval depending on your usage Scenario
app/I2C_RT.h@10:4051c38bf73f, 2018-11-02 (annotated)
- Committer:
- mitea1
- Date:
- Fri Nov 02 17:01:02 2018 +0000
- Revision:
- 10:4051c38bf73f
- Parent:
- 0:f2815503561f
wtf
Who changed what in which revision?
| User | Revision | Line number | New contents of line |
|---|---|---|---|
| mitea1 | 0:f2815503561f | 1 | /** |
| mitea1 | 0:f2815503561f | 2 | * @file I2C_RT.h |
| mitea1 | 0:f2815503561f | 3 | * |
| mitea1 | 0:f2815503561f | 4 | * @author Adrian |
| mitea1 | 0:f2815503561f | 5 | * @date 19.05.2016 |
| mitea1 | 0:f2815503561f | 6 | */ |
| mitea1 | 0:f2815503561f | 7 | |
| mitea1 | 0:f2815503561f | 8 | #ifndef APP_I2C_RT_H_ |
| mitea1 | 0:f2815503561f | 9 | #define APP_I2C_RT_H_ |
| mitea1 | 0:f2815503561f | 10 | |
| mitea1 | 0:f2815503561f | 11 | #include <I2C.h> |
| mitea1 | 0:f2815503561f | 12 | #include <rtos.h> |
| mitea1 | 0:f2815503561f | 13 | |
| mitea1 | 0:f2815503561f | 14 | |
| mitea1 | 0:f2815503561f | 15 | /** |
| mitea1 | 0:f2815503561f | 16 | * @class I2C_RT |
| mitea1 | 0:f2815503561f | 17 | * @brief Controls the I2C device of the mDot. mbed::I2C functionality is wrapped |
| mitea1 | 0:f2815503561f | 18 | * inside it's methods. It's possible to wrap other I2C functionality from different Libraries |
| mitea1 | 0:f2815503561f | 19 | * or write an own implementation. |
| mitea1 | 0:f2815503561f | 20 | */ |
| mitea1 | 0:f2815503561f | 21 | class I2C_RT{ |
| mitea1 | 0:f2815503561f | 22 | public: |
| mitea1 | 0:f2815503561f | 23 | I2C_RT(); |
| mitea1 | 0:f2815503561f | 24 | virtual ~I2C_RT(); |
| mitea1 | 0:f2815503561f | 25 | |
| mitea1 | 0:f2815503561f | 26 | /** |
| mitea1 | 0:f2815503561f | 27 | * @brief Reads data from a specific register |
| mitea1 | 0:f2815503561f | 28 | * @param address address of the I2C Slave device |
| mitea1 | 0:f2815503561f | 29 | * @param reg register from which the data has to be read |
| mitea1 | 0:f2815503561f | 30 | * @param twoBytes defines if two Bytes at once has to be read |
| mitea1 | 0:f2815503561f | 31 | * @param readData storage for the read Data |
| mitea1 | 0:f2815503561f | 32 | * @param dataLength length of the storage in bytes |
| mitea1 | 0:f2815503561f | 33 | */ |
| mitea1 | 0:f2815503561f | 34 | void read_RT(uint8_t address, uint16_t reg, bool twoBytes, uint8_t* readData, uint8_t dataLength); |
| mitea1 | 0:f2815503561f | 35 | |
| mitea1 | 0:f2815503561f | 36 | /** |
| mitea1 | 0:f2815503561f | 37 | * @brief Write data to a specific register |
| mitea1 | 0:f2815503561f | 38 | * @param address address of the I2C Slave device |
| mitea1 | 0:f2815503561f | 39 | * @param reg register where the data has to be write |
| mitea1 | 0:f2815503561f | 40 | * @param twoBytes defines if two bytes at once has to be write |
| mitea1 | 0:f2815503561f | 41 | * @param dataToWrite the actual data that has to be written |
| mitea1 | 0:f2815503561f | 42 | * @param dataLenght the length of the data in bytes |
| mitea1 | 0:f2815503561f | 43 | */ |
| mitea1 | 0:f2815503561f | 44 | void write_RT(uint8_t address,uint16_t reg, bool twoBytes ,uint8_t* dataToWrite ,uint8_t dataLenght); |
| mitea1 | 0:f2815503561f | 45 | |
| mitea1 | 0:f2815503561f | 46 | private: |
| mitea1 | 0:f2815503561f | 47 | |
| mitea1 | 0:f2815503561f | 48 | |
| mitea1 | 0:f2815503561f | 49 | |
| mitea1 | 0:f2815503561f | 50 | }; |
| mitea1 | 0:f2815503561f | 51 | |
| mitea1 | 0:f2815503561f | 52 | #endif /* APP_I2C_RT_H_ */ |