Sara Damiano

To modify the Mayfly to work as a carrier board you’d need to cut and re-solder jumpers SJ8 and SJ9 on the back of the Mayfly to connect Bee Tx and Rx to Tx 0 and Tx 1.  You would want to undo the change to use the Mayfly again normally.  I’ve never actually tried this modification and am not 100% positive it would work.

I suggest you just f…[Read more]

Ok, so you have a stack with a Mayfly, an LTE adapter board, and a XBee3 (3 parts).

You don’t have a separate development or carrier board.  All of my comments about the USB-C/USB 3 apply only to a separate carrier board.  If you don’t have one, don’t worry about that.

I’m not sure the best way to confirm that it’s totally bricked.  If you power it up and still have all the pins reading 0 voltage, that’s probably a bad sign.

If XCTU doesn’t recognize the XBee3, that’s a pretty bad sign.  How are you attaching your XBee to the computer?  Do you have the USB-C XBee3 carrier?  https://www.digi.com/products/models/xbib-cu-th  That development board should make sure the bee is awake and work flawlessly with XCTU.   Are you plugged into the USB-C port, not the side micro…[Read more]

I just added another fix for the XBee wifi and the modem-measured battery voltage.  Have you been able to get it to work for you?

I’m sorry.  I finally fixed pushed what I think should be the changes needed to the develop branch, but I still haven’t programmed an actual board to test it.

This everyone being home all the time situation is brutal.  Anyone doing well with it  is clearly a lot more disciplined and organized than I am.

I’m just seconding what Shannon said about using the hardware UART – always use hardware UART unless you definitely cannot.  In your case where you’ll be parsing long NMEA sentences, I’d recommend actually re-wiring your Bee/modem to give your GPS the better connection if you’re trying to use both.  In your code, you just use “Serial1” to c…[Read more]

I’m so sorry.  I haven’t tested it yet.

No problem!  The wonder of git is that I actually could track back pretty quickly how long it had been since any changes were made and what those were.

I’ve pushed what I think should fix the testing mode to the develop branch of the ModularSensors library, but I haven’t actually tested it myself yet.

I’ll see if I can get it tested tomorrow and then pushed to the master branch.

Working on it right now for you.  It will be a library update.  The lack of modem update in sensor testing mode was an oversight; I want it to be there automatically.

You didn’t manage to connect to the internet for the clock sync.  I’m not sure why that happened.

The modem values won’t update in sensor testing mode and they’re always updated at the *prior* internet connection.  Since you didn’t connect successfully for the clock sync, they didn’t update.

I waded back through my “git blame” and I don’t see any changes I’ve made to the request more recent than 8 months ago, where I removed one single space – from a double space in one of the headers.  The next most recent change was 15 months ago.  Is it possible your libraries were that old?

@stoltzfus-12osu-edu – that is very interesting to know.  Do you happen to know exactly what version of the library you’d had prior to updating?  If not, how long (at least roughly) would a the long time since you updated be?  A month or two? A year?  The specification for the post format hasn’t changed at all since it was first developed, but i…[Read more]

It’s very, very intentional that ModularSensors uses that Atlas sensors only in I2C mode and I do not intend to change this.  When using Atlas sensors in UART mode, each sensor must have an individually dedicated UART port.  The Mayfly has exactly two hardware (processor implemented) UART’s – one dedicated to the computer/programming and the o…[Read more]

It would be so much better if the website at least told you *why* and upload failed!  All you get is a “failed” which could mean anything – the format was bad, the file was too big, there was an internet blip, who knows.  The only way right now to even get an inking as to why it fails is to turn on “developer tools” (F12 in Firefox, I think also i…[Read more]

Also, just so you understand, ModularSensors isn’t powerful enough to “stash” recent data and save it for later.  So when you’re in production and only connecting once an hour, the data being sent on the hour will only be for that one point.  If for some reason there’s something wrong with the cellular connection in that moment it is supposed to s…[Read more]

@w3asa – I don’t have formal training in computer science or even in electrical engineering.   I have one bachelor’s level degree – in chemistry.

@stoltzfus-12osu-edu – two things with your code – and I completely understand why you did it the way you did – because the example did.  Blame the chemist.

1 – you’re creating each variable 3 times in…[Read more]