Hi everyone,
Making progress on the IC-R6 driver - https://chirpmyradio.com/issues/2795
Figured out some of the the frequency mappings thanks to the mention of
6.25k steps in Rich Cochran AG6QR's R2 code. The radio is jumping
between 5k, 6.25k and 9kHz multipliers (so that 9th steps of 5kHz jumps
that is out of sequence is coded as a multiple of 9kHz, not 5kHz and the
pattern therefore repeats every 45kHz). Rest should be fairly easy now
the pattern is obvious.
Back to frequencies and steps... two queries:
Dave provided an ICF on 2795 I'm seeing an "Auto" TS option in CS-R6 for
the channel memories (value 14).
Chirp doesn't seem to like that. When I enter a frequency it's changing
TS from "Auto" to "5" - which is index 0 of my STEPS list). I can set
the TS back to "Auto" manually as it's my STEPS list.
Is there a way to allow "Auto" TS in Chirp? Or let me set it based on
entered frequency? Or block it from the GUI but allow it to be read from
the radio/ICF? Looks like Chirp is coded for floats only (some %.2f seen).
Also CS-R6 rounds frequencies to the nearest valid value (based on TS -
but if it's "Auto" it's more generous - for example will accept valid
multiples of 6.25kHz as well as 5, 10, ...).
I quite like that approach rather than rejecting the entered frequency.
My frequency mapping coded isn't written yet so haven't tried a CSV
import with invalid values but wondering if Chirp has a switch to enable
frequency rounding?
Need to add more validation in the IC-R6 driver (radio only accepts 9kHz
TS over a small AM broadcast range) but not up to playing with the core
code... prefer to get the frequency coding done and raise a pull request.
The driver should be 90% done at that point (some bank channels and and
a GUI for the device settings still needing written) but good enough for
beta testing.
Should I force TS to a numeric value on reading/opening and also accept
that Chirp is designed to reject invalid frequencies rather than round
to nearest valid one?
Thanks.
John.
