You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TX power of ESP32 will drop when we increase the bandwidth. 11mbps would be the best option for my view. (20dbm, need to solve the low bandwidth problem)
as they said on official web esp_wifi_set_promiscuous_rx_cb(packet_received_cb)will have huge impact on total through put as the CPU need to process every packet, instead of the driver (the filer is done by CPU).
there is a function esp_err_t esp_wifi_internal_reg_rxcb(wifi_interface_t ifx, wifi_rxcb_t fn); which works for ESP32 MAC and 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF only. (guess: done by hardware, no test, It is used by esp ip layer)
/** * @brief The WiFi RX callback function * * Each time the WiFi need to forward the packets to high layer, the callback function will be called*/typedefesp_err_t (*wifi_rxcb_t)(void *buffer, uint16_t len, void *eb);
/** * @brief Set the WiFi RX callback * * @attention 1. Currently we support only one RX callback for each interface * * @param wifi_interface_t ifx : interface * @param wifi_rxcb_t fn : WiFi RX callback * * @return * - ESP_OK : succeed * - others : fail*/esp_err_tesp_wifi_internal_reg_rxcb(wifi_interface_t ifx, wifi_rxcb_t fn);
ESP CAM lib loop is running on core 0, however the blocking call back is on core 1
add support for gamepads on gs. My rog z1 120hz screen can achieve 40-50ms latency without vsync, week FEC, 7.0-7.2 mbps, mtk mt7921e chipset
linux appimage version? was trying to run on steamos on rog z1 but lack of libs
CIF 60 FPS mode for fpv is still necessary
FCS is done by wifi hardware (last 4 bytes, u also said in main rx call back fun), no needed to add crc in my view. Most wifi card will drop the packet if FCS is not correct. (no ideals for modified driers) -> https://en.wikipedia.org/wiki/IEEE_802.11
The text was updated successfully, but these errors were encountered:
When comparing 11 Mbps and 24 Mbps, the TX power difference is approximately -2 dBm, with a 2.6 dBm reduction in receiver sensitivity for 24 Mbps.
For reliable Wi-Fi communication, the signal must maintain a +7 dB margin above the noise floor. Given a typical field noise level of -88 to -90 dBm, signals below -83 dBm are generally unreliable. As a result, my preferred choice is 24 Mbps (MCS2). Reducing the speed to 11 Mbps does not provide a great range advantage based on my tests.
Currently, I can only achieve about 35% of the theoretical bandwidth. At 24 Mbps, I see a throughput of 6 MBps. At 11 Mbps, the throughput drops to 2-3 MBps, which is insufficient for good-quality streaming.
Hi:
I did a bit of research and find:
esp_wifi_set_promiscuous_rx_cb(packet_received_cb)
will have huge impact on total through put as the CPU need to process every packet, instead of the driver (the filer is done by CPU).there is a function
esp_err_t esp_wifi_internal_reg_rxcb(wifi_interface_t ifx, wifi_rxcb_t fn);
which works for ESP32 MAC and0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF
only. (guess: done by hardware, no test, It is used by esp ip layer)The text was updated successfully, but these errors were encountered: