[Bernard]

got upload errors, second attempt.

Attachments:

1. debugging_Logging_to_MMW.docx
2. deep_debugging_Logging_to_MMW.docx

[Bernard]

I attached two files, deep and regular debugging for the gprsbee. This in the case of sending the data to MMW. I hope you can find something.

Bernard

[Bernard]

Dear all, a brief follow up on this issue. I have redone the same system to log to MMW. I am sending 4 measurements Bat_volt, MaximDS3231_Temp, Modem_RSSI, Modem_SignalPercent. After enabling debugging I do not get any disturbing messages about the functioning of the Sodaq GPRSbee rev7, however I am still getting the response code 504 (gateway timeout), related to the server.

The same systems does send data to ThingSpeak. I receive about 40% of the data online (so I expect the modem work correctly). After enabling debugging for logging to ThingSpeak I do not get any disturbing messages. Signal strength is about 50% and seems good enough.
Unfortunately both options (MMW and ThingSpeak) still don’t get me at the level I would like to be. If someone has the same experience or any Ideas how to improve the reliability, please let me know.

[Bernard]

Thanks a lot, ThingSpeakDebugger is working!

[Bernard]

I have been doing some testing to better understand what is happening. I first tried to build and compile the same example in my deployments folder, that I made during the Learn EnviroDIY Programming tutorial (which was great!). In that project folder I have much less errors. Apparently, I didn’t made a new project folder with the correct settings in the project wizard (through home, new project). After starting a new project folder with correct settings I am able to successfully build an compile the example using the MS_SODAQ2GBEER6_DEBUG build flag. I am a novice in PlatformIO, I just made a mistake somewhere in the process of making a new project folder. Still, if I add DMS_THINGSPEAKPUBLISHER_DEBUG build flag, the build error described above still exist (because of a redeclaration of ‘uint32_t start’).

below you find the ini file.

[platformio] description = ModularSensors example sending data to ThingSpeak [env:mayfly] monitor_speed = 115200 board = mayfly platform = atmelavr framework = arduino lib_ldf_mode = deep+ lib_ignore = RTCZero build_flags = -DSDI12_EXTERNAL_PCINT -DNEOSWSERIAL_EXTERNAL_PCINT -DMQTT_MAX_PACKET_SIZE=240 -DMS_DATAPUBLISHERBASE_DEBUG -DMS_SODAQ2GBEER6_DEBUG; this enables debugging the GPRSBee ; -DMS_THINGSPEAKPUBLISHER_DEBUG; this enables debugging the thingspeak lib_deps = EnviroDIY_ModularSensors

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

[platformio] description = ModularSensors example sending data to ThingSpeak   [env:mayfly] monitor_speed = 115200 board = mayfly platform = atmelavr framework = arduino lib_ldf_mode = deep+ lib_ignore = RTCZero build_flags =     -DSDI12_EXTERNAL_PCINT     -DNEOSWSERIAL_EXTERNAL_PCINT     -DMQTT_MAX_PACKET_SIZE=240     -DMS_DATAPUBLISHERBASE_DEBUG     -DMS_SODAQ2GBEER6_DEBUG; this enables debugging the GPRSBee ;    -DMS_THINGSPEAKPUBLISHER_DEBUG; this enables debugging the thingspeak   lib_deps =     EnviroDIY_ModularSensors

[Bernard]

Thanks for all the information, this was very helpful. If I try to build using the following build flags,

build_flags = -DSDI12_EXTERNAL_PCINT -DNEOSWSERIAL_EXTERNAL_PCINT -DMQTT_MAX_PACKET_SIZE=240 -DMS_DATAPUBLISHERBASE_DEBUG -DMS_SODAQ2GBEER6_DEBUG

1 2 3 4 5 6

build_flags =     -DSDI12_EXTERNAL_PCINT     -DNEOSWSERIAL_EXTERNAL_PCINT     -DMQTT_MAX_PACKET_SIZE=240     -DMS_DATAPUBLISHERBASE_DEBUG     -DMS_SODAQ2GBEER6_DEBUG

I get the following error.

Archiving .pio\build\mayfly\libFrameworkArduino.a *** [.pio\build\mayfly\firmware.elf] Implicit dependency <code>C:\users\moist\.platformio\platforms\atmelavr\builder\this' not found, needed by target</code>.pio\build\mayfly\firmware.elf'.

1 2	Archiving .pio\build\mayfly\libFrameworkArduino.a *** [.pio\build\mayfly\firmware.elf] Implicit dependency <code>C:\users\moist\.platformio\platforms\atmelavr\builder\this' not found, needed by target</code>.pio\build\mayfly\firmware.elf'.

It does build without the debugging options. Maybe I should not add a second error, but if I drop the DMS_SODAQ2GBEER6_DEBUG and replace it for the DMS_THINGSPEAKPUBLISHER_DEBUG, I get a build error because of a redeclaration of ‘uint32_t start’

#define MS_START_DEBUG_TIMER uint32_t start = millis(); ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src\publishers\ThingSpeakPublisher.cpp:214:5: note: in expansion of macro 'MS_START_DEBUG_TIMER' MS_START_DEBUG_TIMER ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src/ModSensorDebugger.h:73:39: note: 'uint32_t start' previously declared here #define MS_START_DEBUG_TIMER uint32_t start = millis(); ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src\publishers\ThingSpeakPublisher.cpp:190:5: note: in expansion of macro 'MS_START_DEBUG_TIMER' MS_START_DEBUG_TIMER; ^ <command-line>:0:29: warning: ISO C++11 requires whitespace after the macro name *** [.pio\build\mayfly\libb4a\EnviroDIY_ModularSensors_ID1648\publishers\ThingSpeakPublisher.cpp.o] Error 1

1 2 3 4 5 6 7 8 9 10 11 12 13 14

#define MS_START_DEBUG_TIMER uint32_t start = millis();                                        ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src\publishers\ThingSpeakPublisher.cpp:214:5: note: in expansion of macro 'MS_START_DEBUG_TIMER'      MS_START_DEBUG_TIMER      ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src/ModSensorDebugger.h:73:39: note: 'uint32_t start' previously declared here #define MS_START_DEBUG_TIMER uint32_t start = millis();                                          ^ .pio\libdeps\mayfly\EnviroDIY_ModularSensors_ID1648\src\publishers\ThingSpeakPublisher.cpp:190:5: note: in expansion of macro 'MS_START_DEBUG_TIMER'      MS_START_DEBUG_TIMER;      ^ <command-line>:0:29: warning: ISO C++11 requires whitespace after the macro name *** [.pio\build\mayfly\libb4a\EnviroDIY_ModularSensors_ID1648\publishers\ThingSpeakPublisher.cpp.o] Error 1

Any help would be greatly appreciated.

[Bernard]

Thank you – appreciate the quick response. I am not sure if I understand you correctly. At least the parameters that I am sending have correct UUID’s, I double checked, and all the parameters that I listed under the variableList[] have a UUID. However, I do measurements, e.g. soil temperature with a soil moisture sensor, which I do not send to MMW or log to an sd-card. I assume that should not give any problems right?

[Author]

Posts