Sara Damiano

Does the red power light on the lower right of the modem turn on? If not, the modem isn’t getting power. Pin 18 should be the right pin number. I’m not sure why it wouldn’t be powering up. Have you ever messed with the solder jumpers?

If the modem is powering up, you might have a baud rate problem. Try setting the modemBaud to 57600 even…[Read more]

According to the product change notification you attached, there shouldn’t need to be any software changes for “transparent” mode, so most of the examples for ModularSensors should still work.

The underlying cellular chipset on the board *has* changed from the ublox SARA R410M to the Telit ME310G1-WW on the global version or the Telit ME310G1-W1…[Read more]

I’ve been swamped lately, so I’m behind on sensor requests.
<div>
<div>@fionasouthwell Are you sure you’re measuring *specific conductance*? From what I know of the Atlas sensors, they don’t measure specific conductance, they measure conductivity. I just very quickly skimmed their latest manual and it doesn’t look like that’s changed. To get…[Read more]

You need to either upgrade your ModularSensors library from 0.34.0 to 0.35.0 or downgrade your SD fat library from 2.2.3 to 2.1.2.

All the dependent libraries are updated all of the time and not all versions match with each other. It’s best to download the libraries as a package from the ModularSensors releases page on GitHub. That zip file…[Read more]

I know nothing about rosserial. Are you using Hardware Serial with it? Serial or Serial1? Are you using some type of software serial (SoftwareSerial, AltSoftSerial, NeoSWSerial)? Very quickly skimming the rosserial docs and code, it looks like it has some specific boards that are supported and the 1284p in the Mayfly may not be 100%…[Read more]

This code still works for me. Are you sure you have your start and end dates set within the range that your sensor has data?

The list Shannon shared for ModularSensors should be up-to-date.  But the Mayfly itself can interface with many, many more sensors that are supported by libraries other than ModularSensors. We couldn’t make a comprehensive list – almost any sensor that can work in an Arduino environment can be used with the Mayfly.

Are you sure your serial port monitor is set to the same baud rate as the serial baud rate in your program?  Usually when there are nothing but junk characters, it’s a baud rate mis-match. I would suggest using a serial baud rate of 57600. Make sure you have that set in your program and on your serial port monitor.  The baud rate between the s…[Read more]

@bibhutibikramaditya Exactly what output are you getting?  You’re not asking for data in your script, so you should only be getting a response like “00013” not any data values.

Suggestions:

• Confirm that the data pin of the Hydros 21 sensor is plugged into the correct pin (2)
• Confirm the sensor has power
• Confirm that you’re serial port…

[Read more]

Are you using PlatformIO or the Arduino IDE?  In PlatformIO, you can add it to the build_flag section of your platformio.ini file. Add -DMS_SDI12_NON_CONCURRENT right below the -DSDI12_EXTERNAL_PCINT line in the example ini file.  If you’re using the Arduino IDE, you need to open up SDI12Sensors.h and add the line #define MS_SDI12_NON_CONCURRENT a…[Read more]

Have you tried using the -D MS_SDI12_NON_CONCURRENT build flag: https://envirodiy.github.io/ModularSensors/group__sdi12__group.html.  Some SDI-12 sensors don’t properly support the concurrent mode that ModularSensors uses by default.  That could by why they work individually, but not all together.

I finally dug into this.  As I commented on GitHub, I think this loss must be related to a server update or hotfix.  The server did get the data, so it might be recoverable. I doubt it’s related to the older issue.

If you can create a POST request, you can get data to Monitor My Watershed.  There’s information about the POST format here:

https://github.com/ODM2/ODM2DataSharingPortal/blob/main/doc/example_rest_requests.md

I’m sorry; I’m stumped. There’s something wrong with the way the battery voltage is being read. But I don’t understand what. As soon as I turn on the debugging for it.. it works. It also works if I upgrade to the current ModularSensors master branch. But I cannot figure out for the life of me what change makes it work.

So my two suggestions to…[Read more]

I’m looking into it. I would have said “of course they should work together” but I’d never tried it, so I hooked it up and tried it out. And I got the same result as you. I haven’t figured it out yet, though.

The LTE Bee (and WiFi) can change IP addresses at any time.

The WiFi bee is actively being supported. It’s what I test with on my desk. Switching back and forth between WiFi and LTE is fairly simple. But you should still do some LTE testing on your desk before moving to the field.

If you’re using a Mayfly, I’d go with the WiFi Bee. It plugs right in. Any other shield would require jumper wires or other…[Read more]

You need to set the sampling feature UUID for the logger. If you have an EnviroDIYPublisher, this happens automatically, but without the publisher, you need to add it.

So after you set the logger pins in line 283 (dataLogger.setLoggerPins()), add the line dataLogger.setSamplingFeatureUUID(samplingFeature);

I’m sorry I haven’t responded yet. I’ll try to look into this tomorrow.

The radio XBee’s *cannot* be used directly with the logAndPublishData functions. That only works for XBees that have a direct internet connection.

You would have to set up your radio using the Digi software and then write your loop function, which would print your json or csv string out over the serial port for the radio to hear.