06-05-2018, 23:01
Hello,
concerning the TX module with GSM, it is still on my todo list to try it some time - but there are much more points above on my list... the days should have 36h
.
Since I'm working more with the WeatherDuino and trying out different TX modules I miss a feature of tracing all the data. My idea would be to use one of the UARTs of the Mega2560 (e.g. UART2) to send all stored data of the RX Module, TX Modules, AQM to a tracer each minute.
To make it fast and memory saving but easy my idea would be to to send a fixed layout in hex values separated by semicolon, each minute a new row. To parse it, you can just write a simple parser in python
The data_structs.h gives a good overview of the data sent by TX modules and AQM, but I did not find the variables where the data of the RX module like temp, humidity and pressure or the recent timestamp is stored by getting over it quickly.
I will try to make a suggestion for the extra tracing interface the next days.
Regards,
engolling
concerning the TX module with GSM, it is still on my todo list to try it some time - but there are much more points above on my list... the days should have 36h
.Since I'm working more with the WeatherDuino and trying out different TX modules I miss a feature of tracing all the data. My idea would be to use one of the UARTs of the Mega2560 (e.g. UART2) to send all stored data of the RX Module, TX Modules, AQM to a tracer each minute.
To make it fast and memory saving but easy my idea would be to to send a fixed layout in hex values separated by semicolon, each minute a new row. To parse it, you can just write a simple parser in python
The data_structs.h gives a good overview of the data sent by TX modules and AQM, but I did not find the variables where the data of the RX module like temp, humidity and pressure or the recent timestamp is stored by getting over it quickly.
I will try to make a suggestion for the extra tracing interface the next days.
Regards,
engolling