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

Sara Damiano

Forum Replies Created

Viewing 10 posts - 131 through 140 (of 465 total)
  • Author
    Posts
  • Sara Damiano
    Moderator

      I’m sorry; I’ve spent a lot of time reading through that firmware and if there’s something you have to do to get it to start taking readings, I don’t know what it is.  So either I’m just not understanding the firmware or that’s not the firmware that’s actually on your device.  I don’t think there’s any other way I can help you if you cannot get a summary of the commands and registers from Northern Widget.  The problem is definitely NOT your Mayfly.

      in reply to: Atlas Scientific Logger – Sleep between readings #14756
      Sara Damiano
      Moderator

        All of the Atlas sensors do have a built in sleep command that you can use for low power without needing the isolator. You should be able to add ‘RTD.send_cmd(“SLEEP”);’ and ‘EC.send_cmd(“SLEEP”);’ to your system sleep function.

        in reply to: Atlas Scientific Logger – Sleep between readings #14755
        Sara Damiano
        Moderator

          I’m sorry I’m late to the game on this one.

          Shannon said more clearly what I would have said. But re-reading, I remember that the Atlas sensors are special. You can’t cut the power to the Atlas circuits while they’re connected to the I2C bus of the Mayfly or your program will crash. The Atlas circuits have the I2C lines pulled up to the voltage in line. If you set the voltage in to ground (ie, turn it off) the I2C lines get pulled down as well. The Arduino I2C (Wire) library hangs forever when that happens. So if you want to power down your Atlas sensors you need to get an isolator.

          Sara Damiano
          Moderator

            So it is there and responding, but there’s something wrong with my code because it’s not giving data.  Do you know if the firmware on your device *is* that code on github?  Otherwise, I don’t see in that code what I have to do to get it to start reporting values.

            Sara Damiano
            Moderator

              Also try flipping the SCL and SDA pins if you’re getting nothing.  Some versions of the Mayfly had them labeled backwards.

              Also on a Mayfly you should always be finding a device at 0x48 and at 0x68.  Those are the clock and the extra ADC.  If the Walrus is responding, it should show up as a third device.

              Scanner code for the Mayfly:

               

              Sara Damiano
              Moderator

                If (when) that fails, you can try an I2C scanner program on the Mayfly to see if the sensor has a different address.

                Sara Damiano
                Moderator

                  Ok, here’s new code for the Mayfly.  This should be much more verbose and show more clearly if the sensor’s responding.

                   

                  Sara Damiano
                  Moderator

                    No, it’s just *printing* something.  I don’t think the sensor’s responding.

                    in reply to: MayFly Capability with Northern Widget Walrus Sensor #14743
                    Sara Damiano
                    Moderator

                      That’s the full code, you should upload it to the mayfly with the sensor powered and attached to the I2C on the Mayfly.  Then start a serial terminal at 9600 and you should see output.

                      in reply to: MayFly Capability with Northern Widget Walrus Sensor #14741
                      Sara Damiano
                      Moderator

                        No, no, that’s for a Mayfly talking to a sensor with the firmware Northern Widget posted on GitHub.

                      Viewing 10 posts - 131 through 140 (of 465 total)