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

Cannot Connect to Internet with SIM

Home Forums Mayfly Data Logger Cannot Connect to Internet with SIM

Viewing 3 reply threads
  • Author
    Posts
    • #18564
      Elizabeth Watson
      Participant

        I’ve completed two Mayfly loggers, each with a ClariVUE 10 turbidity sensor connected. I used the DRWI_DigiLTE sketch to set the Logger ID, arrange the variable list, and input the UUIDs. However, I keep getting the message “could not wake modem for clock sync” on both Mayflys. The data for the sensor is shown on the serial monitor and it states it is saved to the SD card as a csv, but it isn’t transmitted to MonitorMyWatershed. The connection also appears to be -9999, which I’m assuming means there is no internet connection to the Mayfly.

        My SIM cards are from Hologram and both are activated and in a “ready” state as according to the website. I’ve checked a few other forums but am unable to fix my issue. If other information is needed, I would be happy to provide.
        <div id=”bsp-long18349″></div>

      • #18565
        Elliot Ma
        Participant

          Funnily enough, I’m having the exact same issue! Also using the ClariVUE 10 turbidity sensor. It seems that the logger is writing to the SD card instead of connecting to the SIM. Hologram is basically telling me the SIM is online and ready to be communicated with, it just isn’t receiving anything.

        • #19202
          okamran
          Participant

            Also having the same issues. My LTExBee has an orange and a flashing blue light which I’m pretty sure is a good sign, but I just get that “Could not wake modem for clock sync” message. I’ve tried running the program at least 10 times by now but to no avail. Also the sync session doesn’t take 2 minutes, usually closer to 30 seconds before sending that message.

            • #19224
              Elliot Ma
              Participant

                We solved this problem a couple of months ago but I’m still trying to remember what we did to do fix it.

                If I recall correctly, the script we were using was outdated and we used an updated version from the github, and it worked for a while. But overall we did not have long-term success with the Mayfly + Clarivue10 combination. We eventually replaced our Mayflys in the field with standard Campbell data loggers.

                However, for a separate project, we managed to install 4~ Hydros 21s with the Mayfly with no problem, so its probably just the Clarivue10 that’s acting a bit funky.

                 

            • #19225
              okamran
              Participant

                Actually, I just had my SIM card upside down :/

                But I appreciate you responding! Though I will also be starting to use the Mayfly/Hydros 21/Clarivue 10 combination, so I might have to keep in mind that you replaced the Clarivues with Campbells. If I may ask, what issue were you getting with the Clarivue 10s? Was it -9999 values and a bunch of noise, because I think some people in our lab group was having that. Have the Campbells been more reliable and required less maintenance?

            Viewing 3 reply threads
            • You must be logged in to reply to this topic.