Date   

Re: FT8 AUTO LOGGING

Bob
 

QSOs logged from WSJT-X (and its numerous clones are buffered in memnory for a few seconds before being written to the logbook. FT8 QSOs for 5 seconds, FT4 QSOs for 3 seconds. This is so that Logger32 does not waste CPU cycles in the very busy decode cycle between receive and transmit. 73.

On 01/20/2021 10:21 PM Richard Zalewski <dick.w7zr@...> wrote:
 
 
What appears to be happening is some QSOs are being held in some file that is not being processed.  I log a qso manually and I find that a completely different QSO is put at the bottom of the log.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
 
Be joyful in hope, patient in affliction, faithful in prayer

On Wed, Jan 20, 2021 at 7:16 PM Bill K4BX via groups.io <k4bx= yahoo.com@groups.io> wrote:
When auto logging FT8 QSO's from JTDX they don't show up at the end of the log.... but when I search for the calls they are found in the log. They just don't seem to be sorted by QSO time. Anyway if you right click on the log and do a search for the contacts you will find them. The Cherry-picking event viewer says the contacts were logged. Don't know why they don't appear at the bottom of the log page.
73 Bill K4BX

On 1/20/2021 7:01 PM, Bob wrote:
Richard, I know nothing about 'auto logging from WSJT-X', or for that matter WSJT-X. There is an option in Logger32 to attempt to bypass/override the requirement to click the mouse on the 'log this QSO' popup (the ARRL requirement for 'contemporaneous user input'. Whatever the hell that is) . If it works - Yay! If it doesn't , then :(
 
SeventyThree(s).
On 01/20/2021 7:14 PM Richard Zalewski <dick.w7zr@...> wrote:
 
 
Auto logging does not seem to be working for FT8.  Checked my band plan table all ok as nothing changed from before conversion.  If I manually select log qso from wsjt-x I see a flash on the l32 page but does not go into log.  Something changed from the conversion.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
 
Be joyful in hope, patient in affliction, faithful in prayer

 

 


Re: FT8 AUTO LOGGING

Bob
 

They just don't seem to be sorted by QSO time ... On the Logbook page window is the QSO DATE column header in red text? 73.

On 01/20/2021 10:16 PM Bill K4BX via groups.io <k4bx@...> wrote:
 
 
When auto logging FT8 QSO's from JTDX they don't show up at the end of the log.... but when I search for the calls they are found in the log. They just don't seem to be sorted by QSO time. Anyway if you right click on the log and do a search for the contacts you will find them. The Cherry-picking event viewer says the contacts were logged. Don't know why they don't appear at the bottom of the log page.
73 Bill K4BX

On 1/20/2021 7:01 PM, Bob wrote:
Richard, I know nothing about 'auto logging from WSJT-X', or for that matter WSJT-X. There is an option in Logger32 to attempt to bypass/override the requirement to click the mouse on the 'log this QSO' popup (the ARRL requirement for 'contemporaneous user input'. Whatever the hell that is) . If it works - Yay! If it doesn't , then :(
 
SeventyThree(s).
On 01/20/2021 7:14 PM Richard Zalewski <dick.w7zr@...> wrote:
 
 
Auto logging does not seem to be working for FT8.  Checked my band plan table all ok as nothing changed from before conversion.  If I manually select log qso from wsjt-x I see a flash on the l32 page but does not go into log.  Something changed from the conversion.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
 
Be joyful in hope, patient in affliction, faithful in prayer


Re: FT8 AUTO LOGGING

Richard Zalewski
 

Yes, band/modes were set.  At first they were just carried over from V3 but I checked them all.  Appear to be correct.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV


Be joyful in hope, patient in affliction, faithful in prayer


On Thu, Jan 21, 2021 at 4:15 AM Tom Wylie <thomasgwylie@...> wrote:
Have you set up your band/modes in V4 to show FT4 and FT8??


GM4FDM

On 21/01/2021 00:51, Richard Zalewski wrote:
> More info: Went to the log in WSJT and exported a qso as an adif file. 
> Then imported into L32.  It does not display on the log page.  When I
> try to import the same qso again it tells me it is in the log but still
> not displaying on the log page.
>
> Richard
> *W7ZR* ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU,
> J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
>
>
> */Be joyful in hope, patient in affliction, faithful in prayer/*
>
>
> On Wed, Jan 20, 2021 at 4:15 PM Richard Zalewski via groups.io
> <http://groups.io> <dick.w7zr=gmail.com@groups.io
> <mailto:gmail.com@groups.io>> wrote:
>
>     Auto logging does not seem to be working for FT8.  Checked my band
>     plan table all ok as nothing changed from before conversion.  If I
>     manually select log qso from wsjt-x I see a flash on the l32 page
>     but does not go into log.  Something changed from the conversion.
>
>     Richard
>     *W7ZR* ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF,
>     W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
>
>
>     */Be joyful in hope, patient in affliction, faithful in prayer/*
>
>






Tooltips

IZ5ILJ Lenio
 

Hi Bob, compliments for the great job and tnx so much for the best log program for us OM. 

For the new version 4 I had no problem with the update, I use a dual monitor and in version 4 the tooltips are placed not adjacent to the mouse like the old versions.

To explain better I am attaching a photo.

73's, Lenio - IZ5ILJ - #69.


CQWPX

Carlo Larosi
 

Statistic stops at SJ90 pfx. 73 Carlo IZ3ETU 


Re: FT8 AUTO LOGGING

Tom Wylie
 

Have you set up your band/modes in V4 to show FT4 and FT8??


GM4FDM

On 21/01/2021 00:51, Richard Zalewski wrote:
More info: Went to the log in WSJT and exported a qso as an adif file. Then imported into L32.  It does not display on the log page.  When I try to import the same qso again it tells me it is in the log but still not displaying on the log page.
Richard
*W7ZR* ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
*/Be joyful in hope, patient in affliction, faithful in prayer/*
On Wed, Jan 20, 2021 at 4:15 PM Richard Zalewski via groups.io <http://groups.io> <dick.w7zr=gmail.com@groups.io <mailto:gmail.com@groups.io>> wrote:
Auto logging does not seem to be working for FT8.  Checked my band
plan table all ok as nothing changed from before conversion.  If I
manually select log qso from wsjt-x I see a flash on the l32 page
but does not go into log.  Something changed from the conversion.
Richard
*W7ZR* ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF,
W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
*/Be joyful in hope, patient in affliction, faithful in prayer/*


Re: Enhancement Request - Multiple Radios/ SO2R

ja1nlx
 

How about using multi INI ?

Radio-aaa and bbb with default INI, Radio-ccc and ddd with 2nd INI, etc

73

On 2021/01/21 20:31, David KN2M wrote:
In general, as I have mentioned before, a selection of two radios is limiting.  Is there a way a retained selection three or more could be provided please?  Thank you.
--
73 de aki
JA1NLX


Re: Enhancement Request - Multiple Radios/ SO2R

David KN2M
 

In general, as I have mentioned before, a selection of two radios is limiting.  Is there a way a retained selection three or more could be provided please?  Thank you.


Re: Alert sounds

Jim Altman
 

Ah ha! I found it.  Windows had spontaneously changed to send my Logger32 sounds to the radio instead of the speakers.  Weird.

 

73

 

 

 

Jim Altman

jaltman636@...

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Jim Altman via groups.io
Sent: Thursday, January 21, 2021 6:09 AM
To: hamlogger@groups.io
Subject: [hamlogger] Alert sounds

 

 

I hadn’t noticed this before, as there are very few ‘new ones’ but my alert sounds don’t work.  I push test and nothing happens.  Am I missing something?  Am I the only one?

 

73 w4uck

 

 

 

Jim Altman

jaltman636@...

 


Re: Alert sounds

ja1nlx
 

Jim

This is my test setup. Clicking "Test" play wav. I have not checked using "real" spot though.

73


On 2021/01/21 20:09, Jim Altman wrote:

 

I hadn’t noticed this before, as there are very few ‘new ones’ but my alert sounds don’t work.  I push test and nothing happens.  Am I missing something?  Am I the only one?

 

73 w4uck

 

 

 

Jim Altman

jaltman636@...

 

--
73 de aki
JA1NLX


Alert sounds

Jim Altman
 

 

I hadn’t noticed this before, as there are very few ‘new ones’ but my alert sounds don’t work.  I push test and nothing happens.  Am I missing something?  Am I the only one?

 

73 w4uck

 

 

 

Jim Altman

jaltman636@...

 


Bind Macros

Rick EA4M
 

Hello all
I'm Rick EA4M a new user of Logger32 , I'm wondering if it's possible to bind F1 to F12 keys with shortcuts like CRTL+A to move the rotor or CRTL+C to clear the qso fields.....

Thanks a lot

Rick EA4M



Libre de virus. www.avast.com


Re: L32 LoTW problem

ok1tk
 

Hi Gary,

I do understand what you mean. What is really strange for me: I egenrated an ADIF file in Logger32 -> I uploaded it to LoTW via their SW and the file was accepted -> Then, I downloaded the file from LoTW and tried to upload it to L32 and then the problems appeared. But LoTW received the roginal date from my L32 ADIF file. I am bit confused.

Anyway. I will try to change the operator for 1 or 2 records in my Logger32 from OK1TK/P to OK1TK and the same with OK1RJO records and try if it helps.

It seems you could be right. I am not on my PC now but I checked the records on LoTW for OK1TK and all the QSO made by OK1TK/P were from JAN 2020 (just thrree days I was operating remotly via my friend's equipment). From all QSO made within these days I used as operator OK1TK and I have just 10 QSL on the LoTW web page. ANd there are 10 QSO which are not possible to update with the LoTW file.

All the records done for OK1RJO are with operators (JAKUB, ONDRA, TOMAS....). I tried to use OK1TK as operator while working as club operator of OK1RJO. And then it was not accepted by LoTW so that's why I changed the the op name from OK1TK to TOMAS.


I will test what you mentioned and if it works we will use the comment field for the op. name in Logger32 for OK1RJO. It is a shame that the Operator fidl can't be used for different ops working under one callsign as it is with club stations.

I agree if you use the example above for the user manual.

I thank you very very much for your support and will update you with the results of the test when I am at home this evening..

 
--
73! OK1TK


Re: Error 424

Gary Hinson
 

Hi Bob.

 

No problem here:

 

 

I’m using Windows 8.1, and I also have a localhost cluster connection open.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of infosys4u@...
Sent: 21 January 2021 17:03
To: hamlogger@groups.io
Subject: [hamlogger] Error 424

 

Hi,
I was using Logger 4.0.132 today and encountered this error while using the DX Spot window.  I tried to open the option menu, by right clicking the DX Spot grid and Error 424 popped up.  The error said....  Error 424 (Object required) in procedure MShFlexGrid1_MouseUp of Form wndDxSpot.  Error occured on Lines 400 to 480.

This error only occurs with the DX Cluster window is in use, via Telnet.  If Telnet is not active, no error occurs.  This error did not occur in v 3.5.

Tnx for the Help,
Bob
NE0CQ


Error 424

infosys4u@...
 

Hi,
I was using Logger 4.0.132 today and encountered this error while using the DX Spot window.  I tried to open the option menu, by right clicking the DX Spot grid and Error 424 popped up.  The error said....  Error 424 (Object required) in procedure MShFlexGrid1_MouseUp of Form wndDxSpot.  Error occured on Lines 400 to 480.

This error only occurs with the DX Cluster window is in use, via Telnet.  If Telnet is not active, no error occurs.  This error did not occur in v 3.5.

Tnx for the Help,
Bob
NE0CQ


Re: L32 LoTW problem

Gary Hinson
 

Hello OK1TK.

 

I’ve found the problem, looking carefully at the first QSO you sent.

 

I found it by breaking out the ADIF fields to separate lines, then lining up the two records side-by-side, adding blank lines to align the common fields:

 

 

The black entries match, aside from case changes (those don’t matter).

The orange entries are missing from one record or the other, or are formatted differently (e.g. LoTW explicitly uses the ISO 8601 date and time format).

The bold red entries show the problem: LoTW believes this QSO was with OK1TK but you have logged it under OK1TK/P.  Logger32 does not consider that a match, whereas LoTW evidently does (presuming that the record on the right represents what you signed and uploaded to LoTW.

 

I’m not going to check all the other records but if I were you I would compare the operator and station_callsign fields closely.

 

73

Gary  ZL2iFB

 

PS  If it’s OK by you, I would like to use this as a worked example for the v4 User Manual.

PPS  The manual comparison process is a candidate to develop into an automated utility, if any programmers Out There are inspired/bored …

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of ok1tk
Sent: 21 January 2021 02:30
To: hamlogger@groups.io
Subject: Re: [hamlogger] L32 LoTW problem

 

Hello Garry,

I compared the BAD.ADI file and my loogbook.adi files and can't find anything. Pls, see below. The first row is BAD.ADI and the second is my Logbook.ADI export.

OK1TK

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:6>UA3RLE<BAND:3>40M<FREQ:7>7.07459<FREQ_RX:7>7.07598<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200118<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>155300<APP_LoTW_QSO_TIMESTAMP:20>2020-01-18T15:53:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:2>54<COUNTRY:15>EUROPEAN RUSSIA<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>UA3<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>LO02RR<STATE:2>TB // Tambovskaya oblast' (Tambov Oblast)<CQZ:2>16<ITUZ:2>29<eor>

LOG: <DISTANCE:7>1885.00 <BAND:3>40M <CALL:6>UA3RLE <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>16 <DXCC:2>54 <FREQ:8>7.074590 <GRIDSQUARE:6>LO02rr <ITUZ:2>29 <MODE:3>FT8 <NAME:18>Vasiliy Pochechuev <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:3>UA3 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200118 <TIME_ON:6>155300 <QTH:17>Tambov, Tb 392020 <RST_RCVD:3>-09 <RST_SENT:3>-11 <TIME_OFF:6>155300 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:2>83 <FREQ_RX:8>7.075980 <COUNTRY:15>European Russia <APP_LOGGER32_LAT:16>52.7291666666667 <APP_LOGGER32_LNG:17>-41.4583333333333 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:6>RX3ASP<BAND:3>40M<FREQ:7>7.07619<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200119<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>183700<APP_LoTW_QSO_TIMESTAMP:20>2020-01-19T18:37:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:2>54<COUNTRY:15>EUROPEAN RUSSIA<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>RX3<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>KO85VT<STATE:2>MA // Moskva (Moscow)<CQZ:2>16<ITUZ:2>29<eor>

BAD: <DISTANCE:7>1679.00 <BAND:3>40M <CALL:6>RX3ASP <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>16 <DXCC:2>54 <FREQ:8>7.076190 <GRIDSQUARE:6>KO85vt <ITUZ:2>29 <MODE:3>FT8 <NAME:14>Yury Sarkisyan <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:3>RX3 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200119 <TIME_ON:6>183700 <QTH:26>Moscow, 15th Parkovaya Str <RST_RCVD:3>-01 <RST_SENT:3>-04 <TIME_OFF:6>183800 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:3>119 <FREQ_RX:8>7.076190 <COUNTRY:15>European Russia <APP_LOGGER32_LAT:7>55.8125 <APP_LOGGER32_LNG:17>-37.7916666666667 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:5>OK1TK<STATION_CALLSIGN:5>OK1TK<CALL:5>M0GEB<BAND:3>30M<FREQ:8>10.13770<FREQ_RX:8>10.13640<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20200119<APP_LoTW_RXQSO:19>2021-01-08 07:45:03 // QSO record inserted/modified at LoTW<TIME_ON:6>114700<APP_LoTW_QSO_TIMESTAMP:20>2020-01-19T11:47:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210108<APP_LoTW_RXQSL:19>2021-01-08 07:45:03 // QSL record matched/modified at LoTW<DXCC:3>223<COUNTRY:7>ENGLAND<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:2>M0<APP_LoTW_2xQSL:1>Y<IOTA:6>EU-005<GRIDSQUARE:6>IO80DV<CQZ:2>14<ITUZ:2>27<eor>

LOG: <DISTANCE:7>1284.00 <BAND:3>30M <CALL:5>M0GEB <COMMENT:10>/P, OK9ZAM <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:9>10.137700 <GRIDSQUARE:6>IO80dv <ITUZ:2>27 <MODE:3>FT8 <NAME:14>Graham Beesley <NOTES:24>Yaesu FT-817ND, GR5W, 5W <OPERATOR:7>OK1TK/P <PFX:2>M0 <QSL_SENT:1>Y <QSLSDATE:8>20210110 <QSO_DATE:8:D>20200119 <TIME_ON:6>114700 <QTH:8>Crediton <RST_RCVD:3>-11 <RST_SENT:3>-10 <TIME_OFF:6>115100 <TX_PWR:1>5 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <LOTW_QSL_RCVD:1>Y <APP_LOGGER32_QSO_NUMBER:3>109 <FREQ_RX:9>10.136400 <COUNTRY:7>England <APP_LOGGER32_LAT:16>50.8958333333333 <APP_LOGGER32_LNG:16>3.70833333333334 <EOR>



OK1RJO

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:5>M7DWW<BAND:3>80M<FREQ:7>3.57457<FREQ_RX:7>3.57439<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210115<APP_LoTW_RXQSO:19>2021-01-16 17:31:14 // QSO record inserted/modified at LoTW<TIME_ON:6>212845<APP_LoTW_QSO_TIMESTAMP:20>2021-01-15T21:28:45Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210116<APP_LoTW_RXQSL:19>2021-01-16 17:31:14 // QSL record matched/modified at LoTW<DXCC:3>223<COUNTRY:7>ENGLAND<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:2>M7<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>IO83QI<CQZ:2>14<ITUZ:2>27<eor>

LOG: <DISTANCE:7>1228.00 <BAND:3>80M <CALL:5>M7DWW <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:8>3.574575 <GRIDSQUARE:6>IO83qi <ITUZ:2>27 <MODE:3>FT8 <NAME:16>Duncan C Woodall <OPERATOR:5>JAKUB <PFX:2>M7 <QSO_DATE:8:D>20210115 <TIME_ON:6>212845 <QTH:17>Runcorn, Cheshire <RST_RCVD:3>-20 <RST_SENT:3>-16 <TIME_OFF:6>213029 <eQSL_QSL_SENT:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>121 <FREQ_RX:8>3.574395 <COUNTRY:7>England <APP_LOGGER32_LAT:16>53.3541666666667 <APP_LOGGER32_LNG:5>2.625 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:5>DM2HK<BAND:3>80M<FREQ:7>3.57424<FREQ_RX:7>3.57401<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210115<APP_LoTW_RXQSO:19>2021-01-16 17:31:13 // QSO record inserted/modified at LoTW<TIME_ON:6>211800<APP_LoTW_QSO_TIMESTAMP:20>2021-01-15T21:18:00Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210116<APP_LoTW_RXQSL:19>2021-01-16 17:31:13 // QSL record matched/modified at LoTW<DXCC:3>230<COUNTRY:27>FEDERAL REPUBLIC OF GERMANY<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>DM2<APP_LoTW_2xQSL:1>Y<GRIDSQUARE:6>JO62TI<CQZ:2>14<APP_LoTW_CQZ_Inferred:1>Y // from DXCC entity<ITUZ:2>28<APP_LoTW_ITUZ_Inferred:1>Y // from DXCC entity<eor>

LOG: <DISTANCE:6>262.00 <BAND:3>80M <CALL:5>DM2HK <CONT:2>EU <CQZ:2>14 <DXCC:3>230 <FREQ:8>3.574245 <GRIDSQUARE:6>JO62ti <ITUZ:2>28 <MODE:3>FT8 <NAME:14>Hartmut Kordus <OPERATOR:5>JAKUB <PFX:3>DM2 <QSO_DATE:8:D>20210115 <TIME_ON:6>211800 <QTH:7>Zeuthen <RST_RCVD:3>-12 <RST_SENT:3>-07 <TIME_OFF:6>212059 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>119 <FREQ_RX:8>3.574006 <COUNTRY:27>Federal Republic of Germany <APP_LOGGER32_LAT:16>52.3541666666667 <APP_LOGGER32_LNG:7>-13.625 <EOR>

 

BAD: QSO not found in Logbook:  <APP_LoTW_OWNCALL:6>OK1RJO<STATION_CALLSIGN:6>OK1RJO<CALL:6>EA8AIN<BAND:3>40M<FREQ:7>7.07612<FREQ_RX:7>7.07493<MODE:3>FT8<APP_LoTW_MODEGROUP:4>DATA<QSO_DATE:8>20210109<APP_LoTW_RXQSO:19>2021-01-09 22:14:30 // QSO record inserted/modified at LoTW<TIME_ON:6>212046<APP_LoTW_QSO_TIMESTAMP:20>2021-01-09T21:20:46Z // QSO Date & Time; ISO-8601<QSL_RCVD:1>Y<QSLRDATE:8>20210111<APP_LoTW_RXQSL:19>2021-01-11 19:57:48 // QSL record matched/modified at LoTW<DXCC:2>29<COUNTRY:14>CANARY ISLANDS<APP_LoTW_DXCC_ENTITY_STATUS:7>Current<PFX:3>EA8<APP_LoTW_2xQSL:1>Y<IOTA:6>AF-004<GRIDSQUARE:6>IL18CQ<CQZ:2>33<ITUZ:2>36<eor>

LOG: <DISTANCE:7>3599.00 <BAND:3>40M <CALL:6>EA8AIN <CONT:2>AF <CQZ:2>33 <DXCC:2>29 <FREQ:8>7.076120 <GRIDSQUARE:6>IL18cq <ITUZ:2>36 <MODE:3>FT8 <NAME:33>Aurelio Rodriguez Concepcion Aure <OPERATOR:5>ONDRA <PFX:3>EA8 <QSO_DATE:8:D>20210109 <TIME_ON:6>212046 <QTH:22>Santa Cruz De La Palma <RST_RCVD:3>-19 <RST_SENT:3>-18 <TIME_OFF:6>212229 <eQSL_QSL_SENT:1>Y <eQSL_QSL_RCVD:1>Y <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:3>103 <FREQ_RX:8>7.074928 <COUNTRY:14>Canary Islands <APP_LOGGER32_LAT:7>28.6875 <APP_LOGGER32_LNG:16>17.7916666666667 <EOR>



--
73! OK1TK


Re: FT8 AUTO LOGGING

Richard Zalewski
 

What appears to be happening is some QSOs are being held in some file that is not being processed.  I log a qso manually and I find that a completely different QSO is put at the bottom of the log.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV


Be joyful in hope, patient in affliction, faithful in prayer


On Wed, Jan 20, 2021 at 7:16 PM Bill K4BX via groups.io <k4bx=yahoo.com@groups.io> wrote:
When auto logging FT8 QSO's from JTDX they don't show up at the end of the log.... but when I search for the calls they are found in the log. They just don't seem to be sorted by QSO time. Anyway if you right click on the log and do a search for the contacts you will find them. The Cherry-picking event viewer says the contacts were logged. Don't know why they don't appear at the bottom of the log page.
73 Bill K4BX

On 1/20/2021 7:01 PM, Bob wrote:
Richard, I know nothing about 'auto logging from WSJT-X', or for that matter WSJT-X. There is an option in Logger32 to attempt to bypass/override the requirement to click the mouse on the 'log this QSO' popup (the ARRL requirement for 'contemporaneous user input'. Whatever the hell that is) . If it works - Yay! If it doesn't , then :(
 
SeventyThree(s).
On 01/20/2021 7:14 PM Richard Zalewski <dick.w7zr@...> wrote:
 
 
Auto logging does not seem to be working for FT8.  Checked my band plan table all ok as nothing changed from before conversion.  If I manually select log qso from wsjt-x I see a flash on the l32 page but does not go into log.  Something changed from the conversion.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
 
Be joyful in hope, patient in affliction, faithful in prayer


Re: FT8 AUTO LOGGING

Bill K4BX
 

When auto logging FT8 QSO's from JTDX they don't show up at the end of the log.... but when I search for the calls they are found in the log. They just don't seem to be sorted by QSO time. Anyway if you right click on the log and do a search for the contacts you will find them. The Cherry-picking event viewer says the contacts were logged. Don't know why they don't appear at the bottom of the log page.
73 Bill K4BX

On 1/20/2021 7:01 PM, Bob wrote:
Richard, I know nothing about 'auto logging from WSJT-X', or for that matter WSJT-X. There is an option in Logger32 to attempt to bypass/override the requirement to click the mouse on the 'log this QSO' popup (the ARRL requirement for 'contemporaneous user input'. Whatever the hell that is) . If it works - Yay! If it doesn't , then :(
 
SeventyThree(s).
On 01/20/2021 7:14 PM Richard Zalewski <dick.w7zr@...> wrote:
 
 
Auto logging does not seem to be working for FT8.  Checked my band plan table all ok as nothing changed from before conversion.  If I manually select log qso from wsjt-x I see a flash on the l32 page but does not go into log.  Something changed from the conversion.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
 
Be joyful in hope, patient in affliction, faithful in prayer


Re: FT8 AUTO LOGGING

Bob
 

Richard, I know nothing about 'auto logging from WSJT-X', or for that matter WSJT-X. There is an option in Logger32 to attempt to bypass/override the requirement to click the mouse on the 'log this QSO' popup (the ARRL requirement for 'contemporaneous user input'. Whatever the hell that is) . If it works - Yay! If it doesn't , then :(
 
SeventyThree(s).

On 01/20/2021 7:14 PM Richard Zalewski <dick.w7zr@...> wrote:
 
 
Auto logging does not seem to be working for FT8.  Checked my band plan table all ok as nothing changed from before conversion.  If I manually select log qso from wsjt-x I see a flash on the l32 page but does not go into log.  Something changed from the conversion.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV
 
Be joyful in hope, patient in affliction, faithful in prayer


Re: FT8 AUTO LOGGING

Kenneth Hansen
 

I upgraded to ver.4 yesterday and UDP band map, auto logging and DX spot works as before, using  WSJT-X.

de KB2SSE

On Wed, Jan 20, 2021 at 7:15 PM Richard Zalewski <dick.w7zr@...> wrote:
Auto logging does not seem to be working for FT8.  Checked my band plan table all ok as nothing changed from before conversion.  If I manually select log qso from wsjt-x I see a flash on the l32 page but does not go into log.  Something changed from the conversion.

Richard 
W7ZR ex:5C5Z, CN2ZR, K2JSP, W6SBZ, W7KXR, K9ZIJ, W9KNF, W0KDF, W0MQU, J68ZR, KC6ZR, PJ4/W7ZR, KH2,W7ZR, KH6/W7ZR, V31ZR, VK4AAZ, XE2DV


Be joyful in hope, patient in affliction, faithful in prayer

--
Kenneth Hansen
Owner
ScanAm Technical Services, LLC

2001 - 2020 of 84036