Thanks Jim
 
My issue with this approach is that I support a large group of HAM radio operators that want to keep the "image" in sync with all of their radio's which cover multple, versions, models, and makes of radios (over 200 HAMs) where the CSV file is the common denominator for all of them.  Unfortunately, an image file is unique for each radio.
 
The only work around I have then is to import the CSV and manually repair the entry for every radio programmed.... what would normally take less than 60 seconds per radio to several minutes.
 
Don
 
 
Sent: Tuesday, April 28, 2020 at 5:43 PM
From: "Jim Unroe" <rock.unroe@gmail.com>
To: "Discussion of CHIRP" <chirp_users@intrepid.danplanet.com>
Subject: Re: [chirp_users] Import/Export and CROSS
On Tue, Apr 28, 2020 at 5:10 PM Don Goodrich <don.goodrich@cheerful.com> wrote:
>
> I have an entry in a Chirp Image that uses DCS in a particular memory location addressing a repeater. The DCS code for transmit and receive are different so the Tone mode is CROSS DTCS->DTCS. When I export to a CSV file, the Receive code is not shown in the CSV file and when I attempt to import using this file the Tone mode in the entry comes back as TSQL rather than CROSS and only the transmit DCS code is shown, no receive code. What am I doing wrong?
>
> Don

Hi Don,

You are not doing anything wrong. CSV files only support a single
DtcsCode. They also don't have a column to support Cross Mode
settings.

So instead save it as a native CHIRP Radio Images (*.ing) file to
retain the asymmetrical Dtcs codes.

Jim KC9HI
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Don Goodrich at don.goodrich@cheerful.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com