Sara Damiano

It doesn’t send the data from the gap because the ModularSensors library simply doesn’t have that functionality. It doesn’t attempt to re-send data. The data should be on the SD card, as long as the battery was still high enough to log.

I would really love to have that functionality in ModularSensors, but it’s not simple to implement and I just…[Read more]

You’ve included both “SD.h” and “SdFat.h”. Did you try including only one of those? They might not conflict for the compiler, but they have very similar functionality and shouldn’t be included together. Your code is written for SD. SdFat is better, but for what you’re doing it shouldn’t matter.

What do you mean by “does not work?” What do you see on the serial monitor and on you SD card’s file? When you say “The code itself works to display the data in the serial monitor, but it does not works when recording it into the SD card.” do you mean that you can see data on the Serial Port monitor do you mean that if you replace all instances…[Read more]

Can you post some debugging logs? Along with the Thing Speak / MMW debugging, could you turn on the “deep” debugging for the gprsbee? You’ll need to install the StreamDebugger library.

I’m sorry. Testing with 2G is a hassle for me because the coverage is terrible is my area. It would help if I can see what is going on.

I found the issue with the ThingSpeakDebugger. It’s now been fixed. It might take until tomorrow before PlatformIO “sees” the new version though.

To update your libraries in your current project:
– Open a new terminal in your project in Atom or go to the Terminal pane in VSCode
– type pio lib update
– all your libraries for the project should…[Read more]

I’m sorry I’ve not responded. I’m honestly baffled by the errors.

Could you show your whole ini and a shot of the contents of your .pio/libdeps/mayfly folder?

@fisherba – StreamDebugger is only needed if you include it in your program; it isn’t and never was a dependency of ModularSensors or TinyGSM. It’s not included in ModularSensors.

Oh, and just to note about those other build flags:

-DSDI12_EXTERNAL_PCINT – this tells the library that you don’t want the SDI-12 library to try to monopolize the interrupts on an AVR board, which is required to make it “play nice” with the other libraries. You absolutely must set this because the SDI-12 library is a dependency of…[Read more]

You can also enable all of the debugging using a build flag in your platformio.ini. The result is exactly the same as if you un-comment the line in the header. You can add flags for any (or all) of the different modules.

build_flags =
    -DSDI12_EXTERNAL_PCINT
    -DNEOSWSERIAL_EXTERNAL_PCINT
    -DMQTT_MAX_PACKET_SIZE=240…

[Read more]

Those settings should be right for the XBee Wifi. Are you sure the unit is connected properly to your wifi? Can you connect the unit to XCTU and try to send a test json in the console log of XCTU?

That example sketch should still work, but for anything new I would recommend you switch to using the ModularSensors library to send data to the…[Read more]

@jkirchoff – drive the pin level with the digitalWrite(#, level) function.

If you’re using a Mayfly, the XBee’s sleep request pin is attached to the Mayfly pin 23. So to wake the bee, send data, and put it to sleep all you needs is:
digitalWrite(23, HIGH);
Serial1.print(“some text);
// more print statements as desired
digitalWrite(23, LOW);

Use…[Read more]

There’s a known bug from Digi that any of the XBee3’s with revision “B” of the primary processor, where it will become unresponsive even with very short dips or irregularities in voltage: https://www.digi.com/resources/documentation/Digidocs/90002258/#Troubleshooting/ts_brownout.htm%3FTocPath%3DTroubleshooting%7C_____7

I don’t know about the…[Read more]

You can completely ignore the error “override controls (override/final) only available with -std=c++1 or -std=gnu++11” I’m not sure why it always comes up. I can’t imagine your compiler version isn’t high enough to support it.

If you’re averaging multiple measurements, the first measurement is started stabilizationTime_ms after wake up and the result requested measurementTime_ms later, or as close to that time as the sensor is checked in iterating through all variables. The second measurement is begun in the next loop after the first measurement result is collected, so…[Read more]

You definitely want to update for calculated variables. There’s a big bug in 0.19.6 in the “completeUpdate” function in run inside the “logData” function that will make any calculated variables crash.

After you update, adding the compass as a “calculated” variable should work just as you described. That is, you could call the begin and update to…[Read more]

Shannon designed the board well!