deploy: 9b5541a44d

cli_commands/index.html

@@ -5626,10 +5626,17 @@ minimum and return to it exactly when it is safe.</p>
 - <code>get tx</code>
 - <code>set tx &lt;dbm&gt;</code></p>
 <p><strong>Parameters:</strong>
-- <code>dbm</code>: Power level in dBm (1-22)</p>
+- <code>dbm</code>: Requested radio-chip power in dBm. The valid range depends on the
+  radio family, selected PA path, and any board-specific external-PA limit.</p>
 <p><strong>Set by build flag:</strong> <code>LORA_TX_POWER</code></p>
 <p><strong>Default:</strong> Varies by board</p>
 <p><strong>Notes:</strong> This setting only controls the power level of the LoRa chip. Some nodes have an additional power amplifier stage which increases the total output. Refer to the node's manual for the correct setting to use. <strong>Setting a value too high may violate the laws in your country.</strong></p>
+<p>The command strictly rejects malformed values and saves the new preference
+only after the active radio driver accepts it. On LR2021, the chip range is
+<code>-9</code> to <code>22</code> dBm below 1500 MHz and <code>-19</code> to <code>12</code> dBm above 1500 MHz. A lower
+board-specific external-PA limit still takes precedence. A saved profile is
+clamped to the applicable limit when its frequency changes; temporary radio
+settings use a safe effective power without replacing the saved preference.</p>
 <hr />
 <h4 id="change-the-radio-parameters-for-a-set-duration">Change the radio parameters for a set duration</h4>
 <p><strong>Usage:</strong> 

faq/index.html

@@ -793,6 +793,45 @@
     </span>
   </a>
   
+    <nav class="md-nav" aria-label="3.7. Q: My repeater may be suffering from deafness due to high power interference near my mesh&#39;s frequency, it is not hearing other in-range MeshCore radios. What can I do?">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#371-q-can-firmware-recover-an-external-radio-whose-busy-pin-is-stuck-high" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        3.7.1. Q: Can firmware recover an external radio whose BUSY pin is stuck high?
+      
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#372-q-does-firmware-automatically-update-lr1110-transceiver-firmware" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        3.7.2. Q: Does firmware automatically update LR1110 transceiver firmware?
+      
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#373-q-how-does-firmware-handle-lr2021-lowhigh-band-changes" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        3.7.3. Q: How does firmware handle LR2021 low/high-band changes?
+      
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
           <li class="md-nav__item">
@@ -2420,6 +2459,45 @@
     </span>
   </a>
   
+    <nav class="md-nav" aria-label="3.7. Q: My repeater may be suffering from deafness due to high power interference near my mesh&#39;s frequency, it is not hearing other in-range MeshCore radios. What can I do?">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#371-q-can-firmware-recover-an-external-radio-whose-busy-pin-is-stuck-high" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        3.7.1. Q: Can firmware recover an external radio whose BUSY pin is stuck high?
+      
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#372-q-does-firmware-automatically-update-lr1110-transceiver-firmware" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        3.7.2. Q: Does firmware automatically update LR1110 transceiver firmware?
+      
+    </span>
+  </a>
+  
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#373-q-how-does-firmware-handle-lr2021-lowhigh-band-changes" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        3.7.3. Q: How does firmware handle LR2021 low/high-band changes?
+      
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
         
           <li class="md-nav__item">
@@ -3375,6 +3453,51 @@ Advert means to advertise yourself on the network. In Reticulum terms it would b
 transmitted. When safe, <code>RadioLibWrapper::resetAGC()</code> warm-sleeps the radio,
 returns the wrapper to idle so receive mode is re-armed, reapplies the cached RX
 boost setting, and starts a fresh noise-floor calibration.</p>
