Date   

locked Re: Why you should use split on FT8 #QSO_practices #FT8

Bill Lederer
 

All:

I second this emphatically.

Please use split: set that "hold tx frequency" and try to transmit on as clear a frequency as possible.

w8lvn

On Wed, Mar 17, 2021 at 8:22 AM Tony Collett via groups.io <tony.nbs=btinternet.com@groups.io> wrote:
For those that insist on calling directly on top of someone's frequency instead of calling split on a separate frequency 
And for those that insist on remaining on somebody else's frequency after the QSO has completed......
This is what I observed last night on 80m (sorry it includes real calls).

225615 -21 0.3 2676 ~ CQ VU2DED ML88  India

225631 Tx 2551 ~ VU2DED G4NBS JO02

225645 -20 0.3 2676 ~ SQ8OAU VU2DED -14

225700 17 -0.2 2676 ~ VU2DED SQ8OAU R-13

225730 16 -0.2 2675 ~ VU2DED SQ8OAU 73

225745 0 0.1 2673 ~ SQ8OAU 9A4ZM JN64

225800 -12 0.5 2676 ~ VU2DED DO4MTB JO41

225815 -2 0.1 2672 ~ SQ8OAU 9A4ZM JN64

I doubt if I would have made the QSO as it was in/out with QSB but no chance of seeing the VU again once the third party decided he wanted to use the same frequency!

PLEASE USE SPLIT!!!

73
Tony G4NBS




--
--w8lvn--


locked Re: #JT4 Worrying comment for beacon users #JT4

Joe
 

Hi Andy,

You say someone told you

"the earlier JT4 (which has unfortunately been declared 'obsolete' and removed from the latest release candidate), JT65 and QRA64 (also removed..."

... but you don't identify the source.  Certainly the comment did not come from the WSJT Development Team.  We have no plan to retire either JT4 or JT65.

While I think of it: The wider Q65 submodes work very well on 10 GHz rainscatter.  An example is included in the sample files downloadable from the WSJT-X Help menu.

  -- 73, Joe, K1JT


locked Why you should use split on FT8 #QSO_practices #FT8

Tony Collett
 

For those that insist on calling directly on top of someone's frequency instead of calling split on a separate frequency 
And for those that insist on remaining on somebody else's frequency after the QSO has completed......
This is what I observed last night on 80m (sorry it includes real calls).

225615 -21 0.3 2676 ~ CQ VU2DED ML88  India

225631 Tx 2551 ~ VU2DED G4NBS JO02

225645 -20 0.3 2676 ~ SQ8OAU VU2DED -14

225700 17 -0.2 2676 ~ VU2DED SQ8OAU R-13

225730 16 -0.2 2675 ~ VU2DED SQ8OAU 73

225745 0 0.1 2673 ~ SQ8OAU 9A4ZM JN64

225800 -12 0.5 2676 ~ VU2DED DO4MTB JO41

225815 -2 0.1 2672 ~ SQ8OAU 9A4ZM JN64

I doubt if I would have made the QSO as it was in/out with QSB but no chance of seeing the VU again once the third party decided he wanted to use the same frequency!

PLEASE USE SPLIT!!!

73
Tony G4NBS


locked Re: Time Sync Program. #Timesync

Ria, N2RJ
 

Meinberg avoids sudden shifts in the clock. It’s also set and forget, completely unobtrusive. This is why I prefer it over nettime. 

Ria
N2RJ 

On Wed, Mar 17, 2021 at 6:12 AM Jim Brown <k9yc@...> wrote:
On 3/16/2021 3:48 PM, Bob Lewis wrote:
> The Meinburg monitoring service only works with Meinburg NTP so both
> must be installed and the windows time service (or any other time
> service like D4) must be disabled.

As long as your computer has internet, NetTime is Sooo much simpler.

http://www.timesynctool.com/

73, Jim K9YC




locked Re: Q65 on VHF - which frequencies are used for 2 and 6m? #Q65

ve4cy
 

With scatter, the more power the better..  But 80W into 3 elements will work well.  (I'm getting good results with 100W into 4 elements).  I have a friend who makes contacts using a simple dipole.

There are two great online resources for meteor scatter.   The first is PSK reporter.  Above the map, fill in the filter boxes with the appropriate info.  That will let you see everyone who is running MSK144 on 6 meters over a given time period.  This will also let you see the overall conditions at a glance.  (It works for other digital modes as well).  And... So you can share your results on the site, make sure you have "Enable PSK Reporter Spotting" checked off in the Reporting tab in the Settings menu.


There's an online chat site called Ping Jockey.  All the die hard scatter guys hang out there and discuss current conditions and all things scatter:


73 de Jim VE4CY


From: "va7qi" <ve7mdl@...>
To: main@WSJTX.groups.io
Sent: Tuesday, March 16, 2021 11:38:53 PM
Subject: Re: [WSJTX] Q65 on VHF - which frequencies are used for 2 and 6m? #Q65

OK, thanks.  I will be listening there over the next 24-48 hours and call the occasional CQ.
Running 80 Watts into a 3-element Yagi currently pointing SE.

73 de va7qi,             ....Erik.





locked Re: Q65 on VHF - which frequencies are used for 2 and 6m? #Q65

Buddy Morgan
 

Around here (Florida) using 144.174 or 144.150 would be very unpopular. As long as you stayed below 144.170,  you could set up a Q65 sked on about any frequency you wanted.

Buddy WB4OMG


-----Original Message-----
From: Mike Phipps <qrz@...>
To: main@wsjtx.groups.io <main@WSJTX.groups.io>
Sent: Wed, Mar 17, 2021 7:27 am
Subject: Re: [WSJTX] Q65 on VHF - which frequencies are used for 2 and 6m? #Q65

I haven’t seen anyone come up with a QRG for 2m, but when I had a homebrew 6el Yagi up for 2m, we were testing Q65 out on 144.170 MHz. I’m not sure how that jives with Region 1 or 3 band plans, though… ymmv.

We started out using 30A, but found that 30B works better up there. It’s been weeks since I was active there, and it’ll have to wait until I can build a better Yagi and get it up higher (hopefully with a decent rotator this time), but I’d imagine that they’re still doing Q65-30B on 144.170.


Mike K8WU

> On Mar 17, 2021, at 12:38 AM, va7qi <ve7mdl@...> wrote:
>
> OK, thanks.  I will be listening there over the next 24-48 hours and call the occasional CQ.
> Running 80 Watts into a 3-element Yagi currently pointing SE.
>
> 73 de va7qi,            ....Erik.
>
>





locked Re: Q65 on VHF - which frequencies are used for 2 and 6m? #Q65

Mike Phipps <qrz@...>
 

I haven’t seen anyone come up with a QRG for 2m, but when I had a homebrew 6el Yagi up for 2m, we were testing Q65 out on 144.170 MHz. I’m not sure how that jives with Region 1 or 3 band plans, though… ymmv.

We started out using 30A, but found that 30B works better up there. It’s been weeks since I was active there, and it’ll have to wait until I can build a better Yagi and get it up higher (hopefully with a decent rotator this time), but I’d imagine that they’re still doing Q65-30B on 144.170.


Mike K8WU

On Mar 17, 2021, at 12:38 AM, va7qi <ve7mdl@...> wrote:

OK, thanks. I will be listening there over the next 24-48 hours and call the occasional CQ.
Running 80 Watts into a 3-element Yagi currently pointing SE.

73 de va7qi, ....Erik.


locked #JT4 Worrying comment for beacon users #JT4

Andy Talbot
 

In an email I received today, someone made the comment 

"the earlier JT4 (which has unfortunately been declared 'obsolete' and removed from the latest release candidate), JT65 and QRA64 (also removed..."

I'm hoping above all else this was just a mistake on the writer's part and that JT4 and JT65 will always remain, even if they are less efficient than the others   They have been implemented on a large number of beacons around the World now and it would be catastrophic if the modes were removed from the WSJt-X suite, and users required to keep an older copy in parallel with the latest.  AFAIK, it's only QRA64 that has gone, to be replaced with Q65.

As far as I can see, JT4G is still the only mode that can cope with the really wide spread of rain scatter on 10GHz and 24GHz.
I'm also hoping JT9 stays, too.   Like JT4 its implementation in a small processor, encoding in real time is straightforward, unlike the memory-heavy matrix-encoder later modes.

It really would be a great pity if beacons were forced into using the rather cut-down PI4 mode because of a fear of built in obsolescence on any of those in WSJT-X.  PI4 itself, being inspired by and generated the same way as JT4G
 

Virus-free. www.avg.com


locked Re: Time Sync Program. #Timesync

Jim Brown
 

On 3/16/2021 3:48 PM, Bob Lewis wrote:
The Meinburg monitoring service only works with Meinburg NTP so both must be installed and the windows time service (or any other time service like D4) must be disabled.
As long as your computer has internet, NetTime is Sooo much simpler.

http://www.timesynctool.com/

73, Jim K9YC


locked Re: Q65 on VHF - which frequencies are used for 2 and 6m? #Q65

va7qi
 

OK, thanks.  I will be listening there over the next 24-48 hours and call the occasional CQ.
Running 80 Watts into a 3-element Yagi currently pointing SE.

73 de va7qi,             ....Erik.


locked Re: Waterfall display halts stalls with regular period #IssueReport

Kenneth Williams
 

Stopping dead does not sound like the same problem that I am seeing.  Do you mean that everything halts completely or that you see alternating rx sequences that are being cut short like I see.

Ken
KC6PUQ


locked Re: WSJT-X not Answering Calls #FT8

Dale Martin, KG5U
 

Re: my inquiry about why my WSJT-X was not answering callers responding to my CQ’s.

 

It was right in front of me the whole time—I did a search for every instance of ‘CQ’ in the 2.3.0 instructions and found a reference to “1st call”. I looked over at the other monitor where WSJT-X was sitting and there was “1st call” with an empty checkbox. I checked thet box, called CQ and, Joila!, someone came back to me and my WSJT-X responded accordingly.

 

Sorry for the false alarm. CU on FT8/4.

 

73,

Dale, kg5u

 


locked Re: Not receiving anything... #GeneralGroupInfo

Ron Schunk
 

Thanks for the suggestions...I have Meinberg working and it is doing a better job than D4 or Net Time...and as for the USB yep it is set to that....so Im still stuck....

Virus-free. www.avast.com


On Tue, Mar 16, 2021 at 5:26 PM Karl Beckman <wa8nvw@...> wrote:
I hate to suggest something at such a low level, but I've done it more than once myself:  If you are testing on 40, 60, 75, or 160M, make sure your rig is set to UPPER sideband. That's one thing you can't read on the waterfall.  The worldwide standard for analog voice on ham bands below 9 MHz is LSB, but WJST is always upper..
--
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io



locked Re: Time Sync Program. #Timesync

Buddy Morgan
 

I have used Dimension 4, for several years. A few days ago, I switched to my Bodnar GPSDO, for time sync. Thus far, it has proved to work, at least as well, as Dim 4 and gives you Lat/Lon, on a map.

Buddy WB4OMG


-----Original Message-----
From: RichardH <jrhoye@...>
To: main@WSJTX.groups.io
Sent: Tue, Mar 16, 2021 5:53 pm
Subject: Re: [WSJTX] Time Sync Program. #Timesync

I use NetTime, also.  Very simple and straightforward, lightweight, and works like a charm right out of the gate.  Highly recommend.

dh




locked Re: Time Sync Program. #Timesync

LU4AHR
 

Hi all,

Been running Meinberg since the first version of Joe´s SW  (not tried any other time synching SW though) and never any issues, PC´s here were old pentium 4 running W-XP up to today´s i7-8700k running W10, and in-betweens). 

NTP is periodically updated but you have to check Meinberg´s website manually from time to time (unfortunately no automatic updating, updates should be done manually and although not complicated, IMHO it is not so simple nor straightforward), I understand current version is ntp-4.2.8p15-v2.

About the Monitor I agree it is quite old fashioned and to my knowledge has not been updated so far, but found it to be quite useful since it allows me to have an idea how well  my system is behaving.  I frequently use the NIST US time service to check my offset anyway.

I´m no way related to Meinberg but just a happy user of their software.

My 2¢.  Best 73 and great DXing,  

Marcelo - LU4AHR 


locked Re: Logged Stations Still Show Up In Band Activity As Not Worked - Green Highlighted #logging

Don Bolstad K9DEB
 

Ken

I had not seen that as something to do. Thanks.   
I did the rescan.  Went into Settings Collars and  unchecked the Green  CQ in Message option and checked the New Call and New Call on Band.

That seems to have done the trick...Now stations calling cq that I had worked before are not colored.

Thanks for all the help everybody.

Don K9DEB


locked Re: Logged Stations Still Show Up In Band Activity As Not Worked - Green Highlighted #logging

neil_zampella
 

He's using 2.16.17 which is the latest.    If you're using JT-Alert I would use its B4 display rather than the WSJT-X color scheme.

Neil, KN3ilz

On 3/16/2021 4:33 PM, Bill, WB6JJJ wrote:

Did you update JTAlert after installing the new WSJT program? JTAlert was changed to work with the new version of WSJT.
Bill
WB6JJJ


On Mar 16, 2021, at 2:26 PM, Robert Lorenzini <bob@...> wrote:

 I can duplicate this in 2.2.2 by starting everything from DXLabs launcher even when JTAlert is started last.
Killing JTAlert and restarting will fix it. Until I realized what was going on I made a number of embarrassing
workedB4 contacts. It may be JTAlert is the problem, I will revert and try that when I get back from my bike ride.

dod
JTAlert 2.16.17

On 3/16/2021 7:49 AM, Bob wrote:
No Bill, there is a bug.

dod

On 3/16/2021 6:37 AM, Bill Somerville wrote:
On 16/03/2021 12:02, Don Bolstad K9DEB wrote:
Recently had to re-install programs on PC after a Windows crash requiring a restore.  Fortunately the restore job saved my data and logs. However software programs needed to be re-installed.
Downloaded and installed  WSJt-x V2.3.0 and JTAlert 2.16.17.

Noticed that after I work and log a station, that station still shows up in the Band Activity window with green highlight, indicating not worked.  I checked the 'wsjtx_log.adi" and "wsjx.log" files and the qso has been properly recorded.  This has caused me to chase the station again, even though I may have worked him the same day.   All CQ lines in the band activity window are green.  This was not the way it was before the restore.

Anybody with an idea this is happening?

Don K9DEB
Don,

with the default colour scheme for highlighting decodes in WSJT-X a green background means they are calling CQ, no more, no less.

73
Bill





        




      



locked Re: Logged Stations Still Show Up In Band Activity As Not Worked - Green Highlighted #logging

Robert Lorenzini
 

Found the problem. I was starting JTAlert from a .bat file but I had the wrong argument. Everything
came up fine but the Band Activity colors were not being changed by JTA.

dod

On 3/16/2021 8:28 AM, Bob wrote:

I can duplicate this in 2.2.2 by starting everything from DXLabs launcher even when JTAlert is started last.
Killing JTAlert and restarting will fix it. Until I realized what was going on I made a number of embarrassing
workedB4 contacts. It may be JTAlert is the problem, I will revert and try that when I get back from my bike ride.

dod
JTAlert 2.16.17

On 3/16/2021 7:49 AM, Bob wrote:
No Bill, there is a bug.

dod

On 3/16/2021 6:37 AM, Bill Somerville wrote:
On 16/03/2021 12:02, Don Bolstad K9DEB wrote:
Recently had to re-install programs on PC after a Windows crash requiring a restore.  Fortunately the restore job saved my data and logs. However software programs needed to be re-installed.
Downloaded and installed  WSJt-x V2.3.0 and JTAlert 2.16.17.

Noticed that after I work and log a station, that station still shows up in the Band Activity window with green highlight, indicating not worked.  I checked the 'wsjtx_log.adi" and "wsjx.log" files and the qso has been properly recorded.  This has caused me to chase the station again, even though I may have worked him the same day.   All CQ lines in the band activity window are green.  This was not the way it was before the restore.

Anybody with an idea this is happening?

Don K9DEB

Don,

with the default colour scheme for highlighting decodes in WSJT-X a green background means they are calling CQ, no more, no less.

73
Bill







locked Re: FT8 #logging

Ken <w8ken@...>
 

Thanks Bill & John,
I think I will try John’s approach first.
It sounds simpler. I know how to create another config file.

W8KEN - Ken

On Mar 16, 2021, at 18:45, JP Tucson, AZ <samcat88az@...> wrote:


Hi Ken,

Instead of 2 instances, you can create 2  "CONFIGS"; one setup for each radio & they will both use the same log file.  

73 - John - N7GHZ

On Tue, Mar 16, 2021, 3:33 PM Ken via groups.io <w8ken=yahoo.com@groups.io> wrote:
I have created two instances of WSJT-X, one configured for my K3 and one configured for my IC-7610 Radio.
Both instances work.

Does anyone know how to point configure both Instances to use the same ADI Log file.
I would like to be able to switch between RIGs but maintain a common ADI file so stations worked on either radio will still show up as worked so I do not duplicate previous QSO's.

Ken - W8KEN







locked Re: Time Sync Program. #Timesync

Bob Lewis
 

The Meinburg monitoring service only works with Meinburg NTP so both must be installed and the windows time service (or any other time service like D4) must be disabled.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Bob Turner
Sent: Tuesday, March 16, 2021 5:58 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Time Sync Program. #Timesync

 

I found the Meinburg monitoring software refuses to run because “NTP Service not installed”.   I tried it with Run As Administrator, same results.  It appears we need to install the Meinburg NTP service as well.  I did not.  The “Windows Time” service is running.  My windows 10 version is build 19041.867.

 

I was running Dimension 4.  I recently removed Dim4 to see how inaccurate my PC clock is.  It’s been about 24 hours without Dim4.  My time is 0.027 seconds fast.

 

7 3  Bob

N2SCJ

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of David Ackrill
Sent: Tuesday, March 16, 2021 2:24 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Time Sync Program. #Timesync

 

The NTP system will work anyway, the Meinburg monitoring software is realy only an additional benefit.  I look at the graphs occasionally and check that there are a number of Stratum 2 and 3 systems in the NTP Status tab.  It is old software now, so I doubt Meinburg will be offering any support for it anymore...

Using the command 'ntpq -pn' in a command prompt will tell you that NTP is running and which systems your PC has heard from.

Cheers - Dave (G0DJA)

16581 - 16600 of 39792