Date   

locked Re: WSPR

Stan Gammons
 

On 5/14/22 14:49, Ellis Birt (G7SAI) via groups.io wrote:
If you have the gps for time you may as well use it for location and to discipline your DDS frequency

Yes.  May take a month to get the GPS module from China though :(


73

Stan
KM4HQE


locked Re: error scanning adif log #adiFiles

Bill Parris
 

Thanks Martin ..... yep, I was opening the wrong one. Got it done. Thanks for the help. at 85, my mind "slips" occasionally!!

73,

Bill, AA4R


locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

 

20:17 pm est. I am going to stop transmitting, but my radio will still be on 28.140 and I will still be monitoring FST4-30. If anything changes I will update. From time to time I will transmit for a few minutes and then stop and just monitor. Thank you to all who have listened or tried to reply this evening. I appreciate it. KN4FLO, James, 73.


locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

 

Thank you for at trying! KN4FLO, James, 73.

On Saturday, May 14, 2022, 07:28:23 PM EDT, Gary Rogers <cgaryrogers190@...> wrote:

OK Thanks…I haven’t hear you either.

On May 14, 2022, at 4:27 PM, James Buie <ars.kn4flo@...> wrote:

No copy at EM85. I have a zero copy. TNX, KN4FLO.
    On Saturday, May 14, 2022, 07:25:08 PM EDT, Gary Rogers <cgaryrogers190@...> wrote: 

I’m calling from FL on 30 secs past the minute…Copy?

On May 14, 2022, at 3:41 PM, James Buie <ars.kn4flo@...> wrote:

Thanks. KN4FLO, 73.
    On Saturday, May 14, 2022, 06:38:55 PM EDT, Gary Rogers <cgaryrogers190@...> wrote: 

I am listening via the KFS websdr in Half Moon Bay CA

KO3F

On May 14, 2022, at 3:11 PM, James Buie <ars.kn4flo@...> wrote:

05/14/2022 18:08 pm est. I am going to be transmitting FST4-30 Even on 28.140. F Low will be 1500 and F High will be 2500. I will be at 2000. I will be on the air doing FST4-30 for the next few hours. At some point, I might switch over and go back to FT8. From now until about 20:00 pm est. I will be calling CQ. Thank you. KN4FLO, James, 73.

























locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

 

I am going to extend the time passed 20:00 pm est. I am going to go to at least 21:00 pm est. Thank you to all who are listening or trying to reply. It is much appreciated. KN4FLO, James. 73.


locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

Gary Rogers
 

OK Thanks…I haven’t hear you either.

On May 14, 2022, at 4:27 PM, James Buie <ars.kn4flo@...> wrote:

No copy at EM85. I have a zero copy. TNX, KN4FLO.
On Saturday, May 14, 2022, 07:25:08 PM EDT, Gary Rogers <cgaryrogers190@...> wrote:

I’m calling from FL on 30 secs past the minute…Copy?

On May 14, 2022, at 3:41 PM, James Buie <ars.kn4flo@...> wrote:

Thanks. KN4FLO, 73.
On Saturday, May 14, 2022, 06:38:55 PM EDT, Gary Rogers <cgaryrogers190@...> wrote:

I am listening via the KFS websdr in Half Moon Bay CA

KO3F

On May 14, 2022, at 3:11 PM, James Buie <ars.kn4flo@...> wrote:

05/14/2022 18:08 pm est. I am going to be transmitting FST4-30 Even on 28.140. F Low will be 1500 and F High will be 2500. I will be at 2000. I will be on the air doing FST4-30 for the next few hours. At some point, I might switch over and go back to FT8. From now until about 20:00 pm est. I will be calling CQ. Thank you. KN4FLO, James, 73.

























locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

 

No copy at EM85. I have a zero copy. TNX, KN4FLO.

On Saturday, May 14, 2022, 07:25:08 PM EDT, Gary Rogers <cgaryrogers190@...> wrote:

I’m calling from FL on 30 secs past the minute…Copy?

On May 14, 2022, at 3:41 PM, James Buie <ars.kn4flo@...> wrote:

Thanks. KN4FLO, 73.
    On Saturday, May 14, 2022, 06:38:55 PM EDT, Gary Rogers <cgaryrogers190@...> wrote: 

I am listening via the KFS websdr in Half Moon Bay CA

KO3F

On May 14, 2022, at 3:11 PM, James Buie <ars.kn4flo@...> wrote:

05/14/2022 18:08 pm est. I am going to be transmitting FST4-30 Even on 28.140. F Low will be 1500 and F High will be 2500. I will be at 2000. I will be on the air doing FST4-30 for the next few hours. At some point, I might switch over and go back to FT8. From now until about 20:00 pm est. I will be calling CQ. Thank you. KN4FLO, James, 73.















locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

Gary Rogers
 

I’m calling from FL on 30 secs past the minute…Copy?

On May 14, 2022, at 3:41 PM, James Buie <ars.kn4flo@...> wrote:

Thanks. KN4FLO, 73.
On Saturday, May 14, 2022, 06:38:55 PM EDT, Gary Rogers <cgaryrogers190@...> wrote:

I am listening via the KFS websdr in Half Moon Bay CA

KO3F

On May 14, 2022, at 3:11 PM, James Buie <ars.kn4flo@...> wrote:

05/14/2022 18:08 pm est. I am going to be transmitting FST4-30 Even on 28.140. F Low will be 1500 and F High will be 2500. I will be at 2000. I will be on the air doing FST4-30 for the next few hours. At some point, I might switch over and go back to FT8. From now until about 20:00 pm est. I will be calling CQ. Thank you. KN4FLO, James, 73.















locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

 

Thanks. KN4FLO, 73.

On Saturday, May 14, 2022, 06:38:55 PM EDT, Gary Rogers <cgaryrogers190@...> wrote:

I am listening via the KFS websdr in Half Moon Bay CA

KO3F

On May 14, 2022, at 3:11 PM, James Buie <ars.kn4flo@...> wrote:

05/14/2022 18:08 pm est. I am going to be transmitting FST4-30 Even on 28.140. F Low will be 1500 and F High will be 2500. I will be at 2000. I will be on the air doing FST4-30 for the next few hours. At some point, I might switch over and go back to FT8. From now until about 20:00 pm est. I will be calling CQ. Thank you. KN4FLO, James, 73.





locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

Gary Rogers
 

I am listening via the KFS websdr in Half Moon Bay CA

KO3F

On May 14, 2022, at 3:11 PM, James Buie <ars.kn4flo@...> wrote:

05/14/2022 18:08 pm est. I am going to be transmitting FST4-30 Even on 28.140. F Low will be 1500 and F High will be 2500. I will be at 2000. I will be on the air doing FST4-30 for the next few hours. At some point, I might switch over and go back to FT8. From now until about 20:00 pm est. I will be calling CQ. Thank you. KN4FLO, James, 73.





locked Re: FST4-15 28.140 KN4FLO TESTING #FST4

 

05/14/2022 18:08 pm est. I am going to be transmitting FST4-30 Even on 28.140. F Low will be 1500 and F High will be 2500. I will be at 2000. I will be on the air doing FST4-30 for the next few hours. At some point, I might switch over and go back to FT8. From now until about 20:00 pm est. I will be calling CQ. Thank you. KN4FLO, James, 73.


locked Re: Puzzling QSO endings #QSO_practices

 

Thanks all for replying. It seems as if my practices are consistent with mainstream thoughts on QSO's end and courtesy. I'd like to have a 73, but I don't require it. Every logged QSO is sent to both eQSL and LoTW. I seldom get an eQSL from anyone saying the I am not in their log. When I check my eQSL listings, I see a handful of QSO's that I can't confirm in either my log or in WSJT's ALL.TXT. I keep several years' worth of ALL.TXT to use with a search facility I've written in PHP.

__________
Dan – K4SHQ
CFI/II

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Lawrence Godek
Sent: Friday, May 13, 2022 8:16 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Puzzling QSO endings #QSO_practices

I do the same.


On 5/13/2022 10:03 AM, chas cartmel wrote:
Just for information I always send a '73' or a 'RR73" to a contacted station when signal reports are exchanged and acknowledged.
For me it is operating 'manners' rather than a necessity.

The QSO is logged automatically but I mark it as no '73' and tend not
to QSL these stations unless there is QSB and signal weak . It's only 30 seconds after all.
I also do not work stations responding to my CQ with a signal report rather than a grid square. Again 30 seconds of effort.


73 Charlie
G4EST
www.g4est.me.uk
Stay safe out there



-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Dan
Malcolm
Sent: Friday, May 13, 2022 1:43 PM
To: main@WSJTX.groups.io
Subject: [WSJTX] Puzzling QSO endings #QSO_practices

I've observed this operating practice for some time now and not such a big deal. FT8 QSO should, but don't have to, end with 73's being exchanged. Many don't send a 73, but end the QSO after sending a signal report. That's fine. But I also see some operators will continue sending signal reports until I have answered with a 73 several times. I'll usually get a confirmation via eQSL or LoTW so I assume they received my signal report. This makes me think I'm missing something. Is there an explanation?


__________
Dan - K4SHQ
CFI/II





This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com








locked Re: Puzzling QSO endings #QSO_practices

 

Mike,
I'll reply to an R-XX with a plane 73 up to four times. Then I assume he just can't receive me. Sometimes I'll use JTAlert's message facility to send a notification that I have them in my log.

Thanks for the clarification.
__________
Dan – K4SHQ
CFI/II

-----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Michael Black via groups.io
Sent: Friday, May 13, 2022 11:54 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Puzzling QSO endings #QSO_practices

There are those that expect a 73 and those that don't.
If you or they are using the standard RRR response then both 73's are usually used in FT8.
But...they will log when they send their 73.
I've never seen anybody end after an R-XX report.  If they keep sending it means they didn't get your 73.
Mike W9MDB




On Friday, May 13, 2022, 11:48:14 AM CDT, Dan Malcolm <k4shq@...> wrote:

I've observed this operating practice for some time now and not such a big deal.  FT8 QSO should, but don't have to, end with 73's being exchanged.  Many don't send a 73, but end the QSO after sending a signal report.  That's fine. But I also see some operators will continue sending signal reports until I have answered with a 73 several times.  I'll usually get a confirmation via eQSL or LoTW so I assume they received my signal report.  This makes me think I'm missing something.  Is there an explanation?


__________
Dan - K4SHQ
CFI/II


locked Re: WSPR

Ellis Birt (G7SAI)
 

If you have the gps for time you may as well use it for location and to discipline your DDS frequency


locked Re: error scanning adif log #adiFiles

Martin G0HDB
 

On Sat, May 14, 2022 at 06:10 PM, Bill Parris wrote:

I know this has been covered many times in the past, but my problem continues.
I have upgraded to the latest version, still have the error message. I have
read all of the previous posts regarding fixing this. When I bring up the
file in notepad, the header does not appear, just the first logging entry.
How can I locate the header?
Bill, AA4R
Bill:

Are you sure you're looking at the correct file, namely wsjtx_log.adi? There's another file - wsjtx.log - in the same directory but this isn't the ADIF file that gets read by the software; my understanding is that the .log file simply records all the logging transactions rather than containing the logged QSOs themselves.

--
Martin G0HDB


locked Re: WSPR

Stan Gammons
 

On 5/14/22 02:38, Alan G4ZFQ wrote:
I've seen some drift that was -3 or -4. Anything to be concerned about?
Stan,

If it is only occasional from maybe one or two stations then it is their
problem.
If it is on most spots of your transmission then you are drifting.

A search seems to indicate that some IC-7300s do drift on TX. eg
http://www.wsprnet.org/drupal/node/7967

73 Alan G4ZFQ

Hi Alan,

It looks like the IC-7300 does drift some. I tried with my TS-590SG and
the drift shows as 0 on almost every station that reported hearing me.
The TS-590SG does have the optional TCXO.

I've thought about making a WSPR transmitter using an Arduino UNO with a
GPS module for the time and an AD9850 DDS. Something like this
https://www.george-smart.co.uk/arduino/arduino_wspr/   The sketch
doesn't look quite right though. Will have to see if it works when I get
the Skylab GPS module.

73

Stan
KM4HQE


locked Re: Puzzling QSO endings #QSO_practices

Jeff Stillinger
 

You are right, it is not that big of a deal.    Your station, your process.

In my operation process, I do expect to see confirmation that my signal report was received, either with a RR73 or the full RRR 73 sequence.   If I do not receive acknowledgement after the third attempt, I assume the contact was lost to propagation.   I do not log it and I move on to the next contact without second thought. Win some, loose some, next...  I run my logging and uploads in real time.   With everything else there is to do in life, the chances of me taking time out to reconstruct a broken contact are slim to none.

On Friday 5/13/2022 07:43, Dan Malcolm wrote:
I've observed this operating practice for some time now and not such a big deal. FT8 QSO should, but don't have to, end with 73's being exchanged. Many don't send a 73, but end the QSO after sending a signal report. That's fine. But I also see some operators will continue sending signal reports until I have answered with a 73 several times. I'll usually get a confirmation via eQSL or LoTW so I assume they received my signal report. This makes me think I'm missing something. Is there an explanation?


__________
Dan - K4SHQ
CFI/II





locked Re: error scanning adif log #adiFiles

Reino Talarmo
 

Add this to the top of the fileADIF Export<adif_ver:5>3.1.1<created_timestamp:15>20220331 125620<programid:6>WSJT-X<programversion:5>2.5.4<eoh>
Hi
I don't have any header on the adif file, but wsjt-x reads it without any hiccup. 8000+ records is shortly shown on the info box in the bottom line left hand.
Do your wsjt_log.adi file possibly contains empty rows or a header line somewhere inside the file?
In notepad you could search for <eoh> or some contents of the proposed header above.
By the way I have in another wsjtx_log.adi file header "WSJT-X ADIF Export<eoh>".
73, Reino OH3mA


locked Re: error scanning adif log #adiFiles

Michael Black
 

Add this to the top of the fileADIF Export<adif_ver:5>3.1.1<created_timestamp:15>20220331 125620<programid:6>WSJT-X<programversion:5>2.5.4<eoh>

On Saturday, May 14, 2022, 12:10:10 PM CDT, Bill Parris <aa4r@...> wrote:

I know this has been covered many times in the past, but my problem continues.  I have upgraded to the latest version, still have the error message.  I have read all of the previous posts regarding fixing this.  When I bring up the file in notepad, the header does not appear, just the first logging entry.  How can I locate the header?
Bill, AA4R


locked error scanning adif log #adiFiles

Bill Parris
 

I know this has been covered many times in the past, but my problem continues. I have upgraded to the latest version, still have the error message. I have read all of the previous posts regarding fixing this. When I bring up the file in notepad, the header does not appear, just the first logging entry. How can I locate the header?
Bill, AA4R

2941 - 2960 of 36948