Topics

Kicking out of Enable TX #transmit


Williams, G (af8c)
 

Hi Bill,

1.

Recently I experienced a problem in FT8 operation (V2.2.2) where I was trying to work TI5GAX. After I clicked Enable TX, after two 15 second cycles the Enable TX was turned off without my input.  This happened twice and then after that I was able to continue normally.  This problem occurred today with a different attempted QSO but I now don't remember the other operator's call sign.

So today I decided to look into ALL.TXT to see if there were any clues for the problem. I did not find any crumbs in the file to indicate what the problem was. Nothing was found even with a hexadecimal view. Is there a known reason?

2. Below is a section of ALL.TXT, probably not for when (1) occurred. I have edited all \x20  space characters to comma for clarity.

There are two styles of text strings. First is for most text lines. Second is where my transmit occurred. Notice the long fill of commas at the end of the strings. Is this also by design or perhaps an oversight?  I don't believe this feature is related to the cause of the problem in (1).   (To save space I have removed some unrelated text lines.)

210102_123145,,,,,7.074,Rx,FT8,,,,-14,,0.1,1829,KD4CM,N3JD,EN91
210102_123200,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,R+05,,,,,,,,,,,,,,,,,,,,,
210102_123215,,,,,7.074,Rx,FT8,,,,,,9,,0.1,,958,KD4CM,KC1BUF,FN43
210102_123215,,,,,7.074,Rx,FT8,,,,-11,,0.1,,243,CQ,KA3ZLS,FM28
210102_123215,,,,,7.074,Rx,FT8,,,,,-7,-0.1,2375,HC1DAZ,N2SS,EL96
210102_123215,,,,,7.074,Rx,FT8,,,,,,8,,0.2,1360,N9CBS,W0WKO,R-16
210102_123215,,,,,7.074,Rx,FT8,,,,-16,,0.2,,471,AF8C,VA3BJD,-14
210102_123215,,,,,7.074,Rx,FT8,,,,,-4,,0.1,,957,CQ,K5JF,EL89
210102_123230,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,73,,,,,,,,,,,,,,,,,,,,,,,
210102_123233,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,VA3BJD,AF8C,R-16,,,,,,,,,,,,,,,,,,,,,
210102_123245,,,,,7.074,Rx,FT8,,,,,,9,,0.1,1000,N1GBE,W5MZX,EM50

---

--73, Glenn, AF8C





Virus-free. www.avast.com


Reino Talarmo
 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Williams, G (af8c) via groups.io
Sent: 13. tammikuuta 2021 7:15
To: main@WSJTX.groups.io
Subject: [WSJTX] Kicking out of Enable TX #Transmit

 

Hi Bill,

1.

Recently I experienced a problem in FT8 operation (V2.2.2) where I was trying to work TI5GAX. After I clicked Enable TX, after two 15 second cycles the Enable TX was turned off without my input.  This happened twice and then after that I was able to continue normally.  This problem occurred today with a different attempted QSO but I now don't remember the other operator's call sign.

So today I decided to look into ALL.TXT to see if there were any clues for the problem. I did not find any crumbs in the file to indicate what the problem was. Nothing was found even with a hexadecimal view. Is there a known reason?

2. Below is a section of ALL.TXT, probably not for when (1) occurred. I have edited all \x20  space characters to comma for clarity.

There are two styles of text strings. First is for most text lines. Second is where my transmit occurred. Notice the long fill of commas at the end of the strings. Is this also by design or perhaps an oversight?  I don't believe this feature is related to the cause of the problem in (1).   (To save space I have removed some unrelated text lines.)

210102_123145,,,,,7.074,Rx,FT8,,,,-14,,0.1,1829,KD4CM,N3JD,EN91
210102_123200,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,R+05,,,,,,,,,,,,,,,,,,,,,
210102_123215,,,,,7.074,Rx,FT8,,,,,,9,,0.1,,958,KD4CM,KC1BUF,FN43
210102_123215,,,,,7.074,Rx,FT8,,,,-11,,0.1,,243,CQ,KA3ZLS,FM28
210102_123215,,,,,7.074,Rx,FT8,,,,,-7,-0.1,2375,HC1DAZ,N2SS,EL96
210102_123215,,,,,7.074,Rx,FT8,,,,,,8,,0.2,1360,N9CBS,W0WKO,R-16
210102_123215,,,,,7.074,Rx,FT8,,,,-16,,0.2,,471,AF8C,VA3BJD,-14
210102_123215,,,,,7.074,Rx,FT8,,,,,-4,,0.1,,957,CQ,K5JF,EL89
210102_123230,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,73,,,,,,,,,,,,,,,,,,,,,,,
210102_123233,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,VA3BJD,AF8C,R-16,,,,,,,,,,,,,,,,,,,,,
210102_123245,,,,,7.074,Rx,FT8,,,,,,9,,0.1,1000,N1GBE,W5MZX,EM50

---

--73, Glenn, AF8C

Hi Glenn,
Unfortunately the ALL.TXT clip is not about that instance. ALL.txt file is just a record what you received and sent converted into human readable format. If you provide us an ALL.TXT clip, please, don’t edit it as it is easier to read without editing, hi! The long strings of space characters at the end of some lines are normal.

Only question can ask, were your TX frequency on or close to TI5GAX frequency and did TI5GAX answered to somebody else, when your Tx enable went off?

73, Reino OH3mA

 

 

 

Image removed by sender.

Virus-free. www.avast.com

 


Williams, G (af8c)
 

Hello,
I am looking for any known reasons for TX Enable to be knocked off like that.  It's too late now to see whether my frequency was close to his.  Assuming that in some QSO someday this will happen again, I will then check on the frequencies.

--73, Glenn, AF8C

On 1/13/2021 4:00 AM, Reino Talarmo via groups.io wrote:

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Williams, G (af8c) via groups.io
Sent: 13. tammikuuta 2021 7:15
To: main@WSJTX.groups.io
Subject: [WSJTX] Kicking out of Enable TX #Transmit

 

Hi Bill,

1.

Recently I experienced a problem in FT8 operation (V2.2.2) where I was trying to work TI5GAX. After I clicked Enable TX, after two 15 second cycles the Enable TX was turned off without my input.  This happened twice and then after that I was able to continue normally.  This problem occurred today with a different attempted QSO but I now don't remember the other operator's call sign.

So today I decided to look into ALL.TXT to see if there were any clues for the problem. I did not find any crumbs in the file to indicate what the problem was. Nothing was found even with a hexadecimal view. Is there a known reason?

2. Below is a section of ALL.TXT, probably not for when (1) occurred. I have edited all \x20  space characters to comma for clarity.

There are two styles of text strings. First is for most text lines. Second is where my transmit occurred. Notice the long fill of commas at the end of the strings. Is this also by design or perhaps an oversight?  I don't believe this feature is related to the cause of the problem in (1).   (To save space I have removed some unrelated text lines.)

210102_123145,,,,,7.074,Rx,FT8,,,,-14,,0.1,1829,KD4CM,N3JD,EN91
210102_123200,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,R+05,,,,,,,,,,,,,,,,,,,,,
210102_123215,,,,,7.074,Rx,FT8,,,,,,9,,0.1,,958,KD4CM,KC1BUF,FN43
210102_123215,,,,,7.074,Rx,FT8,,,,-11,,0.1,,243,CQ,KA3ZLS,FM28
210102_123215,,,,,7.074,Rx,FT8,,,,,-7,-0.1,2375,HC1DAZ,N2SS,EL96
210102_123215,,,,,7.074,Rx,FT8,,,,,,8,,0.2,1360,N9CBS,W0WKO,R-16
210102_123215,,,,,7.074,Rx,FT8,,,,-16,,0.2,,471,AF8C,VA3BJD,-14
210102_123215,,,,,7.074,Rx,FT8,,,,,-4,,0.1,,957,CQ,K5JF,EL89
210102_123230,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,73,,,,,,,,,,,,,,,,,,,,,,,
210102_123233,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,VA3BJD,AF8C,R-16,,,,,,,,,,,,,,,,,,,,,
210102_123245,,,,,7.074,Rx,FT8,,,,,,9,,0.1,1000,N1GBE,W5MZX,EM50

---

--73, Glenn, AF8C

Hi Glenn,
Unfortunately the ALL.TXT clip is not about that instance. ALL.txt file is just a record what you received and sent converted into human readable format. If you provide us an ALL.TXT clip, please, don’t edit it as it is easier to read without editing, hi! The long strings of space characters at the end of some lines are normal.

Only question can ask, were your TX frequency on or close to TI5GAX frequency and did TI5GAX answered to somebody else, when your Tx enable went off?

73, Reino OH3mA

 

 

 

Image removed by sender.

Virus-free. www.avast.com

 






neil_zampella
 

The system will disable Tx if you are answering a CQ caller on their frequency or within a few Hz (I forget exactly) of that frequency.  Its always done that.   This is another reason its advised to try to find a clear area on the waterfall, set your Tx frequency there, and check the HOLD TX box.

Neil, KN3ILZ

On 1/13/2021 7:34 AM, Williams, G (af8c) via groups.io wrote:
Hello,
I am looking for any known reasons for TX Enable to be knocked off like that.  It's too late now to see whether my frequency was close to his.  Assuming that in some QSO someday this will happen again, I will then check on the frequencies.

--73, Glenn, AF8C

On 1/13/2021 4:00 AM, Reino Talarmo via groups.io wrote:

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Williams, G (af8c) via groups.io
Sent: 13. tammikuuta 2021 7:15
To: main@WSJTX.groups.io
Subject: [WSJTX] Kicking out of Enable TX #Transmit

 

Hi Bill,

1.

Recently I experienced a problem in FT8 operation (V2.2.2) where I was trying to work TI5GAX. After I clicked Enable TX, after two 15 second cycles the Enable TX was turned off without my input.  This happened twice and then after that I was able to continue normally.  This problem occurred today with a different attempted QSO but I now don't remember the other operator's call sign.

So today I decided to look into ALL.TXT to see if there were any clues for the problem. I did not find any crumbs in the file to indicate what the problem was. Nothing was found even with a hexadecimal view. Is there a known reason?

2. Below is a section of ALL.TXT, probably not for when (1) occurred. I have edited all \x20  space characters to comma for clarity.

There are two styles of text strings. First is for most text lines. Second is where my transmit occurred. Notice the long fill of commas at the end of the strings. Is this also by design or perhaps an oversight?  I don't believe this feature is related to the cause of the problem in (1).   (To save space I have removed some unrelated text lines.)

210102_123145,,,,,7.074,Rx,FT8,,,,-14,,0.1,1829,KD4CM,N3JD,EN91
210102_123200,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,R+05,,,,,,,,,,,,,,,,,,,,,
210102_123215,,,,,7.074,Rx,FT8,,,,,,9,,0.1,,958,KD4CM,KC1BUF,FN43
210102_123215,,,,,7.074,Rx,FT8,,,,-11,,0.1,,243,CQ,KA3ZLS,FM28
210102_123215,,,,,7.074,Rx,FT8,,,,,-7,-0.1,2375,HC1DAZ,N2SS,EL96
210102_123215,,,,,7.074,Rx,FT8,,,,,,8,,0.2,1360,N9CBS,W0WKO,R-16
210102_123215,,,,,7.074,Rx,FT8,,,,-16,,0.2,,471,AF8C,VA3BJD,-14
210102_123215,,,,,7.074,Rx,FT8,,,,,-4,,0.1,,957,CQ,K5JF,EL89
210102_123230,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,73,,,,,,,,,,,,,,,,,,,,,,,
210102_123233,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,VA3BJD,AF8C,R-16,,,,,,,,,,,,,,,,,,,,,
210102_123245,,,,,7.074,Rx,FT8,,,,,,9,,0.1,1000,N1GBE,W5MZX,EM50

---

--73, Glenn, AF8C

Hi Glenn,
Unfortunately the ALL.TXT clip is not about that instance. ALL.txt file is just a record what you received and sent converted into human readable format. If you provide us an ALL.TXT clip, please, don’t edit it as it is easier to read without editing, hi! The long strings of space characters at the end of some lines are normal.

Only question can ask, were your TX frequency on or close to TI5GAX frequency and did TI5GAX answered to somebody else, when your Tx enable went off?

73, Reino OH3mA

 

 

 

Image removed by sender.

Virus-free. www.avast.com

 







Reino Talarmo
 

<I am looking for any known reasons for TX Enable to be knocked off like that.  It's too late now to see whether my frequency was close to his.  Assuming that in some QSO someday this will happen again, I will then check on the frequencies.

