Date   

locked Re: another WSJT-X question #FT8 #GeneralGroupInfo

Joel
 

Glad it helped. I was completely wrong about FT8 on 60M - that’s what happens when you haven’t tried to use it in a couple of years. Check out this thread for an explanation on how to use FT8 on 60M:


Joel

On Apr 4, 2021, at 7:19 PM, w1av via groups.io <bobruzzo@...> wrote:

OK thanks.....I did notice that when I change freq to other FT8 freqs in other bands, the box is black again. There is nothing in the manual I could find to explain this.



locked Re: another WSJT-X question #FT8 #GeneralGroupInfo

w1av
 

OK thanks.....I did notice that when I change freq to other FT8 freqs in other bands, the box is black again. There is nothing in the manual I could find to explain this.


locked Re: #FT4 won't send TX5 #FT4

Martin G0HDB
 

On Sun, Apr 4, 2021 at 05:52 PM, Steve Lund wrote:
Martin,
 
That was the problem, but it is also a bug.
 
I had been listening for C92RU on 80m FT8 F/H and saw a spot for ZL7DX on 20m FT4.
 
I moved to 20m and set mode to FT4.  [Remainder snipped]
Hi again Steve, glad that you found the cause of the issue.

You might want to try setting up different configurations for standard FT8 operation, FT8 Hound operation, and standard FT4 operation.  By using separate configs you can specify exactly which settings you want to use for each different operating mode and scenario, so the situation you encountered with WSJT-X remaining in Hound mode when you changed mode from FT8 to FT4 should never arise.  Having a dedicated config for FT8 Hound mode also enables you to define only the set of frequencies that are used in F/H mode - there's no danger of inadvertently operating as a Hound on the standard FT8 (or FT4!) frequencies.

Switching between configs is as fast as, and potentially faster than, changing from one mode to another, eg. FT8 to FT4, within a single config such as the default one.  All you need to do is, from the Configurations option in the main menu, is point at whichever of your pre-defined configs you want to use and then click on 'Switch to'.  The WSJT-X app will close and then restart in the newly-selected config; this takes maybe 1-2secs on my WIn10 system.

73
--
Martin G0HDB


locked Re: #FT4 won't send TX5 #FT4

Steve Lund
 

Martin,

That was the problem, but it is also a bug.

I had been listening for C92RU on 80m FT8 F/H and saw a spot for ZL7DX on 20m FT4.

I moved to 20m and set mode to FT4. There was no indication that WSJTX was in Hound mode (as in FT8). That is a bug.
Also, after receiving an RR73 the QSO should be logged, but it wasn't - it went back to calling. That is a bug.

But, now that I know this I will be more careful in the future.

I still can't figure out why I can't post to WSJTX. It seems to be related to the change to using main@WSJTX.groups.io and using hashtags.

Thanks,
Steve, K6UM

On Sun, Apr 4, 2021 at 7:17 AM Martin G0HDB <marting0hdb@...> wrote:
On Sun, Apr 4, 2021 at 07:27 AM, Steve Lund wrote:
I can't get FT4 to send the Tx5 73 message in version 2.3.1. It jumps back to Tx1 and won't log the QSO!!
 

032352 Tx 1949 + ZL7DX K6UM CN85

032400 6 -0.0 1737 + K6UM ZL7DX +17

032407 Tx 1949 + ZL7DX K6UM R+06

032415 6 -0.0 1737 + K6UM ZL7DX RR73

032422 Tx 1949 + ZL7DX K6UM CN85

 
Hi Steve, you haven't inadvertently left WSJT-X configured as a 'Hound' via the Settings > Advanced > Special Operating Activity settings, have you?

Although I've never tried it there doesn't seem to be anything to prevent the selection of Fox & Hounds mode when you're in FT4; if you're in Hound mode then your system won't send the Tx5 73 message after it's received the RR73 from the apparent Fox because it's not deemed necessary to send a final, confirmatory 73 to a Fox. 

I know that when operating as an FT8 Hound my system never sends a 73 after receiving the Fox's RR73 but I don't recall if the system automatically reverts to the Tx1 message - I'll have to check when I next operate as a Hound!

73
--
Martin G0HDB



locked Re: #FT4 won't send TX5 #FT4

Martin G0HDB
 

On Sun, Apr 4, 2021 at 07:27 AM, Steve Lund wrote:
I can't get FT4 to send the Tx5 73 message in version 2.3.1. It jumps back to Tx1 and won't log the QSO!!
 

032352 Tx 1949 + ZL7DX K6UM CN85

032400 6 -0.0 1737 + K6UM ZL7DX +17

032407 Tx 1949 + ZL7DX K6UM R+06

032415 6 -0.0 1737 + K6UM ZL7DX RR73

032422 Tx 1949 + ZL7DX K6UM CN85

 
Hi Steve, you haven't inadvertently left WSJT-X configured as a 'Hound' via the Settings > Advanced > Special Operating Activity settings, have you?

Although I've never tried it there doesn't seem to be anything to prevent the selection of Fox & Hounds mode when you're in FT4; if you're in Hound mode then your system won't send the Tx5 73 message after it's received the RR73 from the apparent Fox because it's not deemed necessary to send a final, confirmatory 73 to a Fox. 

I know that when operating as an FT8 Hound my system never sends a 73 after receiving the Fox's RR73 but I don't recall if the system automatically reverts to the Tx1 message - I'll have to check when I next operate as a Hound!

73
--
Martin G0HDB


locked Re: Enable TX button will not function #wsjt-x-crashing #transmit

Bill Somerville
 

On 04/04/2021 13:26, WU9D wrote:
Sometimes the Enable TX button fails to "latch". It flashes red when I click it but doesn't enable. All other functions work fine including the test ptt and test cat. In order to get it working again I have to restart the program. Any ideas? I have RF suppression on all cables and a RF choke toroid at the feedline connection to the radio.
Hi OM,

make sure the selected TxN message is not blank.

73
Bill
G4WJS.


locked Enable TX button will not function #wsjt-x-crashing #transmit

WU9D <mike@...>
 

Sometimes the Enable TX button fails to "latch". It flashes red when I click it but doesn't enable. All other functions work fine including the test ptt and test cat. In order to get it working again I have to restart the program. Any ideas? I have RF suppression on all cables and a RF choke toroid at the feedline connection to the radio.


locked #FT4 won't send TX5 #FT4

Steve Lund
 

I can't get FT4 to send the Tx5 73 message in version 2.3.1. It jumps back to Tx1 and won't log the QSO!!

032352 Tx 1949 + ZL7DX K6UM CN85

032400 6 -0.0 1737 + K6UM ZL7DX +17

032407 Tx 1949 + ZL7DX K6UM R+06

032415 6 -0.0 1737 + K6UM ZL7DX RR73

032422 Tx 1949 + ZL7DX K6UM CN85



73,
Steve, K6UM


locked Re: SignaLink stays stuck in PTT #AudioIssues #signalink #transmit

Joel
 

Sarah

It’s been a while since I’ve setup my SignaLink but it is likely a calibration issue. There are instructions as to how to set up your sound settings on the Tigertronic’s webpage but just off the top of my head...

TX and RX dials should be @ 12 position
Delay should be turned completely off
Look in the windows sound settings / Sound Control Panel under the Playback tab
Find the USB audio codec for the signaLink (you might have to turn the unit on and off to see which one it is if you have multiple codecs). Double click it - here you can re-label it if you want to, mine now says Speakers SignaLink. Open the levels tab and reduce to output level until PTT cycles off (mine is at 65). If you have an ALC meter it should be barely flickering or just below the lowest level it flickers at. Also VOX should not be turned on in the radio.

On my ICOM the SignaLink goes into the ACC port and I had to change the menu setting from DATA MOD USB to DATA MOD ACC. Not certain if Yaesu has a similar setup. As you had it working earlier I would start by checking your sound level.

Good luck 

Joel
AC8WS

On Apr 3, 2021, at 8:39 PM, Sarah Dickey <n6ope@...> wrote:

Equipment: FT-890 with Signalink, Windows10. NOT using CAT control.
Greetings: I'm setting up my own rig to do FT-8 using WSJT-X. Initial QSOs confirmed set up was generally operating correctly.  Signalink was turning radio Tx on and off at 15 second intervals as expected to respond to CQs.  This afternoon I worked on trying to make sure all the computer audio settings and Signalink Tx/Rx knob settings were optimized. Now I'm finding now that the Signalink is not turning off PTT as it should after 15 seconds. Instead PTT remains on and radio continues to transmit until I manually either turn the Signalink or radio power off.

I'm baffled. I've used club equipment for digital comms for a couple of years but getting my own equipment to work together is a new challenge for me. Any trouble-shooting suggestions would be most appreciated!  73, Sarah, N6OPE





locked Re: another WSJT-X question #FT8 #GeneralGroupInfo

Joel
 

That occurs when either:

1. You have accidentally moved your frequency dial off the programmed WSJTX frequency for the mode that you are in
2. The frequency you are attempting to use is not programmed into WSJTX

In your case you are trying to FT8 on 60M and I don’t think those frequencies are programmed into WSJTX

You can add them - settings/frequencies BUT be very careful as if I remember correctly there are only 5 legal frequencies and are very narrow band and also if I remember there is something about only one QSO may occur at a time and if multiple stations are calling out trying to QSO as is usual with FT8 it may have been deemed illegal - which might be why they are not programmed. I can certainly be wrong about my recollections. If someone else wishes to chime in and correct me please feel free to to so.

Joel
AC8WS

On Apr 3, 2021, at 8:39 PM, w1av via groups.io <bobruzzo@...> wrote:

What does it mean when the "USB dial frequency" box background is RED? It used to be BLACK with yellow text. It suddenly turned red????
<1.JPG>



locked Re: Compiling MAP-65 under Linux

Les - AA5NA
 

Is the modified source yet available for download?  I’m interested in it as well.

73,
Lesl - AA5NA


locked another WSJT-X question #FT8 #GeneralGroupInfo

w1av
 

What does it mean when the "USB dial frequency" box background is RED? It used to be BLACK with yellow text. It suddenly turned red????


locked Re: Using 2.2.2 vs 2.3 on 60m #FT8 #Cat_RigControl

Jim Brown
 

On 4/3/2021 10:45 AM, Dave Cole wrote:
When last I checked, (a while ago), it appeared that we have but a single frequency we can transmit on-- center of channel.
Is my understanding correct?  If not, can you point me to where it mentions that center of channel is not an issue anymore?
I spent some time (maybe 20 hours) on 60M FT8 last year, and found users spread out over the same sort of 2.7 kHz of spectrum as on other bands, and I've heard nothing about that being a problem.

73, Jim K9YC


locked SignaLink stays stuck in PTT #AudioIssues #signalink #transmit

Sarah Dickey
 

Equipment: FT-890 with Signalink, Windows10. NOT using CAT control.
Greetings: I'm setting up my own rig to do FT-8 using WSJT-X. Initial QSOs confirmed set up was generally operating correctly.  Signalink was turning radio Tx on and off at 15 second intervals as expected to respond to CQs.  This afternoon I worked on trying to make sure all the computer audio settings and Signalink Tx/Rx knob settings were optimized. Now I'm finding now that the Signalink is not turning off PTT as it should after 15 seconds. Instead PTT remains on and radio continues to transmit until I manually either turn the Signalink or radio power off.

I'm baffled. I've used club equipment for digital comms for a couple of years but getting my own equipment to work together is a new challenge for me. Any trouble-shooting suggestions would be most appreciated!  73, Sarah, N6OPE


locked Re: Help with the settings for IC 7300 and WSJTX #FT8

w1av
 

Yes com port assigned for my HP computer is com13. I did a reset on radio and that fixed things. I guess some of the suggestions online and on youtube as to how to set your ci-v functions are not good. There are so many people suggesting different settings. I must have set something wrong but it's fixed now. I might take screen shots of all my settings on radio for future reference.


locked Re: Help with the settings for IC 7300 and WSJTX #FT8

w1av
 

Thanks Joel
I was able to get my HP computer back up and running with WSJTX and my rig. Made a TON of contacts on 40 meters this afternoon. While looking at different youtube videos and help files I found a lot of discrepancies on what settings should be made mostly in the radio. Some people with the same software (WSJTX) and same radio (IC 7300) set their radio a little different. So I am learning as I go still making small tweaks. Thanks for your help. Bob W1AV


locked Re: #FT8 #FT8

Arthur Bernstein
 

Dave,
Thank you. That explains my not hearing the hound (my local friend) sending 73 as in that mode it ends at TX3. Learn something new every day!
I would think my antenna is more efficient than his. He is however, closer to salt water than me!
73, Art, N2KA..

On Apr 3, 2021, at 1:15 PM, Arthur Bernstein via groups.io <n2ka@...> wrote:

Reino,
Interesting suggestion! For the next DX’Pedition using Fox/Hound I will uncheck “Receive All frequencies” and just listen below 1000 hz. Don’t care what people above 1000 hz are sending as many keep calling. I wonder if all even hear the DX. I’ve had successful Fox/hound QSOs before and see how my transmit frequency is temporary QSY to his frequency. Since I didn’t hear the A25 that’s likely why I didn’t hear complete QSOs!
Next time!!
73, Art, N2KA..
On Apr 3, 2021, at 9:26 AM, Reino Talarmo <reino.talarmo@...> wrote:

Hi Art,

One possibility is limit reception bandwidth of your receiver to cover only frequencies below 1000 Hz. That could make decoding of weak Fox signals a bit easier. On the other hand on DXpedition frequencies other Houd station should not transmit at the same time as Fox is transmitting.

There is a minor failure in your thinking about need of RRR or 73 in that mode. See https://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf for message exchange details.

73, Reino OH3mA

Hello All,

I’ve been using FT8 fairly successfully for a while, but I’ve noticed something that I’m having trouble explaining.

To cut to the chase, I seem to be having trouble hearing the DX station when using the FOX/HOUND mode, while others locally, with comparable stations, seem to be able to hear them. This is mostly noted on 160 meters., for example, with the A25RU expeditioin, a couple of local guys worked him, and I never saw A25RU’s signal “print.” As a matter of fact I am able to copy the local stations sending the signal report, but not even copy the RRR or 73, from the local station, let alone the DX station, but they claim they have made complete contacts. This has happened before with other DX’Peditions, where, granted, the signal of the DX station may be weak. I routinely am able to decode stations at –24db.

I have no trouble working about anything I can hear on 160 and 80 meters, even at extreme distances, often under marginal conditions.

Was just wondering if I may have some parameters that need to be tweaked on either the rig (Elecraft K3) or in WSJTX v2.3.1 in Win 10 64 Bit?

The receiver’s bandwidth is set for its maximum in USB/Digital at 4 kHz and the audio range on the waterfall is set from 100 hz to about 3000 hz, though I cannot tune the program on the waterfall to receive to below 200 hz. The box “hear all signals” is checked.

Any suggestions with regard to the settings on the K3’s AGC (Fast, Slow or OFF?) Backing off on the RF Gain control, in addition, to improve signal/noise ratio? Those bands, in particular are VERY noisy. On 80/160 meters I’m using an Inverted L at least 50 ft. vertical.

Any suggestions or ideas would be appreciated.

73, Art., N2KA..






locked Re: Help with the settings for IC 7300 and WSJTX #FT8

Joel
 

I presume that you downloaded and installed the ICOM USB drivers on the HP before connecting it to the 7300.

