ESPixelStick - E1.3...
 
Notifications
Clear all

ESPixelStick - E1.31 WiFi Pixel Controller

948 Posts
178 Users
0 Reactions
503.7 K Views
sporadic
Posts: 1199
Topic starter
(@sporadic)
Noble Member
Joined: 14 years ago
Kensington wrote:I'm having a different problem. It programs correctly and the status window is clear text, but the serial monitor returns only gibberish, so I don't get an IP address. In past experience, that's indicative of differing baud rates, but I'm at115200, 8 data bits, no parity, 1 stop bit, no flow control. Any thoughts on how to correct the output on the serial monitor?

ESPSFlashTool configures the serial port when programming. What OS are you on? What happens if you hit the reset button on the ESP, do you get any legible text? And lastly, if you have a serial terminal like Putty, could you try it while resetting the ESP? That should help narrow it down.


Reply
Posts: 401
(@kensington)
Reputable Member
Joined: 11 years ago

Windows 10. I saw the parameters the programmer was using to set the serial port coming over the status window, so I figured it might be a baud rate issue. Reset generates gibberish. I tried to PuTTY in, but it doesn't see COM4, which is the USB/Serial cable. That's a problem I've had in the past with various cables. My interim solution is to refresh the wireless router after flashing each ESP-01 and checking the new IP address that shows up. Then I browse to it to verify the stick ID is what it should be.


Reply
sporadic
Posts: 1199
Topic starter
(@sporadic)
Noble Member
Joined: 14 years ago
Kensington wrote:Windows 10. I saw the parameters the programmer was using to set the serial port coming over the status window, so I figured it might be a baud rate issue. Reset generates gibberish. I tried to PuTTY in, but it doesn't see COM4, which is the USB/Serial cable. That's a problem I've had in the past with various cables. My interim solution is to refresh the wireless router after flashing each ESP-01 and checking the new IP address that shows up. Then I browse to it to verify the stick ID is what it should be.

Hmm. Sounds like it could be something with the cable or a driver blocking something. The firmware advertises itself via mDNS as well. You can discover them from an Android phone with this app. Just look for "_e131._udp." and click on it. You'll get a listing of all your ESPixelSticks and IP's by Device ID.


Reply
michaelc
Posts: 1540
(@michaelc)
Noble Member
Joined: 19 years ago

Maybe I'm just not understanding. I was able to use the new flash tool to program all my boards with 1.x with my usb and FTDI board wired up. I then used the same setup to flash everything to 2.0. This version has OTA and I now want to go to 2.1. My understanding is the with OTA I no longer need the FTDI USB setup. What is the process to update and flash OTA using the new .efu?


Reply
sporadic
Posts: 1199
Topic starter
(@sporadic)
Noble Member
Joined: 14 years ago
michaelc wrote:Maybe I'm just not understanding. I was able to use the new flash tool to program all my boards with 1.x with my usb and FTDI board wired up. I then used the same setup to flash everything to 2.0. This version has OTA and I now want to go to 2.1. My understanding is the with OTA I no longer need the FTDI USB setup. What is the process to update and flash OTA using the new .efu?

I'm including the .efu files in the firmware release zip. You just upload them via the admin page and that's it. There are two in the 2.0 release package, one for pixel mode and one for serial mode. Feel free to switch them around and take it for a test drive 🙂


Reply
Page 44 / 190
Share: