Date   

locked Re: Annoyance!

bert.quijalvo@...
 

Austin,

I had the same problems with both a MacBook Pro and an iMac.  The research I did led me to the conclusion that it was a hardware issue.  It would cause output to switch to the speaker daily.  I regret to say that I didn't find a solution to the problem.
I'm now running WSJT-X on a Linux Ubuntu machine with no problems at all.

Bert
AD0DA


locked Re: Noise Only When WSJTX is running rig control #cat #705 #Cat_RigControl

dv.kp3rp@...
 

Thanks Jim. Will study and do adjustments and get back to you. Also today I realize that I am around 500ft away from big electric power distribution lines. What really puzzle me is that it is only when I turn the rig control on WSJT-X. If I leave it off there is no noise and also decodes great. Today I decide to try to transmit and I am experiencing that the connectivity between the Laptop (running on batteries) and the 705 (running on batteries too) is lost right away when it transmit. I tried with 3 different laptops (running on batteries) and it still happens.

73's KP3RP


locked Re: Noise Only When WSJTX is running rig control #cat #705 #Cat_RigControl

dv.kp3rp@...
 

Hi. The only bands that are not seen are on 1.8 Mhz, 3.5 Mhz, 144 Mhz, 440Mhz. All other bands show noise with worst in 10Mhz and 14Mhz


locked Re: Noise Only When WSJTX is running rig control #cat #705 #Cat_RigControl

dv.kp3rp@...
 

Had tried with multiple cables same luck. I just ordered a USB cable with a ferrite included. Should arrive next week. Will keep you posted.


locked Radio disconnects from USB when WSJT start transmitting

dv.kp3rp@...
 

I have a 705 connected via USB, it receives and decodes great. When WSKTX transmit it lose the connection to the PC. Had you guys seen this before?


locked Re: Reinstating Tab 2 ??

Robert Bencsko
 

I agree I LIKE TAB #2  LEAVE IT IN, people have a choice then if they want to use it.

Are you listening developers???
On 01/01/2021 7:30 AM Wayne Thomas - M0WAY <m0way@...> wrote:


Hi everyone, hope you are all keeping well.

I have just installed the 2.3.0 rc2 and found the tab 2 messages missing, i have read in the release notes that it was removed in rc1, i love the layout of tab 2 messages and wonder if it is possible to have it reinstalled?

Regards Wayne M0WAY

Bob Bencsko - W7AMC

Las Vegas, NV  DM26


locked Re: Annoyance!

Joe Subich, W4TV
 

On 2021-01-01 10:26 AM, avaughan585@... wrote:
I would like to think it was something as simple as that, but this
happens randomly at any time, not during periods of inactivity.
The windows "USB Selective Suspend" is notoriously unreliable. It
will occur for a variety of reasons unrelated to inactivity. That
is why *all* of my Windows systems have the Power Options set for
High Performance with USB Selective Suspend disabled when the computer
is plugged in (I do not use battery when running WSJTX, etc.).

73,

... Joe, W4TV


On 2021-01-01 10:26 AM, avaughan585@... wrote:
I would like to think it was something as simple as that,  but this happens randomly at any time, not during periods of inactivity.  I'll be making multiple QSOs and then suddenly, audio through speakers. It'll happen at a critical moment half way through a QSO with a rare DX station


locked Re: Annoyance!

Austin 2E0MNV
 

It happens any time, but just to clarify, it doesn't happen mid transmission.  It happens in between transmissions.  You never know when it will happen, but you hit TX and the sound goes to the speakers instead of the rig.  Restarting WSJTX fixes it, but the other thing I noticed is in the midi setup in Mac Os, the output volume for the USB Audio Codec has reset back to 100%. I usually set it to about -30dB so as not to overdrive.  I wonder if anyone has observed the same behaviour and if it is a known problem with a fix 


locked Reinstating Tab 2 ??

Wayne Thomas - M0WAY
 

Hi everyone, hope you are all keeping well.

I have just installed the 2.3.0 rc2 and found the tab 2 messages missing, i have read in the release notes that it was removed in rc1, i love the layout of tab 2 messages and wonder if it is possible to have it reinstalled?

Regards Wayne M0WAY


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

chmims@...
 

You might try using /dev/serial0 or serial1. 


charles
kg5zlh


locked Re: Annoyance!

Roger
 

On 01/01/2021 15:26, avaughan585@... wrote:
I would like to think it was something as simple as that,  but this happens randomly at any time, not during periods of inactivity.  I'll be making multiple QSOs and then suddenly, audio through speakers. It'll happen at a critical moment half way through a QSO with a rare DX station
Does it happen during CQ's as well?

73
Roger
G#4HZA


locked Re: Annoyance!

Austin 2E0MNV
 

I would like to think it was something as simple as that,  but this happens randomly at any time, not during periods of inactivity.  I'll be making multiple QSOs and then suddenly, audio through speakers. It'll happen at a critical moment half way through a QSO with a rare DX station


