Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of 
@bernard
Active 4 years, 5 months agoForum Replies Created
Viewing 7 posts - 1 through 7 (of 7 total)
-
AuthorPosts
-
2019-08-15 at 4:34 AM in reply to: logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504 #13076
got upload errors, second attempt.
2019-08-15 at 4:32 AM in reply to: logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504 #13075I 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
2019-08-13 at 3:52 AM in reply to: logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504 #13065Dear 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 debugginDear 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.2019-08-13 at 3:23 AM in reply to: best practices enabling debugging modular sensors using platformIO #13064Thanks a lot, ThingSpeakDebugger is working!
2019-08-06 at 6:53 AM in reply to: best practices enabling debugging modular sensors using platformIO #13000I 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 ProgrammingI 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.
1234567891011121314151617181920[platformio]description = ModularSensors example sending data to ThingSpeak[env:mayfly]monitor_speed = 115200board = mayflyplatform = atmelavrframework = arduinolib_ldf_mode = deep+lib_ignore = RTCZerobuild_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 thingspeaklib_deps =EnviroDIY_ModularSensors2019-08-02 at 8:04 AM in reply to: best practices enabling debugging modular sensors using platformIO #12995Thanks for all the information, this was very helpful. If I try to build using the following build flags,123build_flags =-DSDI12_EXTERNAL_PCINT-DNEOSWSThanks for all the information, this was very helpful. If I try to build using the following build flags,123456build_flags =-DSDI12_EXTERNAL_PCINT-DNEOSWSERIAL_EXTERNAL_PCINT-DMQTT_MAX_PACKET_SIZE=240-DMS_DATAPUBLISHERBASE_DEBUG-DMS_SODAQ2GBEER6_DEBUGI get the following error.
12Archiving .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’
1234567891011121314#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 1Any help would be greatly appreciated.
2019-05-21 at 9:57 AM in reply to: logging to mmw with GPRSbee rev.7, issue wake/sleep and server response 504 #12905Thank 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 parametThank 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? -
AuthorPosts
Viewing 7 posts - 1 through 7 (of 7 total)
