Date   

locked Re: Cannot Call PB75A

Charlie Hoffman
 

I thought it was only me.

I've had that happen with other calls but figured it was just something I did.

I've also had stations call me and when I reply it jumps to RR73 and will not allow even a manual reply.

I figured that maybe the problem was that the specific call signs were on some "black list"

I'm running the latest general release version.


locked Re: Crowded frequencies

chapron
 

De : "Markku SM5FLM"
A : main@WSJTX.groups.io
Envoyé: vendredi 18 décembre 2020 14:56
Objet : Re: [WSJTX] Crowded frequencies
 
Even if a slot is empty at your location, you don't know if the slot is empty in other places.

This is a problem when calling as station. On which frequency should you transmit? I have found it's best to use frequencies high >2500 or low <500, even if the more middle one's seems to be unused.

Hello
I use when I can an other way.
FT4 and FT8 are not QRM when the offset is some few Hz ( my offset is brtween 6 and 10 Hz)so no QRM and postly Freq is free in other side!The station will not choose a busy Freq to make his call.

This is possible when I see a station and wait him to end QSO (73) to call him. But if I want to reply to a CQ I have not the time to enter my new Freq!

So an idea is if it is possible to choose in the config some adjustable offset ( say + or - 0-20Hz) that will be add to our TX FREQ .

For me this new feater will be nice and very usefull. If you don't want it just enter 0Hz.

May be I am wrong and don't see a big dr(awback

F6EAO Jean-Michel


 
 


locked Re: ALL.txt question...

JP Tucson, AZ
 

Hi Bill,

Since it foxed for the next release, I'm going to hound you for that futuristic v3.2.0 general release!

Hahaha...

73 - John - N7GHZ

On Fri, Dec 18, 2020, 9:52 AM Bill Somerville <g4wjs@...> wrote:
On 18/12/2020 16:37, Dave Cole wrote:
> Hello,
>
> My ALL.txt file does not contain time information.  Is there a setting
> someplace I am missing to include this?
>
> It used to have a time stamp on the front of each line...  Here is a
> cut from my most recent entires of this morning:
>
> 14.074 Rx FT8     -2  0.4 2988 CQ KC1NYY FN42
> 14.074 Rx FT8     -1  1.1 1823 K0TN W2DXD DM43
> 14.074 Rx FT8    -17  0.5  930 CQ K0DME DN70
> 14.074 Rx FT8    -14  0.8  826 W4EYJ N5OKY DM78
> 14.074 Rx FT8     -2  0.4 1277 K0TN K0VN DM43
> 14.074 Rx FT8    -10  0.5 1444 ND6H F5SSQ JN06
> 14.074 Rx FT8    -16  0.4  769 K0TN NY4JB EM66
> 14.074 Rx FT8    -14  0.8 1244 CQ CO8LY FL20
> 14.074 Rx FT8    -10  0.4 1290 ND6H N0DCW DM78
> 14.074 Rx FT8    -12  0.4 1681 DL4SDW KE8IOL EN82
> 14.074 Rx FT8     -4  1.2  445 CQ N0JFD EN17
>
> I seem to not be able to locate any sort of reference to all.txt in
> the on line help...  Any hints on how to turn on the timestamp on a
> per line basis?
> --
> 73, and thanks,
> Dave (NK7Z)

Hi Dave,

you don't mention which version of WSJT-X you are using, if it is v3.2.0
RC2 then there is a known defect that means timestamps re not printed
for decoded messages. It is foxed for the next release.

73
Bill
G4WJS.





locked Re: ALL.txt question...

Dave (NK7Z)
 

Thanks, I have been pulling my hair out...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources

On 12/18/20 8:51 AM, Bill Somerville wrote:
On 18/12/2020 16:37, Dave Cole wrote:
Hello,

My ALL.txt file does not contain time information.  Is there a setting someplace I am missing to include this?

It used to have a time stamp on the front of each line...  Here is a cut from my most recent entires of this morning:

