Skip to content

Fix ESP32-S3 ESP-NOW startup timing - #241

Open
halfmanbear wants to merge 1 commit into
ExpressLRS:masterfrom
halfmanbear:patch-1
Open

Fix ESP32-S3 ESP-NOW startup timing#241
halfmanbear wants to merge 1 commit into
ExpressLRS:masterfrom
halfmanbear:patch-1

Conversation

@halfmanbear

Copy link
Copy Markdown

Add an S3-only 10 ms delay before disconnecting Wi-Fi, allowing station and channel setup to complete. The ESP-NOW diagnostic receiver already uses the same settling delay.

This resolves ESP-NOW telemetry reception on the MFD Crossbow ESP32-S3 target. The classic ESP32 target works without the delay and remains unchanged.

Other S3 VRX targets using Vrx_main.cpp may also benefit, although only the MFD Crossbow configuration has been hardware-tested.

Add an S3-only 10 ms delay before disconnecting Wi-Fi, allowing station and channel setup to complete. The ESP-NOW diagnostic receiver already uses the same settling delay.

This resolves ESP-NOW telemetry reception on the MFD Crossbow ESP32-S3 target. The classic ESP32 target works without the delay and remains unchanged.

Other S3 VRX targets using Vrx_main.cpp may also benefit, although only the MFD Crossbow configuration has been hardware-tested.

@pkendall64 pkendall64 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it would probably be a good idea to keep it consistent across backpack types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants