Bug #5979: split plus cross tone yields error on PX-777 - CHIRP

Actions

Copy link

Bug #5979

closed

split plus cross tone yields error on PX-777

Added by Chris Kantarjiev over 6 years ago. Updated about 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

chirp-legacy

Start date:

07/26/2018

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

Puxing PX-777+

Platform:

Windows

Debug Log:

I read the instructions above:

Description

The PX-777 is happy to support odd splits and cross tone, but the chirp driver rejects such channel definitions when reading from a CSV file.

For example:
Location,Name,Frequency,Duplex,Offset,Tone,rToneFreq,cToneFreq,DtcsCode,DtcsPolarity,Mode,Tstep,Skip,Comment
21,VTC37R,154.4525,split,158.7375,Cross,156.7,136.5,23,NN,NFM,5 KHz,,cross tone

This seems to work fine for the Anytone 588.

(Side note: it would be really useful if the CSV format were documented - especially the column names, which don't match the UI.)

Actions

Copy link

Updated by Chris Kantarjiev over 6 years ago

Err, Anytone 5888.

Actions

Copy link

Updated by Bernhard Hailer over 4 years ago

Status changed from New to Feedback
Target version set to chirp-legacy
Chirp Version changed from 0.4.0 to daily

(Side note: it would be really useful if the CSV format were documented - especially the column names, which don't match the UI.)
Actually it is documented, see here: CSV HowTo.
And I think, you might find the key to your problem in this document; I suspect your CSV isn't formatted correctly.

Actions

Copy link