Sorry guys ... I'm been busy with other things that are interfering with
my ham radio time .. :)
See attached ...
Neil, KN3ILZ
On 6/26/2017 1:00 PM, Black Michael wrote:
Nope...haven't heard anything from him.
de Mike W9MDB
---
Hi Mike,
Thanks! I uninstalled and then reinstalled all files and now it is working.
I'm on 20 meter running r7738 right now.
73,
---Paul AK1P
On 6/26/2017 5:23 PM, Black Michael via wsjt-devel wrote:
You've got an older version of JTSDK.
You apparently didn't install all the updates.
You
Hi all,
I try RX on 6m in "JT9+JT65" mode working with:
- no VHF feature enabled
- no split enabled
- no doppler traking enabled
The decodes are good, as several stations use JT65A in Europe in this
band and mode.
The problem is that the frequency change is logged to ALL.TXT only if it
is le
You've got an older version of JTSDK.
You apparently didn't install all the updates.
Your window title should say "v2.0.5-1 Release 696"
So you need to do the rest of the updates.
You probably just installed the 1st binary.
Look here:
https://sourceforge.net/projects/jtsdk/files/win32/2.0.0/
de M
On Mon,6/26/2017 11:07 AM, Bill Somerville wrote:
On 26/06/2017 18:36, Jim Brown wrote:
On Mon,6/26/2017 10:27 AM, Bill Somerville wrote:
To give an example of what we face, the current IARU region 1 band
plan requires all MGM activity to be between 50300 and 50400 so
expecting to run transatl
On 26/06/2017 18:36, Jim Brown wrote:
On Mon,6/26/2017 10:27 AM, Bill Somerville wrote:
To give an example of what we face, the current IARU region 1 band
plan requires all MGM activity to be between 50300 and 50400 so
expecting to run transatlantic QSOs on 6m JT9E/H on 50290 or indeed
JT65/JT
I know Joe and the group are working on a better mode to take better advantage
of 6 meter multihop sporadic e openings. It would be good if a seperate
frequency for continent-continent communications could be agreed upon by the
band planners prior to implementation. Then it could be added to yo
On Mon,6/26/2017 10:27 AM, Bill Somerville wrote:
To give an example of what we face, the current IARU region 1 band
plan requires all MGM activity to be between 50300 and 50400 so
expecting to run transatlantic QSOs on 6m JT9E/H on 50290 or indeed
JT65/JT9 on 50276 is going to cause the region
On 26/06/2017 18:16, Jay Hainline wrote:
In NA, the 6 meter msk144 calling frequency has been moved down to
50260 to get away from the JT65 users.
50290 is being used for JT9E, JT9H fast modes for North America to
Europe contacts.
This is what I have observed this season on 6 meters. Good Lu
Daunting task Bill.
In NA, the 6 meter msk144 calling frequency has been moved down to 50260 to get
away from the JT65 users.
50290 is being used for JT9E, JT9H fast modes for North America to Europe
contacts.
This is what I have observed this season on 6 meters. Good Luck!
Jay KA9CFD
Sent fro
Nope...haven't heard anything from him.
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, June 26, 2017 11:56 AM
Subject: Re: [wsjt-devel] Question about QSO Start & End Times
On 25/06/2017 13:40, Bill Somerville wrote:
> Hi Neil,
>
> can you pro
On 25/06/2017 13:40, Bill Somerville wrote:
Hi Neil,
can you provide a portion of your ALL.TXT file that covers one of the
QSOs that are logged with equal start and end times please?
Nothing heard on this. Are you debugging this with Mike, W9MDB, off
list? If so I have a patch from Mike fro
Hi All,
there has been much discussion here and many other places about the
suggested working frequencies offered by WSJT-X. In general we have
followed the crowd and set default frequencies that have already become
common usage. This is because we do not claim to be the arbiters of band
plan
13 matches
Mail list logo
