Date   

Re: FT8 F/H no reports #WSJTX_config

Joe Subich, W4TV
 

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 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 :)


Re: Rig control error #wsjt-x-crashing #Windows10 #FlexRadio

Michael Black
 

Please place this file in C:\Users\[username]\AppData\Local\WSJT-X
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=yahoo.com@groups.io> 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@gmail.com> 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


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
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@gmail.com> 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


Re: Rig control error #wsjt-x-crashing #Windows10 #FlexRadio

Michael Black
 

On Sunday, January 23, 2022, 11:12:10 AM CST, John Caulfield <johnradioham@gmail.com> 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


Re: Request for views on equipment offered free threads #EquipmentOfferedFree

Jeff Stillinger
 

I think that it would be alright only if the "product" is directly related to WSJT-X.  For example:  A person who makes free scripts available to assist in building WSJT-X.  Radios, sound cards, dummy loads, antennas, etc...  already have groups where the item can be listed.   No need to reinvent the wheel.

On 1/20/22 16:30, Roger wrote:
Whilst for sale advertisements are not allowed in the group free offers are not specifically banned.

I could be interested in hearing members views about allowing free offers or not?

Threads using #EquipmentOfferedFree are automatically deleted after a week, are not retained in the archive, and fully moderated for now.

What are members' views?

73
Roger
moderator



--
Jeff Stillinger
KB6IBB Laboratories, Wylie Texas
http://kb6ibb-15.ham-radio-op.net/Ham-Radio/


FT8 F/H no reports #WSJTX_config

J28PJ Jean-Philippe
 

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@01D81071.68F90A10] [cid:image003.png@01D81071.742DB110]


John Caulfield
 

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


WSJTX_LOG issues with 2 calls. #logging #WSJTX_config

Mike G8NSZ
 

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


New hits only (not new & unconfirmed) Alert #WSJTX_config

MikeMc
 

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


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.
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@darc.de> 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:
On 01/11/2021 18:53, Stefan U. Hegner wrote:
Am 01.11.21 um 19:17 schrieb Bill Somerville:
On 01/11/2021 18:00, Stefan U. Hegner wrote:

Up to WSJT-X 2.3.1 all works fine and as desired. However if I
upgrade to 2.4.x or 2.5.x I get the following problem:

Hitting PTT won't put any NF trough the TRX and hence send no HF
signal.
Hamlib is statically linked into WSJT-X in our pre-built Linux
packages, so you must re-build WSJT-X to change the Hamlib version.
Maybe I wasn't clear on this one: It's the hamlib rigctld that is
manually started and listens for commands from wsjtx via the net api.
the Hamlib linked into WSJT-X is involved as well as rigctld, it is
that which communicates with rigctld. I suspect the issue may have
been fixed already. Understood on not wanting to rebuild WSJT-X with
a more recent Hamlib version, I suggest you stay with WSJT-X v2.3.1
until a new version is available, you will not have long to wait.
That sounds like a plan.

Actually that was the plan after 2.4.1. - I waited for 2.5.1 ... and
as this was not yet fixed, I started asking my questions here.
Vy 73

Stefan.

--
Stefan U. Hegner    <db4st@darc.de>
              * * *
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


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:
On 01/11/2021 18:53, Stefan U. Hegner wrote:
Am 01.11.21 um 19:17 schrieb Bill Somerville:
On 01/11/2021 18:00, Stefan U. Hegner wrote:

Up to WSJT-X 2.3.1 all works fine and as desired. However if I
upgrade to 2.4.x or 2.5.x I get the following problem:

Hitting PTT won't put any NF trough the TRX and hence send no HF
signal.
Hamlib is statically linked into WSJT-X in our pre-built Linux
packages, so you must re-build WSJT-X to change the Hamlib version.
Maybe I wasn't clear on this one: It's the hamlib rigctld that is
manually started and listens for commands from wsjtx via the net api.
the Hamlib linked into WSJT-X is involved as well as rigctld, it is
that which communicates with rigctld. I suspect the issue may have
been fixed already. Understood on not wanting to rebuild WSJT-X with
a more recent Hamlib version, I suggest you stay with WSJT-X v2.3.1
until a new version is available, you will not have long to wait.
That sounds like a plan.

Actually that was the plan after 2.4.1. - I waited for 2.5.1 ... and
as this was not yet fixed, I started asking my questions here.
Vy 73

Stefan.

--
Stefan U. Hegner <db4st@darc.de>
* * *
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


Re: Power amplifier RX/TX relay damage-high SWR -From Halt TX during Q65-60B TX #Q65

Reino Talarmo
 

Since arching can occur when a contact is made or broken, I was wondering if using the Halt TX button in the middle of a high power 60 sec TX happens too fast?
Hi Richard,

Unless you have a long latency in your audio string this should not be possible. Well, I assume that PTT signaling is initiated only after power down tapering at the end of power off.