1. Make certain the Dell is turned off or at least not connected in any way to the 7300.
2. Check and see what COM port the HP assigned to your 7300 USB connection it might not be the same as the Dell. If it is a different COM port, update your Hamlib configuration.
3. CV-I for the 7300 is 94 - that does not change.
4. DATA MOD should be USB
5. Set the COM port speed on the HP WSJTX to match the 7300 setting (or try auto on the 7300 if #2 does not fix it.

Hope this helps
Joel
AC8WS

On Apr 3, 2021, at 1:15 PM, w1av via groups.io <bobruzzo@...> wrote:

OK I have 2 computers, a DELL and an HP. I had WSJTX working GREAT on the DELL.....make a ton of contacts on FT8. When I got up today, before turning anything on I switched to the HP computer cause its faster with an SSD and 32 GB ram. And its really the MAIN computer I use. So when I booted into Windows (10) I turned on power supply, then the 7300. I opened WSJTX only to find this stupid error. For the life of me I just couldnt get anything to work. Here are the errors...Is there ANY WAY I can get STEP BY STEP proper settings for running FT* on my IC 7300? I looked at many websites/videos and they are all showing different settings under MENU>SET>CONNECTORS>CI-V.....plus maybe a couple more settings in the menu. I am sure I have all the right things set in the SETTINGS of WSJTX. But there are still a couiple of settings that others have differently. I just need to know the correct settings for the WSJTX software and the IC 7300 for running FT8. Like I said it was working FB on my DELL computer last night. When I switched computers I couldnt get it to work, as you can see in the attached pictures. After reading manuals, going online etc I still cant find EXACT settings. I ended up switching back to DELL computer where I also ran into SAME ISSUE!!!! So I did a TOTAL RESET on the IC 7300 and apparently that helped because its working again. But WHY the unstable issues? Maybe someone can look at the errors and see what I need to fix. Thanks!
<hamlib error.PNG>
<error 2.PNG>



locked VS: [WSJTX] Using 2.2.2 vs 2.3 on 60m #FT8 #Cat_RigControl

Reino Talarmo
 

[WSJTX] Using 2.2.2 vs 2.3 on 60m #FT8 #Cat_RigControl

 

K4TAX said:

Mar 12  


"As written, the FCC states that PSK31 and Pactor III may be used on 60 meters. Pactor III is a full 2 kHz wide - several dozen FT8 stations can operate within that bandwidth. ... FT8 activity takes place on a VFO frequency of 5357.0 kHz.  and not 5.358.5."

Bob, this is confusing as well.  I have hard-coded unerasable memory channels in the FTDX-3000 for 60m and 5357.0 isn't one of them.  But I see the full FT-8 spectrum when I select "5M-03" memory at 5385.5.  In version 2.2.2, in memory mode, using this channel, FT8 operation is no problem whatsoever. (Matter of semantics? 5385.5 is the center of the 5357.0 channel. All the 60m pre-programmed channels reference the center frequency, not the lower edge.  I don't know why Yaesu does it this way).



Upgrading to 2.3.0 or 2.3.1, I can't operate in this same manner.  The first transmission in memory mode always works, but when it finishes, WSJTX forces the radio back to VFO A mode and the red TX light starts flashing indicating "not allowed."  That is as simple an explanation as I can provide.  Again, I ask the question, how to I keep WSJTX 2.3.0/2.3.1 from kicking me back to VFO mode after every transmission?  I have SPLIT turned off and I am not using FREQUENCY CALIBRATION.

Dave N7RF

[Reino Talarmo]

 

Hi Dave,

Bill proposed to make a new configuration for 60 m band and set rig to None and Mode to USB. You need manually select the channel and no CAT control is not possible. Use for PTT either VOX or DTR or RTS. I have checked how those latter two options can be used with FTdx3000.

 

73, Reino OH3mA


locked Re: Using 2.2.2 vs 2.3 on 60m #FT8 #Cat_RigControl

Dave (NK7Z)
 

Hi,

When last I checked, (a while ago), it appeared that we have but a single frequency we can transmit on-- center of channel.

Is my understanding correct? If not, can you point me to where it mentions that center of channel is not an issue anymore?

Not being snarky, just want to understand the allowed frequency use before I got on it much more...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net

On 4/3/21 9:26 AM, Dave Moore wrote:
"/As written, the FCC states that PSK31 and Pactor III may be used on *60 meters*. Pactor III is a full 2 kHz wid/

14161 - 14180 of 37956