Activity

You had a working library and code this whole time.

?!?

Well I feel really, really stupid.

The previous is the code that they gave me to begin with. It does work when directly connected to the MayFly and Arduino Uno. IT does also work on the Arduino Uno (5v) when using the 3m cable.

// Include the Walrus library
#include "Walrus_I2C.h"

// Declare variables -- just as strings
String header;
String data;

// Instantiate class
Walrus myWalrus;

void setup(){
    // Begin Serial connection to computer at 38400 baud
    Serial.begin(38400);
    // Obtain the header just once
    header = myWalrus.getHeader();
    // Print the…

[Read more]

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?

They are good values and slightly vary. I have verified the output with the MPL115A2 sensor that I have and the values are the same.

They said that the 3m cable works great with their data loggers on I2C protocol, but yes it would make sense to use an RS485 to just be sure that the signal won’t be lost over the length.

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]

Is there anything strange about the fact that the walrus sensor does output good values when I have it connected directly (via grove connector) to the MayFly? And of course it is only when I connect it via the 3m cable that the values do not output.

It sounds as if Northern Widget is not willing at this time to do any more trouble shooting with…[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]

See the link below to the firmware that they say is on the sensor. It is probably the same firmware you are looking at. I am requesting also the I2C registers and commands.

https://github.com/NorthernWidget-Skunkworks/Project-Walrus/tree/master/Firmware/Walrus_I2C_5BA

Hi Brian, You may want to describe the type of tipping bucket and the electrical interface for counting .  Some types of relay contacts can oxidize and require a minimum wetting current at some point.    Do you have a link for the ProTrinket.? regards

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 will contact Northern Widget to see if they will send the firmware that they uploaded for verification on this end.

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.

Ran the second bit of code and the scanner code. The scanner codes serial output is at the end.

See attached

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.