Sara Damiano

Hopefully @aufdenkampe will confirm but I think he went the USB route mainly to avoid power losses in the step down. If you go that way you probably need a relatively expensive 12V to USB to make sure you are getting less loss than the built in step down.

Oops, yes, sorry, the modem would have power without the battery, just not enough. The naked u-blox SARA R410 cellular chip uses just barely under half an amp at peak. (Assuming you’re using the LTE model.) Add the Digi processor and it’s too much. I’ve never had any luck getting it to connect without a battery. It browns out and stops…[Read more]

I’m sure the LSM303 could be integrated into ModularSensors. You should also be able to use it along with ModularSensors without actually integrating it. You might not be able to use the “logData” function though – you might have to break it up some.

So, do you have your program somewhere I could look at? Are you turning off the power to the…[Read more]

Depending on the version of the Mayfly you have, there’s a 12V power input that you can step down and use. If I remember correctly, though, @aufdenkampe once told me he’d had smoother power and less loss using a separate 12V to USB step down and powering the Mayfly via the USB port.

Unfortunately, though, with either option you would still need…[Read more]

I haven’t encountered those sensors yet. Hmmm..

@gregcutrell – The _numReturnedVars isn’t a “user set” variable in the typical way you might be thinking of it. It is *not* intended to be set by a user in a program. It’s intended to be set in the header file for a specific sensor. When creating it, the writer of the header file should know exactly how many values the sensor can and will…[Read more]

If you’re curious, I’m working on the objectInitialization branch for this.

The “base” (master) branch of the SDI12 library should claim all possible on change interrupts so you don’t need to mess with calling them yourself. You only need to define the interrupts if you work off the ExtInts branch or if you compile with a build flag to set SDI12_EXTERNAL_PCINT. I think the latter is only possible in PlatformIO. If you’re…[Read more]

Ugh. I’m sorry. I can definitely reproduce this, but I haven’t solved it yet. I’m fairly certain it’s because I’m linking object together in the constructors, but they’re not being created in the right order. This is causing important things (like the whole variable array) to be recreated.

I’m working to solve it.

Sorry!

With AltSoftSerial, data in to the Mayfly goes on pin 6, out from Mayfly on pin 5. It’s kind-of a pain because the Tx and Rx are broken into different Grove ports, but for something like the Maxbotix that you only need Rx for, it’s fine.

I’m starting to look at the calculated variables.

Have you read the threads on the LTE-M XBee? I’ve gotten it to work; hopefully you can too! https://github.com/EnviroDIY/ModularSensors/issues/162#issuecomment-459879699

Oh dear. I’ll get on this ASAP and let you know how it’s going.

A warning on the ublox shield:the native baud rate is 112500, which is to fast for the Mayfly. Look at the gitgub issue on the sodaq uBee for how we worked around it. There’s code in the soon-to-be released as master atlas branch for it.

Oops. Sorry. I’d typed that and didn’t see your response. But yes, slowing down the ESP8266 is the way to go if you want to make sure everything is heard correctly.

Yes, I’ve had problems with the Mayfly receiving data at 115200. The Mayfly is only running at 8MHz and Atmel says the error rate at that baud and crystal combination is 8.5%. The error is a much bigger problem on the receiving end than the sending end. So the serial port monitor and the ESP8266 understand what the Mayfly is saying at 115200,…[Read more]

All of the Mayfly pins are at 3.3V.

I’ve done a decent amount with a Mayfly and an ESP8266 using the “AT” firmware on the ESP8266. I haven’t had any problems with it.

I haven’t done any comparisons, but I bought Taoglas Maximus FXBU66 antennas and they seem to work quite well: https://www.taoglas.com/product/maximus-fxub66-ultra-wide-band-flex-antenna-smam/

I just want to be really clear that the very slow connection speed and non-response is A PROBLEM WITH THE XBEE ITSELF, NOT THE CODE.

The messages like “no response received” are merely letting you know that the Bee is not responding.

There is nothing I’ve done in the code recently that changed it from “not working” to “working” with the LTE-M…[Read more]

The XBee’s are all 3.3V logic levels.

I used pin A4.

Shannon soldered a jumper on a board for me to connect the reset pin to a data pin on the Mayfly’s mcu so I could try it with the XBee. Unfortunately, it won’t work if you’re powering the XBee off of the battery (ie, w/ solder jumper 13). Erm… or rather, unfortunately, the board I had her put the jumper on seems to have gone very flakey. It…[Read more]