UM FeatherS3 - has anyone tested these? Or tested ESPNow with ESP32-S3? #12017
Replies: 5 comments 4 replies
-
I got a Feather S3 from UM shortly after they were first produced. I had an issue with reliable wifi connection that showed up when I was testing that my wifi code on the board was reliably working when testing that the board would powering up and run after a power cut. It turned out that several of these boards were having wifi issues and it was replace with a new and tested by UM board via pimoroni where I purchased the board. The replacement board seems OK, but I moved to project to a rpi pico and have not used the Feather S3 much since then. When I had the wifi issue I reached out to UM on their discord site, and Seon was very helpful. It would probably be worth your while connecting to Seon directly to see what his thoughts are. |
Beta Was this translation helpful? Give feedback.
-
Hey @peterhinch - Sorry to hear you are potentially having some issues with your FS3. Firstly, can you let me know what the Also, when you say it work's ok with an ESP32 reference board, do you mean an ESP32-S3 DevKit board? or just an original ESP32 board? The ESP32-S3 it quite a temperamental beast compared to the original ESP32 and even the ESP32-S2. It has radio issues when native USB is active and you are using wifi channels below Channel 9 (degraded TX strength due to native USB interference) - and it's also got secondary harmonics issues and can switch TX off when you try to use max strength on the radios. That said, you should not be seeing stability issues - It should either work or not work in a situation - at least from my experience. Cheers, |
Beta Was this translation helpful? Give feedback.
-
Thanks for the clarification, Yeah, P4 ad P7 are the same on the RF side. The changes were only DFM things and moving the second STEMMA/QT onto different IO to allow different I2C busses on each STEMMA/QT connector. Ok, first thing you should try is using channel 9 or above - you should see an improvement just from that if what you are seeing is USB interference related. For reference, in MP and CP, USB is enabled all of the time, even if you are not plugged in via USB or have a REPL open, so it will always be agitating the lower channels - by how much is unknown - I've been told 1-2dB loss from some Espressif folks and 3-4dB from others :( The other thing you might want to try (might not be possible from within MP as I've not looked at the new ESPNow stuff) is to reduce the TX output strength down to a lower value - in the IDF, 20 is the max (and I believe the default) but setting it to 16 or 17 might help with the stability. If you want to send me a private message with your address, I can send you a new P8 revision board to try out - it has a new antenna & RF layout due to the white Ignion antennas I was using going EOL with out a drop in replacement. I'd be curious to see if the P8 revision works any better in your setup - I have broadened the freq bandwidth on the P8 version to help compensate for the USB issue, but of course that also means a slight reduction in dB overall, but that should be unnoticeable for general WiFi related projects. Cheers :) |
Beta Was this translation helpful? Give feedback.
-
@UnexpectedMaker Thanks for the suggestions. I will try channel 9 and It may be a week or so before I can be confident of a positive outcome because the appearance of the fault is so erratic. I have sent you an email with my address. Thank you for your help. |
Beta Was this translation helpful? Give feedback.
-
@peterhinch, Did setting a higher channel number and reducing the TX power level improve the reliability in your ESPNow experiments? I have a number of UM FeatherS3 boards and would love to use them in an ESPNow deployment. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been working on ESPNow for a while with erratic results from these boards. They don't seem to like communicating, going through periods of repeated ESPNow transmission failures. Replacing the Feather with the ESP32 reference board the problem goes away with thousands of messages being passed with very rare errors.
The fault is highly variable. At one point I convinced myself I had one bad board, when another Feather worked fine for a few days. Then it started dropping messages. The Feather is a nice board - aside from this I can't fault the hardware; but if it's not capable of reliable communication it's a turkey.
I'm unsure if the issue is specific to the Feather, or if it's an S3 problem, or whether it's associated with SPIRAM. I'm currently testing an ESP32 with SPIRAM which is working perfectly so far.
I'd be glad of any feedback on this.
Beta Was this translation helpful? Give feedback.
All reactions