|
Locked
Re: WSJT-X 2.5.4 Start-up crash
#Windows10
Michael Black
Rename C:\Users\[username]\AppData\Local\WSJT-X
toggle quoted message
Show quoted text
Then start WSJT-X. It will be a new configuration. Sounds like something got corrupted. Please send the WSJT-X.ini file that's in the old directory. Mike W9MDB On Sunday, January 23, 2022, 01:17:48 PM CST, spillo84topp@... <spillo84topp@...> wrote:
Hello to eweryone, i have installed WSJT-X 2.5.4 on my Windows 10 PC but at the 1st start-up after few secondes the program will close, i don't have the time to set the com port of my rig, can anyone help me? See the screen shot of the errors: [url=https://imgbb.com/][img]https://i.ibb.co/GsFCqy6/Cattura.png[/img][/url] [url=https://imgbb.com/][img]https://i.ibb.co/dfWYhrM/Cattura2.png[/img][/url] |
|
|
|
Locked
Re: WSJT-X crashes witrh error messages not understood
#stopped_working
Dick McClain
Yes, Laurie, that fixed my startup errors. Thank you. I should have thought of that.
73, Dick, KD4S |
|
|
|
neil_zampella <neilz@...>
I'm fairly sure that it would go in the same directory that you find the
toggle quoted message
Show quoted text
log files. Just open that directory using the File -> Open log directory. It should work the same on the Mac as it would on Windows. Neil, KN3ILZ On 1/23/2022 1:42 PM, florida randy wrote:
I'd like to update the cty.dat file but I'm certain how to do it on macOS. please advise. thanks |
|
|
|
Locked
Re: FT8 F/H no reports
#WSJTX_config
Jim Brown
On 1/23/2022 11:06 AM, J28PJ Jean-Philippe wrote:
I understand. I will continue to use ft4 and ft8 without F/H.Do the conditions of your license require /P? If not, don't use it! Simply by including your grid in a CQ tells callers all they need to know about your location. 73, Jim K9YC |
|
|
|
I'd like to update the cty.dat file but I'm certain how to do it on macOS. please advise. thanks
|
|
|
|
Locked
Re: FT8 F/H no reports
#WSJTX_config
Bruce Jungwirth
I worked 3X2021 on 1/9/2022 FT8 on 17m. It was not a F/H contact. The QSO went normal, and was a verified match on LOTW later that same day.
toggle quoted message
Show quoted text
Bruce. K0SON On Jan 23, 2022, at 11:13 AM, J28PJ Jean-Philippe <j28pj@...> wrote: 
|
|
|
|
Locked
Re: WSJTX_LOG issues with 2 calls.
#logging
#WSJTX_config
Karza <kari.sillanmaki@...>
Hi Mike,
On 22.1.2022 17.59, Mike G8NSZ wrote: H All,The log file name needs to have ".adi" suffix, ie "wsjtx_log.adi", not "wsjtx_log". If you are on Windows, make sure that Bill Gates has not appended some other suffix, such as ".txt" or something. 73's de Kari, ohqgqc |
|
|
|
Locked
Re: WSJTX_LOG issues with 2 calls.
#logging
#WSJTX_config
Did you lose the .adi file name extension in the process? The full file name should be wsjtx_log.adi . One of the most stupid decisions made by Microsoft (IMO) was at some point to decide to hide extensions for known file types by default. You can turn this behavior off and I recommend doing so if you want to use your computer as more than just an interenet appliance.
73 -Jim NU0C On Sat, 22 Jan 2022 07:59:21 -0800 "Mike G8NSZ" <gm4nsz@...> wrote: Once I returned home I did the same in reverse, so to speak, by saving the GM log as _GM and replacing the original in the log folder and renaming it as WSJTX_LOG. However, the programme does not appear to be reading the log as all the new call/new zone/new square colours which I know I have worked before are all there. Is that how it shows previously worked stations? |
|
|
|
Locked
WSJT-X 2.5.4 Start-up crash
#Windows10
spillo84topp@...
Hello to eweryone, i have installed WSJT-X 2.5.4 on my Windows 10 PC but at the 1st start-up after few secondes the program will close, i don't have the time to set the com port of my rig, can anyone help me?
See the screen shot of the errors: [url=https://imgbb.com/][img]https://i.ibb.co/GsFCqy6/Cattura.png[/img][/url] [url=https://imgbb.com/][img]https://i.ibb.co/dfWYhrM/Cattura2.png[/img][/url] |
|
|
|
Locked
Re: FT8 F/H no reports
#WSJTX_config
J28PJ Jean-Philippe <j28pj@...>
Hello,
toggle quoted message
Show quoted text
I understand. I will continue to use ft4 and ft8 without F/H. It's slower for stations that want to make contact but I have no choice. 73 jean philippe -----Message d'origine-----
De : main@WSJTX.groups.io <main@WSJTX.groups.io> De la part de Joe Subich, W4TV Envoyé : dimanche 23 janvier 2022 17:31 À : main@WSJTX.groups.io Objet : Re: [WSJTX] FT8 F/H no reports #WSJTX_config Jean-Phillipe, Unfortunately, that is one of the limitations with non-standard and compound callsigns and F/H mode. Non-standard callsigns force the messages into free text mode with its limited message size. Your sent report (and any grid) is being truncated - particularly when using /p! 73, ... Joe, W4TV On 2022-01-23 10:54 AM, J28PJ Jean-Philippe wrote: I encounter a bug with the FT8 F/H mode. My correspondents cannot |
|
|
|
Locked
Re: FT8 F/H no reports
#WSJTX_config
Joe Subich, W4TV
Jean-Phillipe,
toggle quoted message
Show quoted text
Unfortunately, that is one of the limitations with non-standard and compound callsigns and F/H mode. Non-standard callsigns force the messages into free text mode with its limited message size. Your sent report (and any grid) is being truncated - particularly when using /p! 73, ... Joe, W4TV On 2022-01-23 10:54 AM, J28PJ Jean-Philippe wrote:
I encounter a bug with the FT8 F/H mode. My correspondents cannot receive my reports or other RR73. This is the case for my callsign 3x2021 or for 3x2021/p No problem in FT4 it seems. Any of you have an idea? Thanks in advance 73 jean philippe 3X2021 Note: this callsign was given to me without my asking. Guinea is currently ruled by a transitional government since the September coup. I can't see myself asking for a change of call sign at the moment :) |
|
|
|
Locked
Re: Rig control error
#wsjt-x-crashing
#Windows10
#FlexRadio
Michael Black
Please place this file in C:\Users\[username]\AppData\Local\WSJT-X
toggle quoted message
Show quoted text
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 Restart WSJT-X and duplicate the problem. Shut down WSJT-X Then send me the WSJT-X_RigControl.log file that will be in the same location. Mike W9MDB On Sunday, January 23, 2022, 11:19:03 AM CST, Michael Black via groups.io <mdblack98@...> wrote:
Please place this file in C:\Users\[username]\AppData\Local\WSJT-Xhttps://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 Restart WSJT-X and duplicate the problem.Shut down WSJT-X Then send me the WSJT-X_RigControl.log file that will be in the same location. Mike W9MDB On Sunday, January 23, 2022, 11:12:10 AM CST, John Caulfield <johnradioham@...> wrote: Windows 10, Flex 6400, Version 2.5.4 WSJT-X, All works fine for a while (five minutes or so) then I get the Rig Control Error with the following detail: Hamlib error: IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) rig.c(1047):rig_open return(-6) IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) iofunc.c(361):port_close return(0) while opening connection to rig Only programs running are Flex SDR and WSJTX - no add-ins. Ugraded to the most recent versin of WSJT-X in hopes that would fix it but same thing happened. Any help would be greatly appreciated. John K0FUZ |
|
|
|
Locked
Re: Rig control error
#wsjt-x-crashing
#Windows10
#FlexRadio
Michael Black
Please place this file in C:\Users\[username]\AppData\Local\WSJT-Xhttps://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
toggle quoted message
Show quoted text
Restart WSJT-X and duplicate the problem.Shut down WSJT-X Then send me the WSJT-X_RigControl.log file that will be in the same location. Mike W9MDB On Sunday, January 23, 2022, 11:12:10 AM CST, John Caulfield <johnradioham@...> wrote:
Windows 10, Flex 6400, Version 2.5.4 WSJT-X, All works fine for a while (five minutes or so) then I get the Rig Control Error with the following detail: Hamlib error: IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) rig.c(1047):rig_open return(-6) IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) iofunc.c(361):port_close return(0) while opening connection to rig Only programs running are Flex SDR and WSJTX - no add-ins. Ugraded to the most recent versin of WSJT-X in hopes that would fix it but same thing happened. Any help would be greatly appreciated. John K0FUZ |
|
|
|
Locked
Re: Rig control error
#wsjt-x-crashing
#Windows10
#FlexRadio
Michael Black
Does this help?
toggle quoted message
Show quoted text
https://community.flexradio.com/discussion/7897139/seting-up-wsjt-x-with-6400m Mike W9MDB On Sunday, January 23, 2022, 11:12:10 AM CST, John Caulfield <johnradioham@...> wrote:
Windows 10, Flex 6400, Version 2.5.4 WSJT-X, All works fine for a while (five minutes or so) then I get the Rig Control Error with the following detail: Hamlib error: IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) rig.c(1047):rig_open return(-6) IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) iofunc.c(361):port_close return(0) while opening connection to rig Only programs running are Flex SDR and WSJTX - no add-ins. Ugraded to the most recent versin of WSJT-X in hopes that would fix it but same thing happened. Any help would be greatly appreciated. John K0FUZ |
|
|
|
Locked
FT8 F/H no reports
#WSJTX_config
J28PJ Jean-Philippe <j28pj@...>
I encounter a bug with the FT8 F/H mode. My correspondents cannot receive my reports or other RR73. This is the case for my callsign 3x2021 or for 3x2021/p No problem in FT4 it seems. Any of you have an idea? Thanks in advance 73 jean philippe 3X2021 Note: this callsign was given to me without my asking. Guinea is currently ruled by a transitional government since the September coup. I can't see myself asking for a change of call sign at the moment :) [Image][cid:image001.png@...] [cid:image003.png@...]
|
|
|
|
Locked
Rig control error
#wsjt-x-crashing
#Windows10
#FlexRadio
John Caulfield <johnradioham@...>
Windows 10, Flex 6400, Version 2.5.4 WSJT-X,
All works fine for a while (five minutes or so) then I get the Rig Control Error with the following detail: Hamlib error: IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) rig.c(1047):rig_open return(-6) IO error network.c(441):network_close return(0) iofunc.c(361):port_close return(0) iofunc.c(361):port_close return(0) while opening connection to rig Only programs running are Flex SDR and WSJTX - no add-ins. Ugraded to the most recent versin of WSJT-X in hopes that would fix it but same thing happened. Any help would be greatly appreciated. John K0FUZ |
|
|
|
Locked
WSJTX_LOG issues with 2 calls.
#logging
#WSJTX_config
H All,
I have an issue with, I think, WSJT-X not reading the log file caused by me removing, renaming, reinstalling the file into the log folder. I changed my callsign when I operated from a holiday cottage in Scotland. So, I thought, I will copy and paste my G8 logfile to another location and rename it _G8. I then deleted that log from the folder using the delete command in the dropdown, then changed the callsign in settings to GM8. Once I returned home I did the same in reverse, so to speak, by saving the GM log as _GM and replacing the original in the log folder and renaming it as WSJTX_LOG. However, the programme does not appear to be reading the log as all the new call/new zone/new square colours which I know I have worked before are all there. Is that how it shows previously worked stations? What did I do wrong, or can the programme not cope with what I have done? Many thanks. 73 Mike - G8NSZ |
|
|
|
Locked
New hits only (not new & unconfirmed) Alert
#WSJTX_config
Is there anyway of getting just New hit alerts instead of new + unconfirmed?? DXCC is checked but I don't want to get notifications on every unconfirmed QSO.
Mike |
|
|
|
Locked
Re: Kenwood TS-2000 - no TX-NF in Versions above 2.3.1
#IssueReport
#Kenwood
#linux
#Cat_RigControl
#txaudio
Michael Black
Hamlib 4.5 is due Mar 1st.
toggle quoted message
Show quoted text
For now you can compile the latest yourself and use rigctld from the latest version and have WSJT-X use Hamlib NET rigctl. I think this problem was fixed. At least I haven't heard any complaints recently. http://n0nb.users.sourceforge.net/ Mike W9MDB On Sunday, January 23, 2022, 08:53:55 AM CST, Stefan U. Hegner <db4st@...> wrote:
Hi there, ... 3 months later, now at WSJT-X 2.5.4 ... Kenwood TS-2000 with back-panel NF-in does not send a signal, despite active PTT via extra serial RTS. TX Moni also has no signal for playback. Briefly again my setup, that works perfectly up to WSJT-X 2.3.1 on Ubuntu 20.04 LTS: * rigctld (using the hamlib delivered with wstjtx) with "-m 2014" * wsjt-x uses net rigctl, second serial port with RTS for PTT ... any news on this or additonal ideas? Or should I rather post this in parallel to the hamlib-list, as we are moving from hamlib 4.2 to hamlib 4.5? Current status-quo from Nov was: Am 01.11.21 um 20:04 schrieb Stefan U. Hegner: Am 01.11.21 um 19:58 schrieb Bill Somerville:Vy 73On 01/11/2021 18:53, Stefan U. Hegner wrote:That sounds like a plan.Am 01.11.21 um 19:17 schrieb Bill Somerville:the Hamlib linked into WSJT-X is involved as well as rigctld, it isOn 01/11/2021 18:00, Stefan U. Hegner wrote:Maybe I wasn't clear on this one: It's the hamlib rigctld that isUp to WSJT-X 2.3.1 all works fine and as desired. However if IHamlib is statically linked into WSJT-X in our pre-built Linux Stefan. -- Stefan U. Hegner <db4st@...> * * * DB4ST --- German Ham Radio Station D-32584 Löhne ----- Locator JO42IE * * * GPG-Key | C3CC 23A4 FBA8 622B 48AE F-Print | 4F19 D0EE E39E ABDC 2BCE |
|
|
|
Locked
Kenwood TS-2000 - no TX-NF in Versions above 2.3.1
#IssueReport
#Kenwood
#linux
#Cat_RigControl
#txaudio
Stefan U. Hegner
Hi there,
... 3 months later, now at WSJT-X 2.5.4 ... Kenwood TS-2000 with back-panel NF-in does not send a signal, despite active PTT via extra serial RTS. TX Moni also has no signal for playback. Briefly again my setup, that works perfectly up to WSJT-X 2.3.1 on Ubuntu 20.04 LTS: * rigctld (using the hamlib delivered with wstjtx) with "-m 2014" * wsjt-x uses net rigctl, second serial port with RTS for PTT ... any news on this or additonal ideas? Or should I rather post this in parallel to the hamlib-list, as we are moving from hamlib 4.2 to hamlib 4.5? Current status-quo from Nov was: Am 01.11.21 um 20:04 schrieb Stefan U. Hegner: Am 01.11.21 um 19:58 schrieb Bill Somerville:Vy 73On 01/11/2021 18:53, Stefan U. Hegner wrote:That sounds like a plan.Am 01.11.21 um 19:17 schrieb Bill Somerville:the Hamlib linked into WSJT-X is involved as well as rigctld, it isOn 01/11/2021 18:00, Stefan U. Hegner wrote:Maybe I wasn't clear on this one: It's the hamlib rigctld that isUp to WSJT-X 2.3.1 all works fine and as desired. However if IHamlib is statically linked into WSJT-X in our pre-built Linux Stefan. -- Stefan U. Hegner <db4st@...> * * * DB4ST --- German Ham Radio Station D-32584 Löhne ----- Locator JO42IE * * * GPG-Key | C3CC 23A4 FBA8 622B 48AE F-Print | 4F19 D0EE E39E ABDC 2BCE |
|
|
