Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, an initiative of Stroud Water Research Center designed to help people advance knowledge and stewardship of fresh water.
New to EnviroDIY? Start here

Dan

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 11 total)
1 2
  • Author
    Posts
  • 2020-01-14 at 5:20 PM in reply to: uBee R410 setup issues #13621
    Dan
    Participant

      Cool, thanks for that info. Yeah, I have found the GPRSbee to be pretty good; we have four of them that have been operating for over a year now and they all just keep trucking along.

      It’s strange, I do also have an XBee3 (XB3M1, XB3-C-A2-UT-001 RevH) but have never been able to get it to power up or respond in any way on the Mayfly. I have SJ13 soldered to LiPo and am certain I have the pins right but can’t get it to wake up, using either the transparent or bypass constructors, or even just by setting the pins and trying to wake it up directly. I guess I could open a new thread for that one 🙂

      2020-01-14 at 2:10 PM in reply to: uBee R410 setup issues #13612
      Dan
      Participant

        Thank you Sara. Unfortunately those changes didn’t do the trick. I may have to fall back to using some GPRSbees for this project and hope that T-Mobile doesn’t shut down their 2G towers too soon 🙂

        2020-01-09 at 8:34 PM in reply to: uBee R410 setup issues #13586
        Dan
        Participant

          Sara, this is really amazing support. Thank you very much for your contributions to the community.

          Unfortunately, problems persist. As far as I can tell, switching to synchronous close did not improve the situation. I’m attaching another log, this time with TINY_GSM_DEBUG enabled. We are still sometimes getting +CME ERROR: Operation not allowed with USOCL. Hopefully the TINY_GSM_DEBUG messages will help with tracking down what’s going on… I don’t really follow all the internals of the AT commands but I do wonder why it’s closing immediately after the Connecting to NIST daytime Server message.

          2020-01-09 at 1:03 PM in reply to: uBee R410 setup issues #13576
          Dan
          Participant

            Thanks Sara. Some more info for you. First, the CGMR and GMR commands both result in the response ERROR, as you can see in the output below.

            Additionally, it sometimes seems to struggle getting a connection to NIST, also as in the example below. It took two tries before it finally connected, and this seems to be commonb. Note also the funkiness in the shutdown code.

            No USOWRs with OK responses (only +CME ERROR: Operation not allowed), No UUSOCL anywhere, and the result of USOCR was variable. You can see the different USOCR responses in the NIST connection below.

            Now, I am using a bit of a homebrew solution for sending data. I’m not using EnviroDIY publisher or any of the other built-in methods but instead am using the Hologram Cloudsocket API. I modified EnviroDIYPublisher.cpp and .h to create HologramPublisher.cpp, .h to send data to Hologram, which has been working quite well on the two other modems I have (Sodaq GPRSbee and uBee U201). It seems a bit weird that there are double AT commands echoed to the log when trying to send data.

            and then sending data:

            2020-01-08 at 7:19 PM in reply to: uBee R410 setup issues #13560
            Dan
            Participant

              Thank you Sara.

              Inching closer. Prior to switching to the modemLast branch I tried something similar to what @acgold suggested. I added the following lines:

              if (modemVccPin >= 0)
              {
              pinMode(modemSleepRqPin, OUTPUT);
              digitalWrite(modemSleepRqPin, HIGH);
              }

              to my file, just after greenredflash();. This allowed the modem to wake up successfully and connect to the NIST timeserver on initial boot, which is certainly the farthest I’ve gotten with the R410. It does not successfully upload data after taking a reading, however, even though it goes through a lot of AT commands with “OK” responses, until it gets to:

              I’ll try modemLast and see if I can get anywhere.

              2020-01-07 at 6:55 PM in reply to: uBee R410 setup issues #13545
              Dan
              Participant

                Hi Sara,

                Thanks for the reply and the helpful annotated logs. Unfortunately, that didn’t fix it, and it’s still doing the hard reset. Bummer! This issue seems reminiscent of the last post by acgold on that GH issue. This is what the relevant lines of my setup look like now, but still no dice. I also tried with a 1 second delay. Anything else?

                and the output

                2018-11-30 at 8:45 PM in reply to: Trouble initializing XBee3 LTE-M #12670
                Dan
                Participant

                  Thanks Sara. The modem responds with an “OK” to the “+++” in setup() but once it’s in the loop it does not respond to anything I type in the serial monitor (AT commands, +++, etc). That’s the purpose of the StreamDebugger, right?

                  2018-11-20 at 9:39 PM in reply to: Trouble initializing XBee3 LTE-M #12655
                  Dan
                  Participant

                    Well, I have regressed even further. Now I can’t even get the modem to turn on. I confirm ~4.2V between pins 10 and 1 on the Xbee, so it is definitely getting power (and from the LiPo to boot) but it is no longer responding to the first initialization in e.g. logging_to_EnviroDIY.ino. Unforunately I don’t have any development board other than the MayFly to test on. Am I missing something major here?

                    2018-10-26 at 12:58 PM in reply to: Trouble initializing XBee3 LTE-M #12617
                    Dan
                    Participant

                      Thank you Shannon.

                      OK, I cut the trace and confirmed no continuity between BEE_Vcc and 3v3 at SJ13. Then I made a solder bridge between BEE_Vcc and LIPO. I have ~4.1V between GND and LIPO/BEE_Vcc.

                      The modem powers up and is evidently powered by the battery now but I still end up with the NO RESPONSE messages…

                      2018-10-25 at 7:09 PM in reply to: Trouble initializing XBee3 LTE-M #12613
                      Dan
                      Participant

                        OK, looking at the GitHub issue, it looks like I may need to Solder SJ13 after all…?

                      • Author
                        Posts
                      Viewing 10 posts - 1 through 10 (of 11 total)
                      1 2