[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 to uninstall ModularSensors and install the modemLast branch. However, I got a permissions error during build as PlatformIO was trying to install dependencies (see permissions.txt). I tried creating a brand new project in a newly created folder on the C drive and repeated the test, with the same permissions error. I re-tried the build, and then got build errors in SdFat_ID322\FatLib (see sdfat.txt). I’ve been able to return to the main branch of ModularSensors and rebuild, and the modem works (again, only in Bypass). What would you suggest? Should we go ahead and deploy this Mayfly with the modem in Bypass mode?

There is one error I get when running in Bypass:

AT+CGACT=0 ERROR

1 2 3

AT+CGACT=0   ERROR

(See Bypass.txt for context.) Is this expected?

What a bummer to hear about all the nonfunctional XBee3’s. We’ll be very interested to hear of new developments on that front, and happy to assist in any way we can.

Best,
Matt

Attachments:

1. transparent.txt
2. permissions.txt
3. SdFat.txt
4. Bypass.txt

[Matt Barney]

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

1 2 3

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 embedded systems…

So once he gets back to his office and I can reconnect, I’ll continue to troubleshoot as you suggested and report back.

Matt

Attachments:

1. afterTinyGSMupdate.txt

[Matt Barney]

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 threshold for data transmission, and so that it will flexibly choose the best cell carrier based on signal strength. To do this update, we’ve programmed a new Mayfly with the latest ModularSensors (don’t know whether the existing Mayfly is using that lib or not), and have moved the XBee, LTEBee, SIM, LiPo, and SD card from the existing to the new Mayfly. The existing Mayfly has been successfully communicating (when its battery and cell signal strength are sufficient).

You mentioned us hitting issues with the UBee, but we haven’t been using one here.

It sounds like our next step should be to apply your latest TinyGSM fixes and re-test, switching between Bypass and Transparent to try to beat the XBee into submission.

Question: How many sleep/wake cycles would you suggest I let the Mayfly run before I abort, make a code change (e.g. the Bypass/Transparent switch), and re-test? While debugging, I’ve set the logging interval to 3 minutes.

Thanks,
Matt
Trout Unlimited

[Matt Barney]

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.

[Matt Barney]

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 logfiles here and hope you can spot something that we can fix. Thanks again!

-Matt

Attachments:

1. TransparentMode.txt
2. BypassMode.txt

[Matt Barney]

Global update did it – thanks!

[Matt Barney]

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:\Users\Jacob.Lemon\Documents\PlatformIO\Projects\BearCT\.pio\libdeps\mayfly Updating EnableInterrupt @ 1.1.0 [Up-to-date] Updating EnviroDIY_DS3231 @ 1.3.2 [Up-to-date] Updating EnviroDIY_ModularSensors @ 0.23.16 [Up-to-date] Updating SdFat @ 1.1.0 [Up-to-date] Updating StreamDebugger @ 1.0.1 [Up-to-date]

1 2 3 4 5 6 7

$ pio lib update Library Storage: C:\Users\Jacob.Lemon\Documents\PlatformIO\Projects\BearCT\.pio\libdeps\mayfly Updating EnableInterrupt                 @ 1.1.0          [Up-to-date] Updating EnviroDIY_DS3231                @ 1.3.2          [Up-to-date] Updating EnviroDIY_ModularSensors        @ 0.23.16        [Up-to-date] Updating SdFat                           @ 1.1.0          [Up-to-date] Updating StreamDebugger                  @ 1.0.1          [Up-to-date]

And the errors from the subsequent build are in the attachment. I also tried Clean, pio lib update, and then Build, with the same result.

Thanks,
Matt

Attachments:

1. Build-1.txt

[Matt Barney]

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 last summer or fall with the Mayfly, so I picked it up again, and wow! what an advance in documentation! And y’all even incorporate user input – quickly!

One day, hopefully soon, we intend to be a value-add rather than a resource drain for the Mayfly-EnviroDIY community. 😀

[Matt Barney]

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.

[Matt Barney]

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.

[Author]

Posts