Rick Vogel

That is the version of XBee I use as well. They are very short supply. I only have some cause we bought a large supply of them bout a year ago.  The dev board I use with mine to upgrade the cellular firmware and normal XCTU operations is the XBIB-CU-TH. Digi-Key has 200+ of those.

No, the apn would need to be loaded via XCTU or you can place it in the python code before the cellular connection action…

xbee.atcmd(“AN”, “hologram”) —–or whatever your apn is

conn = network.Cellular()

Any arduino code you would like to use. The key is to identify which serial port you have connected to the XBee. For instance if you have it connected to Serial1 then you would want to print out the statements you want sent to Thingspeak like so…

Topic posting to includes multiple fields

Serial1.println(#Pfield1=60&field2=45)

Topic posting to…[Read more]

Try this one:

https://drive.google.com/file/d/1TiLQtE16-ZmfP6aWsBKG9qDgYH7BN1Lv/view?usp=sharing

it seems I have to add your contact email to allow the share. I’ll see if I can post the zip file. It didn’t like the .py files before

I misspoke on the DC/DC supply. It is a Meanwell DDR-15G-5. Pic of the guts on that polycase is attached.

We use a polycase 12x10x6 customized enclosure for under $85 with everything predrilled https://www.polycase.com/yh-121006.

We made a custom din rail bracket to hold the two batteries. 10W panel for solar but charger will accommodate up to 30W

AWS for Xbee

https://www.digi.com/resources/documentation/digidocs/90002219/container/cont_aws.htm

12V to 5V is a DC/DC Din Rail supply P/N: MDR-20-5. The board takes in 5V and and has a 3.3V LDO onboard for those 3.3V parts that pull more than the teensy 3.3V output can provide.

@neilh,

Yes, we have solar to the charger and into (2)12V 9aH batteries (in parallel). The Teensy and Xbee are on a custom motherboard we designed. Has lots of the IO broken out and spots for Adafruit GPS, RTC battery, ESP32 (older requirement) and Wiz850io Ethernet.

See pic attached

See page 16 4.4.8.1

http://www.sdi-12.org/current_specification/SDI-12_version-1_4-Jan-30-2021.pdf

@neilh

Teensy 3.5 topic set up.

@Both

Working on the google drive link for the XBee files if either one of you want them in the future.

Are these Verizon Jetpacks with Wifi or do your modems have a serial connection? We started out with AWS, Verizon Jetpacks w/WiFi and the ESP32. It worked, we just didn’t have an active AWS contract in place so the free trial accounts were running out of room for us. We at that point just set up an internal MQTT Broker so we (National Weather…[Read more]

@dan

I agree with @neilh in that AWS can be a little cumbersome. I have used it with the ESP32 platforms in the past via WiFi, but in the end opted for using other end points than AWS. Lots of free dashboards out there for starting out and learning. Most of the really nice ones start adding costs once you decide to scale up the number of data…[Read more]

@neilh20

I’ll put the files up on a google drive and send a link for a folder to download here in a bit.

Yes, micro-python gives you lots of option. We use TLS1.2 encryption of our data, run a broker at one of our regional headquarters and also have a FTP-Secure server to remotely update both the XBee and the Teensy 3.5 processor I use as the…[Read more]

@zeke-holloman

Everything I was talking about is MQTT with Thingspeak.  I tested it on my Thingspeak connection I created. It was just allowing the micro-python code in the Xbee to handle all the network and MQTT items vice using the AT commands from the MayFly to the Xbee as it looks like is happening in the enviroDIY libraries.

Here are the python files if you ever decide to look at that option. Please feel free to manipulate however you need to.

• Open up the main.py file in a ‘python’ editor and use the credentials you get from the MQTT device you created on thingspeak, not your API keys. Save file.
• Within Digi XTCU you will need to go to File System Manager on the…

[Read more]

@neilh20 and @zeke-holloman

Gonna let you all work through this on the mayfly code using the xbee transparent mode. If at some point you would like to use the micro-python option in the xbee I can provide some code to just use simple serial.println() on the mayfly to send payload to the xbee and it will handle all the MQTT stuff in the background.