[Sara Damiano]

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

[Sara Damiano]

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 using an example PlatformIO configuration file from the ModularSensors library, you should see the build flag set there.

What changes needed to be made inside the sdi-12 library? Bigger buffer? Anything else?

[Sara Damiano]

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!

[Sara Damiano]

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.

[Sara Damiano]

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

[Sara Damiano]

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.

[Sara Damiano]

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.

[Sara Damiano]

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, but the Mayfly has a hard time hearing back from the esp at that speed. And it gets especially bad when running a program like yours that’s trying to synchronously write and read from both serial ports at the same time. So when the Mayfly said “AT” to the ESP8266, the esp actually echoed “AT” and then said “OK” but the Mayfly misheard and it got garbled into that “au?” (AT) and “C?j5” (OK). After AT+RST you’ll always see some junk because the ESP8266 prints out some notes when it boots at a different baud rate than it’s normal talk speed.

So.. in short:
– If you just want to talk to the ESP8266 and don’t care about what it says back, you’re fine doing just as you are

– If you want to talk to the ESP and can handle listening to it in your program without simultaneously printing it to Serial, you’re probably also alright, but somethings might be garbled

– If you want to talk to the ESP and echo its responses and make sure they’re always correct, you need to slow the ESP down.

To change the baud rate of the ESP8266: (for 9600, 8N1)
“AT+UART_DEF=9600,8,1,0,0”

[Sara Damiano]

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.

[Sara Damiano]

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/

[Author]

Posts