14.074 Rx FT8     -2  0.4 2988 CQ KC1NYY FN42
14.074 Rx FT8     -1  1.1 1823 K0TN W2DXD DM43
14.074 Rx FT8    -17  0.5  930 CQ K0DME DN70
14.074 Rx FT8    -14  0.8  826 W4EYJ N5OKY DM78
14.074 Rx FT8     -2  0.4 1277 K0TN K0VN DM43
14.074 Rx FT8    -10  0.5 1444 ND6H F5SSQ JN06
14.074 Rx FT8    -16  0.4  769 K0TN NY4JB EM66
14.074 Rx FT8    -14  0.8 1244 CQ CO8LY FL20
14.074 Rx FT8    -10  0.4 1290 ND6H N0DCW DM78
14.074 Rx FT8    -12  0.4 1681 DL4SDW KE8IOL EN82
14.074 Rx FT8     -4  1.2  445 CQ N0JFD EN17

I seem to not be able to locate any sort of reference to all.txt in the on line help...  Any hints on how to turn on the timestamp on a per line basis?
--
73, and thanks,
Dave (NK7Z)
Hi Dave,
you don't mention which version of WSJT-X you are using, if it is v3.2.0 RC2 then there is a known defect that means timestamps re not printed for decoded messages. It is foxed for the next release.
73
Bill
G4WJS.


locked Re: ALL.txt question...

Bill Somerville
 

On 18/12/2020 16:37, Dave Cole wrote:
Hello,

My ALL.txt file does not contain time information.  Is there a setting someplace I am missing to include this?

It used to have a time stamp on the front of each line...  Here is a cut from my most recent entires of this morning:

14.074 Rx FT8     -2  0.4 2988 CQ KC1NYY FN42
14.074 Rx FT8     -1  1.1 1823 K0TN W2DXD DM43
14.074 Rx FT8    -17  0.5  930 CQ K0DME DN70
14.074 Rx FT8    -14  0.8  826 W4EYJ N5OKY DM78
14.074 Rx FT8     -2  0.4 1277 K0TN K0VN DM43
14.074 Rx FT8    -10  0.5 1444 ND6H F5SSQ JN06
14.074 Rx FT8    -16  0.4  769 K0TN NY4JB EM66
14.074 Rx FT8    -14  0.8 1244 CQ CO8LY FL20
14.074 Rx FT8    -10  0.4 1290 ND6H N0DCW DM78
14.074 Rx FT8    -12  0.4 1681 DL4SDW KE8IOL EN82
14.074 Rx FT8     -4  1.2  445 CQ N0JFD EN17

I seem to not be able to locate any sort of reference to all.txt in the on line help...  Any hints on how to turn on the timestamp on a per line basis?
--
73, and thanks,
Dave (NK7Z)
Hi Dave,

you don't mention which version of WSJT-X you are using, if it is v3.2.0 RC2 then there is a known defect that means timestamps re not printed for decoded messages. It is foxed for the next release.

73
Bill
G4WJS.


locked ALL.txt question...

Dave (NK7Z)
 

Hello,

My ALL.txt file does not contain time information. Is there a setting someplace I am missing to include this?

It used to have a time stamp on the front of each line... Here is a cut from my most recent entires of this morning:

14.074 Rx FT8 -2 0.4 2988 CQ KC1NYY FN42
14.074 Rx FT8 -1 1.1 1823 K0TN W2DXD DM43
14.074 Rx FT8 -17 0.5 930 CQ K0DME DN70
14.074 Rx FT8 -14 0.8 826 W4EYJ N5OKY DM78
14.074 Rx FT8 -2 0.4 1277 K0TN K0VN DM43
14.074 Rx FT8 -10 0.5 1444 ND6H F5SSQ JN06
14.074 Rx FT8 -16 0.4 769 K0TN NY4JB EM66
14.074 Rx FT8 -14 0.8 1244 CQ CO8LY FL20
14.074 Rx FT8 -10 0.4 1290 ND6H N0DCW DM78
14.074 Rx FT8 -12 0.4 1681 DL4SDW KE8IOL EN82
14.074 Rx FT8 -4 1.2 445 CQ N0JFD EN17

I seem to not be able to locate any sort of reference to all.txt in the on line help... Any hints on how to turn on the timestamp on a per line basis?
--
73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources


locked Re: Crowded frequencies

Patrick Hung
 

This is for Jim - W4GMU:

To switch to the FT4 Mode, go to the Mode pull-down menu in WSJT-X, and select "FT4". WSJT-X will automatically select its default FT4 frequency (by band) for you, and you'll see a magenta-colored FT4 indicator light up at the bottom-left of the WSJT-X window.

