Date   

locked Re: Annoyance!

Floyd Sense
 

This happens to me almost daily.  I'm usually up early chasing FT8 DX on 80M and when I'm done I just leave WSJT-X up and come back for more in the late afternoon.  About 50% of the time, the audio out has been redirected to the PC speakers (that's the default audio output device).  100% of the time, restarting WSJT-X fixes the problem. There has been no other activity on the PC during the off time.   I'm running Windows 10 Home Edition at the latest maintenance level.  Using a microHam Digikeyer II as the interface with my FTDX-5000.  No RF problems in the shack - things are properly controlled with chokes.  Besides, there is NO RF generated during the period when the audio problem occurs.  I've been experimenting with JTDX recently and have not yet had the problem occur with it.

73, K8AC


locked Re: FT8 success after sunset

Dennis Jacobson
 

I had a problem going to the lower bands myself. What I found was that my radio was automatically set to go to lower sideband on the lower frequencies.  Make sure your radio isn't switching to L S B on the lower bands.
Good luck
Dennis N6NG


locked Re: Auto Uploading to LOTW and QRZ

Dave AA6YQ
 

+ AA6YQ comments below

Good morning, Ronnie

I use a DXKEEPER add on LogPublisher program that does exactly what your looking for. I use it with JTALERT. Once the contact is completed and logged into WSJTX and automatically sent to DXKEEPER , LogPublisher sends it QRZ AND HRDlognet. I then use QRZ to upload contacts to LOTW. I am not a contester or avid award chaser. So this works for me. You can try the program for free. Cost about 10 Euro.

+ To be clear,

1. DXKeeper and the other components of the DXLab Suite are entirely free.

2. DXKeeper can submit QSOs to LoTW directly, either automatically as they are logged, or with two mouse clicks to submit all QSOs not yet submitted to LoTW.

73,

Dave, AA6YQ


locked Re: Auto Sequencing Changed

Vin
 

Hi Gary,

The logging window no longer comes up because the Tx sequence has changed.

After calling CQ and receiving a report, the sequence 'used' to go to Tx5
sending the 73 and having the logging window open, allowing me to manually
send the contact to my logging program.

Now, after I receive my report, the sequence goes to Tx4 which is RRR. In
order for the logging window to open, I have to manually click on either
"Next" or "Tx5" to send the 73 after I receive my report.

I didn't change anything in WSJT-X v2.3.0-rc2 so I'm confused how the
sequence has changed without me changing a setting.

Vin, 73
K1VC

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Gary -
AG0N
Sent: Thursday, December 31, 2020 1:02 PM
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Auto Sequencing Changed



On Dec 31, 2020, at 08:22, Vin <k1vc@...> wrote:

It only happens if I call CQ, when I reply to a CQ, the sequence is fine.
The logging window should only come up when you send one of the responses
containing 73. 73 is the trigger as I understand it.

Gary - AG0N


locked Re: Auto Sequencing Changed

Gary - AG0N
 

On Dec 31, 2020, at 08:22, Luca B <k1vc@...> wrote:

It only happens if I call CQ, when I reply to a CQ, the sequence is fine.
The logging window should only come up when you send one of the responses containing 73. 73 is the trigger as I understand it.

Gary - AG0N


locked Re: Auto Uploading to LOTW and QRZ

Jeff Stillinger
 

On the contrary.   QRZ is a full service log book. 

Here is a screen shot of a logged QSO I made this morning and logged to QRZ.   Of course it contains everything for confirmation when I sync it to LoTW, but it also houses everything that CQR Log does.   Then some.


On 12/31/20 11:30 AM, Bill Somerville wrote:

On 31/12/2020 17:26, Jeff Stillinger via groups.io wrote:
I would have to disagree with the policy when it comes to online LOGBOOK Services.  Such as QRZ (US) and QRZCQ (EU).  These are full service log books online.   Housing much more information than just the QSO it self, and they are linked to external confirmation services.  In short, doing it online instead of locally.

Hi Jeff,

unless QRZ or QRZCQ handle management of awards using eQSL and LoTW etc. then for you they do not seem to be a "full service log book". I was under the impression that these services have a rather narrower focus.

73
Bill
G4WJS.






locked Re: Annoyance!

Austin 2E0MNV
 

Ok, thanks, I will try and see if I get disconnected from the rig again. It is intermittent and random which makes it hard to trace.


locked Re: Annoyance!

Bill Somerville
 

On 31/12/2020 17:30, avaughan585@... wrote:
OK thanks.  I've created an Aggregate Device and assigned Audio USB Codec to the Aggregate Device.  In WSJTX though, Aggregate Device is not an option.  Only USB Audio Codec.
Hi Austin,

with WSJT-X v2.2.2 you will need to restart WSJT-X to see the new audio devices.

73
Bill
G4WJS.


locked Re: Auto Uploading to LOTW and QRZ

Bill Somerville
 

On 31/12/2020 17:26, Jeff Stillinger via groups.io wrote:
I would have to disagree with the policy when it comes to online LOGBOOK Services.  Such as QRZ (US) and QRZCQ (EU).  These are full service log books online.   Housing much more information than just the QSO it self, and they are linked to external confirmation services.  In short, doing it online instead of locally.
Hi Jeff,

unless QRZ or QRZCQ handle management of awards using eQSL and LoTW etc. then for you they do not seem to be a "full service log book". I was under the impression that these services have a rather narrower focus.

73
Bill
G4WJS.


locked Re: Annoyance!

Austin 2E0MNV
 

OK thanks.  I've created an Aggregate Device and assigned Audio USB Codec to the Aggregate Device.  In WSJTX though, Aggregate Device is not an option.  Only USB Audio Codec.


locked Re: Auto Uploading to LOTW and QRZ

Jeff Stillinger
 

While I understand and accept the projects policy.   I have some thoughts worth pondering.

I would agree that it is not WSJT-X's responsibility to upload into QSL CONFIRMATION Services.  Such as LoTW, eQSL, Clublog, HamQTH, HRDLog, etc...   These are not log books, they are confirmation services.  Housing very limited QSO data.

I would have to disagree with the policy when it comes to online LOGBOOK Services.  Such as QRZ (US) and QRZCQ (EU).  These are full service log books online.   Housing much more information than just the QSO it self, and they are linked to external confirmation services.  In short, doing it online instead of locally.

It's worth looking into and discussing.

--
DE KB6IBB



On 12/31/20 7:27 AM, Bill Somerville wrote:

On 31/12/2020 13:14, Ronnie Hull wrote:
Good morning folks.  I did a quick search on this subject and I'm a bit confused.   I want to be able to upload my contacts to qrz logbook and lotw AS I LOG THEM.  Will WSJT-X do this? if so how do I set it up in settings?  don't assume I'm as smart as you LOL.. step by step is good

Or if not.. do I need additional software to do this?

thanks joe and gang for such a wonderful program I am having a ball

thanks and 73

Ronnie W5SUM

Hi Ronnie,

WSJT-X cannot do this directly, and nor should it. The normal reason for uploading to QSL services is to track and acquire confirmations of QSOs for awards and certificates across all modes of operation, this is outside of the scope of WSJT-X and should be the responsibility of your main station logging application which should be capable of maintaining the extra administrative records necessary to carry out these tasks. If the QRZ.COM logbok is your main station log then it should be able to upload and track confirmations in LoTW, if it can't do that, which I suspect is the case, then it is not fit for purpose as your main station log.

73
Bill
G4WJS.






locked Re: Auto Sequencing Changed

Reino Talarmo
 

Hi Vin,

Perhaps my addition gives a hint what is happening, see inline.

 

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Luca B
Sent: 31. joulukuuta 2020 17:23
To: main@WSJTX.groups.io
Subject: [WSJTX] Auto Sequencing Changed

 

Hello,

 

I’m using WSJT-X v2.3.0-rc2 (64-bit) and the auto sequence changed yesterday.  Prior to this change, the auto sequence was:

 

Calling CQ on FT8:

Tx6 (CQ)        You got report not QRA

Tx2 (Call MyCall report)   You got RR73

Tx5 (73)

Log QSO window pops up, I hit OK and the QSO is sent to my logging program and I enter some additional information in my logging program.

 

Now it’s:

Tx6 (CQ)        You got QRA

Tx2 (Call MyCall report)    You got R and report

Tx4 (RRR)      You have RRR meaning you wish to see 73 from the other station. If you had RR73 things change.

No Log QSO window pops up, I have to manually hit Tx5 or the Log QSO window will not open.

 

I have Auto Seq box checked (I did uncheck it, made a QSO, ran through the sequence manually and then checked Auto Seq again, called CQ, made a QSO but Tx4 came up, not Tx5.

 

It only happens if I call CQ, when I reply to a CQ, the sequence is fine.

 

I’ve reinstalled WSJT-X v2.3.0-rc2 (64-bit) twice, I reinstalled my logging program (just in case my logging program changed anything), I searched the archives but couldn’t find a similar post and I looked at section 7.3 Auto-Sequencing in the manual.

 

How do I go back to my original sequence of Tx6 > Tx2 > Tx5 when calling CQ?

 

Thank you,

Vin, 73

K1VC

 


locked Re: Annoyance!

Bill Somerville
 

On 31/12/2020 17:15, avaughan585@... wrote:
As stated above, it's none of that. It is a Yaesu FT450D, Yaesu SCU-17 interface and Mac OS Catalina.  The driver cannot be set to anything other than 48000, 48000 is the only option.
Hi Austin,

OK, try this. Create a new Aggregate Device in Audio MIDI Setup and assign your rig's audio codec to it, then change the WSJT-X "Preferences->Audio" to use that device. You can also give the new Aggregate Device a meaningful name like FT-450D if you wish.

73
Bill
G4WJS.


locked Re: Annoyance!

Austin 2E0MNV
 

As stated above, it's none of that. It is a Yaesu FT450D, Yaesu SCU-17 interface and Mac OS Catalina.  The driver cannot be set to anything other than 48000, 48000 is the only option.


locked Re: Annoyance!

Jim Bennett <w6jhb@...>
 

I used to have that problem on my Mac computers. From what I was able to determine, Apple changed something in the way they handle USB2. It is NOT an RFI problem. You can try the 44,000 baud setting, which will greatly help, but is not a cure-all. If you have a USB3 port, give that a try - it also seems to help. Another thing that worked 100 percent for me was to route your USB audio device through a USB to Thunderbolt adapter.

Jim Bennett / W6JHB
Folsom, CA

On Dec 31, 2020, at 9:01 AM, avaughan585@... wrote:

Yep, that was already in place. Already done. It happens once in a while and random



locked Re: Being called when just monitoring and not transmitting

TOM N4LSJ
 

I finished up 15 meters doing exactly that.  I -did- in fact get one, finally.   Only a fraction of them will answer back, but it's always worth a shot!

On 12/30/20 5:24 PM, Timothy Brannon wrote:

Are you sending automatic spots to PSKReporter.info?
While working on 5-band WAS and trying to get close-by states on 15 and 17 meters (inside my skip zone), I have been known to make blind calls to stations I see just spotting me on PSKReporter. It's worked a few times. Probably not the cause here, though.
de Tim, WA5MD in Dallas.


locked Re: Annoyance!

Andy_501 <andrew.webb.501.ve4per@...>
 

windows or linux and is it an ICOM rig with built in USB audio/CAT bridge?

On 2020-12-31 10:35 a.m., avaughan585@... wrote:

Every now and then, on transmit, my sound suddenly switches to speaker and not to the rig.  I happens randomly and I have to restart WSJT-X.  It always happens at the most critical moments when I'm working a new DXCC.  Anyone else having this issue and is there a solution?



locked WSJT-X and JTDX programs experiencing bad lag on decodes

Andy_501 <andrew.webb.501.ve4per@...>
 

Aquaintance of mine has TS-570D rig and SignalinkUSB sound device Win10 Pro OS  dual core, 4 thread CPU with 16 GB Ram ,  both WSJT-X & JTDX FT4 & FT8  is having problem with program apparently lagging on decodes; any solutions or tips/pointer where to investigate?  (Not sure of vers of JTDX or WSJT-X )

"lagging is upon decoding the FT4/8 signals, have had up to +8.5 delay on decoding, and missed out on a few contacts."
any pointers are appreciated
Best in 2021

thanks

Andy VE4PER


locked Decode lag

Andy_501 <andrew.webb.501.ve4per@...>
 

Aquaintance of mine has TS-570D rig and SignalinkUSB sound device Win10 Pro OS  dual core, 4 thread CPU with 16 GB Ram and is having problem with program apparently lagging on decodes; any solutions or tips/pointer where to investigate?

"lagging is upon decoding the FT4/8 signals, have had up to +8.5 delay on decoding, and missed out on a few contacts."

Best in 2021

thanks Andy VE4PER


locked Auto Sequencing Changed

Vin
 

Hello,

 

I’m using WSJT-X v2.3.0-rc2 (64-bit) and the auto sequence changed yesterday.  Prior to this change, the auto sequence was:

 

Calling CQ on FT8:

Tx6 (CQ)

Tx2 (Call MyCall report)

Tx5 (73)

Log QSO window pops up, I hit OK and the QSO is sent to my logging program and I enter some additional information in my logging program.

 

Now it’s:

Tx6 (CQ)

Tx2 (Call MyCall report)

Tx4 (RRR)

No Log QSO window pops up, I have to manually hit Tx5 or the Log QSO window will not open.

 

I have Auto Seq box checked (I did uncheck it, made a QSO, ran through the sequence manually and then checked Auto Seq again, called CQ, made a QSO but Tx4 came up, not Tx5.

 

It only happens if I call CQ, when I reply to a CQ, the sequence is fine.

 

I’ve reinstalled WSJT-X v2.3.0-rc2 (64-bit) twice, I reinstalled my logging program (just in case my logging program changed anything), I searched the archives but couldn’t find a similar post and I looked at section 7.3 Auto-Sequencing in the manual.

How do I go back to my original sequence of Tx6 > Tx2 > Tx5 when calling CQ?

 

Thank you,

Vin, 73

K1VC

 

19941 - 19960 of 39791