Hi Dwight
in times of CW (what was this?) we had 2,5 minutes TX periods in EME or 5 minutes in high speed CW with full power. A QSO easily lasted up to one our ... Once a 70cm meteorscatter QSO I could complete after 4 hours and I was a very happy guy. But nowadays we live in sort of a "highspeed society" ....
--
---

Christoph Petermann DF9CY

JO54al (Baltic Sea Coast)
7 MHz Dipole @9,5m - 400w

50MHz 6 ele OP-DES Yagi - 270w

144MHz 9 ele DK7ZB - 330w
432MHz 23 ele - 35w

https://www.df9cy.de

This is the map of the current Beacon candidates https://www.google.com/maps/d/u/1/edit?mid=14X0GJ4vSQ7D8piZfuHDs902Y9tINuPqB&usp=sharing nothing finalized yet

Where do I find the setting to enable the transfer of a station listed in JtAlert window
To the WSJT-X generate message window ?

Both downloaded version and compiled on computer crash after approx 20 minutes with the following error:

Jimmy
You have not indicated what version of HRD you are using. Also if you click on tune does the radio go in to TX?
It would be most helpful to know what radio you are using??
Neil   N4FN

Hi All--

There is no audio when I transmit. My PC keys my xcvr correctly, but without audio. I am decoding correctly, so I know my audio setup is at least partially correct.

No audio on transmit.

I use a Ham Radio Deluxe and a FTdx3000 with the internal CODECs. They were working fine until I tried to install another device that used the CODECs. It seems to have corrupted the Yaesu drivers and wsjt-x stopped sending audio. After reloading the Yaesu drivers many, many times, wsjt-x now receives audio (and decodes) but doesn't transmit audio.

The CODECs are selected with the soundcard in wsjt-x and DM780 (the digital modes program in HRD.) The internal speaker and microphone are selected as the devices for all other applications.

I have been at this for 5 days (no, truly) and I cannot get wsjt-x to transmit audio.

Does anyone have a fix?

Bill K1NS

FYI:

On Raspberry OS 64 bit with PI 4 hardware, I’m getting a segmentation fault (and wsjtx stops running) whenever I try to change bands on my Elecraft K2.  This fault does NOT occur on my Yaesu transceiver.  I’m connected to the K2 using FLrig.

FLrig works fine with FLdigi on either radio.

Hi Walt,

you may be able to help with diagnosis as follows:

Start WSJT-X from a terminal like this:

gdb wsjtx

If that errors out because gdb is not installed then install gdb (sudo apt install gdb). Then do what is required to cause the crash, gdb should trap the signal, at the (gdb) prompt type:

bt

and hit ENTER. Report back with what gets printed. Quit gdb with q then ENTER.

73
Bill
G4WJS.

On 03/06/2021 18:17, jaime r wrote:

Hello all,
I yesterday started to use multiple (two) instances of wsjtx on my raspberry pi.
One connected to a IC7300 and another one to a IC9700.
I am starting with wsjtx --rig-name 7300 or 9700.
Well, if i start one single instance, decodes show the right colors but if I start it with the --rig-name wsjtx does not show colors, not even wrong colors, just the green one if I select CQ on green but without considering the log.
I have copied the .adi file to the WSJT-X - 7300 folder, there wsjtx shows the .adi file and clicked to rescan the adi file in the setup->color tab jut nothing happens.
Does anybody has a clue for me?
Thank you!
Jaime, EA4K

Hi Jamie,

have you checked the "Settings->General->Show DXCC, grid, and worked before status" option?

BTW, rather than copy your WSJT-X log file to each instance's log files directory, make a symlink so they all share the same file.

73
Bill
G4WJS.

FYI:

On Raspberry OS 64 bit with PI 4 hardware, I’m getting a segmentation fault (and wsjtx stops running) whenever I try to change bands on my Elecraft K2.  This fault does NOT occur on my Yaesu transceiver.  I’m connected to the K2 using FLrig.

FLrig works fine with FLdigi on either radio.

All of a sudden the program quit transmitting even though it shows a cq being transmitted and I am a complete idiot when it come to these computers, I have installed WSJT-X and HRD and neither one will key the radio and my transmit is working.

I also sent this via the developers list.  Just a FYI here.

 

WSJT-X 2.5.0  rc1

Windows 10

 

I was working some MA to FL Es on 50.313 on FT8 and all worked great.  No problems at all.

Then I switched to Q65-30A on 50.275 and called four CQs.  No one around.

Then I switched back to FT8 on 50.313 and the FT8 signals were not decoding.

I stopped WSJT-X and restarted it and all was fine.  FT8 was decoding as normal.

TIME.IS shows the time as exact.

This is repeatable 100%.

 

So, after a FT8-Q65-FT8 mode change sequence, FT8 stops decoding.  A restart fixes it.  It is repeatable 100%.

 

73,

Joe, K1YOW

I am running on OS X and in the Reporting tab for UDP Server under outgoing interfaces, the local interface (lo0) is selected by default which is fine and probably what most people need. However I want to deselect it and select another interface to use. This appears to work fine and data only goes out the one interface until you visit any part of the configuration again or reload the configuration. At that point the local interface is again auto selected in addition to the other interface I want to use and data is going out both of them. I appears the local preference is overriding the setting chosen by the user.

Jeff
K9KLD

Dave,

I am running the latest release.On the rcv pane and am getting worked before
in read. This is on the Windows 7 computer. On the Windows 10 computer it's
not showing this.
I have WSJT parameters set the same.
Any thoughts and help would be appreciated.

do you have the same logfile ( wsjtx_log.adi ) on both computers?
WSJT-X uses this logfile for "B4" information.

73's de Kari, oh2gqc