[Matt Barney]

Here’s our platformio.ini, which I didn’t post earlier. It’s identical to what works from my desk, so don’t suspect there’s a problem here.

;PlatformIO Project Configuration File ; ; Build options: build flags, source filter ; Upload options: custom upload port, speed and extra flags ; Library options: dependencies, extra library storages ; Advanced options: extra scripting ; ; Please visit documentation for the other options and examples ; https://docs.platformio.org/page/projectconf.html [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 -DTINY_GSM_RX_BUFFER=64 -DTINY_GSM_YIELD_MS=2 ; additional build_flags for modem debugging: ; -DTINY_GSM_DEBUG=Serial ; -DMS_LOGGERMODEM_DEBUG ; -DMS_LOGGERMODEM_DEBUG_DEEP ; -DMS_DIGIXBEE_DEBUG ; -DMS_DIGIXBEECELLULARTRANSPARENT_DEBUG ; -DMS_DIGIXBEECELLULARTRANSPARENT_DEBUG_DEEP ; -DMS_DIGIXBEELTEBYPASS_DEBUG ; -DMS_DIGIXBEELTEBYPASS_DEBUG_DEEP lib_deps = EnviroDIY_ModularSensors@0.23.16 ; ^^ Use this when working from an official release of the library ; https://github.com/EnviroDIY/ModularSensors.git#develop ; ^^ Use this when if you want to pull from the develop branch StreamDebugger ; ; The following monitor_flags setting is needed becasue in transparent mode the XBee3 ; uses CR line endings instead of the more typical CR+LF. This setting enables you ; to see all back and forth communication. ; (https://www.envirodiy.org/topic/connecting-xbee3-lte-to-the-internet/#post-13312) ;monitor_flags = ; --eol ; CR

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46

;PlatformIO Project Configuration File ; ;   Build options: build flags, source filter ;   Upload options: custom upload port, speed and extra flags ;   Library options: dependencies, extra library storages ;   Advanced options: extra scripting ; ; Please visit documentation for the other options and examples ; https://docs.platformio.org/page/projectconf.html   [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     -DTINY_GSM_RX_BUFFER=64     -DTINY_GSM_YIELD_MS=2 ;    additional build_flags for modem debugging: ;    -DTINY_GSM_DEBUG=Serial ;    -DMS_LOGGERMODEM_DEBUG ;    -DMS_LOGGERMODEM_DEBUG_DEEP ;    -DMS_DIGIXBEE_DEBUG ;    -DMS_DIGIXBEECELLULARTRANSPARENT_DEBUG ;    -DMS_DIGIXBEECELLULARTRANSPARENT_DEBUG_DEEP ;    -DMS_DIGIXBEELTEBYPASS_DEBUG ;    -DMS_DIGIXBEELTEBYPASS_DEBUG_DEEP lib_deps =     EnviroDIY_ModularSensors@0.23.16 ;  ^^ Use this when working from an official release of the library ;    https://github.com/EnviroDIY/ModularSensors.git#develop ;  ^^ Use this when if you want to pull from the develop branch     StreamDebugger ; ;  The following monitor_flags setting is needed becasue in transparent mode the XBee3 ;  uses CR line endings instead of the more typical CR+LF. This setting enables you ;  to see all back and forth communication. ;  (https://www.envirodiy.org/topic/connecting-xbee3-lte-to-the-internet/#post-13312) ;monitor_flags = ;    --eol ;    CR

I guess the next step is to test it while connected to a laptop so that we can capture debug info.

Thanks for your help.

[Matt Barney]

No problem.

So, to make sure I’m understanding: the funky date issue aside, had the Mayfly connected to the internet successfully, we believe it would have set its clock from NIST and would have begun uploading successfully to MMW, right? Testing at my desk, I’m able to take a new, out of the box Mayfly, drop in an XBee3 (with previously registered SIM) on an LTEBee adapter, and no coin cell, and it connects and uploads data.

[Matt Barney]

That’s good to hear. Yep, all looked as expected in the data file on the SD card. It was named with 2000-01-01, so apparently never connected and synced to NIST. I’ll zip and attach the csv file, in case that illuminates anything. I am noticing that the Mayfly temp has a bad value (-17966.2), which is odd.

[Matt Barney]

I’ll attach the code here. Thanks, Matt

Attachments:

1. BearCT.zip

[Matt Barney]

Yes

[Matt Barney]

Thanks for your quick responses! The shipping constraints are good to know; going forward I won’t remove the battery after setting the clock.

I was able to confirm, using PCSync, that my development mayfly does lose its clock setting with power and coin cell disconnected. No surprise there. And then I disconnected USB power again, then reconnected and uploaded my MMW testing sketch, still with no coin cell installed. The Mayfly connected to NIST via 4G successfully, set its clock, and uploaded data properly to MMW. So, it seems that the clock/battery question is not the cause of Jake’s board not uploading data. Not sure what is though. The UUIDs are all set properly as far as I can see. The Mayfly’s modem (and SIM) were transferred from an operational Mayfly into this newly-programmed board.

Thanks,

Matt

[Matt Barney]

Hi Neil, thanks so much – the detail is appreciated! I need to check with our hydrology staff to learn their accuracy requirements. To date, our Mayfly deployments have used the CTD-10 from Meter, but we have a new site where we’re only interested in depth, and the MaxSonar would be a cost savings over the CTD-10 in that case. However, I’m hesitant to go that route now because of @shicks ‘ comment about having trouble with MaxSonar’s reliability.
Matt

[Matt Barney]

If you all have found that a submersible pressure transducer is a more reliable way to measure depth, we may consider that. Do you have a model that you would recommend?

Thanks,
Matt

[Matt Barney]

Excellent info! Thanks to you both!
Matt

[Matt Barney]

Hi Jim,

We noticed that Friday morning as well. Another user has reported the problem on Github, but I have not seen a response yet.

Matt

[Author]

Posts