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

Could not wake modem for clock sync.

Home › Forums › Mayfly Data Logger › Could not wake modem for clock sync.

Tagged: , , , , , ,

Viewing 8 reply threads
  • Author
    Posts
    • 2024-02-22 at 12:25 PM #18335
      Noori Nagra
      Participant

        Hello,

        I have spent the past week trying to fix my code to wake up the modem, but I have not been able to fix it. Every time I run the code, I get this: Could not wake modem for clock sync.  Meaning, I am getting data from the sensors, but instead of being able to send it to Monitor my Watershed, it saves as a file on an SD card. I would be very grateful if anyone could share some advice as to how I could fix this.

        Thank you!

      • 2024-02-22 at 1:17 PM #18336
        Shannon Hicks
        Moderator

          We’d need more information in order to troubleshoot your problem.  Are you using an EnviroDIY Mayfly board, and if so what hardware version do you have?  What cell or wifi board are you using?  What Arduino sketch are you using on the board and are you using it mostly as-is, or did you rewrite any part of it or the supporting libraries?

        • 2024-02-27 at 12:08 PM #18344
          Noori Nagra
          Participant

            Hello!

            Thank you for being so willing to help. I am using the Mayfly version 1.1 and the wifi/cell board is the Envirodiy LTE Bee. I am attempting to run the Modular Sensor code of Menu a la Carte on Arduino and have made some adjustments mostly in cutting out unnecessary sensors.

            Thanks!

          • 2024-02-27 at 4:11 PM #18347
            Shannon Hicks
            Moderator

              It’s likely that you deleted something important and that’s why the code isn’t working properly.  What sensors are you trying to use with your logger?

            • 2024-02-27 at 7:14 PM #18348
              Noori Nagra
              Participant

                A CTD sensor (Decagon) and turbidity sensor (Campbell OBS3).

                • 2024-02-27 at 10:30 PM #18349
                  Shannon Hicks
                  Moderator

                    The example code for a CTD/OBS3/SIM7080 station can be found here:  https://github.com/EnviroDIY/ModularSensors/tree/master/examples/DRWI_SIM7080LTE

                    The only changes you’ll have to make is to enter the turbidity sensor calibration information in the correct place (lines 157 to 186), give the logger a unique name in line 59, and enter your UUID from MonitorMyWatershed in the section lines 220-238 (making sure that the order of the parameters in the UUIDs match the order of the variables in lines 194-201).  If your UUIDs from the website are in a different order than the code, then rearrange the variables in lines 194-201 to match the order of the UUIDs.  DO NOT rearrange the order of the UUIDs in lines 194-201.

                    If you’re using a provider other than Hologram, you’ll need to change the APN as listed in line 106.  And make sure the SDI12 channel of your CTD sensor has been change to something other than ‘0’ (we usually use ‘1’ which is why it’s set to 1 in line 146.)  And make sure the jumper next to the Aux Analog Grove Jacks is set to 5v (the middle position) in order to power the analog OBS3 sensors with the appropriate 5v excitation voltage.

                • 2024-02-28 at 9:06 AM #18350
                  Noori Nagra
                  Participant

                    Wow, thank you so much! I am very grateful for all of the help.

                  • 2024-03-26 at 2:22 PM #18398
                    Noori Nagra
                    Participant

                      Hello,

                      I am still sadly having some difficulties and was wondering if you could help me overcome them.

                      This is the output I am recieving:

                      Now running DRWI_SIM7080LTE.ino on Logger Logger_GeorgeSchool_Creek

                      Using ModularSensors Library version 0.34.0
                      TinyGSM Library version 0.11.5

                      Logger timezone is set to UTC -5
                      RTC timezone is set to UTC
                      Current RTC time is: 2024-03-26T18:13:54-05:00
                      Current localized logger time is: 2024-03-26T13:13:54-05:00
                      TurbHigh has a non-unique UUID!
                      Battery has an invalid UUID!
                      BoardTemp has an invalid UUID!
                      dccb783f-477b-45f4-846c-9f4e9245a9bc -> Hydros21cond
                      3de9d1c9-642e-4b60-b45b-07d718261ff6 -> Hydros21temp
                      6e56ba5a-8ba2-4ba1-bd3e-240cd25fa4c0 -> Hydros21depth
                      fbfdb500-c8dc-4c4e-9de8-1a8828e3b4f6 -> TurbLow
                      -> TurbHigh
                      -> Battery
                      -> BoardTemp
                      -> signalPercent

                      This logger has a variable array with 8 variables, of which 7 come from 5 sensors and 1 are calculated.
                      Sampling feature UUID is: 21815a48-9cf3-4e20-84af-39dd1dda7397
                      Logger portion of setup finished.

                      Setting up sensors…
                      Waking modem and setting Cellular Carrier Options…
                      Attempting to connect to the internet and synchronize RTC with NIST
                      This may take up to two minutes!
                      Clock already within 5 seconds of time.
                      Setting up file on SD card
                      Data will be saved as Logger_GeorgeSchool_Creek_2024-03-26.csv
                      Putting processor to sleep

                      I think that the problem is coming from my UUIDS and Modem. Out of all of the UUIDS on the variable list, I don’t have both ones for the turbidity sensor, I only have one, where can I find the two for TurbLow and TurbHigh. Further, I don’t have the DS3231, Battery, or Signal Percent UUIDS. Where can I locate these?

                      Thank you so much!

                      Noori

                       

                       

                    • 2024-03-26 at 5:35 PM #18400
                      Shannon Hicks
                      Moderator

                        The UUIDs for the various parameters are generated by the MonitorMyWatershed website.  When you created the site for your particular station, you had to manually add whatever parameters you were interested in receiving from the Mayfly logger.  It looks like you added the 3 parameters for the Hydros21 and one turbidity parameter for the OBS3 sensor.  The old OBS3 turbidity sensors have two analog outputs, one low range and one high range (there’s more about this in the Monitoring Station Manual).  So you’ll need to log in to MonitorMyWatershed, go to your station details, then hit the Manage Sensors button and then add the additional parameters, starting with another OBS3 turbidity value.  Then you’ll need to add the parameters from the Mayfly itself, which are battery voltage, ds3231 temperature (Mayfly board temp that’s sometimes helpful for diagnostics), and the EnviroDIY LTEbee sim7080 signal percent.  All 3 of those parameters can be found on MMW dropdown menu under the sensor manufacturer name of EnviroDIY.

                      • 2024-05-06 at 5:57 PM #18460
                        MMP
                        Participant

                          Hi!

                           

                          I was hoping to piggyback on this thread since I am having a similar problem with the clock sync and LTE connection. I am also working with a 1.1 Mayfly model with LTE Bee, hologram, and a Hydros 21 CTD sensor.

                          So far I have tried several locations with full LTE coverage through AT&T, reprogramming the Mayfly to make sure all changes Shannon mentioned here and in the instructional video were correct, and installing another LTE Bee module with no change.

                          Any help would be greatly appreciated.

                          Thank you!

                      • Author
                        Posts
                      Viewing 8 reply threads
                      • You must be logged in to reply to this topic.