Get a 32 inch 4K monitor. You will really appreciate it. Be sure to use a video card to drive all monitors to save CPU. For decoding.

73 Bill W9JJB

Hi,

new UHSDR firmware 2.12.2 has been released and tested successfully with WSJTX 2.5.0 and 2.5.2. Both the mcHF and the FT817 entry work now as expected.

73 Danilo DB4PLE

Thanks for the info Kari.

That worked for me, but I did have to change the name of the downloaded on line help file from the drop-down box in WSJT-X that saved as WSJT-X User Guide.html to wsjtx-main-2.5.2.html

John, W0GN

Perhaps I'm seeing an unintended consequence of using (skinny) fonts for WSJT-X that are not the defaults. Otherwise this is a rather vanilla Windows machine and I don't have a resizing problem in other apps. 

Anyway, we can consider the matter closed. I should ask Santa for a 28-Inch 3840x2160 monitor, assuming I can make room for it. Ham radio does seem to be headed in that direction. :) 

73 Chuck K4RGN 

Excellent point!

73
Red  K0LUZ

I agree with you about the US replies to my CQ DX, but I look at it this way:

• They may need my state, county, grid for some type of award and if I can make someone's day a little nicer, then OK.

• FTx QSOs are so short that the interruption into my CQ DX can easily be accomodated and I can restart my CQ DX.

If I need the state, country, etc and I find them on the band and they are calling CQ DX I wait until they are approximately 2-3 minutes after their starting the CQ DX cycle and then call them.  Figuring that the DX they are interested in, has already had a good chance to call them.   I hope they understand that I need them for some reason and they have made my a day a little nicer.

73

Bruce

  

• They may need my state, county, grid for some type of award and if I can make someone's day a little nicer, then OK.

• FTx QSOs are so short that the interruption into my CQ DX can easily be accomodated and I can restart my CQ DX.

WSJT-X 2.5.2 will not place IC-9100 into USB-D mode

Here is the error I get:

Hamlib error: Command rejected by the rig

icom.c(2157):icom_set_mode_with_data return(-9)

rig_set_mode: targetable retcode after set_mode=-9

rig.c(2396):rig_set_mode return(-9) while setting current VFO mode

 

When the rig is manually placed into USB-D everything seems to work fine. However, since this rig is operated remotely, manually setting the mode is an issue.

I re-installed WSJT-X 2.4 and all works as it should. Went back to 2.5.2 and its back to needing to be set manually before any TX will work.

I tried replacing libhamlib-4.dll as mentioned in a v 2.5 related post and that didn’t resolve the issue.

Please advise.

-Francis, KV5W

Hi Francis,

so I can see what is happening put the attached file into your WSJT-X configuration files directory (on MS Windows that is the same directory as the log files directory "Menu->File->Open log directory"), restart WSJT-X, carry out a minimal sequence of steps that demonstrates the issue, then quit WSJT-X. It will have created a file called WSJT-X_RigControl.log on your Windows Desktop. Send me (g4wjs <at> classdesign <dot> com) the logfile for analysis please?

Once you have sent the logfile you can delete it and the log configuration file to return to normal operation.

73
Bill
G4WJS.

On 06/11/2021 08:07, Pietro Molina wrote:

Chuck, where did you install it? May be  that in program directory the config can't be writable.

Pietro I2OIM

Pietro,

the WSJT-X settings file and other writable files are not written to the installation directories.

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.5.2.html#_file_locations

73
Bill
G4WJS.

On 06/11/2021 08:08, Pietro Molina wrote:

Try to run it as administrator

Hi Peitro,

please do not do that, it is not necessary and creates an unnecessary security risk.

73
Bill
G4WJS.

Try to run it as administrator

Chuck, where did you install it? May be  that in program directory the config can't be writable.

Pietro I2OIM

Bill and Mike, thanks for an excellent support. It was interesting to follow the "on-line" debugging. Too many "new bytes" to handle for my corrupted rig.

73 Goran SM7DLK

Is it just me, or did I miss something in the manual?  When calling CQ on MSK144 and I get a response, the software does NOT shift into QSO mode....it doesn't even act like I have received a call.

Once I double click on the callsign of the station that called me, it will go through the auto-sequence.

This is not the expected behavior.  With FT4 and FT8 the software does recognize a response to my CQ and initiates the next sequence for the QSO.

Thanks

Mark, WD4ELG

WSJT-X 2.5.2 will not place IC-9100 into USB-D mode

Here is the error I get:

Hamlib error: Command rejected by the rig

icom.c(2157):icom_set_mode_with_data return(-9)

rig_set_mode: targetable retcode after set_mode=-9

rig.c(2396):rig_set_mode return(-9) while setting current VFO mode

 

When the rig is manually placed into USB-D everything seems to work fine. However, since this rig is operated remotely, manually setting the mode is an issue.

I re-installed WSJT-X 2.4 and all works as it should. Went back to 2.5.2 and its back to needing to be set manually before any TX will work.

I tried replacing libhamlib-4.dll as mentioned in a v 2.5 related post and that didn’t resolve the issue.

Please advise.

-Francis, KV5W

Thanks Jamie.  I did check that.  

Is there any way to filter out US hams that reply to my CQ DX? Yeah, I know. There are bigger problems in life, but I'm trying to focus on DXCC.
73 Don NA6Z

John,

How can I set up the local user guide?  I'm using v. 2.5.2 on a Raspberry
Pi-4b

I do have the On Line User Guide as a file in the documents folder.  It works
if opened from the Documents folder, but I cannot seem to move it so it will
open from the Help drop-down menu in WSJT-X.

you need to copy the file as the 'root' user.
Open terminal and type following 2 commands:

sudo mkdir -p /usr/local/share/doc/wsjtx/
sudo mv ~/Documents/wsjtx-main-2.5.2.html /usr/local/share/doc/wsjtx/

"sudo" will ask you for your password, type it when requested.

HTH
73's de Kari, oh2gqc

--
Tom (LA4LN)

Bill, I appreciate the response but I'm not reducing the main window to its minimum width. Rather, I'm reducing it to about 1 cm wider than the minimum. It still won't retain that size upon restart. This is a relatively minor issue, I admit. 

73 Chuck K4RGN