Bug #10682
closed
Added by Will G over 1 year ago.
Updated over 1 year ago.
Model affected:
Yaesu VX-6R
I read the instructions above:
Description
When setting DCS as "SQL TYP" in the VX-6R through Chirp, the VX-6R incorrectly identifies the set code as "RV TN." Setting "DCS" through the VX-6R menus itself works fine.
Can you capture a .img
of the radio with the value set to DCS via chirp, then fix it in the radio and capture another .img
and attach both here?
Hi Dan,
Sorry for not including it earlier - I was under a time crunch and wanted to at least track the issue.
After some further investigation... I'm not really sure what's going on, and need to investigate further. I would recommend closing this issue for now until I can really find out what's happening, and if CHIRP was a factor at all.
DCS seems to be mapping to DCS now (I'm certain sure it was mapping to RV TN earlier, but I've been wrong before :) ). DCS also seems to have some strange behavior in the VX-6R.
In regards to DCS codes with assorted radios I have:
Yaesu <-> Yaesu works fine (VX-6R <-> FT-4XR)
Wouxun <-> Wouxun works fine
Motorola <-> Wouxun works fine
Motorola <-> Yaesu works fine
Wouxun -> Yaesu works fine
FT-4XR -> Wouxun works fine
VX-6R -> Wouxun does not work
So it looks like either the decoder on the Wouxun or the encoder on the VX-6R is problematic. I might be able to do some further investigation with an RTL-SDR, but it's out of scope for CHIRP. I was initially using a Wouxun radio to test my setup.
- Status changed from New to Not a bug
Hmm, seems weird as I would expect that to be a pretty widely-known issue. But I don't have one to test with so I can't say for sure.
Anyway, I'll close this and we can re-open if you figure something out.
Also available in: Atom
PDF