Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of 
@dan-wachusett
Active 1 months agoForum Replies Created
-
AuthorPosts
-
Matt,
Sorry for the delayed response. You probably have the Gen 1 Hydros 21 sensor since the Gen 2 is brand new and I think I may have been the first one to get it. In fact, I can’t even use it yet because the ModularSensors library needs to be updated to handle some of the updates to the communications protocols. My Gen 2 has a black cable and the sensor sidewalls do not have holes like the Gen 1 has.
-Dan
Hi Scott, I look forward to seeing your test results. Meter Group exchanged my Gen 1 Hydros21 with a brand new Gen2. I am programming it right now and will post new results after I test it. We are gearing up to expand our Mayfly network and I want to make sure we are using a dependable sensor before we purchase several units.
Dan
My experience with Hologram Pilot Plan on the 2g network was as follows:
3 parameters (Conductivity, Temp, Depth) returned in addition to DateTime @ 15 minute intervals
Average daily use = 715 B per day. As an example we used 1.34 MB in the month of March 2020.
So for 1 station the cost is easily < $20 per year (in the pilot plan). However, like Shannon said 2g will be going away at some point soon, depending where you are, so cost for 4g may be different. I do plan on updating to 4G at some point.
Hope that helps!
Brian,
I rebuilt the project with ModularSensors Library version 0.23.11 and it worked! I don’t really know what all the differences were between versions, but I did notice a couple of things that may have been the cause (though maybe not, I really have no idea what most of these settings mean)…
I Removed the suggested build flags from my .ino file for the GSM_RX Buffer, Max Packet size and GSM_Yield.
I noticed that the 0.23.16 had a buffer set to 64, whereas library 0.23.11 has it set to 512. Perhaps that was an issue???
Also, I tried to change the timeZone to 0 so it would use UTC and I got the 504 Response Code again, so maybe this was the actual problem in the first place. After I switched back to timeZone = -5 the data was uploaded to EnviroDIY just fine. I got my sensor out in the water today:
http://monitormywatershed.org/sites/WACHUSETT-01/Thanks for all the assistance, I really appreciate it!
I was able to compile and upload the sketch using PlatformIO on Atom, however the Response Code 504 persists. I used the ModularSensors Library version 0.23.16. Since the data is being written to the microSD card and the 2G cell modem is sending the data to EnviroDIY, I am out of ideas on why the EnviroDIY host is not able to take the data. I double checked all the UUIDs again, they are all correct.
Any other ideas on what could be going wrong? I am getting no error messages, so its difficult to debug anything.
Thanks
Brian,
Other than your Response code [201], the only difference I see between my output and yours is that you use a 6 hour offset from UTC, while I do not. I know my data is being transmitted because I can see the event in the activity log on my Hologram IO account. Did you use Arduino IDE or Platform IO? Would that make any difference in how the sketch is compiled and uploaded to the Mayfly? I used Arduino IDE.
That was a good suggestion Brian. I updated my ModularSensor library from GitHub to version 0.23.16. I am still getting the 504 Response code however:
123456789101109:00:16.719 -> Sending data to [ 0 ] data.envirodiy.org09:00:17.656 -> POST /api/data-stream/ HTTP/1.109:00:17.738 -> Host: data.envirodiy.org09:00:17.738 -> TOKEN: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx09:00:17.738 -> Content-Length: 40509:00:17.738 -> Content-Type: application/json09:00:17.738 ->09:00:17.738 -> {"sampling_feature":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","timestamp":"2019-10-08T13:00:00Z","xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx":0.0,"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx":20.50,"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx":2.8,"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx":4.700,"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx":22.00,"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx":-93,"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx":32}09:00:17.738 ->09:00:29.527 -> -- Response Code --09:00:29.527 -> 504I am unable to tell from this output if something is not right. The first line looks suspicious – “Sending data to [0] data.envirodiy.org”.
Perhaps someone else can spot something not right in this output?Thanks
Yes, the board seems to perform just fine while only 1 card is inserted. There are most definitely electrical irregularities when 2 cards are in at the same time! I had erroneously assumed that the horizontal card was for uploading sketches and that data would be logged to the second (vertical) microSD card, which could be extracted easily to download data. There were no details in the Mayfly Manual explaining this aspect of the board. From now on I will just use 1 card on the vertical port. Thank you for helping me troubleshoot.
As for my original question about the SDI-12 address change for the Hydros 21 – is the data pin #7 and power pin #22 on the Mayfly? I could not find any details on this either. I am assuming it is, since it was in the EnviroDIY sample sketch, but I figured it would be wise to verify.
Yes, this is a brand new board.
The microSD card is not the issue – I have switched cards and get the same result. Both cards work fine if used alone.
I believe the problem lies in the circuitry between the two SD card slots… When only 1 card is inserted (either slot) the board powers on. If both slots have microSD cards inserted simultaneously – no power.
As an extra test, and to isolate the problem, I unplugged everything else from the board except the usb cable to the computer – I get the exact same behavior.I was able to fix the issue, though I’m not sure at all why it worked. When I have a microSD card in extra slot for datalogging the Mayfly board will not even power up. As soon as I pull the microSD card out the LED lights blink, the red one stays on and all is well. This seems to be a rather serious issue since the entire purpose of the mayfly is to log data. I can now communicate with the device/upload sketches. However, it seems my solution now leaves me with another problem…
-
AuthorPosts
