From cb8c31b025d5b2ffff488d90d2291dd6a8672d1a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20Pyykk=C3=B6?= Date: Mon, 25 Mar 2019 10:47:27 +0200 Subject: [PATCH] Updated docs to have correct command for binding --- docs/FrSky SPI RX.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/FrSky SPI RX.md b/docs/FrSky SPI RX.md index 29d035b8b..8334a98c3 100644 --- a/docs/FrSky SPI RX.md +++ b/docs/FrSky SPI RX.md @@ -53,7 +53,7 @@ The supported protocols are: 3. click 'Save & Reboot'. After the reboot, the RX LED will confirm that the FrSky RX is active by blinking slowly; 4. enter bind mode by either: - pressing the 'Bind' button on the flight controller (if there is one and it's reachable); -- entering CLI, and typing 'frsky_bind[Enter]'. +- entering CLI, and typing 'bind_rx_spi[Enter]'. 5. the flight controller will indicate that bind mode is active by changing the RX LED to be permanently on. Now, on your TX, enter bind mode for the selected FrSky protocol (see screenshots for OpenTX): FrSky D protocol: @@ -64,7 +64,7 @@ FrSky X and X_LBT protocol: ![FrSky SPI RX FrSky X binding with OpenTX](assets/images/frsky_spi_rx_x_binding.png) -6. Once binding has completed, the flight controller will indicate this by blinking the RX LED slowly. A reboot of the flight controller is not required. +6. Once binding has completed, the flight controller will indicate this by blinking the RX LED slowly. There's no indication on the CLI, but you can also observe successful binding by taking a diff and seeing new parameter values. A reboot of the flight controller is not required. ## Tips & Tricks