Matt Barney

Hi Sara,

I want to update you on the results of our latest testing. I noticed that there was a new release of EnviroDIY/TinyGSM, so I installed that and re-tested. Transparent mode still failed (see transparent.txt), but Bypass works. I tried flipping back and forth several times, and Transparent never worked; Bypass always did. Next, I decided…[Read more]

This is all very helpful – thank you!

I just updated TinyGSM via pio:

From https://github.com/EnviroDIY/TinyGSM
   30f09b2..5efcc5a  master     -> origin/master
Updating 30f09b2..5efcc5a

and re-tested (still in Transparent). No joy…and then Skype disconnected me from Jake’s computer, where the Mayfly is… not the ideal way to troubleshoot…[Read more]

The voltage levels logged during these tests were from 4.67 to 4.776V. The mayfly was powered via USB and LiPo.

I don’t know the Digi firmware version number on the XBee, but it was installed July 25, 2019. Additional background: What we’re attempting to do is to take this station and update it so that it’s more lenient on battery voltage…[Read more]

OK. What’s perplexing to me about this one is that Jake’s been able to reinstall the same LTEBee and SIM back into the “old” Mayfly (the one we’re trying to swap out), and it will connect and upload data successfully.

Thanks for continuing to sleuth out all the LTEBee issues.

Well, we’re still unable to connect to the internet. We were using transparent mode on the XBee3, but I tried switching to bypass, and still no luck. Then, thinking that the project’s library/build environment might somehow be corrupt, I created a new PlatformIO project and pasted the code into new files there, still no luck. I’ll attach two…[Read more]

Global update did it – thanks!

Hmm… still having errors with the TINY_GSM_DEBUG macro after updating libraries. Here’s the pio lib update’s output:

$ pio lib update
Library Storage: C:UsersJacob.LemonDocumentsPlatformIOProjectsBearCT.piolibdepsmayfly
Updating EnableInterrupt                 @ 1.1.0          [Up-to-date]
Updating EnviroDIY_DS3231                @ 1.3.2…

[Read more]

Haha… If your metric is Amazon reviews, well….      🙂

The doc effort definitely shows. I first came to a Stroud workshop in ~12/2017; then we (TU) jumped in deep with the Mayfly, so I picked it up again last summer or fall, and wow! what an advance in documentation! And y’all even incorporate user input – quickly!

One day, hopefully so…[Read more]

Great, thanks, we’ll try the library update and see if we can get some useful traces. We’re using transparent.

Reading docs is on my to-do list. =:D  Good documentation is definitely hard! Actually, the Mayfly manual is impressively good, as are the docs in ModularSensors github repo.

One additional detail: after it failed to build, I commented out –DTINY_GSM_DEBUG=Serial, and it built, but of course, got no debugging info in Serial Monitor.

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
;…

[Read more]

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…[Read more]

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.

I’ll attach the code here. Thanks, Matt

Yes

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…[Read more]

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…[Read more]

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