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

I haven’t used it for a while but the JTDX program will display what you want. I don’t know if it up to date with WSJT-X revisions.

Bill
WB6JJJ

Equipment tends to overheat with two minute transmissions. It also tends to be rather boring to have QSOs that take that long.

Dwight
Ko6fe
CN71

On Wed, Jun 2, 2021 at 10:05 AM, Hasan Schiers N0AN wrote:120E is magical, but way long and hard on equip

Can you expand on this comment. I haven’t tried the mode yet but I have 6m antennas up. 
 
--
Don
W6CZ/W6ZB
DM07bk

JoAnn,

Is there a way to have the left side display show the country of the station
even when it is not sending a CQ?
JoAnnAB8YZ

no, there's no way to do that other than by modifying the program.
The country lookup would also slow down the decoding.

73's de Kari, oh2gqc

Maybe, but you need an hor glass to watch PSK reporter....DX Maps refreshes on the minute...

TK, K7TRK

Great info, Hasan! Many thanks.

73, Jim K9YC

Hi Steve,

On Wed, Jun 2, 2021 at 10:05 AM, K5DOG wrote:

The ability to change TX DF in Map65 would be very helpful on 23 cm in particular, so that a reply on the caller's echo could be accommodated.
TX DF can "apparently" be changed in the lower part of the Wide Graph window by use of the right mouse button, but experiments here tell me that the actual TX DF (audio frequency) does not change.

Several points are relevant here.  As I'm sure you know, MAP65 does not do any kind of rig control.  It has never allowed a user to change the audio frequency sent to the output soundcatrd channel.  Yes, you can right-click and change the frequency of the red Tx marker, but all that has even done is to send requested Tx frequency information to the azel.dat file, where a user-supplied rig-control program might make use of it. 

MAP65's notions about signal frequency, DF, etc., are rather different from those of WSJT-X.  As noted in the "Quick-Start Guide to WSJT-C 2.5.0 and MAP65 3.0.0", we are not planning large changes or additions to MAP65. Instead, we plan to import the most important MAP65 capabilities into WSJT-X, including wideband reception with polarization diversity.  Of course, rig-control convenience features of the sort you mention are already present in WSJT-X.

Please report on your experiences with WSJT-X 2.5.0-rc1 and MAP65 3.0.0-rc1, after you have been using them for a bit.  We value your input!

  -- 73, Joe, K1JT

On the Kenwood TS-2000 when using a Signalink with built-in VOX to operate with WSJT-X software, you CANNOT use the CAT feature to provide PTT into the radio.  The software MUST be set to VOX, and the correct transceiver must be selected on the radio, either to HF+6 or 144/440 MHz.. If the wrong radio side is selected, the CAT test will fail (My TS2000 has the latest firmware update 1.12)

NOTE:  As I recall, version 2.4.0 GA uses a new release of HamLib and others have reported errors that were not caught in early testing.  If you still can't get transmit to work after changing the PTT method to VOX, reply back to this group for additional troubleshooting assistance. 
--
Karl  WA8NVW  OH
WA8NVW@...
in WSJTX@groups.io