loggingInterval being ignored on v1.1 board. Logs every minute no matter what.

Tagged: interval, mayfly

This topic has 5 replies, 2 voices, and was last updated 2024-12-20 at 11:42 AM by Shannon Hicks.

Viewing 4 reply threads

Author

Posts
- 2024-12-06 at 3:26 PM #18781
  TDDCR
  Participant
  We have some Mayfly stations set up already and I’m trying to launch a new one with the v1.1 board. Everything seems to be working fine except for the fact that it ignores whatever loggingInterval I put in and it just logs every minute. It writes to the SD card and sends the data online.
  To test if there was some minor issue with my sketch, I went back to an example sketch DRWI_DigiLTE and modified it to work with my modem, Verizon account, and UUIDs. Again, it works fine, except that it’s logging every minute instead of every 15 minutes (as I set with loggingInterval).
  Has anyone run into this issue? I’m attaching that example sketch I modified with the UUIDs removed.
  Attachments:
  
  TEST-DRWI-DigiLTE.ino
- 2024-12-06 at 4:57 PM #18783
  Shannon Hicks
  Moderator
  What modem are you using with this setup?
  - 2024-12-09 at 8:25 AM #18787
    TDDCR
    Participant
    Hi Shannon. I’m using a Digi XBee modem. We can’t get a hologram account through our agency and we have a contract with Verizon, so we’re using this modem with a Verizon SIM card. We have other stations using a similar setup, though some have the v0.5 Mayfly boards with a modem adapter. I’ve attached a picture of this one that’s been giving me problems.
    
    Attachments:
    IMG_5504-scaled.jpeg
- 2024-12-10 at 6:04 PM #18790
  Shannon Hicks
  Moderator
  That’s one of the older, now-discontinued Xbee models. Have you used that module before or is it completely new and unused? We had many of them die after about a year of service. Did you modify the SJ19 solder jumper on the back of the Mayfly to change the bee status pin from the usual Bee pin 12 to Bee pin 13. I see you have it listed correctly in your sketch, but the jumper also has to be changed. Have you tried running the sketch without the modem attached at all, to see if it sleeps and wakes appropriately (maybe set it to 5 minute interval instead of 15 so you don’t have to wait quite so long during testing). It might also help to manually set the RTC first in case you haven’t successfully made a cell connection with that board yet to sync the clock.
- 2024-12-18 at 3:10 PM #18802
  TDDCR
  Participant
  I wanted to come back to this thread to give an update. I did get this working! I had tried unplugging the modem and even commenting out any code related to the modem, it still would log every minute, so it wasn’t related to that. I had some code from another site that we knew worked, so I tried to use that, but then my version of the Modular Sensors library was too new and I got a bunch of errors. I reverted to Modular Sensors v0.34.0. and that meant I also needed to revert two more libraries: SdFat back to 2.2.2 and TinyGSM to 0.11.7 in order to avoid cascading errors in compiling. After that, the code I had for another site worked and it’s logging every 15 minutes! I deployed it and it seems to be doing well now. Until that worked, I was beginning to think there must be a hardware issue with the board.
  
  I’m not sure why it wasn’t logging with Modular Sensors v0.36.0, especially when I was using example code that came with that version. I don’t mind using these older versions of libraries as long as it works. It might be better anyway for the time being since these are the versions of the libraries that we used to launch other stations.
- 2024-12-20 at 11:42 AM #18805
  Shannon Hicks
  Moderator
  Thanks for the update. We’re looking into it, my guess is there’s a conflict between two libraries that is causing some issues, so we’ll have to dig into it and narrow it down.
Author

Posts