Date   

locked Re: WSJT-X on Raspeberry Pi: Rig Control Woes

Bill Somerville
 

On 31/12/2020 17:59, dpsm64@... wrote:
Hi, I'm fairly new to WSJT-X, but I have gotten it up and running on my Ubuntu desktop with my IC-7200. I built a Raspberry Pi to use specifically for digital modes using KM4ACK's Build-a-Pi v3. I've tried about everything I can think of to get WSJT-X talking to my rig over USB, but no dice. I'm using /dev/ttyUSB0, same serial settings that worked when I ran WSJT-X on my Ubuntu machine, but all I get is a dialog saying "Rig Failure Hamlib error: IO error when opening connection to rig."

I double checked group membership - /dev/ttyUSB0 is in the dialout group, as is the user I'm logged in as (pi). When I use rigctl from the command line to test hamlib, this is what I get:

pi@raspberrypi:~ $ rigctl -r /dev/ttyUSB0 -m 361
rig_open: error = IO error

Curiously, when I sudo that same command, rigctl prompts me for a rig command. But if I type "f", for instance, I just get "get_freq: error = Communication bus error". I've tried rigctl both ways with verbose logging, too, and it appears rigctl is sending and receiving something, but it's not liking what it's seeing. Here's the log when I start rigctl with sudo:

Rig command: f
rig_get_freq called
icom_get_freq called
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
read_string(): RX 5 characters
0000    fe fe 76 e0 03                                      ..v..           
read_string called
read_string(): Timed out 1.1058 seconds after 0 chars
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
0000    fe                                                  .               
read_string(): read() failed - Resource temporarily unavailable
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
read_string(): Timed out 1.1038 seconds after 0 chars
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
0000    fe                                                  .               
read_string(): read() failed - Resource temporarily unavailable
get_freq: error = IO error

I get similar treatment trying flrig for rig control -- just a dialog saying "Transceiver not responding" on /dev/ttyUSB0

This seems like something really basic that I'm missing. Has anyone seen this before? WSJT-X 2.2.2 and Hamlib 3.3 on an 8 GB Raspberry Pi 4 with Raspbian Buster, btw.

Thanks, and Happy New Year!

Hi OM,

have you added your user id to the dialout group?

sudo adduse $USER dialout

then log out and back in (log out the whole desktop session, not just the terminal), reboot if you are not sure how to do that.

73
Bill
G4WJS.


locked Re: Being called when just monitoring and not transmitting

K8BL BOB LIDDY <k8bl@...>
 

Tim... Great idea!! I'm gonna try that for those close-in States I need.  ...73,  Bob  K8BL 

On Wednesday, December 30, 2020, 08:08:44 PM EST, Timothy Brannon <timbmd@...> 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: Decode lag

Danny Bush
 

Andy,
 
What software is he using to synchronize the time? 
 
73,
Danny  NF4J

 
 
Sent: Thursday, December 31, 2020 at 9:55 AM
From: "Andy_501" <andrew.webb.501.ve4per@...>
To: WSJTX@groups.io
Subject: [WSJTX] Decode lag
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 Re: FST4 modes with TS-890S - slow RF envelope rise problem #txaudio

G4SDG
 

Hello Peter,

I'm using a Class E amplifier and am having similar issues to you. I've not investigated deeply so far and have no problems with WSPR but on FST4 modes the power supply often momentarily trips at the beginning of a sequence. When seen on an analyser the carrier rise from the FT-817 driver rig seems to be stepped in level which perhaps upsets the TC4427 FET driver chip. 

73 Chris G4SDG    


locked Re: Being called when just monitoring and not transmitting

Austin 2E0MNV
 

False decodes do happen.  I was called by 3G6MZN out of the blue today.  Apparently that's Chile, but it can't be found on QRZ.com or anywhere I look.  No way. I would bet a million dollars that was a false decode.


locked WSJT-X on Raspeberry Pi: Rig Control Woes

dpsm64@...
 

Hi, I'm fairly new to WSJT-X, but I have gotten it up and running on my Ubuntu desktop with my IC-7200. I built a Raspberry Pi to use specifically for digital modes using KM4ACK's Build-a-Pi v3. I've tried about everything I can think of to get WSJT-X talking to my rig over USB, but no dice. I'm using /dev/ttyUSB0, same serial settings that worked when I ran WSJT-X on my Ubuntu machine, but all I get is a dialog saying "Rig Failure Hamlib error: IO error when opening connection to rig."

I double checked group membership - /dev/ttyUSB0 is in the dialout group, as is the user I'm logged in as (pi). When I use rigctl from the command line to test hamlib, this is what I get:

pi@raspberrypi:~ $ rigctl -r /dev/ttyUSB0 -m 361
rig_open: error = IO error

Curiously, when I sudo that same command, rigctl prompts me for a rig command. But if I type "f", for instance, I just get "get_freq: error = Communication bus error". I've tried rigctl both ways with verbose logging, too, and it appears rigctl is sending and receiving something, but it's not liking what it's seeing. Here's the log when I start rigctl with sudo:

Rig command: f
rig_get_freq called
icom_get_freq called
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
read_string(): RX 5 characters
0000    fe fe 76 e0 03                                      ..v..           
read_string called
read_string(): Timed out 1.1058 seconds after 0 chars
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
0000    fe                                                  .               
read_string(): read() failed - Resource temporarily unavailable
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
read_string(): Timed out 1.1038 seconds after 0 chars
serial_flush called
write_block called
write_block(): TX 6 bytes
0000    fe fe 76 e0 03 fd                                   ..v...          
read_string called
0000    fe                                                  .               
read_string(): read() failed - Resource temporarily unavailable
get_freq: error = IO error

I get similar treatment trying flrig for rig control -- just a dialog saying "Transceiver not responding" on /dev/ttyUSB0

This seems like something really basic that I'm missing. Has anyone seen this before? WSJT-X 2.2.2 and Hamlib 3.3 on an 8 GB Raspberry Pi 4 with Raspbian Buster, btw.

Thanks, and Happy New Year!


locked Re: Auto Uploading to LOTW and QRZ

John Morphet
 

GridTracker identified a callsign on the air that you have not previously had a QSO with. The criteria for identification is based on the filtering criteria set up in GridTracker.

 

John, WØZI

www.w0zi.com

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of avaughan585@...
Sent: Thursday, December 31, 2020 10:11 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Auto Uploading to LOTW and QRZ

 

Do you know what "New Hit!" means?


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.

18121 - 18140 of 37978