Sending Data Through Verizon Network

The Mayfly stations with 4G-LTE modules that we deployed for you earlier this year were all configured to only use AT&T as the provider, but since then we have tweaked the code to allow them to work with either AT&T or Verizon, whichever carrier has the strongest signal at your location. It still uses the same Hologram SIM card, it’s just a configuration that the Mayfly writes to the LTE Bee when you boot up the Mayfly. If you download the latest Modular Sensors libraries (0.23.16) from our Github repo and use an example sketch from that directory, then it will configure the module properly for either cell carrier. If you haven’t programmed a logger with ModularSensors yet, you’ll probably need a bunch of the other libraries as well, so it’s easiest to just grab everything from here: https://github.com/EnviroDIY/Libraries
Follow the instructions in the ReadMe that tells you how to properly download all of the files in the Libraries repo. And if you’re using the Arduino IDE and you already have some of the folders that are contained in the EnviroDIY Libraries repo (which is probably very likely), then you might end up with conflicts due to having multiple copies of similar libraries, so you might have to resolve those. Using something like PlatformIO as your IDE will solve the library conflicts, though it has a pretty steep learning curve if you’re new to programming.

Hi Shannon, I’ll be helping Jake modify the code for our loggers according to your instructions. I’m wondering whether I should start with the code that was installed on our loggers when they were deployed (assuming you have a copy?) or should we start building again from the example code on GitHub?

Thanks,
Matt Barney

The code we put on your loggers a few months ago needs to be replaced with the newer version because the latest updates account for the addition of Verizon as a carrier, and make a few other tweaks to the basic functions of the station we’ve made since deploying a few dozen LTE stations in the last month and examining their performance. All you need to customize the code is three things: enter your station ID /stream name into the correct part of the code near the beginning (line 47), the UUID information for each station (which Jake will have to get from the MMW site since only the site owner can view those values), and you’ll also need the turbidity sensor calibration information, which is written in the “Notes” field of the two turbidity parameters in each of your stations (these are the values obtained from the calibration sheet that comes from the turbidity sensor manufacturer and is unique to each individual turbidity sensor).

So you have all the info you need to customize the sketch for all of your stations. If you want to email the sketches to me before you write them to the logger so I can check them for accuracy, that might be a good idea. Just zip all the .ino files into one ZIP file. Many email clients won’t let you attach a raw sketch file due to antivirus/security filters, so it’s best to zip them before sending.

Great – Thanks Shannon!

Matt