Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, a web toolkit designed to help citizens, conservation practitioners, municipal decision-makers, researchers, educators, and students advance knowledge and stewardship of fresh water. New to EnviroDIY? Start here

Sara Damiano

Forum Replies Created

Viewing 9 reply threads
  • Author
    Posts
    • #15450
      Sara Damiano
      Moderator

      No, I don’t think I’ve seen that.

    • #15354
      Sara Damiano
      Moderator

      I’d put it in the power up, since it’s supposed to happen right away and setting the pin is nearly instant and won’t slow down other things powering up.

    • #15352
      Sara Damiano
      Moderator

      I added 10 extra ms of wake time in v2.1.3.  You can revert everything back to the original by adding a second argument of 0 to your send command functions.

    • #15337
      Sara Damiano
      Moderator

      Doh, yes, Shannon’s right!  I didn’t look closely enough before I deleted it, but there probably is a missing UUID!

      Looking back, I replaced all the UUID’s with <<REMOVED>> for you because you probably don’t want those to be public.  I can’t see or revert it to the original, but looking at it, your last measurement has just "":-9999} so it looks like I didn’t replace the UUID there, there wasn’t one.

       

    • #15330
      Sara Damiano
      Moderator

      Hmm.  Does Hologram show any data being transferred?

      Monitor My Watershed is known to sometimes drop or not respond for no apparent reason.  But usually if one station is working all the time and another isn’t it’s either the UUID and tokens or the internet connection.  When you’re looking at MonitorMW, are you seeing anything at all?  The numbers are usually updated near instantly, but the plots are all delayed by up to an hour.  The pages also do not automatically refresh, you have to manually refresh to see anything.

    • #15328
      Sara Damiano
      Moderator

      I should add that we haven’t figured out why some connect right away and others don’t.  So even with an apparently identical batch of sims and modems, it wouldn’t surprise me if some connect immediately and others don’t.

      I removed the UUID’s from your post.

    • #15327
      Sara Damiano
      Moderator

      Do you see any connections or activity from the SIM cards on Hologram?  Sometimes it takes a really long time to connect to the network with a new SIM card, a new modem, or at a new location.

      Are you sure your tokens and UUIDs are all correct?

    • #15323
      Sara Damiano
      Moderator

      Woops.  The invalid version number was my fault; I screwed up the semantic versioning.  I released a new version yesterday which is identical except for the version number which is now a valid 0.28.3.

      But  that isn’t actually your problem.  The invalid version number and the stuff about “requestFrom…” are just warnings.  It compiled anyway.  The real problem is that it didn’t find your Mayfly at your selected COM3.  Are you sure the Mayfly is actually connected, powered on, and enumerated as COM3?  Sometimes after a reset Windows will decide that the same Mayfly is a new device and will assign it a new serial port with a higher number.

    • #15314
      Sara Damiano
      Moderator

      Done

    • #15303
      Sara Damiano
      Moderator

      I would do as Neil suggested and make sure the trigger pin for the Turner is set low before sleep.

      We’ve had the same problem with RS485 adapters that pull power through the Tx/Rx lines.  Because the stop bit is high those lines will stay high if you don’t force them low at the end.  It’s kind-of a PITA with the Tx/Rx bits; you have to actually write it setting those low into your loop because ModularSensors doesn’t know anything about the Tx and Rx pins, only the serial stream.

      It could also be that the wiper is causing a whole lot of noise on the line which is keeping the Mayfly awake (acting as a pin-change interrupt).  But I think if that were the case you’d see the going to sleep/waking up lines continuously, not just once a minute.  The once a minute thing is because the alarm on the DS3231 doesn’t allow for every x minutes, just at one exact time or every second, every minute, every hour, etc.  To get it to wake only in 5 minutes (or 15 or whatever your logging interval is) you’d get the current time and then calculate and reset the alarm for 5 minutes in the future each time.  Since the board should only wake for a few ms every minute, it seemed safer to use the every minute alarm than to reset it to a new time each time.

Viewing 9 reply threads