First let's install a new Hamlib -- then if that doesn't fix things we'll go to
the debug stage...
New hamlib for installation directions
#1 Shut down WSJTX
#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of
WSJTX -- hopefully your browser doesn't block it but may w
On 26/12/2019 17:40, DX Jami via wsjt-devel wrote:
My point is WSJT-X should allow "non-standard" call signs.
Danny,
WSJT-X goes to a lot of trouble to support "non-standard" callsigns, but
there is no free lunch. The non-standard callsigns supported by WSJT-X
in MSK144, FT4, and FT8 modes a
Thanks Saku. I understand the work-around and use various versions myself.
My point is WSJT-X should allow "non-standard" call signs. Those non-standard
calls are only non-standard for WSJT-X and A-OK for the rest of the ham radio
world. Many DXpeditions have similar problems as does almost
DX Jami via wsjt-devel kirjoitti 24.12.2019 klo 15.26:
Another shortfall with non-standard calls is signing like me -
W4/AH6FX. The "real estate" shortfall does not allow passing my grid,
so that is very bothersome to some folks.
Hi!
There is a good practice for this used by F5MYK/MM. For ev
Zoli,
That is a shortfall within WSJT-X. There is not enough "real estate" in the
programming framework to allow two non-standard call signs to trade exchanges.
Another shortfall with non-standard calls is signing like me - W4/AH6FX. The
"real estate" shortfall does not allow passing my grid
Thank you all for the response!
Shouldn’t there be a way to not let one user with a special call-sign call
someone else with the same type of call-sign.
I had to wait for quite a while for someone to let go trying and continue
working as he was locking me by calling me.
All the best!Zoli
Sent
Zoli!
You got a nice work-around for working non-standard call signs. The Users Guide
states in clause 7.5 Except for the special cases involving /P or /R used in
VHF contesting, WSJT-X 2.1 offers no support for two nonstandard callsigns to
work each other.
Good luck and 73, Reino oh3mA
Two non standard calls can not work each other.
On Dec 23, 2019 9:14 AM, Zoltan Vodinszki via wsjt-devel
wrote:
Hi,
These days I am working with a special call sign (YP3XMAS).
During my work, I have observed a strange behavior when two special call-signs
try to work each other or when a specia
Zoli!
Use free text and give his call sign and report
73 Keijo OG55W
From: Zoltan Vodinszki via wsjt-devel
Sent: Monday, December 23, 2019 4:14 PM
To: wsjt-devel@lists.sourceforge.net
Cc: Zoltan Vodinszki
Subject: [wsjt-devel] WSJT-X bug report
Hi,
These days I am working with a special call
Thanks Joe
All OK now with r5690 and does now give decodes with G bin-width.
Rex VK7MO
On 7/07/2015 3:57 AM, Joe Taylor wrote:
> Hi Rex and Charlie,
>
> Thanks for your help in identifying the bug in decoding submode JT4G
> with MinW=G. I believe it has been fixed in revision 5690.
>
>
Hi Rex and Charlie,
Thanks for your help in identifying the bug in decoding submode JT4G
with MinW=G. I believe it has been fixed in revision 5690.
-- Joe
On 7/6/2015 10:41 AM, char...@sucklingfamily.free-online.co.uk wrote:
> Hi Joe
>
> Rex is probably in bed now.
>
> You don't need a
Hi Joe
Rex is probably in bed now.
You don't need a specific file to demonstrate this bug - simply set MinW
to G and submode to G.
Here's an example I just did:
2146-125-0.69 599 *
2146 -8 3.40 801 * DL0SHF 46HID * F
2146-125-0.69 599 *
line 1 and line 3 with MinW at G, line 2 wi
Hi Rex,
Thanks for catching and reporting this bug. I'm not presently at a
location where it's convenient to generate test files. Could you send
me one or two example files that contain signals with suitable S/N and
spread that should be decodable in the "G" submode?
-- Joe, K1JT
On
13 matches
Mail list logo