I truly enjoy FT4, as I can easily work every station that decodes, at twice the speed. If I elect to respond to a call using exclusively TX2, it's even faster, at 3 cycles to RR73. 
--
73,
Patrick, W2TAR


locked Re: Crowded frequencies

Jim Shorney
 

A station far away from you will be hearing a very different palette of signals than you are. That's just the way it is. On a busy band you will never find a frequency that is clear everywhere in the world. Just do the best you can.

73

-Jim
NU0C

On Thu, 17 Dec 2020 22:31:39 -0800
"Jason B" <sydbowen@...> wrote:

Yes, I've had issues myself with FT-8 on 40 meters. I had a perfectly clear slot, was calling a DX station and suddenly I saw KB5VXX QRM...I immediately hit halt TX and went to look where I was transmitting, but still didn't see anyone in the slot I had chosen. Idk, but it was pretty crowded. First time I've ever been called out for QRM. I call myself trying to be careful. Oops.


locked Re: v2.2.2 hamlib error

Reino Talarmo
 

Jan,

Yes as all communication through com ports is managed by Hamlib, even in the case no data is conveyed only RTS or DTR.

That’s why the related com port needs to be a valid one on Windows point of view. You may test that in wsjt-x without connecting any rig (set to none). By the way how you are connecting PTT to rig?

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of jan kappert
Sent: 18. joulukuuta 2020 16:09
To: main@WSJTX.groups.io; Reino Talarmo <reino.talarmo@...>; main@WSJTX.groups.io
Subject: Re: [WSJTX] v2.2.2 hamlib error

 

Reino,

 

Is a hamlib error like this generated while we have no rig and only PTT function?

 

Br. Jan, PAoPLY

 

Op vr, dec. 18, 2020 om 10:25 schreef Reino Talarmo

 


locked Re: Crowded frequencies

mchenryproj <mchenryproj@...>
 

Be aware that the audio bandwidth you see in the spectrum window is the norm and if you go lower than say 200 Hz or higher than say 2500 Hz you may not be found by everyone.  I would be in favor of maybe a second freq on 40m though. That's a crazy spot most of the day for me here in mid Ohio.

A lot of radios kick in a bandwidth filter when they go to either USB or a digital modes and may loose a part of the audio spectrum at the edges is another thing to consider.

I do know that if you attempt to TX very late in a given cycle the program will wait it out until the next TX cycle but maybe that TX timer should be a little tighter? That is, I see little reason for any partial transmissions past the longest delay of those doing EME. that you need a few seconds for but I see no reason for a partial transmissions at the halfway mark for example.  This would need to be by type as MS pounds it out multiple times so a partial TX sequence there makes some sense.

If I understand the software and procedures correctly that is.

I will say I have had decent success lately on 6m, 10m and 15m in FT8.  A local and I have run everything including 222 up to and including 1296.  We skipped 928 as there is almost nothing available for that band unless you go with pricey transverters.

Best of luck in the hunts and Happy Holidays to all.

Sean
KB8JNE
EN80qc (and beyond)

Spell checked by the NSA.

On Fri, Dec 18, 2020 at 10:06 AM, James Gill via groups.io
<jimvgill@...> wrote:



locked Re: Crowded frequencies

Kermit Lehman
 

  Jim writes:

I almost never respond to a CQ on the caller's frequency ...

My rule is: If someone makes an initial CQ it I'll jump right on his frequency.  Often that's all the time I have for and I hope I'll be the first one in.

But if he comes back to someone else, I'll move my TX to a vacant spot not too far away (if there is one) and tail end after his final 73 or RR73 transmission.  Repeat as necessary.  That often works, especially when a whole crowd of people jump on his frequency all at once and obliterate each other.

73,
Ken, AB1J


-----Original Message-----
From: James Gill via groups.io <jimvgill@...>
To: main@WSJTX.groups.io
Sent: Fri, Dec 18, 2020 2:52 pm
Subject: Re: [WSJTX] Crowded frequencies

Thanks to everyone who responded to my "crowded frequencies" email.

I almost never respond to a CQ on the caller's frequency although I often get calls on "my" frequency. In some respects that's not a bad idea. If I find an empty "channel" (it looks like a channel on the waterfall), unless I'm completely confused and I often am at my age, what I am seeing is not the time slot I will transmit on but the time slot I would listen on. So that time slot would be open for someone to call me on. Of course, if more than one person calls -- and I'm always surprised when that happens -- it may make things difficult. I try to remind myself that since I can't see the time slot I will transmit on, I may not be on a frequency that is not in use. And I hate it when WSJT-X sends a call 8 seconds late and can't be decoded. That's just QRM.

