Hello!
One of fldigi's options to control the transceiver is to use the program
"flrig". Especially with the new version 3.22.*, the tendency to use
this option becomes stronger because of the new S-meter function.
The communication between fldigi and flrig occurs via XMLRPC.
Although flrig is
Hi All,
this night I am surprised from call on 80m from Philippines
on screen:
2236 -3 -1.3 1379 # CQ DX I ~Philippines
It is possible to check if there is almost 3 characters and not OOO RRR
The some also for "Look up" button that with no entry return first
locator in CALL3.TXT
Than in adv
Hello All,
* Bill ( G4WJS ) has recently updated his public release of Hamlib3. As
such, I've re-built the version being used by JTSDK-QT and added it to
the WSJT repository.
* I've also updated the MSYS build script to allow building both Static
( default ) and Shared versions for testing.
See
Hello all,
When switching between different bands to check for activity, I soon loose
track of which time period / set of decodes belong to which band.
Maybe it would be possible to add the band concerned to the end of the
optional line between decodes in some future release?
73,
Ton PA0TBR
On Thu,11/13/2014 9:36 AM, Edson W. R. Pereira wrote:
> Besides the issue on 80m, we may also encounter the same in 40m where
> digital modes are now allocated in the 7040~7053 kHz segment.
That's going to run into considerable opposition from CW operators who
regularly occupy this range for con
On 13/11/2014 17:33, Michael Black wrote:
Hi Mike,
> I work 80M most every night.4 states shy of WAS on JT65, 25 states shy
> of WAS on JT9. Only 4 countries though (compared to 62 countries on 10m and
> 15m).
> I've never seen any other modes show up in the 3.576+3.5kHz band while I was
> ope
GM Team,
Living a few miles from the Pacific, I'm equally challenged with respect
to knowing current usage on 80 between EU and the east coast, but I
think it is QUITE critical that we get a good handle on it before
proceeding. I don't use JT65 or JT9 on 80, and the only times I get into
that
Hello Joe,
The IARU has recently released new bandplans and a lot of though has been
put into them in order to attempt consolidation between all three regions
as much as possible. I think it would be good for us if the JT modes
activity would happen in the proposed segments. Besides the issue on 8
I work 80M most every night.4 states shy of WAS on JT65, 25 states shy
of WAS on JT9. Only 4 countries though (compared to 62 countries on 10m and
15m).
I've never seen any other modes show up in the 3.576+3.5kHz band while I was
operating so I'm under the impression we aren't interfering with
On 13/11/2014 16:36, Joe Taylor wrote:
> Hi all,
Hi Joe,
>
> I have been advised that the default 80-meter frequency compiled into
> WSJT-X, 3.576 MHz, is not compliant with the current IARU recommendation
> for region 1 and 2. Frequencies 3.580 or 3.586 MHz were suggested as
> possible alternativ
Hi all,
I have been advised that the default 80-meter frequency compiled into
WSJT-X, 3.576 MHz, is not compliant with the current IARU recommendation
for region 1 and 2. Frequencies 3.580 or 3.586 MHz were suggested as
possible alternatives.
Comments on this possible change would be apprecia
Joe Taylor writes:
> Hi Greg,
>
> N1DAM wrote:
>> ...
>> Thanks for the explanation. It would be good to have that be readily
>> understandable by someone starting at the web site and trying to
>> understand everything. Perhaps the "now go install kvasd" section could
>> turn into an "optional
Hi Greg,
N1DAM wrote:
> ...
> Thanks for the explanation. It would be good to have that be readily
> understandable by someone starting at the web site and trying to
> understand everything. Perhaps the "now go install kvasd" section could
> turn into an "optional/recommended" section, with that
On 13/11/2014 13:29, Bill Somerville wrote:
> You may ask why the normal WSJT-X build script does do this all already.
but he really meant to write:
"You may ask why the normal WSJT-X build script doesn't do this already."
Sorry
73
Bill
G4WJS.
On 13/11/2014 13:00, Greg Troxel wrote:
Hi Greg,
> Bill Somerville writes:
>
>> OK, hopefully the WSJT-X superbuild project mentioned previously will
>> help you with that as it aims to provide a "proper" upstream source
>> tarball that will build on any *nix system. There are some restrictions
Bill Somerville writes:
> OK, hopefully the WSJT-X superbuild project mentioned previously will
> help you with that as it aims to provide a "proper" upstream source
> tarball that will build on any *nix system. There are some restrictions
> in that it requires Qt 5 at least, other than that
Joe Taylor writes:
> N1DAM wrote:
>> How bad is it for someone to choose not to use KVASD? Does it cost them
>> decode performance, or CPU time, or both? Or is it really not a
>> feasible choice? The documentation I've found doesn't address this; it
>> just says "go get this non-free code, w
Hi Joe
Many thanks.
73
Nick G3VNC
On 12/11/14 19:59, Joe Taylor wrote:
> Hi Nick and all,
>
> Apologies for this slow response to your query. The simple answer is
> that the decoder does its work in order of increasing frequency,
> starting at the left edge of your waterfall display. If your
18 matches
Mail list logo
