Activity

Hm. Thanks @srgdamiano, thats one way of doing it. The use case I envisage is pretty simple. Lets take a single technician with a portable water quality monitor, like a YSI or something. He/She drops it into a river at Position A, records data. Then turns device off, moves to Position B, records data etc etc. Once “home” uploads the data to…[Read more]

Oops. So, it never tried for longer than 15 minutes with that sketch because the watchdog doesn’t get “fed” while it’s waiting for the internet and it “bites” (ie, forces the board to reset) after 15 minutes. But 15 minutes is still a pretty long time to wait.

After the first connection in a new location, it should connect much faster in…[Read more]

Hm. I’m not quite sure I follow you.

It sounds like you have a sensor package that you deploy at one spot for a while, then you stop it, pack it up, and move it somewhere else. After some time, you move the sensor package back to the original site. Is there ever data being collected while it’s moving, or is the GPS data only being collected to…[Read more]

I had a similar problem – see my comment in https://www.envirodiy.org/topic/trouble-registering-with-lte-m-network-on-hologram/
The fix that seemed to work was if it didn’t connect after a 100 AI status polls it issues
gsmModem.sendAT(GF(“+CREG”));
Search for +CREG in…[Read more]

Thanks @srgdamiano, this is a great way to display the data and I think my application is simpler than that. In principle, I want to create “spot” checks of sampled data similar to what has been done for decades with water quality monitors from YSI, Horiba, OTT etc but map them on a GIS system.
This means, the _device_ moves around (as it is…[Read more]

I modified line endings and changed the wait time to 30 minutes: modem.connectInternet(1800000L). I then had to leave and left the Mayfly running overnight. Still no data at MMW, but I now see connections being logged on my Hologram dashboard, and a single message that shows data usage:…[Read more]

Hi Sara,

Initially I was testing on USB power only, but will now keep the LiPo plugged in as well, though no success so far with that. (I’m guessing the LiPo is needed to provide adequate current for signal transmission?) I’m testing in my office in an urban area where we have good Verizon and AT&T signals. I did carefully press the antenna’s…[Read more]

I think

File Conductivity1 = SD.open(“Conductivity.txt”,FILE_WRITE);

should be

Conductivity1 = SD.open(“Conductivity.txt”,FILE_WRITE);

You also should have a

Conductivity1.close()

before the last delay.

Are you using a Mayfly? Are you using the built-in microSD card slot or the vertical adapter? What output do you get?

Did you ever ge…[Read more]

@ensign – yup, it’s a nice video. But… creating a video like that automatically for every set of uploaded trajectory data is just a little bit more difficult than making a simple plot with time on the x axis.

The WinRiverII software for the moving acoustic Doppler current profilers that we use to take discharge measurements has some nice…[Read more]

Hm. You have the LiPo plugged in in addition to the USB, right?

Are you sure you have service and the antenna is well connected? Don’t yank the antenna off unless you really have to; those u.Fl connectors are fragile and after 3 or 4 times of being disconnected and reconnected they stop working.

Have you ever gotten your XBee3 to connect?…[Read more]

Thanks @ensign and @srgdamiano, for your reply. Scott, I saw a write up of your floating buoy some time ago and really wanted to find out what happened to it. That was cool stuff!

My project is a little lengthy to explain but I would love your input – I’ll call next week if that is ok with you. Can you pm me a good time/number to call?

Many thanks!

Hi Oscamo. Indeed, I was formerly at Planktos Instruments but now at the Stroud Center. In responding to Sara’s comment about trajectory data being hard to visualize, check out this video showing dissolved oxygen data along 22 miles of the Neuse River in North Carolina.

We’ve been collecting trajectory data with drifter technology here at the…[Read more]

Scott Ensign, formerly of Planktos Instruments, is not at Stroud. (He’s @ensign.)

I don’t know how “unusual” trajectory data is, but, at least in long term stream monitoring, it’s definitely far less common than fixed station monitoring. That type of data is also harder to manage, visualize, or conceptualize. I’d guess if others don’t support…[Read more]

Thanks @Sara,
I was aware of the floating sensors, I didn’t know they connected to a GIS and the company listed doesn’t seem to exist anymore. That was a very cool project though, do you have more information?

The trajectory approach you explain above appears indeed a little “cludgey”, I appreciate your explanation but was wondering why this…[Read more]

@ensign has done some work with a moving/drifting sensor stations: https://www.fondriest.com/news/hydrosphere-drifter-brings-lagrangian-sampling-freshwater.htm

The way Monitor My Watershed’s data portal is set up right now is very “site-centric” – the web pages are just not set up to accept moving sensor data like you would generate. The…[Read more]

Well it’s certainly not intended that less than 100% of the data makes it online, if that’s what your asking.

Beyond that I can’t really help without a lot more information. So, here goes:

Do you know where in the chain the data is being lost? Are you using a Mayfly? What code are you running? If ModularSensors, what version of both…[Read more]