Hi all,
I have a small patch for WSJT-X which I think would also be useful for
other users and would like to see it added in the mainstream.
The patch puts the band info in the last n characters of the separator line
in the decodes windows, like:
-10m
0900 -8
Yes it does. That's not the same as selecting it though.
Can probably be emulated through swapping VFOs if needed...so check if VFO
wanted is current vfo, swap if needed, then swap back if needed.
Mike W9MDB
-Original Message-
From: Dave AA6YQ [mailto:aa...@ambersoft.com]
Sent: Sunday,
Hi Bill,
Thanks for tackling this question and offering what looks like a good
solution. I hope it will shake out well in testing.
-- Joe, K1JT
--
Dive into the World of Parallel Programming The Go Parallel Web
Hi Bill,
Thanks for tackling this question and offering what looks like a good
solution. I hope it will shake out well in testing.
-- Joe, K1JT
--
Dive into the World of Parallel Programming The Go Parallel Web
Thanks!
73,
Dave, AA6YQ
-Original Message-
From: Michael Black [mailto:mdblac...@yahoo.com]
Sent: Monday, March 02, 2015 8:12 AM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] Yaesu FT-991 CAT Codes released
Yes it does. That's not the same as selecting it
On 28/02/2015 23:53, Bill Somerville wrote:
Hi All,
Hi All again,
I got the attached e-mail from Mel KD7DCR and I wonder if anyone knows
what might be causing the error he is getting?
Mel has sent me the exact error message and it is as attached. It looks
like the device numbers are correctl
Well, it helps to know the actual error message.
##
WSJT ver 10.0 r4285
Rev date 2014-09-09
AudioInput Output
DeviceChans Chans
02 0 Microsoft Sound Mapper Input
12 0 Mic (RigBlas
On 02/03/2015 21:49, Joe Taylor wrote:
Hi Joe,
> Well, it helps to know the actual error message.
Indeed!
>
> ##
> WSJT ver 10.0 r4285
> Rev date 2014-09-09
>
> AudioInput Output
> DeviceChans Chans
>
> 02
Hope I didn't lose you, did I? Still waiting to hear from the last test I
sent you.
Mike W9MDB
-Original Message-
From: Chuck Forsberg WA7KGX [mailto:c...@omen.com]
Sent: Sunday, March 01, 2015 11:29 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Yaesu FT-991 CAT Codes releas
Hi All,
to anyone using the test version linked below. I would advise not using
it on air as there is a flaw in my proposal.
The messages like:
DE TI4/N0URE R-10
will not work because the report will not be collected at the far end :(
I need to think about this further but it looks like there
Hi Bill,
On 3/2/2015 5:45 PM, Bill Somerville wrote:
> to anyone using the test version linked below. I would advise not using
> it on air as there is a flaw in my proposal.
>
> The messages like:
>
> DE TI4/N0URE R-10
>
> will not work because the report will not be collected at the far end :(
N
Hi All,
OK, take 2:- here's a new test version:
https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.4.0-rc3-win32-r4996-genmsg.exe
I would like some testing by someone with a type 1 compound call and
especially by someone with a type 2 compound call. If you can work each
other; better still ;)
On 03/03/2015 00:22, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
>
> On 3/2/2015 5:45 PM, Bill Somerville wrote:
>> to anyone using the test version linked below. I would advise not using
>> it on air as there is a flaw in my proposal.
>>
>> The messages like:
>>
>> DE TI4/N0URE R-10
>>
>> will not work b
Bill --
> The message is indeed a valid standard message but that is not the
> issue. The issue is that current software will not extract the report
> from a message that doesn't contain the DE call.
Maybe we're arguing semantics. When you say "the report will not be
collected at the far end" a
On 03/03/2015 00:53, Joe Taylor wrote:
> Bill --
Hi Joe,
>
>> The message is indeed a valid standard message but that is not the
>> issue. The issue is that current software will not extract the report
>> from a message that doesn't contain the DE call.
> Maybe we're arguing semantics. When you sa
Bill --
> Agreed but the received report is only captured (automatically) if the
> message contains the DE call sign i.e. if I decode:
>
> DE TI4/N0URE R-10
>
> WSJT-X does not record that -10 report unless I manually enter it.
Yes. I wasn't too worried about that; we do, after all, offer a chan
On 03/03/2015 01:11, Joe Taylor wrote:
> Bill --
Hi Joe,
>
>> Agreed but the received report is only captured (automatically) if the
>> message contains the DE call sign i.e. if I decode:
>>
>> DE TI4/N0URE R-10
>>
>> WSJT-X does not record that -10 report unless I manually enter it.
> Yes. I wasn
Bill --
> Either way, I am making the required change so that WSJT-X will extract
> a received report from a standard message containing only the QSO
> partner call sign. This seems safe and proper to me.
Sounds like the right thing to do.
-- Joe
vs; elicits a question mark.
On 03/02/2015 02:05 PM, Michael Black wrote:
> Hope I didn't lose you, did I? Still waiting to hear from the last test I
> sent you.
> Mike W9MDB
>
> -Original Message-
> From: Chuck Forsberg WA7KGX [mailto:c...@omen.com]
> Sent: Sunday, March 01, 2015 11:
Try replacing the wsjtx.exe from the 1.5 install with this one
https://www.dropbox.com/s/mj6qgyjphr1ts7v/wsjtx.exe?dl=0
Here's the install if you need it again or missed the last one I sent
https://www.dropbox.com/s/lih67pu5vp9yw9v/wsjtx-1.5.0-devel-win32-r4988-ft95
1-4.exe?dl=0
Install this first
20 matches
Mail list logo
