DevelopersToneModes » History » Version 3
Dan Smith, 05/07/2012 01:28 PM
| 1 | 1 | Dan Smith | h1. Tone Modes in CHIRP |
|---|---|---|---|
| 2 | |||
| 3 | 2 | Dan Smith | h2. (None) |
| 4 | 1 | Dan Smith | |
| 5 | An empty Memory.tmode means that no tone is transmitted or received |
||
| 6 | |||
| 7 | h2. Tone |
||
| 8 | |||
| 9 | A Memory.tmode of "Tone" means that the radio will transmit a single sub-audible tone, according to the Memory.rtone value. In this mode, the receiver is carrier squelch. |
||
| 10 | |||
| 11 | h2. TSQL |
||
| 12 | |||
| 13 | 3 | Dan Smith | A Memory.tmode of "TSQL" means that the radio will transmit a sub-audible tone, according to either the Memory.rtone or Memory.ctone value. In this mode, the receiver uses tone squelch with the same value as the transmitter. If the radio's feature set includes "has_ctone" (most Icom and Kenwood radios) then the value used in this case is Memory.ctone. Otherwise, use Memory.rtone. |
| 14 | 1 | Dan Smith | |
| 15 | h2. DTCS |
||
| 16 | |||
| 17 | A Memory.tmode of "DTCS" means that the radio will transmit a DCS code, according to Memory.dtcs. In this mode, the receiver uses DTCS squelch with the same value of Memory.dtcs. |
||
| 18 | |||
| 19 | h2. Cross |
||
| 20 | |||
| 21 | A Memory.tmode of "Cross" means that the radio will use an asymmetric squelch configuration according to the value of Memory.cross_mode: |
||
| 22 | |||
| 23 | h3. Tone->Tone |
||
| 24 | |||
| 25 | A cross_mode of "Tone->Tone" means the radio will use sub-audible tones for transmit and receive, the values of which are Memory.rtone and Memory.ctone respectively. |
||
| 26 | |||
| 27 | h3. Tone->DTCS |
||
| 28 | |||
| 29 | A cross mode of "Tone->DTCS" means that the radio will use a sub-audible tone for transmit, according to Memory.rtone, and a DCS code for receiver squelch, according to Memory.dtcs. |
||
| 30 | |||
| 31 | h3. DTCS->Tone |
||
| 32 | |||
| 33 | A cross mode of "DTCS->Tone" means that the radio will use a DCS code for transmit, according to Memory.dtcs, and a sub-audible tone for receiver squelch, according to Memory.ctone. |
||
| 34 | |||
| 35 | h3. ->Tone |
||
| 36 | |||
| 37 | A cross mode of "->Tone" means that the radio will not transmit a sub-audible tone, but will enable tone squelch on the receiver according to the value of Memory.ctone. |
||
| 38 | |||
| 39 | h3. ->DTCS |
||
| 40 | |||
| 41 | A cross mode of "->DTCS" means that the radio will not transmit a sub-audible tone, but will enable DCS squelch on the receiver according to the value of Memory.dtcs |
||
| 42 | 3 | Dan Smith | |
| 43 | h1. Radio Behavior |
||
| 44 | |||
| 45 | h2. Icom/Kenwood style |
||
| 46 | |||
| 47 | Most (maybe all?) Icoms and Kenwoods behave in a specific way. They store two tone values, one of which gets used in Tone mode, and the other which gets used in TSQL (CTCSS) mode. No Icom (that I'm aware of) can use the two values for separate TX and RX tones, nor can *most* Kenwoods. However, at least the Kenwood D72 can operate this way. |
||
| 48 | |||
| 49 | h2. Yaesu style |
||
| 50 | |||
| 51 | Most Yaesu radios store just a single tone value, which gets used regardless of whether or not the radio is in Tone or TSQL mode. |
||
| 52 | |||
| 53 | h3. Commercial style (Wouxun, Baofeng, etc) |
||
| 54 | |||
| 55 | These radios store separate TX and RX tones all the time (and often overload the same field for DTCS and tone values, storing a flag if the value is not to be used). These are effectively in "Cross" mode all the time, but CHIRP detects the common modes and provides the appearance of the other radios (emulating Tone, TSQL, and DTCS where possible). |