Date   

locked Re: Annoyance!

Chuck Reti
 

This is an issue on older Mac hardware that's been reported frequently over past years (Austin did not specify what hardware he's running Catalina on). Bill's reply early on in this thread is the correct one. Use Audio MIDI Setup to change audio sample rate to 44.1kHz. This one is not an RF issue, ferrite beads are not the solution, this time.

Chuck
WV8A


locked Calibration?

Ken Arck AH6LE
 

Hi All

I run WSJT-10, WSJT-x and MAP65 for my various digital escapades.

I remember when originally installing one of them, one of the installation steps was the soundcard being checked and some parameters being calibrated but I don't remember which program did that.

Does anyone know which one does (from what I've seen, I don't believe they all do although I am leaning towards WSJT-10 being the one that does.

Also, how to force the calibration routine again?

Ken
------------------------------------------------------------------------------
President and CTO - Arcom Controllers
Makers of repeater controllers and accessories.
https://www.arcomcontrollers.com/
Authorized Dealers for Kenwood and Telewave.
We offer complete turn-key repeater packages!
AH6LE/R - IRLP Node 3000
http://www.irlp.net
"We don't just make 'em. We use 'em!"
[]


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

Roger
 

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 ( https://github.com/km4ack/pi-build ). 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 yourself to the "dialout" group?

73 and happy new year
Roge
G#4HZA


locked Re: Annoyance!

Joe Subich, W4TV
 

It sounds as if your computer is going to sleep while not being
used which turns off the external sound card forcing audio back
to the internal sound card.

*DISABLE* Sleep/Hibernate and use the Windows Power Options to
disable USB Selective Suspend.

73,

... Joe, W4TV

On 2020-12-31 3:04 PM, Floyd Sense wrote:
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: WSJT-X on Raspeberry Pi: Rig Control Woes

Karza
 

On 31.12.2020 23.51, Bill Somerville wrote:
sudo adduse $USER dialout
That's > sudo adduser $USER dialout

'Kari, oh2gqc


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

dpsm64@...
 

Yes, that was the first thing I checked. /dev/ttyUSB0 is in the dialout group, as is the user pi. I've logged in and out and rebooted several times with no change.


locked Re: FT8 success after sunset

Georgina Joyce <gena@...>
 

Hello All,

Thanks for your suggestions. I just had a goal to get a number of contacts before the end of the year. As I write I have a few hours left of this year. But have given up and will look to see what my total is after writing this message.

I do not have an antenna that has an SWR problem. I have a TW1 and the TS-590SG that speaks the SWR and I am quite capable of using them.

From the responses it appears that it is just competition within crowded bands.

Thanks,

On 30 Dec 2020, at 23:27, John Morphet <jmorphet@...> wrote:

It is normal for the higher bands to go quiet and the lower bands to come
alive at night. Since 20m works well, but the lower bands do not, I would be
suspicious of how your antenna is tuned to the lower bands. Check the SWR of
the antenna at the lower bands. It could be something else, but kind of hard
to tell without being there. Maybe you can find a local ham to help you.

John, WØZI
www.w0zi.com


-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Georgina
Joyce
Sent: Wednesday, December 30, 2020 2:34 PM
To: WSJTX@groups.io
Subject: [WSJTX] FT8 success after sunset

Hello All,

I have noticed I can get contacts quite easily during daylight time,
typically 20m and on 40m. I have observed 20m goes flat slowly after sunset.
On 40m and 80m where I can hear activity during darkness, I find it nearly
impossible to get a contact. Being a blind ham I cannot observe what of the
audio levels are changed by the onset of darkness. While I understand that
changes of the layers of the ionosphere affect propagation. I do not know
what effects this is having on my audio levels. Are they excited or subdued?
If so, are both affected? Or is it nothing to do with audio levels? What can
I do to improve my chances of successful contacts during darkness? It
certainly sounds like there's a lot of activity at night. So I assume they
are usually successful but why aren't I?

Many thanks,

Georgina


Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS





Georgina


Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS


locked Re: Auto Sequencing Changed

neil_zampella
 

Vin,

it sounds like somehow you double clicked on the Tx4 radio button, which can switch from RR73 to RRR.  Double click there to switch back to RR73.

Neil, KN3ILZ

On 12/31/2020 12:31 PM, Vin wrote:
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 Uploading to LOTW and QRZ

neil_zampella
 

Ron,

have you tried asking for assistance on the hamapp.groups.io list?     I also use JT-Alert, to DXKeeper, but I have DXKeeper upload to LoTW, QRZ, eQSL, and Clublog.

That said, you could use the other part of the DXLab's suite, Spotcollector, which will also interface with DXKeeper, which will then do the necessary uploads.

http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes

Neil

On 12/31/2020 10:15 AM, Ronnie Hull wrote:
Thanks Rob but no matter what I try 
JTALERT just won’t function for me. 
I gave up trying to make it work

Ron

On Dec 31, 2020, at 10:10 AM, Rob Kivell <kk4eun@...> wrote:

 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. 

Rob kk4eun


On Dec 31, 2020, at 8:10 AM, John Morphet <jmorphet@...> wrote:



Try GridTracker. It will upload your QSOs.

https://gridtracker.org/

 

 

John, WØZI

www.w0zi.com

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Ronnie Hull
Sent: Thursday, December 31, 2020 6:14 AM
To: main@WSJTX.groups.io
Subject: [WSJTX] Auto Uploading to LOTW and QRZ

 

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











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

18201 - 18220 of 38067