--73, Glenn, AF8C

Glenn,

If you still have all.txt file covering that time available, then it should contain almost all information needed to find out what happened. Well, not operator actions and Enable Tx state. If you wish help on that contact me directly.

73, Reino, OH3mA


Ed W2LCQ
 

I also experience Enable TX going off for no apparent reason. I have to watch it carefully if I’m in the middle of calling a station to restore it quickly. If you have a remedy for this I would greatly appreciate knowing. Thanks a lot. 

73 de W2LCQ, Ed Jones

Frankford Radio Club
BUG 204 - TBDXC 1337 - CWops (Life) 701 - SKCC 5474T - FISTS 12294 - QCWA 33438 - LICWC (Life) 51 Instructor - ARRL - New York County (Manhattan) FN30AT DXCC WAS

The scientists of today think deeply instead of clearly. One must be sane to think clearly, but one can think deeply and be quite insane.” ...Nicola Tesla



On Jan 13, 2021, at 8:35 AM, Williams, G (af8c) via groups.io <af8c@...> wrote:

 Hello,
I am looking for any known reasons for TX Enable to be knocked off like that.  It's too late now to see whether my frequency was close to his.  Assuming that in some QSO someday this will happen again, I will then check on the frequencies.

--73, Glenn, AF8C

On 1/13/2021 4:00 AM, Reino Talarmo via groups.io wrote:

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Williams, G (af8c) via groups.io
Sent: 13. tammikuuta 2021 7:15
To: main@WSJTX.groups.io
Subject: [WSJTX] Kicking out of Enable TX #Transmit

 

Hi Bill,

1.

Recently I experienced a problem in FT8 operation (V2.2.2) where I was trying to work TI5GAX. After I clicked Enable TX, after two 15 second cycles the Enable TX was turned off without my input.  This happened twice and then after that I was able to continue normally.  This problem occurred today with a different attempted QSO but I now don't remember the other operator's call sign.

So today I decided to look into ALL.TXT to see if there were any clues for the problem. I did not find any crumbs in the file to indicate what the problem was. Nothing was found even with a hexadecimal view. Is there a known reason?

2. Below is a section of ALL.TXT, probably not for when (1) occurred. I have edited all \x20  space characters to comma for clarity.

There are two styles of text strings. First is for most text lines. Second is where my transmit occurred. Notice the long fill of commas at the end of the strings. Is this also by design or perhaps an oversight?  I don't believe this feature is related to the cause of the problem in (1).   (To save space I have removed some unrelated text lines.)

210102_123145,,,,,7.074,Rx,FT8,,,,-14,,0.1,1829,KD4CM,N3JD,EN91
210102_123200,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,R+05,,,,,,,,,,,,,,,,,,,,,
210102_123215,,,,,7.074,Rx,FT8,,,,,,9,,0.1,,958,KD4CM,KC1BUF,FN43
210102_123215,,,,,7.074,Rx,FT8,,,,-11,,0.1,,243,CQ,KA3ZLS,FM28
210102_123215,,,,,7.074,Rx,FT8,,,,,-7,-0.1,2375,HC1DAZ,N2SS,EL96
210102_123215,,,,,7.074,Rx,FT8,,,,,,8,,0.2,1360,N9CBS,W0WKO,R-16
210102_123215,,,,,7.074,Rx,FT8,,,,-16,,0.2,,471,AF8C,VA3BJD,-14
210102_123215,,,,,7.074,Rx,FT8,,,,,-4,,0.1,,957,CQ,K5JF,EL89
210102_123230,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,73,,,,,,,,,,,,,,,,,,,,,,,
210102_123233,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,VA3BJD,AF8C,R-16,,,,,,,,,,,,,,,,,,,,,
210102_123245,,,,,7.074,Rx,FT8,,,,,,9,,0.1,1000,N1GBE,W5MZX,EM50

---

--73, Glenn, AF8C

Hi Glenn,
Unfortunately the ALL.TXT clip is not about that instance. ALL.txt file is just a record what you received and sent converted into human readable format. If you provide us an ALL.TXT clip, please, don’t edit it as it is easier to read without editing, hi! The long strings of space characters at the end of some lines are normal.

