Re: [wsjt-devel] rigctld and itu_region

2020-07-24 Thread Black Michael via wsjt-devel
"If it's there...they will come"movie phrase from Field of Dreams. Manufacturers don't put out rigs by ITU anymore...now they are using self-invented country codes. This was prompted by the IC9700 which has 5 models: USA, KOR, EUR, TPE (TaiPei), ITR (Italy).   Rigs still don't have the

Re: [wsjt-devel] rigctld and itu_region

2020-07-24 Thread Claude Frantz
On 7/24/20 3:15 PM, Black Michael via wsjt-devel wrote: 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. Hi Mike,

Re: [wsjt-devel] rigctld and itu_region

2020-07-24 Thread Black Michael via wsjt-devel
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

Re: [wsjt-devel] rigctld and itu_region

2020-07-24 Thread Bill Somerville
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"

[wsjt-devel] rigctld and itu_region

2020-07-24 Thread Claude Frantz
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

Re: [wsjt-devel] Hashed Call Sign

2020-07-24 Thread Gary Rogers
OK Reino…Thanks > On Jul 24, 2020, at 12:22 AM, Reino Talarmo wrote: > > The < . . . > is somebody who don't know how special calls are supported and > wanted to make a fast QSO with you and used Tx2! He did not seem to know that > he need to respond with an un-hashed call sign that is

Re: [wsjt-devel] Hashed Call Sign

2020-07-24 Thread Reino Talarmo
The < . . . > is somebody who don't know how special calls are supported and wanted to make a fast QSO with you and used Tx2! He did not seem to know that he need to respond with an un-hashed call sign that is available in Tx1. 73, Reino OH3mA -Original Message- From: Gary Rogers