Merge pull request #354 from deadbytefpv/dbExpandRxWiFi

Update Enable RX WiFi image and make expandable sections more obvious
ExpressLRS · Nov 15, 2023 · d59d230 · d59d230
2 parents 9e18431 + 807bd10
commit d59d230
Show file tree

Hide file tree

Showing 53 changed files with 220 additions and 219 deletions.
diff --git a/docs/quick-start/binding.md b/docs/quick-start/binding.md
@@ -5,7 +5,7 @@ description: Binding ExpressLRS is easy! With the Binding Phrase, no button pres
 
 ![Setup-Banner](https://raw.githubusercontent.com/ExpressLRS/ExpressLRS-Hardware/master/img/quick-start.png)
 
-??? note "Compatibility (click to expand)"
+??? note "Compatibility (click/tap to expand)"
     The first number in the Version string should match between a TX Module and a Receiver. Examples:
 
     - a TX Module with version string of 3.1.2 will sync and work with a Receiver with firmware version 3.0.1
@@ -48,7 +48,7 @@ Alternatively, you can also change the Binding Phrase via the WebUI if your devi
 
 We recommend using a **unique** phrase with at least 8 alpha-numeric characters. The best candidate is your Pilot Handle. This phrase need not be complicated or super-secret as it isn't a password or encryption key. 
 
-??? info "Is my binding phrase a secret? (click to expand)"
+??? info "Is my binding phrase a secret? (click/tap to expand)"
     No, just like what channel your VTX is on is not a secret. The binding phrase is not for security, it is for anti-collision. If everyone kept their VTX channel a secret, the chances of you blasting someone out of the sky accidentally are pretty high. To provide the best chance of not interfering with other pilots and them not interfering with you, be sure you're not using the same dumb bind phrase as someone else. Express your style and some creativity with a hilarious or saucy bind phrase.
 
 ## Traditional Binding
@@ -64,7 +64,7 @@ The Receiver LED should also be blinking when powered up.
 ![LEDSEQ_DISCONNECTED](https://cdn.discordapp.com/attachments/738450139693449258/921065812985520268/LEDSEQ_DISCONNECTED_50_50.gif)
 </figure>
 
-??? danger "Receiver LED doesn't Blink (click to expand)"
+??? danger "Receiver LED doesn't Blink (click/tap to expand)"
     Here are the things you can do if the Receiver is in Bootloader Mode:
 
     1. Check if the Boot button on the Receiver is being pressed or if it's damaged.
@@ -145,7 +145,7 @@ Using the [ExpressLRS Lua Script](transmitters/lua-howto.md), look for a `C` in
     ![Lua Loaded](../assets/images/tx-internalLuaCheck.jpg)
     </figure>
 
-??? tip "Model Mismatch (click to expand)"
+??? tip "Model Mismatch (click/tap to expand)"
     If the ExpressLRS Lua Script is showing a `C` in the top-right corner alright, but then that line disappears and is replaced with a line saying "Model Mismatch", do not worry. ExpressLRS has detected that the set Model ID in the Receiver is different from the Receiver ID set in the current Model in your Radio Model Configuration.
 
     This is also indicated by the Receiver LED as 3 fast blinks then a pause:

diff --git a/docs/quick-start/receivers/axisflying-thor.md b/docs/quick-start/receivers/axisflying-thor.md
@@ -118,7 +118,7 @@ Some of the following procedures will not go through, particularly the via Passt
     3. Plug in your UART Adapter into a USB Port on your Computer.
         - The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
 
-        ??? Warning "Receiver LED already Solid"
+        ??? Warning "Receiver LED already Solid (click/tap to expand)"
             If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
         
     4. Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
@@ -275,7 +275,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
@@ -287,7 +287,7 @@ Some of the following procedures will not go through, particularly the via Passt
             - If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
             - `expresslrs` is the Password for this Access Point.
 
-            ??? question "Where's the Access Point?"
+            ??? question "Where's the Access Point? (click/tap to expand)"
                 If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
 
                 If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
@@ -419,15 +419,15 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
 
         8. With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
             - If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
 
-            ??? tip "MDNS is not working!"
+            ??? tip "MDNS is not working! (click/tap to expand)"
                 === "The `arp` Command"
 
                     1. Open up a Command Prompt window on your computer.
@@ -525,7 +525,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
@@ -574,7 +574,7 @@ Some of the following procedures will not go through, particularly the via Passt
             </figure>
 
 [Lua Running]: ../../assets/images/lua/config-bw.png
-[Lua WiFi]: ../../assets/images/lua/wifi-bw.png
+[Lua WiFi]: ../../assets/images/lua/wifi-bw-rx.png
 [Configurator Release]: ../../assets/images/ConfiguratorRelease.png
 [Temp RX]: ../../assets/images/build-temp-rx.png
 [Flash]: ../../assets/images/BuildFlash.png

diff --git a/docs/quick-start/receivers/betafpv-superd.md b/docs/quick-start/receivers/betafpv-superd.md
@@ -107,7 +107,7 @@ Some of the following procedures will not go through, particularly the via Passt
     3. Plug in your UART Adapter into a USB Port on your Computer.
         - The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
 
-        ??? Warning "Receiver LED already Solid"
+        ??? Warning "Receiver LED already Solid (click/tap to expand)"
             If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
         
     4. Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
@@ -264,7 +264,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
@@ -276,7 +276,7 @@ Some of the following procedures will not go through, particularly the via Passt
             - If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
             - `expresslrs` is the Password for this Access Point.
 
-            ??? question "Where's the Access Point?"
+            ??? question "Where's the Access Point? (click/tap to expand)"
                 If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
 
                 If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
@@ -408,15 +408,15 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
 
         8. With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
             - If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
 
-            ??? tip "MDNS is not working!"
+            ??? tip "MDNS is not working! (click/tap to expand)"
                 === "The `arp` Command"
 
                     1. Open up a Command Prompt window on your computer.
@@ -514,7 +514,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
@@ -563,7 +563,7 @@ Some of the following procedures will not go through, particularly the via Passt
             </figure>
 
 [Lua Running]: ../../assets/images/lua/config-bw.png
-[Lua WiFi]: ../../assets/images/lua/wifi-bw.png
+[Lua WiFi]: ../../assets/images/lua/wifi-bw-rx.png
 [Configurator Release]: ../../assets/images/ConfiguratorRelease.png
 [Temp RX]: ../../assets/images/build-temp-rx.png
 [Flash]: ../../assets/images/BuildFlash.png

diff --git a/docs/quick-start/receivers/betafpv-superd900.md b/docs/quick-start/receivers/betafpv-superd900.md
@@ -107,7 +107,7 @@ Some of the following procedures will not go through, particularly the via Passt
     3. Plug in your UART Adapter into a USB Port on your Computer.
         - The LED on the Receiver should light up Solid. If it's Blinking, repeat the previous step.
 
-        ??? Warning "Receiver LED already Solid"
+        ??? Warning "Receiver LED already Solid (click/tap to expand)"
             If the Receiver LED has become Solid from a failed update, and you're reflashing through this method, you still need to do the previous step: Manually putting the receiver into Bootloader Mode. This ensures the Receiver is indeed in a Bootloader state rather than some random boot loop.
         
     4. Determine whether your UART Adapter is being detected correctly as a USB-to-UART Device.
@@ -264,7 +264,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
@@ -276,7 +276,7 @@ Some of the following procedures will not go through, particularly the via Passt
             - If your Receiver is flashed or configured with your Home WiFi SSID and Password, and can connect to that WiFi Network, then the Access Point will not appear.
             - `expresslrs` is the Password for this Access Point.
 
-            ??? question "Where's the Access Point?"
+            ??? question "Where's the Access Point? (click/tap to expand)"
                 If you cannot find the Access Point, make sure the device you're using is capable of connecting to 2.4GHz WiFi Networks. Also try putting the devices closer together.
 
                 If you still cannot find the Access Point, chances are that you have set it with your WiFi SSID and Password before, and it has connected to your WiFi Network.
@@ -408,15 +408,15 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
 
         8. With your receiver now in WiFi Mode and it was able to connect to your Local WiFi Network, open a Browser window on any WiFi-capable device that is also connected to the same Local WiFi Network. Type in the Address http://elrs_rx.local on your browser's Address Bar. The ExpressLRS Web UI should load.
             - If your browser cannot resolve this address and it cannot load the ExpressLRS Web UI, this means that MDNS is not working on your device or network.
 
-            ??? tip "MDNS is not working!"
+            ??? tip "MDNS is not working! (click/tap to expand)"
                 === "The `arp` Command"
 
                     1. Open up a Command Prompt window on your computer.
@@ -514,7 +514,7 @@ Some of the following procedures will not go through, particularly the via Passt
                     ![LEDSEQ_WIFI_UPDATE](https://cdn.discordapp.com/attachments/738450139693449258/921065813983760384/LEDSEQ_WIFI_UPDATE_2_3.gif)
                     </figure>
 
-            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode!"
+            ??? Warning "My Receiver has Solid LED and won't go into WiFi Mode! (click/tap to expand)"
                 Go back to the [Receiver Wiring] step.
                 
                 If you have previously attempted updating your receiver, there's a possibility it was soft-bricked. Go over the [Unbricking] procedure to recover it.
@@ -563,7 +563,7 @@ Some of the following procedures will not go through, particularly the via Passt
             </figure>
 
 [Lua Running]: ../../assets/images/lua/config-bw.png
-[Lua WiFi]: ../../assets/images/lua/wifi-bw.png
+[Lua WiFi]: ../../assets/images/lua/wifi-bw-rx.png
 [Configurator Release]: ../../assets/images/ConfiguratorRelease.png
 [Temp RX]: ../../assets/images/build-temp-rx.png
 [Flash]: ../../assets/images/BuildFlash.png