gomaomao/DIY-Multiprotocol-TX-Module
1
0
Fork 0
mirror of https://github.com/pascallanger/DIY-Multiprotocol-TX-Module.git synced 2025-02-04 17:48:11 +00:00
Code Issues Projects Releases Wiki Activity

Frequency tuning page

Browse Source
This commit is contained in:
Pascal Langer 2018-01-02 22:08:22 +01:00
parent bef562964d
commit d70d8f62a4
3 changed files with 40 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
Protocols_Details.md
View File

@ -142,11 +142,8 @@ Models: FrSky receivers V8R4, V8R7 and V8FR.
Extended limits supported
Option for this protocol is fine frequency tuning. This value is different for each Module. To determine this value:
- find a value where the RX accepts to bind. A good start is to use one of these values -40, 0 and 40.
- find the values min/max where the RX loses connection. In serial mode you can change the value and see the effect live.
- set the value to half way between min and max.
- [video showing the process](https://youtu.be/C483uNWwAaM)
Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and **must** be accurate otherwise the link will not be stable.
Check the [Frequency Tuning page](/docs/Frequency_Tuning.md) to determine it.
CH1|CH2|CH3|CH4
---|---|---|---
@ -159,11 +156,8 @@ Extended limits supported
Telemetry enabled for A0, A1, RSSI, TSSI and Hub
Option for this protocol is fine frequency tuning. This value is different for each Module. To determine this value:
- find a value where the RX accepts to bind. A good start is to use one of these values -40, 0 and 40.
- find the values min/max where the RX loses connection. In serial mode you can change the value and see the effect live.
- set the value to half way between min and max.
- [video showing the process](https://youtu.be/C483uNWwAaM)
Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and **must** be accurate otherwise the link will not be stable.
Check the [Frequency Tuning page](/docs/Frequency_Tuning.md) to determine it.
CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8
---|---|---|---|---|---|---|---
@ -176,11 +170,8 @@ Extended limits and failsafe supported
Telemetry enabled for A1 (RxBatt), A2, RSSI, TSSI and Hub
Option for this protocol is fine frequency tuning. This value is different for each Module. To determine this value:
- find a value where the RX accepts to bind. A good start is to use one of these values -40, 0 and 40.
- find the values min/max where the RX loses connection. In serial mode you can change the value and see the effect live.
- set the value to half way between min and max.
- [video showing the process](https://youtu.be/C483uNWwAaM)
Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and **must** be accurate otherwise the link will not be stable.
Check the [Frequency Tuning page](/docs/Frequency_Tuning.md) to determine it.
### Sub_protocol CH_16 - *0*
FCC protocol 16 channels @18ms.
@ -215,17 +206,40 @@ Models: Futaba RXs and XK models.
Extended limits and failsafe supported
Option for this protocol is fine frequency tuning. This value is different for each Module. To determine this value:
- find a value where the RX accepts to bind. A good start is to use one of these values -40, 0 and 40.
- find the values min/max where the RX loses connection. In serial mode you can change the value and see the effect live.
- set the value to half way between min and max.
- [video showing the process](https://youtu.be/C483uNWwAaM)
Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and **must** be accurate otherwise the link will not be stable.
Check the [Frequency Tuning page](/docs/Frequency_Tuning.md) to determine it.
CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8
---|---|---|---|---|---|---|---
A|E|T|R|CH5|CH6|CH7|CH8
Channels 9 to 16 are used as failsafe values for the channels 1 to 8.
## CORONA - *37*
Models: Corona 2.4GHz FSS and DSSS receivers.
Extended limits supported
Option for this protocol corresponds to fine frequency tuning. This value is different for each Module and **must** be accurate otherwise the link will not be stable.
Check the [Frequency Tuning page](/docs/Frequency_Tuning.md) to determine it.
CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8
---|---|---|---|---|---|---|---
CH1|CH2|CH3|CH4|CH5|CH6|CH7|CH8
### Sub_protocol COR_V1 - *0*
Corona FSS V1 RXs
### Sub_protocol COR_V2 - *1*
Corona DSSS V2 RXs: CR8D, CR6D and CR4D
To bind V2 RXs you must follow the below procedure (original):
- press the bind button and power on the RX
- launch a bind from Multi -> the RX will blink 2 times
- turn off the RX **and** TX(=Multi)
- turn on the RX **first**
- turn on the TX(=Multi) **second**
- wait for the bind to complete -> the RX will flash, stop and finally fix
- wait some time (more than 30 sec) before turning off the RX
- turn off/on the RX and test that it can reconnect instantly, if not repeat the bind procedure
***
# CYRF6936 RF Module

6
docs/Frequency_Tuning.md
View File

@ -6,11 +6,12 @@ The protocols which require frequency tuning are:
* **FrSkyV** (e.g. FrSky V8R4, V8R7 and V8FR receivers)
* **FrSkyX** (e.g. FrSky X4R, X6R, X8R, and XSR receivers)
* **S-FHSS** (e.g. Futaba S-FHSS receivers)
* **Corona** (e.g. Corona V1 FSS and Corona V2 DSSS CR8D/CR6D/CR4D receivers)
There is a [video](#video) at the end of this page which gives an example of the tuning process.
## More information
Original FrSky and Futaba receivers have been frequency-tuned by the manufacturer at the factory. Because of variations in the oscillator crystals used in multiprotocol modules it is necessary to fine-tune the module to match the manufacturer frequencies.
Original FrSky, Futaba and Corona receivers have been frequency-tuned by the manufacturer at the factory. Because of variations in the oscillator crystals used in multiprotocol modules it is necessary to fine-tune the module to match the manufacturer frequencies.
'Compatible' receivers suffer the same variation in crystal oscillators as multiprotocol modules, but have to be compatible with genuine (manufacturer-tuned) transmitters so they will typically have auto-tuning built in, and will self-tune to the radio's frequency when they are bound.
@ -60,7 +61,7 @@ These settings can also be used to force different tuning values for different m
/*******************************/
/*** CC2500 FREQUENCY TUNING ***/
/*******************************/
//For optimal performance the CC2500 RF module used by the FrSkyD, FrSkyV, FrSkyX, and SFHSS protocols needs to be tuned for each protocol.
//For optimal performance the CC2500 RF module used by the FrSkyD, FrSkyV, FrSkyX, SFHSS and CORONA protocols needs to be tuned for each protocol.
//Initial tuning should be done via the radio menu with a genuine FrSky or Futaba receiver.
//Once a good tuning value is found it can be set here and will override the radio's 'option' setting for all existing and new models which use that protocol.
//Valid range is -127 to +127
@ -69,6 +70,7 @@ These settings can also be used to force different tuning values for different m
//#define FORCE_FRSKYV_TUNING 0
//#define FORCE_FRSKYX_TUNING 0
//#define FORCE_SFHSS_TUNING 0
//#define FORCE_CORONA_TUNING 0
```
## Video

7
docs/Troubleshooting.md
View File

@ -46,12 +46,7 @@ If your module is always/sometime binding at power up without pressing the butto
- check that your module case is not pressing the bind button.
FrSky & SFHSS bind issues, heratic moves and telemetry losses are ususally due to Option=fine frequency tuning not set properly. This value is different for each RF module and some RXs. To determine this value:
- find a value where the RX accepts to bind. A good start is to use one of these values -40, 0 and 40.
- find the values min/max where the RX loses connection. In serial mode you can change the value and see the effect live.
- set the value to half way between min and max ( (min+max)/2 ).
Note: it's better to use a genuine RX to find the real RF module frequency tuning value for a given protocol. After that you should apply the same value for the all other RXs of that protocol and rebind them if they were already bound. This is because most of the none genuine RXs are doing an auto frequency tuning at bind time to compensate for frequency deviation. If you change the frequency tuning of the transmitter then the RX has to relearn it.
FrSky & SFHSS & Corona bind issues, heratic moves and telemetry losses are ususally due to Option=fine frequency tuning not set properly. This value is different for each RF module and some RXs. To determine this value check this [Frequency Tuning page](/docs/Frequency_Tuning.md).
## Report issues