Activity

Thank you for your response.
I used TinyGSM directly and got into this problem. I was deploying broker locally,, the code on the inside check for dns lookup.. Currently I commented this code out and tinygsm works.
https://github.com/issues/created?issue=vshymanskyy%7CTinyGSM%7C854

This is what my full code looks without tinygsm:

#define XBEE_PWR…

[Read more]

Are you using anything else from the Modular Sensors library? Post your entire sketch as code (use the <> button to post as code)?  Are you setting the host and port for the mqttClient? (mqttClient.setServer(ip, port)) Use your local IP there.  If you do that, I don’t see why you’re not getting a connection even with the bad DL setting in the e…[Read more]

Thank you for your response.
I think it’s the master branch.

Also, this is what I am trying to do.

DigiXBeeWifi modemXBWF(&Serial1, powerPin, statusPin, false,
modemResetPin, modemSleepRqPin,
ssid, pwd, false);

Client* netClient = nullptr;
MqttClient* mqttClient = nullptr;

void setup() {
Serial.begin(9600);
Serial1.begin(9600);
delay(2000);

if…

[Read more]

Ooooh.. yup, there’s a bug in DigiXBeeWifi.cpp.  I’ll look into it.

Exactly which version of the library are you using (release, master branch, develop branch)?

For now, you may be able to get it working by commenting out lines ~303-310 in src/modems/DigiXBeeWifi.cpp, the section starting with “set the destination IP to 0”

If that doesn’t compile for you, update your TinyGSM library or just delete lines 87-92 to remove the forceModemBaud command, which needs the version of TinyGSM within the last few weeks.

It it’s working for you, comment out the section that resets the modem to defaults (lines 107-126) and run it one more time to get the modem to 9600. It should…[Read more]

Use 3.3V to power the WiFi bee and make sure that you’re adapter uses 3.3V logic.  The 0.5A most USB ports can provide should be enough for the WiFi bee without browning out.  You are seeing the lights on the bee go on, right?

This script worked for me to force the baud rate on three different WiFi Bee’s.  The script forces the baud rate and th…[Read more]

I’ve tried some more witht hat code and no luck. So I decided to confrim the AT firmware and I’m not sure if I did or not. Using a USB to TTL I connected directly to the Wifif Bee and used Putty. I did see some text and a brownout warning on the screen. So I used the TTL for RX and TX and I connected a 3.7V Lipo battery to VCC and GND and also the…[Read more]

Thank you very much Sara. I have tried something like that before (but likely not quite rightly coded). This failed to switch baud rates too unfortunately. I have tried this on 3 out of 4 wifi bees that I have (but just one with you sketch so far) and no luck, that’s how I ended up asking about the firmware.
Did your sketch in a hurry, so will…[Read more]

Once you’ve successfully changed the WiFi bee’s baud rate, it will stay at the slower baud. You should only have to reset the baud rate if you factory reset the bee or update it’s firmware – neither of which you can do by accident.

The WiFi bee should have the AT firmware on it. The problem probably is the baud rate. The default baud rate for the ESP32 (the brain on the WiFi bee) is 115200. That’s too fast for stable communication with the 8MHz Mayfly.  The Mayfly can usually *talk* fairly accurately at 115200, but it can’t listen that fast.  The auto-baud function depends o…[Read more]