+<h4 id="371-q-can-firmware-recover-an-external-radio-whose-busy-pin-is-stuck-high">3.7.1. Q: Can firmware recover an external radio whose BUSY pin is stuck high?</h4>
+<p><strong>A:</strong> Current firmware first attempts a non-destructive RX/AGC re-arm and then
+uses a physical radio reset when the board exposes one. A normal RadioLib
+reinitialization is not reported as a hard reset unless firmware can actually
+pulse NRST or cycle the radio's power rail.</p>
+<p>Most supported external-radio boards expose NRST directly. RAK3401 pulses its
+dedicated NRST while leaving the shared peripheral rail and SPI controller
+intact, and LilyGo T-Beam 1W can cycle the radio regulator. The generic Tenstar
+C3 target describes a user-wired radio and has no reset connection by default.
+For unattended recovery on that target, wire NRST to a free GPIO and override
+<code>P_LORA_RESET</code> with that GPIO in the build configuration.</p>
+<p>The SenseCAP T1000-E LR1110 path was hardware-qualified with 50 successful
+radio-only resets: 25 in continuous receive and 25 with RX power saving active.
+The saved radio tuple, TX power, RX gain, and RX power-saving configuration were
+restored after every reset, bidirectional LoRa status traffic still passed, and
+the nRF52840 uptime remained continuous.</p>
+<p>An integrated STM32WL radio has no independently resettable RF peripheral, so
+it intentionally remains on the bounded soft-recovery path. If its radio core
+cannot recover, resetting only the radio is electrically impossible; the MCU
+must be restarted.</p>
+<h4 id="372-q-does-firmware-automatically-update-lr1110-transceiver-firmware">3.7.2. Q: Does firmware automatically update LR1110 transceiver firmware?</h4>
+<p><strong>A:</strong> No. A transceiver update erases and rewrites the LR1110 itself, so it is
+not performed as a side effect of installing ordinary device firmware. Use the
+hardware vendor's physical-access maintenance procedure and verify the exact
+LR1110 and bootloader versions before changing them.</p>
+<p>Full remediation of
+<a href="https://www.semtech.com/company/security/security-bulletins/sem-psa-2026-001">Semtech SEM-PSA-2026-001</a>
+requires LR1110 BL2 0x1001 as well as the applicable transceiver firmware. It
+is a separate two-stage maintenance procedure and is not performed
+automatically by MeshCore.</p>
+<h4 id="373-q-how-does-firmware-handle-lr2021-lowhigh-band-changes">3.7.3. Q: How does firmware handle LR2021 low/high-band changes?</h4>
+<p><strong>A:</strong> Firmware first selects the board's matching RF path, retunes the radio,
+and then reapplies output power so the LR2021 selects the correct low- or
+high-frequency PA. It also uses the matching RF-switch mode when RX or TX is
+launched. LR2021 high-band output power is limited to 12 dBm; a lower
+board-specific limit still takes precedence.</p>
+<p>On Meshnology W12, the two external FEM supplies are mutually exclusive:
+GPIO4 powers the sub-GHz GC1109 path and GPIO3 powers the 2.4 GHz RFX2402E
+path. Both supplies are disabled before the selected one is enabled. Temporary
+radio settings preserve the saved TX power and safely clamp only the active
+band; returning to the saved settings restores its applicable power. A
+permanent frequency change clamps the saved TX power to the new band's limit.</p>
+<p>The external SX1262, SX1268, LLCC68, LR1110, and LR2021 drivers also bound the
+post-SetTx BUSY wait. A failed PA ramp therefore returns an error and can enter
+the physical-reset recovery path instead of hanging the node indefinitely.</p>
 <h3 id="38-q-how-do-i-make-my-repeater-an-observer-on-the-mesh">3.8. Q: How do I make my repeater an observer on the mesh?</h3>
 <p><strong>A:</strong> The observer instruction is available here: <a href="https://analyzer.letsmesh.net/observer/onboard">https://analyzer.letsmesh.net/observer/onboard</a></p>
 <h3 id="39-q-what-is-multibyte-support-what-do-1-byte-2-byte-3-byte-adverts-and-messages-mean">3.9. Q: What is multibyte support? What do 1-byte, 2-byte, 3-byte adverts and messages mean?</h3>

terminal_chat_cli/index.html

@@ -1323,7 +1323,9 @@ opening that port from an app.</p>
 <p>Set the LoRa frequency. Example:  set freq 915.8</p>
 <pre><code>set tx {tx-power-dbm}
 </code></pre>
-<p>Sets LoRa transmit power in dBm.</p>
+<p>Sets LoRa-chip transmit power in dBm. The firmware rejects values outside the
+radio/board limit; external-PA boards can have a lower input-power ceiling than
+the radio chip itself.</p>
 <pre><code>set name {name}
 </code></pre>
 <p>Sets your advertisement name.</p>