Date   

locked Re: FT8 Feature Suggestion #FT8

William Smith
 

Pietro, I think you misunderstand how FT8 works.  Your QSO partner can hear you no matter what your transmit frequency is, so there's no need to move to his transmit frequency.  In fact it's counter productive:

1) I call CQ from a rare location at (say) 1500Hz.

2) Dozens of hams reply on 1500Hz because that's the default(*) and they don't know any better.  I don't hear any of them because of the QRM.

3) You transmit on 435Hz (or really, anywhere _except_ 1500Hz, and because there's no QRM, I hear you just fine, and we complete the QSO.

(*) So, this shouldn't be the default, not sure why it is the default, but that's a rathole for another day.  This is why everyone tells you to use "Hold Tx Freq", though no-one bothers to explain why.

73, Willie N1JBJ

On Aug 28, 2021, at 4:13 AM, Pietro Molina <pietro@...> wrote:

On Sat, Aug 28, 2021 at 09:43 AM, Gary - AG0N wrote:
If you jump to my transmit frequency, I’ll move as soon as I realize it. Move to me again and I’ll move again. Do it again and I’ll be gone. Just stay where you are.
And why you move? Not only is it not necessary, but it is not useful.
If I want to work you and you jump around, I have " a lot of work" to follow you. @Rory: but only if I don't use JTAlert or similia.

Pietro I2OIM




locked Re: FT8 Feature Suggestion #FT8

Pietro Molina
 

On Sat, Aug 28, 2021 at 09:43 AM, Gary - AG0N wrote:
If you jump to my transmit frequency, I’ll move as soon as I realize it. Move to me again and I’ll move again. Do it again and I’ll be gone. Just stay where you are.
And why you move? Not only is it not necessary, but it is not useful.
If I want to work you and you jump around, I have " a lot of work" to follow you. @Rory: but only if I don't use JTAlert or similia.

Pietro I2OIM


locked Invito: [WSJTX] WWDigi practice session #ContestMode - sab 28 ago 20:00 - lun 30 ago 2021 01:59 (CEST) (main@wsjtx.groups.io) #ContestMode

Pietro Molina
 

Sei stato invitato al seguente evento.

[WSJTX] WWDigi practice session #FT8 #ContestMode #FT4

Quando
sab 28 ago 20:00 – lun 30 ago 2021 01:59 Ora dell’Europa centrale - Amsterdam
Calendario
main@wsjtx.groups.io
Chi
pietro@... - organizzatore
ktfrog007@...
main@wsjtx.groups.io
rttydigital@groups.io
WWDigi practice session Friday evening.



**************************************************************

0200-0259 UTC, Saturday 28 August (Friday evening, NA time) Use the recommended sub-bands in the rules:

II. BANDS: Six bands only: 1.8, 3.5, 7, 14, 21 and 28 MHz.
A. FT4 recommended sub-bands:
1.840-1.844
3.580-3.589
7.080-7.089
14.080-14.089
21.080-21.089
28.080-28.089
Set the radio dial at the bottom of the sub-band and work stations on audio frequencies within the radio passband, typically 2.5-4 kHz wide. If a sub-band becomes crowded, move the radio dial frequency up in 3 kHz increments, as needed. (For example: 7.080, 7.083 and 7.086)
B. FT8 recommended sub-bands:
1.844-1.848
3.590-3.599
7.090-7.099
14.090-14.099
21.090-21.099
28.090-28.099
Set the radio dial at the bottom of the sub-band and work stations on audio frequencies within the radio passband ...

Parteciperai (main@wsjtx.groups.io)?    - Forse - No    altre opzioni »

Invito da Google Calendar

Hai ricevuto questo messaggio email di cortesia all'account main@wsjtx.groups.io perché sei uno dei partecipanti a questo evento.

Per disattivare la ricezione di aggiornamenti futuri per questo evento, rifiuta l'evento. In alternativa, puoi registrarti per un Account Google in https://calendar.google.com/calendar/ e verificare le impostazioni di notifica per l'intero calendario.

Se inoltri questo invito potresti consentire al destinatario di inviare una risposta all'organizzatore e di essere aggiunto all'elenco degli invitati oppure di invitare altre persone indipendentemente dallo stato dell'invito o ancora di modificare la tua risposta. Ulteriori informazioni.


locked Re: FT8 Feature Suggestion #FT8

Gary - AG0N
 

On Aug 25, 2021, at 10:03, Rory Bowers <k6cks01@...> wrote:

If you want to contact a station and have him in your receive frequency window but then he moves it would be really neat to "track him". I have found a lot of stations that "hop around" and keeping up with them can be a lot of work.
Why do you need to “track him”? Why would it “be a lot of work”? Are you one of those who thinks he must transmit where the other guy is? That’s wrong. The receiver monitors all frequencies within the bandpass of the receiver and waterfall. If you jump to my transmit frequency, I’ll move as soon as I realize it. Move to me again and I’ll move again. Do it again and I’ll be gone. Just stay where you are.

73, Gary - AG0N


locked Re: Help setting up WSJTX #FT8 #Cat_RigControl #JT65

Mark Finkelstein
 

Hi Bill,

Thank you for your patience.  I have everything working but radio control.  It seems the new Mac OS 11.5.2 with the M1 chip doesn’t recognize the driver. There is something about using applications to install the driver and that looks way beyond my abilities.

I tried the Mac support and they really didn’t have an idea about how to install the driver.  Also the driver site says that for the new Mac operating system the driver is a beta version.

Is there any other ways to control the radio that I might try?

Thanks,
Mark




On Aug 26, 2021, at 7:36 PM, Bill Somerville <g4wjs@...> wrote:


Hi Mark,

CAT control is separate from audio interfaces, you need both for full control of the rig. Looking at images of the TX-500 I see two sockets marked REM/DATA and CAT respectively. If you have a CAT interface then I would expect both to be populated. The CAT cable may need drivers installed for the virtual serial port that is the CAT connection.

73
Bill
G4WJS.

On 27/08/2021 00:30, Mark Finkelstein via groups.io wrote:
I do have the CAT cable for the radio that is a USB Connector. I’m using the audio cable and VOX and truthfully I’m not sure what the difference is.  The sound card I have, Sabrent, has the 3.5 mm plugs that go in to the audio cable for the TX500 (REM/DATA).

I could try using the CAT cable directly to the computer but I’m not sure if the MacBook Pro has a sound card that will work. Would I need an external sound card with a rectangular USB connection for the CAT cable? 

The folks at Lab599 (the radio company) suggested adjusting the TX/RX Gain levels as that may help key the radio.  Thoughts?

I’m really close if I can only get the computer to key the radio.  

Thanks for all your help!
Mark
On Aug 26, 2021, at 6:53 PM, Bill Somerville <g4wjs@...> wrote:

On 26/08/2021 23:10, Mark Finkelstein via groups.io wrote:
Well first off thank everyone for helping me. I have the software running and am copying transmissions on the band.  I can double click on CQ’s and if I enable the TX it appears to be sending. However, the radio does is not being keyed.  I tried both 20m and 40m with similar results.  I’m using the Sabrent adapter for Mac to the REM/Data port.  Tx500 radio is in Digital mode. I did a time.is and the computer clock is exact.

Any thoughts on where to look? 
Hi Mark,

do you have a CAT interface?

73
Bill
G4WJS.






locked WWDigi practice session #FT8 #ContestMode #FT4

Kermit Lehman
 

WWDigi practice session Friday evening.
 
 
 
**************************************************************
 
0200-0259 UTC, Saturday 28 August (Friday evening, NA time)  Use the recommended sub-bands in the rules:
 
II. BANDS: Six bands only: 1.8, 3.5, 7, 14, 21 and 28 MHz.
A. FT4 recommended sub-bands:
1.840-1.844
3.580-3.589
7.080-7.089
14.080-14.089
21.080-21.089
28.080-28.089
Set the radio dial at the bottom of the sub-band and work stations on audio frequencies within the radio passband, typically 2.5-4 kHz wide. If a sub-band becomes crowded, move the radio dial frequency up in 3 kHz increments, as needed. (For example: 7.080, 7.083 and 7.086)
B. FT8 recommended sub-bands:
1.844-1.848
3.590-3.599
7.090-7.099
14.090-14.099
21.090-21.099
28.090-28.099
Set the radio dial at the bottom of the sub-band and work stations on audio frequencies within the radio passband typically 2.5-4 kHz wide. If a sub-band becomes crowded, move the radio dial frequency up in 3 kHz increments, as needed. (For example: 7.090, 7.093 and 7.096)
C. JA sub-bands on 80 and 40 meters:
FT4:
3.528 (JA-JA), 3.570 (JA-DX)
7.038 (JA-JA), 7.080-7.089 (JA-DX)
FT8:
3.531 (JA-JA), 3.573 (JA-DX)
7.041 (JA-JA), 7.090-7.099 (JA-DX)
 
73,
Ed W0YK_._,_._,_


locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Michael Black
 

What's your Decode menu show for the depth?
Reduce it.

Mike W9MDB




On Friday, August 27, 2021, 12:55:40 PM CDT, Jim Pennino via groups.io <penninojim@...> wrote:


Bill,


After running process explorer it is obvious what the problem is.

No system resource, i.e. CPU, memory, etc., gets anywhere near 100%.

wsjtx shows a peak CPU usage of about 15% and jt9 shows a peak of about 25%.

Individual core usage never gets above about 50%.

There are no strange I/O wait states that would indicate anything like an audio discontinuity.

The only thing left is that a 1.95 GHz CPU is too slow to process all the data when there are a large number of signals within a cycle, continues to process into the next cycle, and misses all the data from the next cycle.

One solution, which would only effect those with a slow CPU, would be to put a hard limit on how long WSJTX attempts to decode a cycle such that if it were nearing the time when it would lose the next cycle, it gives up on the current cycle. The result for those with slow CPU's would be to lose a few possible decodes in the current cycle as opposed to losing everything from the next.

The other solution is to get a faster CPU, but that isn't an option for those using the Raspberry Pi4.




locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Bill Somerville
 

On 27/08/2021 18:54, Jim Pennino via groups.io wrote:
Bill,

After running process explorer it is obvious what the problem is.

No system resource, i.e. CPU, memory, etc., gets anywhere near 100%.

wsjtx shows a peak CPU usage of about 15% and jt9 shows a peak of about 25%.

Individual core usage never gets above about 50%.

There are no strange I/O wait states that would indicate anything like an audio discontinuity.

The only thing left is that a 1.95 GHz CPU is too slow to process all the data when there are a large number of signals within a cycle, continues to process into the next cycle, and misses all the data from the next cycle.

One solution, which would only effect those with a slow CPU, would be to put a hard limit on how long WSJTX attempts to decode a cycle such that if it were nearing the time when it would lose the next cycle, it gives up on the current cycle. The result for those with slow CPU's would be to lose a few possible decodes in the current cycle as opposed to losing everything from the next.

The other solution is to get a faster CPU, but that isn't an option for those using the Raspberry Pi4.
Hi Jim,

are you running a 64-bit o/s on your Raspberry Pi Model 4?

Does this issue occur when you select "Menu->Decode->Normal" or "Menu->Decode->Fast"?

73
Bill
G4WJS.


locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Jim Pennino
 

Bill,

After running process explorer it is obvious what the problem is.

No system resource, i.e. CPU, memory, etc., gets anywhere near 100%.

wsjtx shows a peak CPU usage of about 15% and jt9 shows a peak of about 25%.

Individual core usage never gets above about 50%.

There are no strange I/O wait states that would indicate anything like an audio discontinuity.

The only thing left is that a 1.95 GHz CPU is too slow to process all the data when there are a large number of signals within a cycle, continues to process into the next cycle, and misses all the data from the next cycle.

One solution, which would only effect those with a slow CPU, would be to put a hard limit on how long WSJTX attempts to decode a cycle such that if it were nearing the time when it would lose the next cycle, it gives up on the current cycle. The result for those with slow CPU's would be to lose a few possible decodes in the current cycle as opposed to losing everything from the next.

The other solution is to get a faster CPU, but that isn't an option for those using the Raspberry Pi4.


locked Re: #FT8 Responding to FT8 "73" in QSO at end to contact not working #FT8

Dick Bingham
 

Hello Bill and everyone who has responded to my email

I was just reporting what WAS different in the way v2.4.0 functioned compared to what I had been using.
That v2.4.0 works this way was new to me, I just have to accept it or return to the older SW.

Thank you to everyone who has replied.

Dick - w7wkr


locked Re: After upgrade to WSJT-X 2.4.0, an IC-7600 no longer changes bands on SPE Expert 1K-FA power amplifier #Cat_RigControl

Bengt SM6MUY
 

It works for some. But not for all. I have the IC-7300, not the 7600. Don't have that ANT setting. No problems until I installed V2.4.0. I friend of mine also have the IC-7300. No problems for him. Exactly the same settings. Since the response on the forum is low it seems that the SPE Expert PA is not widely used. Or at least very few have this problem. I can live with it no problem. I Just change band from the rig instead. Don't spent too much time on it.

73/Bengt, SM6MUY


On 2021-08-26 06:39, Allan Saul wrote:
Frode,
I really dont understand why you have a problem because its working for me with exactly
the same hardware setup.
1: Check you have the latest firmware in the IC-7600 (rev 2.00)
2: Check you have CI-V Output (for ANT) set to ON.



It is working here on any version of WSJT-X regardless of split mode etc,
73 de Allan ZS1LS



locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Bill Somerville
 

On 27/08/2021 14:39, Jim Pennino via groups.io wrote:
Hi Bill,

You keep assuming I am running something like SNTP.

I am not.

The system runs NTP and has an attached USB GNSS receiver that keeps the system to within about 3 milliseconds absent any other time source, but it also uses two local stratum 1 NTP servers that keep the system to well within 100 microseconds when it is on the network, which is most of the time. The system clock does NOT drift outside the microsecond range.

Perhaps if I rephrase the question: Would it have much effect on the resources used if the documentation suggestion to run something like NTP was changed to a requirement to keep the clock within, say 100 milliseconds or so?
Jim,

if I am assuming something then it is because you have not provided sufficient information. Note that saying your PC clock is always within 100 ms of UTC doesn't tell me you are running a full NTP implementation. What is sure is that a step adjustment to the PC clock during a receive period will cause an audio stream discontinuity, and that in turn may disrupt all decoding for that period. You asked what might be the cause of occasional failures to decode any signals, I offered one common reason. If that is not the case for you then you need to look for other causes, audio discontinuities are still likely to be the cause so perhaps some peak of CPU or interrupt loading is disrupting smooth audio streaming.

73
Bill
G4WJS.


locked Re: #FT8 Responding to FT8 "73" in QSO at end to contact not working #FT8

Martin G0HDB
 

On Thu, Aug 26, 2021 at 11:56 PM, Dick Bingham wrote:
Greeting to everyone

AFTER getting FT8 to run after installing WSJT-X v2.4.0 software, I have discovered a
new problem.

I call CQ and another station responds. The software runs us thru the contact 
process and finally the calling station sends the 73 and sign-off sequence.

At this point my software ends the QSO without going thru the 73 by me. The screen
appearance then looks like it is ready to send another CQ by me or me calling
another station.
Dick:

You've received a 73 from the other station, which confirms beyond all reasonable doubt that all the essential information for the QSO has been successfully exchanged and received by both parties, so irrespective of whether you sent the other station an RRR or an RR73 to complete your end of the QSO, the QSO is de facto complete and there's no need whatsoever for you to send a further 73.

Clearly, if you want to then you can do as you've described, ie. re-enable Tx and click on the Tx5 message button, but doing so is (IMO) entirely unnecessary and there's no reason for the auto-sequencing to do it.

--
Martin G0HDB


locked Re: occasional FT8 no decode, new computer? #Windows10 #raspberryPi #decode

Jim Pennino
 

Hi Bill,

You keep assuming I am running something like SNTP.

I am not.

The system runs NTP and has an attached USB GNSS receiver that keeps the system to within about 3 milliseconds absent any other time source, but it also uses two local stratum 1 NTP servers that keep the system to well within 100 microseconds when it is on the network, which is most of the time. The system clock does NOT drift outside the microsecond range.

Perhaps if I rephrase the question: Would it have much effect on the resources used if the documentation suggestion to run something like NTP was changed to a requirement to keep the clock within, say 100 milliseconds or so?


locked Re: #txaudio #linux WSJT-X No TX audio issue #txaudio #linux

KM4OVZ
 

I tried it with my laptop, using an icom 7300. Cat control worked fine and so did the audio. Maybe wsjtx just doesn't play nice with built in soundcards.


locked Re: Adding WSJTX to Mac #TechnicalHelpQuestion #macOS

Bill Somerville
 

On 27/08/2021 02:43, mbigos@... wrote:

Bill -

 

Thanks for the feedback. 

 

My rig is a KX3 @ 5W with a MacBook Air, OSX 11.4, using CAT controls and the USB sound card. Elecraft says that in DATA A mode the audio level should just “tickle” the ALC (4-5 bars on the meter). The 3 controls I have to accomplish this are the (1) Audio MIDI left channel, (2) Power slider on WSJT-X, and (3) Mic gain on the KX3 (the output level in System Preferences Sound is tied to (1) ).

 

MIDI goes from -33db to 0, the pwr slider goes from -45db to 0, and the mic gain goes from 0 to 80 (no units). To meet the Elecraft requirements I’ve set the Audio MIDI at -8db, the per slider at -27db, and the mic gain at 25.

 

Is your recommendation to set the MIDI and pwr slider to 0db (full scale)? In that case a hairs touch of the mic gain sends the KX3 into ALC.

 

Is there a batter setting for the MIDI and pwr controls than I’m using that allows a reasonable mic gain? Especially if it allows better decoding of my signal! Monitoring stations on PSK Reporter hear me, but it takes work to get QSOs (probably due to my compromise antenna)!

 

73, and thanks again

 

Marty

Hi Marty,

the reason for recommending that the last level control in the chain is used for level setting, and all other digital controls before that being left at 0 dB, is that there is no advantage to adding digital attenuation to the Tx audio chain (other than convenience). If the sensitivity of the KX3 is such that an un-attenuated output from your sound card is almost too high to cope with, then look to the prior control to add some attenuation. I would still try and keep the digital gain controls near 0 dB. Your example settings include 35 dB of digital attenuation, while that is still within the range where the reduction of signal resolution is of little significance, that is still a lot of attenuation on what should be a roughly compatible line out to line in interface! Are you sure you are not using a headphone or speaker output with unnecessary extra gain?

73
Bill
G4WJS.


locked Re: #FT8 Responding to FT8 "73" in QSO at end to contact not working #FT8

Bob G8HGN
 

Hi,

I'm not getting into the debate about whether you need the "extra" 73, BUT, the program used to send it if RRR was selcted.

I've been on 6M most of the Summer so haven't really needed to use RRR for weak signals. I've been using RR73.

Now 6M has started to wane I've gone back to 2M and had occasion to use RRR, and to my surprise found that it wasn't sending the "final" 73.

It may be I upgraded to V2.4.0 early Summer, and didn't use RRR, so never noticed until now.

Is there any point in having a choice between RRR/RR73 now as there's no difference in the auto sequence.

73 Bob G8HGN


locked Re: Adding WSJTX to Mac #TechnicalHelpQuestion #macOS

Marty Bigos
 

Bill -

 

Thanks for the feedback. 

 

My rig is a KX3 @ 5W with a MacBook Air, OSX 11.4, using CAT controls and the USB sound card. Elecraft says that in DATA A mode the audio level should just “tickle” the ALC (4-5 bars on the meter). The 3 controls I have to accomplish this are the (1) Audio MIDI left channel, (2) Power slider on WSJT-X, and (3) Mic gain on the KX3 (the output level in System Preferences Sound is tied to (1) ).

 

MIDI goes from -33db to 0, the pwr slider goes from -45db to 0, and the mic gain goes from 0 to 80 (no units). To meet the Elecraft requirements I’ve set the Audio MIDI at -8db, the per slider at -27db, and the mic gain at 25.

 

Is your recommendation to set the MIDI and pwr slider to 0db (full scale)? In that case a hairs touch of the mic gain sends the KX3 into ALC.

 

Is there a batter setting for the MIDI and pwr controls than I’m using that allows a reasonable mic gain? Especially if it allows better decoding of my signal! Monitoring stations on PSK Reporter hear me, but it takes work to get QSOs (probably due to my compromise antenna)!

 

73, and thanks again

 

Marty

 


locked Re: Help setting up WSJTX #FT8 #Cat_RigControl #JT65

Mark Finkelstein
 

Ok Bill Thanks! I believe the radio manual references some drivers and I’ll get them installed.  I’ll keep you posted!


On Aug 26, 2021, at 7:36 PM, Bill Somerville <g4wjs@...> wrote:


Hi Mark,

CAT control is separate from audio interfaces, you need both for full control of the rig. Looking at images of the TX-500 I see two sockets marked REM/DATA and CAT respectively. If you have a CAT interface then I would expect both to be populated. The CAT cable may need drivers installed for the virtual serial port that is the CAT connection.

73
Bill
G4WJS.

On 27/08/2021 00:30, Mark Finkelstein via groups.io wrote:
I do have the CAT cable for the radio that is a USB Connector. I’m using the audio cable and VOX and truthfully I’m not sure what the difference is.  The sound card I have, Sabrent, has the 3.5 mm plugs that go in to the audio cable for the TX500 (REM/DATA).

I could try using the CAT cable directly to the computer but I’m not sure if the MacBook Pro has a sound card that will work. Would I need an external sound card with a rectangular USB connection for the CAT cable? 

The folks at Lab599 (the radio company) suggested adjusting the TX/RX Gain levels as that may help key the radio.  Thoughts?

I’m really close if I can only get the computer to key the radio.  

Thanks for all your help!
Mark
On Aug 26, 2021, at 6:53 PM, Bill Somerville <g4wjs@...> wrote:

On 26/08/2021 23:10, Mark Finkelstein via groups.io wrote:
Well first off thank everyone for helping me. I have the software running and am copying transmissions on the band.  I can double click on CQ’s and if I enable the TX it appears to be sending. However, the radio does is not being keyed.  I tried both 20m and 40m with similar results.  I’m using the Sabrent adapter for Mac to the REM/Data port.  Tx500 radio is in Digital mode. I did a time.is and the computer clock is exact.

Any thoughts on where to look? 
Hi Mark,

do you have a CAT interface?

73
Bill
G4WJS.






locked Re: Logger32 & WSJT-X #JT65 #JT9

Panos
 

Hi thanks, now I have to look for some JT signals 73

7381 - 7400 of 35419