[chirp_users] Thoughts after looking at the most recent build
dsmith at danplanet.com
Tue Aug 9 06:45:59 PDT 2011
> 1. Why did you delete the Name field? I would find this very helpful for
> organizing and editing the data in my .CVS file. From our previous email
> conversation, I understood you were going to retain it in the CSV file
> and only drop it when writing data to the dual_band.dat file for
> uploading into the radio?
The UV-3R doesn't support names, so that column shouldn't be displayed
when editing such a file. It's still supported in CSV, of course.
> 2. Vero/Baofeng uses one "menu" for manually setting the Tx-Code
> (transmitted CTSS or DTCCS code) and a second "menu" for manually
> setting the Rx-Code (received or SQL tone code, either CTSS or DTCCS).
Yes, but almost all ham radios only support one code (for TX and RX) at
a time. CHIRP was designed with this in mind and thus adding support for
a split code is non-trivial.
> 2. Is a repeater operator precluded from selecting different CTSS or
> DTCCS codes for Rx and Tx?
Yes, at the moment.
> 3. Is a repeater operator precluded from selecting CTSS for the user's
> Tx Code and DTCCS for the user's Rx Code (or vice versa)?
At the moment, yes. Some of the Ham radios support a "cross mode" that
lets them use CT and DT for RX and TX (or vice versa). I can see about
enabling the UV-3R driver for that if it's important to you.
> 3. Can an operator set a repeater up to use DTCCS on what it receives
> (the user's Tx Code) and transmit without a code?
> I don't see where the UV-3R uses the DTCS Polarity information at all;
> it does not appear to be an option as I read my .dat file.
Yes, it can. When you're entering a DTCS code on the front panel, press
the menu button and it will change from N (normal) to I (inverted).
More information about the chirp_users