Bug #5979

split plus cross tone yields error on PX-777

Added by Chris Kantarjiev almost 2 years ago. Updated 17 days ago.

Status:Feedback Start date:07/26/2018
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Puxing PX-777+

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.)

History

Updated by Chris Kantarjiev almost 2 years ago

Err, Anytone 5888.

Updated by Bernhard Hailer 17 days ago

  • Status changed from New to Feedback
  • Target version set to chirp-daily
  • 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.

Also available in: Atom PDF