locked Re: Decode lag

Nc8q-mesh@gelm.net
 

Sounds to me like a huge operating system on a minimal CPU.
View system resources to see how busy the system/CPU is.
During a decode you may see one core/thread at 100%.
The decode elapsed time depends on CPU performance.
Response time is based on level of decode setting.
Deep consumes maximum CPU time.
Fast uses less.
Normal uses least.
I hope this helps,
Chuck


locked Re: Annoyance!

Floyd Sense
 

Well Joe, it may be just that simple.  Back in the spring I installed a new HP PC in the station after decades of using only home assembled PCs.  It took many days to overcome all the HP "features" and to get everything working again and in the chaos I thought I had fixed all the Windows sleep problems, but they were actually missed.  I have a total of 5 "sound card" devices, a couple of them being external USB attached and have had no problems with the others but I should have focused on the one that was having problems and didn't do that.  I've eliminated all the sleep functions and will carefully monitor things now to see if that solves the problem.  It sure would be nice if Windows had a single button or option to kill ALL system sleep functions at least for troubleshooting purposes. 

73, Floyd - K8AC


locked Re: Auto Sequencing Changed

Vin
 

Hello Karl and Neil,

 

That was it !!!!  THANK YOU !!!!!!  I double clicked on Tx4, it changed over to RR73 and now the log window opens after each QSO. 

 

I have no idea how that changed unless I accidentally double clicked Tx4 during a QSO. 

 

Again a HUGE thank you to you both!

 

HAPPY NEW YEAR !!!

 

Vin, 73

K1VC

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Karl Beckman
Sent: Thursday, December 31, 2020 8:30 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Auto Sequencing Changed

 

[Edited Message Follows]

VIN -
My install sends RR73 as the Tx4 message, and it terminates the automated contact sequence upon receiving 73 from my contact. 
Are you sure you are using the messages preloaded into tab #1, rather than tab 2 or 3? 
Whoops!  Apologies, I hadn't seen Neil's message just above mine.  Just click the Tx4 tab to switch back. 
 
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io


locked Re: FST4 modes with TS-890S - slow RF envelope rise problem #txaudio

Peter Hall, VK6HP
 

Hi Chris

Thank you for the information.  It's very useful to know of a similar problem, especially since you're using an entirely different exciter.

I condensed the story a bit for a concise description of the issue but I actually use a doubler after the transceiver output, followed by a divide-by-two flip-flop to give very symmetrical drive waveforms to the MCP1404 FET drivers and push-pull HEXFETs.  With the FST4 modes, the (Schmitt) FF clocking becomes intermittent as the RF envelope spends a long time rising through the switching point, activating the protection circuit until things have settled down. However, using the segmented memory triggering options on my scope to account for delays, I can quite clearly see the problem starts with the envelope shaping of the waveform emerging from the TS-890S.

I did wonder if the rise time issue may be a product of an over-zealous attempt to contain "key clicks" with fast FST4 but I come back to the demonstration by Rick, ON7YD, with his bare bones sound-card system:

https://groups.io/g/rsgb-lf-group/topic/77212765#11958

However, perhaps if there's a capable transceiver selected, there's an attempt made to slow things down.  Just my speculation, of course.  Anyway, with the FST4 modes aimed at LF/MF users, it'd obviously be good to have those modes compatible with typical hardware.

73, Peter.


locked Re: Auto Sequencing Changed

Karl Beckman WA8NVW - NNV5BH
 
Edited

VIN -
My install sends RR73 as the Tx4 message, and it terminates the automated contact sequence upon receiving 73 from my contact. 
Are you sure you are using the messages preloaded into tab #1, rather than tab 2 or 3? 
Whoops!  Apologies, I hadn't seen Neil's message just above mine.  Just click the Tx4 tab to switch back. 
 
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io


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

Joel
 

If you can get into the settings tabs for WSJT-x make certain the baud rate matches that of the RPi serial/usb cable as well as that of the radio..... I’m using a Pi to run an Elecraft KX2. The radio settings match the WSJT-x in setup.....

Good luck
Joel






On Dec 31, 2020, at 4:46 PM, 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!




locked Re: FT8 success after sunset

Dave
 

Yes,

Keep in mind that the band is very busy and a QRP signal is often lost.

Just today I was on 20 watching South Africa pop up but not able to work it.

Dave KC3AM

On 12/31/2020 17:10, Georgina Joyce wrote:
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






--
Hams should be seen as well as heard, 73, Dave KC3AM


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

Karza
 

Hi there,

On 31.12.2020 19.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

1) Have you tried to specify the serial baudrate with the "-s" command line option?

2) Have you considered compiling WSJT-X from the source-tarball?

https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.2.2.tgz

That way you would get WSJT-X with statically linked Hamlib.

If you do this, then please note that the model number for IC-7200 is 3061.

About a year ago I compiled WSJT-X on Pi 4 from source tarball and it worked fine.

73's & HNY de Kari, oh2gqc

18181 - 18200 of 38067