I've been a ham for 60 years (not active in many of them) and I've never been able to work DX the way I have with FT8 over the last couple months with my 20 watts and a wire antenna. I have worked South Africa and New Zealand for the FIRST time. I had two stations in France call me after one CQ which was a pleasant shock. And, I worked both of them! I've never had a dx station answer my CQ until FT8.

The last "On the Air" magazine had an article about making a dual band antenna with ladder line. I'm going to try it for 30 and 17. My EFHW works 40-20-15 and 10. I think 30 may be an option when 40 is jammed.

I will also try FT4 if I can figure out how to do it.

It was also suggested to me that I could use the edges of the band by moving my VFO up or down a little bit. I will be trying that. The bottom edge seems to be busier than the top edge.

Thanks again for all of your suggestions. Sorry to run on so long.


73s

Jim - W4GMU



locked Re: Crowded frequencies

K8BL BOB LIDDY <k8bl@...>
 

Lots of excellent comments/suggestions have come on this thread. Bravo!!

For my 2 cents, I have observed a thick cluster of stations smack in the
middle of the audio bandpass. They sit right on 1500 Hz +/- 500 Hz. Folks
having trouble making Q's might want to try what QRPers do and that is
to hang out on the edges of busy portions where there is a lesser chance
of being covered by stronger stations. Try going around 500 or 2500 Hz
and you'll see your contacts increase. I usually run 10-30W and that has
worked well for me.

GL/73,   Bob  K8BL


On Friday, December 18, 2020, 09:19:44 AM EST, Bob McGraw - K4TAX <rmcgraw@...> wrote:


The software does a great job in terms of timing.  Also, it deals very efficiently with QRM from adjacent stations.   What is unknown is how your radio AGC deals with strong signals.   What I find in a crowded band, when I'm transmitting, other stations I saw on my waterfall are receiving.   Also, the software will select if you should use even or odd  time segments.   Although I've called stations and had others answer by the station I was calling, I wait for them to send RR73 or RRR and then call them again.    There's lots of "channels" in the WSJT-X FT-8 segment.

I find that many stations are running excessive power.  Not wanting to start a power war but remember we should run the power needed for effective communication.  And this is not a specifically a "low power mode".    Just try working the JA's on 160 M and you'll see what I mean.   I typically run 100 watts or less, depending on band conditions, although I may run more if needed.  But never run everything at full bore just to make contacts.

73

Bob, K4TAX

On 12/18/2020 12:31 AM, Jason B wrote:
Yes, I've had issues myself with FT-8 on 40 meters. I had a perfectly clear slot, was calling a DX station and suddenly I saw KB5VXX QRM...I immediately hit halt TX and went to look where I was transmitting, but still didn't see anyone in the slot I had chosen. Idk, but it was pretty crowded. First time I've ever been called out for QRM. I call myself trying to be careful. Oops. 



  

Virus-free. www.avg.com



locked Re: Crowded frequencies

NR4U Bob AFMARS
 

On 12/18/2020 09:16, lmeeny wrote:
Hello,

Just an observation ... in my experience WSJT-X can decode signals just
a few Hz apart.

Thanks for saying that. Saved me ti me, hihi

literally, just a few or maybe even one Hz apart. Many times.


--
73
Bob KD7YZ
AMSAT LM #901


--
--
Bob KD7YZ in NE Kentucky


locked ft4 and tx5

Dave Garber
 

i noticed today, the using 2.3.0 rc2, that while I was trying to respond to a station, tx5 became one of my messages, and not a generated hiscall mycall 73 as normal

has this been reported yet


Dave Garber
VE3WEJ / VE3IE


locked Re: Crowded frequencies

James Gill
 

Thanks to everyone who responded to my "crowded frequencies" email.

I almost never respond to a CQ on the caller's frequency although I often get calls on "my" frequency. In some respects that's not a bad idea. If I find an empty "channel" (it looks like a channel on the waterfall), unless I'm completely confused and I often am at my age, what I am seeing is not the time slot I will transmit on but the time slot I would listen on. So that time slot would be open for someone to call me on. Of course, if more than one person calls -- and I'm always surprised when that happens -- it may make things difficult. I try to remind myself that since I can't see the time slot I will transmit on, I may not be on a frequency that is not in use. And I hate it when WSJT-X sends a call 8 seconds late and can't be decoded. That's just QRM.

