Matt Barney

@jamesbailey @neilh20

I’ve confirmed that the Verizon SIM we used was this one, from NimbeLink:
https://www.digikey.com/en/products/detail/nimbelink-llc/NL-SIM-VER-M1/7101751

@jamesbailey I’ll check with my colleague to find out exactly which SIM he used for the test; he’s in the field for a few days. My test code is based on https://github.com/EnviroDIY/ModularSensors/blob/master/examples/DRWI_SIM7080LTE/DRWI_SIM7080LTE.ino, and the only modem-related code change I made was to the APN.

-Matt

Hi @neilh20, I believe the SIM we used was a RevX.

The SIMCom 7080G modem chip upon which the EnviroDIY LTE Bee is built did not have Verizon certification until early August. Once they notified me, I asked SIMCom support what APN setting to use for Verizon, and this was their response:

Set you APN as…

[Read more]

OK, got it, thanks.

I’ve made the hardware and software modifications you recommended and all seems to work perfectly.

Thanks again.

Thanks for this excellent detail.

So we could continue to use the LTEBee adapter with the Digi modem on a v1.1 Mayfly, which would retain the functionality of the white and blue modem status LEDs, and would connect the Bee socket’s pin to the proper status pin on the Digi (without need to modify SJ19), and we would not need the power jumper to…[Read more]

A couple bits of additional info. To visually identify whether your Hydros 21 is a Gen 1 or a Gen 2, see attached photos of the sensor head on each version. Note that some Gen 1’s had red cables, but not all.

Second, as Shannon noted in the post she linked to above, the address-setting on the Gen 2 is slightly more finicky; you just have to…[Read more]

That was it – thanks!

-Matt

We’ve just had a failure to communicate with our newest Hydros 21 sensors (likely Gen 2). While I’ve had success setting the address with the b_address_change sketch, my standard Mayfly code can’t talk to the sensor and returns  values of -9999. It looks to me like the SDI-12 library has not changed since May 2021…[Read more]

These were just deployed 3 days ago and have been doing this from the beginning.

We are also seeing the missing display of “Last observation” values for all new stations we deploy, though it continues to work for stations that were deployed prior to the MonitorMyWatershed release on December 7th.

I’m also unable to delete sites (Server Error 500), and unable to delete sensors (no errors, but nothing gets deleted). I am going to report this via an issue at the Github site for the MMW data portal:
https://github.com/ODM2/ODM2DataSharingPortal/issues

Very helpful to know. Thanks for sharing, James.

Matt

Thanks for the schematic – that is helpful. I removed the solder blob using solder wick and re-added it to the res-div position, but it wasn’t pretty; it looks like I overheated the board a bit, but it still works. Later, I found a different technique in this video, which I’ll share here for anyone else who needs it.

FYI, Turner tech support tells me that Signal Ground and Supply Ground must be “Kept separate so that noise isn’t injected into the response.”

Thanks Shannon. I’m not positive that I need to use differential measurement… I’m approaching the edge of my knowledge as a non-EE. Turner doesn’t specify whether it’s OK to connect signal and power grounds to the same point — maybe I’ll ask their tech support. But when the sensor is on, I’m measuring around 13 mV between its signal ground and…[Read more]