Skip to content

webui: document Voltage Calibration, WiFi State and the password reveal - #554

Draft
MUSTARDTIGERFPV wants to merge 1 commit into
ExpressLRS:masterfrom
MUSTARDTIGERFPV:webui-tabs
Draft

webui: document Voltage Calibration, WiFi State and the password reveal#554
MUSTARDTIGERFPV wants to merge 1 commit into
ExpressLRS:masterfrom
MUSTARDTIGERFPV:webui-tabs

Conversation

@MUSTARDTIGERFPV

Copy link
Copy Markdown
Member

Three parts of the 4.1 Web UI are missing from this page.

Voltage Calibration

A whole tab that is not mentioned anywhere on the site. Added between Hardware Layout and Continuous Wave to match the navigation menu order in app.js.

Scope and gating come from app.js: the menu entry sits inside <!-- FEATURE:NOT IS_TX --> and is only emitted when elrsState.settings?.voltage_source_count > 0, so it is receivers only and only when the Hardware Layout defines a voltage source.

The four steps match voltage-calibration-panel.js exactly:

Step Panel
1. High Voltage '1. High Voltage', "Set a known voltage near ... and capture it", input labelled Known voltage (mV)
2. Low Voltage '2. Low Voltage', same input
3. No Voltage '3. No Voltage', "Disconnect the source and capture the idle reading, or skip if it is always present", with Capture and Skip
4. Review '4. Review', shows offset, scale, no-reading and the low/high fit error, then "Reconnect or adjust the PSU and confirm the live reading before saving"

Saving writes <source>_offset, <source>_scale, <source>_atten and <source>_noreading into hardware.json with customised: true via saveJSONWithReboot, which is why the section says the receiver reboots and why the calibration travels with the Hardware Layout on export.

The attenuation sweep is ESP32 only. CALIBRATION_ATTENUATIONS is [4,5,6,7] on ESP32 and [-1] under FEATURE:IS_8285, so the text limits that claim to ESP32.

The warning about input voltage is included because the wizard has no way to protect the hardware; the limit is set by the divider on the board.

Information Tab

The WiFi State row was not described. It is formatWifiRssi() from state.js, rendered by info-panel.js. Note this is on the Information tab, not the WiFi tab.

It shows Client [ssid] or AP mode, plus the strength in dBm when wifi_dbm is non-zero. The note records that the value means different things per mode, because wifi_GetClientRssi() returns WiFi.RSSI() in STA mode but the RSSI of the single connected client in AP mode, and returns nothing on ESP8285. A weak signal causing a failed firmware upload is a common support question, so that is called out.

I deliberately did not reproduce the quality strings verbatim. They include a joke tier and an easter egg at exactly -69dBm, so the page describes them generically rather than treating them as a stable interface.

WiFi Tab

The control that reveals the stored password was not documented. wifi-panel.js toggles the field between password and text with an eye button. The text notes the obvious consequence before sharing a screenshot.

Three parts of the 4.1 Web UI are not covered by this page.

Voltage Calibration is a whole tab that is not mentioned at all. It is
added between Hardware Layout and Continuous Wave to match the order of
the navigation menu. The tab only appears on receivers, and only when
the Hardware Layout defines at least one voltage source, so the section
says so. The four wizard steps match the panel: High Voltage, Low
Voltage, No Voltage, Review. Values are entered in millivolts.

The Information Tab section did not describe the WiFi State row. It
reports Client with the network name, or AP mode, and adds the signal
strength in dBm where the device can measure it. The note records that
the number means different things in the two modes, since in Access
Point mode it is the RSSI of the single connected client and is absent
on ESP8285. A weak signal is a common cause of a failed firmware
upload, so that is called out.

The WiFi Tab section did not mention the control that reveals the
stored password, or the obvious consequence of using it.
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.

1 participant