I've been a ham for 60 years (not active in many of them) and I've never been able to work DX the way I have with FT8 over the last couple months with my 20 watts and a wire antenna. I have worked South Africa and New Zealand for the FIRST time. I had two stations in France call me after one CQ which was a pleasant shock. And, I worked both of them! I've never had a dx station answer my CQ until FT8.

The last "On the Air" magazine had an article about making a dual band antenna with ladder line. I'm going to try it for 30 and 17. My EFHW works 40-20-15 and 10. I think 30 may be an option when 40 is jammed.

I will also try FT4 if I can figure out how to do it.

It was also suggested to me that I could use the edges of the band by moving my VFO up or down a little bit. I will be trying that. The bottom edge seems to be busier than the top edge.

Thanks again for all of your suggestions. Sorry to run on so long.

73s

Jim - W4GMU


locked Re: Crowded frequencies

lmeeny
 

Hello,

Just an observation ... in my experience WSJT-X can decode signals just a few Hz apart.

Ed W2GHD


locked Re: Crowded frequencies

Bob McGraw - K4TAX <rmcgraw@...>
 

The software does a great job in terms of timing.  Also, it deals very efficiently with QRM from adjacent stations.   What is unknown is how your radio AGC deals with strong signals.   What I find in a crowded band, when I'm transmitting, other stations I saw on my waterfall are receiving.   Also, the software will select if you should use even or odd  time segments.   Although I've called stations and had others answer by the station I was calling, I wait for them to send RR73 or RRR and then call them again.    There's lots of "channels" in the WSJT-X FT-8 segment.

I find that many stations are running excessive power.  Not wanting to start a power war but remember we should run the power needed for effective communication.  And this is not a specifically a "low power mode".    Just try working the JA's on 160 M and you'll see what I mean.   I typically run 100 watts or less, depending on band conditions, although I may run more if needed.  But never run everything at full bore just to make contacts.

73

Bob, K4TAX

On 12/18/2020 12:31 AM, Jason B wrote:
Yes, I've had issues myself with FT-8 on 40 meters. I had a perfectly clear slot, was calling a DX station and suddenly I saw KB5VXX QRM...I immediately hit halt TX and went to look where I was transmitting, but still didn't see anyone in the slot I had chosen. Idk, but it was pretty crowded. First time I've ever been called out for QRM. I call myself trying to be careful. Oops. 



Virus-free. www.avg.com


locked Re: v2.2.2 hamlib error

jan kappert <2016pa0ply@...>
 

Reino,

Is a hamlib error like this generated while we have no rig and only PTT function?

Op vr, dec. 18, 2020 om 10:25 schreef Reino Talarmo
<reino.talarmo@...>:



locked Re: Crowded frequencies

Angelo Bione
 

Try 60M. I have been enjoying this band for some time.


locked Re: Crowded frequencies

mchenryproj <mchenryproj@...>
 

One of the cool things about the digital concept is that you can return or instigate a call anywhere in the audio range and still get responses or complete a Q.

If I see that someone interesting is on say 1100 Hz but it is crowded there or say the opposite "time slot" has many people returning their CQ, you can pick an open space in the audio spectrum and still return the call successfully. I think a lot of folks forget this at times.

The other thing is, if I am responding to a CW half the world away I have to realize that just because a spot seems empty in the spectrum at my location, there could be half a dozen people in that range where the person calling CQ is.  I hear this happen all the time on SSB and everyone immediately goes all negative on the party returning the call but they too need to realize that where I am it may be a totally empty spot in the spectrum.

As the band evolves we sort of drift into each other and folks get all upset that someone is on top of them, mid QSO when what may have happened is 2 complete conversations were happening on the same frequency but due to changing "conditions" they start drifting in top of each other when earlier they could successfully have both conversations happening without issue.

Anyway, it's crowded at times so everyone should have some benefit of the doubt in their heads in such situations.  As I mentioned, I jump over to FT4 if it's too crowded.

Happy Holidays everyone.

Sean
KB8JNE

Spell checked by the NSA.

On Fri, Dec 18, 2020 at 1:54 AM, Jason B
<sydbowen@...> wrote: