Sara Damiano

I’ve made some tweaks to try to make the LTE XBee work better. Code wise, it should have already been working, though. The problem was more about slowness/inability to make a connection to the internet and periodic non-responsiveness. That problem is somewhat upstream of ModularSensors.

I’ve spent a lot more time playing with the LTE-M XBee3 so I think I can help a bit better now.

I cannot get it to connect without the solder jumper – it just needs the extra uumph. And the antenna is also definitely not optional.

No matter what I do, it sometimes stops responding. I’m seeing this whether I have it powered off the mayfly or if…[Read more]

Ugh. I’m sorry you’re having so much trouble understanding what’s going on in ModularSensors. It’s a very heavy-weight library.

While you’re deep debugging your modem connection, though, sticking to TinyGSM and a basic sketch, or even just XCTU, is probably the way to go.

Neil’s right about the symbol – it’s a reset-not pin – pull it low to reset.

But… it’s not connected to anything else on the board, so you can’t pull it in any direction without some hacking. You could use the pin stubs on the back of the board to solder on a wire to connect the bee reset pin to some processor pin. The Digi documentation…[Read more]

No, the gerbers are not available.

Assuming you’re using the modular sensors library, the 2 minute reading on the start-up was a feature that was supposed to help with debugging. The idea was that right after deploying a station you’d want to make sure it was working so you’d want frequent measurements. I took it out in the most recent release because nearly everyone was confused…[Read more]

The default settings allow up to 10 seconds before it times out and drops you out of command mode and has a 1 second “guard” time around the +’s to get back in. TinyGSM cuts the guard down to 100ms.

Yes, that’s what the streamdebugger is supposed to do.

Hmm.. try forcing a reset to all default values. The TinyGSM library drops the timeouts for xbee communication really low, which is great for the mayfly sending commands, but not as good for human typists.

#include <Arduino.h>
#include <StreamDebugger.h>
StreamDebugger StreamDbg(Serial1,…

[Read more]

ModularSensors doesn’t support the teensy at all and it’s very unlikely that I’ll ever be able write in the support for it there. Your have to switch to an AVR or SAMD based board to use it.

I’m not familiar with the Teensy at all, but based on my <5 minutes of google research:

– They’re ARM Cortex-M4 boards – totally different processor style
– But the core libraries support the same attachInterrupt() routine that I use to support interrupts on the SAMD boards – good – you can just copy the SAMD interrupt includes
– google isn’t…[Read more]

Get StreamDebugger here: https://github.com/vshymanskyy/StreamDebugger

My first guess would be that you put it to sleep and it won’t wake up.

Can run a really simple script just to hold the pins to wake it up and allow you to type in commands from your serial port monitor?

#include <Arduino.h>
#include <StreamDebugger.h>
StreamDebugger StreamDbg(Serial1, Serial);

void setup(){
  Serial.begin(115200);…

[Read more]

I’ve spent more time fiddling with the LTE-M XBee and I’m seeing the same results.

It’s a hardware problem, not software; the modem really does stop responding. I wonder if it’s that there’s not enough capacitance along the power line causing very short voltage drops even when it’s tied right to the battery. The user guide for the LTE-M XBee…[Read more]

I’ve made an Arduino library for communicating with the Yosemitech sensors: https://github.com/EnviroDIY/YosemitechModbus

It’s built on top of my modbus library: https://github.com/EnviroDIY/SensorModbusMaster

In the modbus library there’s a hardware folder with the plans for a little “wing” board to more easily connect a Yosemitech sensor to…[Read more]

Oh dear. That definitely *is* a problem. And that’s entirely my fault; I hadn’t error-checked that json in a long time. It should be fixed now.

Just FYI, there’s a lot in that library bundle.

I’ve usually seen that “no response” pattern with the 3G XBee’s without the solder jumper. I’ve assumed it was them “browning out” as they tried to connect to the internet. With those, switching the solder jumper seemed to fix the problem. Have you been able to connect to the internet at all with the LTE-M XBee? Is it working attached to a…[Read more]

We’ve bought these ones from Oregon Rule: https://oregonrule.com/product/superior-staff-gauges/ They don’t rust like the WaterMark ones eventually do. And, at least in the US, they’re cheaper.

Up to you whether you want to work with the develop or master branch. They are currently **not** compatible with each-other though, so if you’re flipping back and forth, you’ll need to adjust your code each time to match up. I think all the changes are in the modem structure.

I don’t know if the May code is compatible with the current master or…[Read more]

It looks like you mis-typed the last GUID’s; you put a space on the end of it. The parser doesn’t expect a space inside of the GUID, so it fails. The error is at character 333, which is the guilty space.

Update! I got the Digi LTE-M XBee to work on Hologram!

It turns out I needed a brand new sim; one that had never been registered with another device. As soon as I put that in, it worked.