I've been looking for somebody who cares about the itu_region stuff.
Claude -- why are you using that parameter? It really doesn't do anything. I
know some are using frequency ranges but nobody using the itu_region option.
Mike W9MDB
On Friday, July 24, 2020, 07:54:30 AM CDT, Bill Somerville
<[email protected]> wrote:
On 24/07/2020 13:37, Claude Frantz wrote:
> Hi Mike, Bill and all,
>
> In the past, I was able to start with:
>
> /usr/local/rigctld -m129 -s4800 -r/dev/ttyUSB0 --dcd-type=RIG
> --setconf=timeout=500,retry=2,write_delay=5,post_write_delay=50,itu_region=1
>
>
> When using the new hamlib, the "itu_region=1" is not more accepted. Of
> course, "-m129" must be changed. What is the reason of the rejection
> of this argument ?
>
> Best wishes,
> Claude (DJ0OT)
Hi Claude,
that configuration option has been removed, perhaps temporarily. Here's
a comment added to the sources that explains the situation:
// we need to be able to figure out what model radio we have
// before we can set up the rig_state with the rig's specific freq range
// if we can't figure out what model rig we have this is impossible
// so we will likely have to make this a parameter the user provides
// or eliminate this logic entirely and make specific RIG_MODEL entries
https://github.com/Hamlib/Hamlib/commit/c40ff7fce6a138424267b91384ddb24b696efed5
I don't know why this change has to be a breaking change, I would have
though a warning message that pointed out that the option is now ignored
would have been more friendly.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