73, Reino OH3mA


Re: WSJTX Rus interface #WSJTX_config

Michael Black
 

Given that Bill Sommerville created the original and he was a Great Britain person you should use wsjtx_en_GB.ts
Mike W9MDB

On Saturday, January 22, 2022, 09:10:31 PM CST, Victor R3BB via groups.io <r3bb=mail.ru@groups.io> wrote:

Hello! What should be taken as a basis
(template wsjtx_??.ts) for translating
the interface into Russian (wsjtx_ru.ts) ?
Victor (R3BB) 73!


Power amplifier RX/TX relay damage-high SWR -From Halt TX during Q65-60B TX #Q65

G Richard Kreuter
 

I have had my Tajfun 1000 432MHz PA shutdown-zero power out-during TX of a string of EME Q65-60B CQ's. I had been running 425W out and seeing 2.2W REV. Antenna array tested 1.1SWR and 50 ohms. Tajfun memory showed shutdown due to high SWR. TX/RX relay was inspected, and pitting was found on the TX contact side. Since arching can occur when a contact is made or broken, I was wondering if using the Halt TX button in the middle of a high power 60 sec TX happens too fast?


moderated Re: Can't update Tx2 signal report #QSO_practices

Mike Koralewski K8VA
 

Gary,
I agree...it just doesn't make any sense to fret over SNR numbers. SURE they would be better IF the transmitting station was stronger into the receiving stations inherent noise level, or the noise level on each other's receiving end was lower.
But that's the challenge of ham radio. A completed contact is a completed contact.
73 Mike K8VA


WSJTX Rus interface #WSJTX_config

Victor R3BB
 

Hello! What should be taken as a basis
(template wsjtx_??.ts) for translating
the interface into Russian (wsjtx_ru.ts) ?
Victor (R3BB) 73!


Re: Request for views on equipment offered free threads #EquipmentOfferedFree

MikeMc
 

As long as it's one ham posting a personal free offer to hams, no issue. Don't want to see a bunch of free offers from McDonalds.
Don't see any issue with them being deleted after one week, if no one has taken it up then no one wants it. If it was claimed and the author never deletes the post then it just junks up the board. And they should be moderated, don't want to see a motorcycle being offered.


Re: Two WSPR self decodes with 30-50 dB SNR delta #WSPR

Reino Talarmo
 

Hi Scott,
Is your mains frequency 60 Hz. If so, then another possibility is that your
WSPR transmitter DC voltage contains a bit 120 Hz brum and that amplitude
modulates your transmitter signal generating sidebands at 120 Hz difference.

You can check that by looking your signal at wsjt-x waterfall.
73, Reino OH3mA

-----Original Message-----
From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of
William Smith
Sent: 22. tammikuutata 2022 22:20
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] Two WSPR self decodes with 30-50 dB SNR delta #WSPR

Rx overload, try turning down the RF gain on your 7300, or adding 20-30db
attenuation in the Rx antenna lead.

73, Willie N1JBJ

On Jan 22, 2022, at 2:36 PM, Scott Eckert via groups.io
<sbeckert=verizon.net@groups.io> wrote:
I'm testing my .2W 17m WSPR transmitter using a local antenna and
receiving with my 7300. I'm running WSJT-X 2.5.4 and every decode period
shows two entries with 30-50 dB difference in SNR (e.g., one will be -13 and
the other +23. One was even +24 and -29) . The two decodes show about 130Hz
frequency delta. WSPR reporting seems normal. Any ideas on what's going on?
Thx. Scott


Re: Two WSPR self decodes with 30-50 dB SNR delta #WSPR

William Smith
 

Rx overload, try turning down the RF gain on your 7300, or adding 20-30db attenuation in the Rx antenna lead.

73, Willie N1JBJ

On Jan 22, 2022, at 2:36 PM, Scott Eckert via groups.io <sbeckert=verizon.net@groups.io> wrote:
I'm testing my .2W 17m WSPR transmitter using a local antenna and receiving with my 7300. I'm running WSJT-X 2.5.4 and every decode period shows two entries with 30-50 dB difference in SNR (e.g., one will be -13 and the other +23. One was even +24 and -29) . The two decodes show about 130Hz frequency delta. WSPR reporting seems normal. Any ideas on what's going on? Thx. Scott


Two WSPR self decodes with 30-50 dB SNR delta #WSPR

Scott Eckert
 

I'm testing my .2W 17m WSPR transmitter using a local antenna and receiving with my 7300. I'm running WSJT-X 2.5.4 and every decode period shows two entries with 30-50 dB difference in SNR (e.g., one will be -13 and the other +23. One was even +24 and -29) . The two decodes show about 130Hz frequency delta. WSPR reporting seems normal. Any ideas on what's going on? Thx. Scott

1 - 20 of 31319