Missing docs for usbradio.conf

[mkmer]

Noticed we are missing docs for usbradio.conf.

Specifically, this behavior should be documented:
If we ONLY have rxctcssfreqs, all in the list will be decoded.
If we have txctcssfreqs <= rxctcssfreqs, only the number of entries in txctcssfreqs will be referenced in rxctcssfreqs. Extra rxctcssfreqs will be ignored.

We do log a warning that there is a mismatch.

I have this working now, but I found what I consider a bug. The number of tones entered in the txctcssfreqs has to match the NUMBER of tones in the rxctcssfreqs entry. In the first example below, only 100.0 will be decoded, since there is only one entry in txctcssfreq. The tones do not have to match, as expected.

ONLY THE FIRST RX TONE WILL BE DECODED

txctcssdefault = 100.0    ; Default TX CTCSS frequency, any frequency permitted
rxctcssfreqs = 100.0,91.5,94.8,103.5    ; RX CTCSS frequencies in floating point.  This list is comma delimited. Frequency must be in table.
txctcssfreqs = 100.0    ; TX CTCSS frequencies in floating point, any frequency permitted.  This list is comma delimited.  Will follow the RX CTCSS Frequency.
rxctcssoverride = 0    ; Set to 1 or yes to start out in carrier squelch mode

FOUR TONES WILL BE DECODED

txctcssdefault = 94.8      ; default TX CTCSS frequency, any frequency permitted
rxctcssfreqs = 100.0,91.5,94.8,103.5   ; RX CTCSS frequencies list in floating point. must be in table
txctcssfreqs = 94.8,94.8,94.8,94.8   ; TX CTCSS frequencies list. any frequency permitted. will follow RX CTCSS frequency
rxctcssoverride = no        ; Set to yes to start out in carrier squelch mode

[ve7fet]

Yeah, USBradio docs are on the to-do list... but it is a bigger animal to tackle than documenting simpleUSB. :)

[mkmer]

Yeah, USBradio docs are on the to-do list... but it is a bigger animal to tackle than documenting simpleUSB. :)

I figured - Really just wanted to capture the comment around CTCSS "stuff" as it's behavior was recently "fixed".