Only question can ask, were your TX frequency on or close to TI5GAX frequency and did TI5GAX answered to somebody else, when your Tx enable went off?

73, Reino OH3mA

 

 

 

Virus-free. www.avast.com

 








Dave Garber
 

In addition. If you select hold and the party you are calling moves to your hold frequency it will also kick you out if he answers someone else.


On Wed., Jan. 13, 2021, 9:28 a.m. neil_zampella, <neilz@...> wrote:

The system will disable Tx if you are answering a CQ caller on their frequency or within a few Hz (I forget exactly) of that frequency.  Its always done that.   This is another reason its advised to try to find a clear area on the waterfall, set your Tx frequency there, and check the HOLD TX box.

Neil, KN3ILZ

On 1/13/2021 7:34 AM, Williams, G (af8c) via groups.io wrote:
Hello,
I am looking for any known reasons for TX Enable to be knocked off like that.  It's too late now to see whether my frequency was close to his.  Assuming that in some QSO someday this will happen again, I will then check on the frequencies.

--73, Glenn, AF8C

On 1/13/2021 4:00 AM, Reino Talarmo via groups.io wrote:

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Williams, G (af8c) via groups.io
Sent: 13. tammikuuta 2021 7:15
To: main@WSJTX.groups.io
Subject: [WSJTX] Kicking out of Enable TX #Transmit

 

Hi Bill,

1.

Recently I experienced a problem in FT8 operation (V2.2.2) where I was trying to work TI5GAX. After I clicked Enable TX, after two 15 second cycles the Enable TX was turned off without my input.  This happened twice and then after that I was able to continue normally.  This problem occurred today with a different attempted QSO but I now don't remember the other operator's call sign.

So today I decided to look into ALL.TXT to see if there were any clues for the problem. I did not find any crumbs in the file to indicate what the problem was. Nothing was found even with a hexadecimal view. Is there a known reason?

2. Below is a section of ALL.TXT, probably not for when (1) occurred. I have edited all \x20  space characters to comma for clarity.

There are two styles of text strings. First is for most text lines. Second is where my transmit occurred. Notice the long fill of commas at the end of the strings. Is this also by design or perhaps an oversight?  I don't believe this feature is related to the cause of the problem in (1).   (To save space I have removed some unrelated text lines.)

210102_123145,,,,,7.074,Rx,FT8,,,,-14,,0.1,1829,KD4CM,N3JD,EN91
210102_123200,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,R+05,,,,,,,,,,,,,,,,,,,,,
210102_123215,,,,,7.074,Rx,FT8,,,,,,9,,0.1,,958,KD4CM,KC1BUF,FN43
210102_123215,,,,,7.074,Rx,FT8,,,,-11,,0.1,,243,CQ,KA3ZLS,FM28
210102_123215,,,,,7.074,Rx,FT8,,,,,-7,-0.1,2375,HC1DAZ,N2SS,EL96
210102_123215,,,,,7.074,Rx,FT8,,,,,,8,,0.2,1360,N9CBS,W0WKO,R-16
210102_123215,,,,,7.074,Rx,FT8,,,,-16,,0.2,,471,AF8C,VA3BJD,-14
210102_123215,,,,,7.074,Rx,FT8,,,,,-4,,0.1,,957,CQ,K5JF,EL89
210102_123230,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,TI5GAX,AF8C,73,,,,,,,,,,,,,,,,,,,,,,,
210102_123233,,,,,7.074,Tx,FT8,,,,,,0,,0.0,1330,VA3BJD,AF8C,R-16,,,,,,,,,,,,,,,,,,,,,
210102_123245,,,,,7.074,Rx,FT8,,,,,,9,,0.1,1000,N1GBE,W5MZX,EM50

---

--73, Glenn, AF8C

Hi Glenn,
Unfortunately the ALL.TXT clip is not about that instance. ALL.txt file is just a record what you received and sent converted into human readable format. If you provide us an ALL.TXT clip, please, don’t edit it as it is easier to read without editing, hi! The long strings of space characters at the end of some lines are normal.

Only question can ask, were your TX frequency on or close to TI5GAX frequency and did TI5GAX answered to somebody else, when your Tx enable went off?

73, Reino OH3mA

 

 

 

Virus-free. www.avast.com