Sara Damiano

Could it possibly be a problem with the temperature inside your logger box rather than the water temperature?  Maybe Shannon can pipe in and confirm, but I remember that we used to have issues like this when we were using black boxes with clear lids facing summer sun.  I think the Mayfly’s ADC starts acting up when it gets too hot.  Are you re…[Read more]

Also, with PlatformIO version 5 you can now specify the owner along with the library name in the lib_deps section so you’re sure you get the right one.

I’m sorry for being late on this.

It’s definitely something with the newest versions of PlatformIO and the very weird part is that for me *sometimes* it works and other times it does.

What I’ve usually ended up doing is putting *everything* into the lib_deps section.

lib_deps =
	envirodiy/EnviroDIY_ModularSensors @…

[Read more]

<!–more–>Yeah, so 99.99% of what I’ve said on this thread can be completely disregarded. Obviously the sensor and firmware work just fine and there never was any problem with them.  The biggest problem was my understanding of the problem.

If everything is perfect except the 3m cable, then it’s just the 3m length that is the problem. It’s…[Read more]

You had a working library and code this whole time.

?!?

Well I feel really, really stupid.

What code are you running to get the values?  The results you shared with me based on the code I gave you didn’t have any good values at all.  I thought you didn’t have any working code for communication.

I’m guessing you’ve made one of these:  https://github.com/EnviroDIY/TippingBucketRainCounter

I’ve edited the code that makes it work with ModularSensors, but I haven’t ever built one.  Sorry.

@aufdenkampe?

Does it output good value*S* or one single good value over and over?  If the former, then..I just don’t know how to read this firmware.  If the latter, then, no that’s what I expect.

3m is beyond the maximum expected transmission length for I2C, so, no, it’s not at all strange that it wouldn’t work over that long a distance.  If you need that di…[Read more]

That’s the firmware I’ve been looking at.

You know what, I don’t think this firmware even functional.  It won’t ever take a sample.  Well, it should sample 1 time at the beginning, and then never again.  Ugh.  I wasted a lot of time parsing the I2C bits of the firmware and writing code for you and didn’t ever question that that sampling part of…[Read more]

You don’t need the whole firmware; actually I’d prefer not to get the firmware, but instead to get a short breakdown of the required I2C registers and commands.  All I would be doing with the full firmware is trying to decode what the registers are anyway.

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…[Read more]

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.

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…[Read more]

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.

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:

// This sk…

[Read more]

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

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

#include <Arduino.h>
#include <Wire.h>

#define DEVICE_I2C_ADDRESS 
    0x4D  // I *think* this is the address it's using for itself
//…

[Read more]

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

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.

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