1. hamlogger@groups.io
   Date   
Re: Omni VI

John
 
Edited

I was so pumped to search for this topic and find someone who was having the exact problem I was.

 

...until I found it was my thread from a decade ago, having the same problem (albeit in another thread of the same era)

The solution was (in addition to all the other stuff like baud rate , port, word length , stop bit, etc. was to assert DTR.

 

Closing the loop (slowly)

John K5MO
Re: Error in OC-298 location

Bob <k4cy@...>
 

Click TOOLS | IOTA MAINTENANCE. Scroll down to OC-298 and click on the row. On the window that opens Change the Lat/Long to whatever you like, and click the MODIFY button (the one to the left of where you changed the Lat/Long). Now look at the Lat/Long of whatever Islands are listed and modify their Lat/Long one row at a time and clicking the lower MODIFY Button after each row is changed.

SeventyThree(s).

On 11/02/2020 11:05 AM Mike <ch25@...> wrote:


While hunting OC-298 I noticed, that Logger gives me wrong antenna direction.
After checking I noticed, that coordinates in database are wrong.
Should be -17,34 and 138,4 according to a map.
Mike

Error in OC-298 location

Mike
 

While hunting OC-298 I noticed, that Logger gives me wrong antenna direction.
After checking I noticed, that coordinates in database are wrong.
Should be -17,34 and 138,4 according to a map.
Mike
Re: Saound card window not available

Vytenis LY2KZ
 

Its Windows 10 here. Started program with Run As.. Administrator and after few blinks window opened. Checked file permissions and there was no "Modify" permission on MMTTY.exe. Set it and now windows seems to open each time I click button.

73
Vytenis ly5t
Re: Import

Paul F6EXV
 

Ooooops, I take this back, L32 does have both times... Sorry

Le 01/11/2020 à 21:22, Paul F6EXV a écrit :
Since L32 only keeps track of one time ( from what you explained, it must be time off of the JTDX adi file), why does the import takes the other time (time on) ?
73

Le 01/11/2020 à 21:18, Bob a écrit :
If you think Logger32 is reading the time from the import ADI and writing the wrong time to the logbook, it is easy to check ... Compare the ADI record TIME_ON field with the QSO TIME_ON in the logbook. SeventyThree(s)

On 11/01/2020 3:08 PM Paul F6EXV <f6exv@hotmail.com> wrote:


It could as well be a L32 problem of selecting the wrong time when
importing, compared to the time logged when both programs are talking to
each other....
Right ?

SeventyFour (yes, we do get a little bit of inflation)

Le 01/11/2020 à 21:05, Bob a écrit :
Question 1: No.
Question 2: You are not the only one, and I have asked for the WSJT developers to fix the problem.

Anything else? SeventyThree(s).



On 11/01/2020 2:48 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Thanks Bob, but you are not answering my questions...
Attached is a screen shot. The dupes are the results of
1/ logging live, direct and automatic "import" from JTDX into L32,
without me doing anything (besides proper setup of course)
2/ import the JTDX adif file (which is supposed to be the same) as such.

My import created 700+ dupes, which I do not plan on deleting one by one...

The second question was : is there a way to tell L32 to ignore import of
a QSO if it is a dupe (same call/band/mode) if the time if off by x
minutes ?
I think not, but can you confirm ?

Why don't the developpers of both programs work on solving this import
issue (unless I am the only one with it) ?

Thanks +73
Paul

Le 01/11/2020 à 18:52, Bob a écrit :
Paul, this has been written/discussed here many times ... UDP QSO logged messages from WSJT/JTDX include both the QSO start/end times. That is what Logger32 uses to log the QSO. Because the QSO start time is imaginary, there is an option on the UDP BandMap to log the QSOs start time to be the same as QSO end time.

Why do I say the QSO start time is imaginary? Try this. At 11:30 call a station. Call once and click Halt Tx. Go to the Mosque for noon prayers. Return at 14:00 and inshallah the station you called at 11:00 is still there. Call him again at 14:05. Your visit to the Mosque is rewarded, you QSO the station, and the QSO is logged. What is the QSO start time logged? 14:05? Ha! You wish.

SeventyThree(s).


On 11/01/2020 12:25 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just
dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all
other info is the same (call, band, mode), this import should be
considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the
program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus










--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Re: Import

Paul F6EXV
 

Since L32 only keeps track of one time ( from what you explained, it must be time off of the JTDX adi file), why does the import takes the other time (time on) ?
73

Le 01/11/2020 à 21:18, Bob a écrit :
If you think Logger32 is reading the time from the import ADI and writing the wrong time to the logbook, it is easy to check ... Compare the ADI record TIME_ON field with the QSO TIME_ON in the logbook. SeventyThree(s)

On 11/01/2020 3:08 PM Paul F6EXV <f6exv@hotmail.com> wrote:


It could as well be a L32 problem of selecting the wrong time when
importing, compared to the time logged when both programs are talking to
each other....
Right ?

SeventyFour (yes, we do get a little bit of inflation)

Le 01/11/2020 à 21:05, Bob a écrit :
Question 1: No.
Question 2: You are not the only one, and I have asked for the WSJT developers to fix the problem.

Anything else? SeventyThree(s).



On 11/01/2020 2:48 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Thanks Bob, but you are not answering my questions...
Attached is a screen shot. The dupes are the results of
1/ logging live, direct and automatic "import" from JTDX into L32,
without me doing anything (besides proper setup of course)
2/ import the JTDX adif file (which is supposed to be the same) as such.

My import created 700+ dupes, which I do not plan on deleting one by one...

The second question was : is there a way to tell L32 to ignore import of
a QSO if it is a dupe (same call/band/mode) if the time if off by x
minutes ?
I think not, but can you confirm ?

Why don't the developpers of both programs work on solving this import
issue (unless I am the only one with it) ?

Thanks +73
Paul

Le 01/11/2020 à 18:52, Bob a écrit :
Paul, this has been written/discussed here many times ... UDP QSO logged messages from WSJT/JTDX include both the QSO start/end times. That is what Logger32 uses to log the QSO. Because the QSO start time is imaginary, there is an option on the UDP BandMap to log the QSOs start time to be the same as QSO end time.

Why do I say the QSO start time is imaginary? Try this. At 11:30 call a station. Call once and click Halt Tx. Go to the Mosque for noon prayers. Return at 14:00 and inshallah the station you called at 11:00 is still there. Call him again at 14:05. Your visit to the Mosque is rewarded, you QSO the station, and the QSO is logged. What is the QSO start time logged? 14:05? Ha! You wish.

SeventyThree(s).


On 11/01/2020 12:25 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just
dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all
other info is the same (call, band, mode), this import should be
considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the
program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Re: Import

Bob <k4cy@...>
 

If you think Logger32 is reading the time from the import ADI and writing the wrong time to the logbook, it is easy to check ... Compare the ADI record TIME_ON field with the QSO TIME_ON in the logbook. SeventyThree(s)

On 11/01/2020 3:08 PM Paul F6EXV <f6exv@hotmail.com> wrote:


It could as well be a L32 problem of selecting the wrong time when
importing, compared to the time logged when both programs are talking to
each other....
Right ?

SeventyFour (yes, we do get a little bit of inflation)

Le 01/11/2020 à 21:05, Bob a écrit :
Question 1: No.
Question 2: You are not the only one, and I have asked for the WSJT developers to fix the problem.

Anything else? SeventyThree(s).



On 11/01/2020 2:48 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Thanks Bob, but you are not answering my questions...
Attached is a screen shot. The dupes are the results of
1/ logging live, direct and automatic "import" from JTDX into L32,
without me doing anything (besides proper setup of course)
2/ import the JTDX adif file (which is supposed to be the same) as such.

My import created 700+ dupes, which I do not plan on deleting one by one...

The second question was : is there a way to tell L32 to ignore import of
a QSO if it is a dupe (same call/band/mode) if the time if off by x
minutes ?
I think not, but can you confirm ?

Why don't the developpers of both programs work on solving this import
issue (unless I am the only one with it) ?

Thanks +73
Paul

Le 01/11/2020 à 18:52, Bob a écrit :
Paul, this has been written/discussed here many times ... UDP QSO logged messages from WSJT/JTDX include both the QSO start/end times. That is what Logger32 uses to log the QSO. Because the QSO start time is imaginary, there is an option on the UDP BandMap to log the QSOs start time to be the same as QSO end time.

Why do I say the QSO start time is imaginary? Try this. At 11:30 call a station. Call once and click Halt Tx. Go to the Mosque for noon prayers. Return at 14:00 and inshallah the station you called at 11:00 is still there. Call him again at 14:05. Your visit to the Mosque is rewarded, you QSO the station, and the QSO is logged. What is the QSO start time logged? 14:05? Ha! You wish.

SeventyThree(s).


On 11/01/2020 12:25 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just
dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all
other info is the same (call, band, mode), this import should be
considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the
program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Re: Import

Paul F6EXV
 

It could as well be a L32 problem of selecting the wrong time when importing, compared to the time logged when both programs are talking to each other....
Right ?

SeventyFour (yes, we do get a little bit of inflation)

Le 01/11/2020 à 21:05, Bob a écrit :
Question 1: No.
Question 2: You are not the only one, and I have asked for the WSJT developers to fix the problem.

Anything else? SeventyThree(s).



On 11/01/2020 2:48 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Thanks Bob, but you are not answering my questions...
Attached is a screen shot. The dupes are the results of
1/ logging live, direct and automatic "import" from JTDX into L32,
without me doing anything (besides proper setup of course)
2/ import the JTDX adif file (which is supposed to be the same) as such.

My import created 700+ dupes, which I do not plan on deleting one by one...

The second question was : is there a way to tell L32 to ignore import of
a QSO if it is a dupe (same call/band/mode) if the time if off by x
minutes ?
I think not, but can you confirm ?

Why don't the developpers of both programs work on solving this import
issue (unless I am the only one with it) ?

Thanks +73
Paul

Le 01/11/2020 à 18:52, Bob a écrit :
Paul, this has been written/discussed here many times ... UDP QSO logged messages from WSJT/JTDX include both the QSO start/end times. That is what Logger32 uses to log the QSO. Because the QSO start time is imaginary, there is an option on the UDP BandMap to log the QSOs start time to be the same as QSO end time.

Why do I say the QSO start time is imaginary? Try this. At 11:30 call a station. Call once and click Halt Tx. Go to the Mosque for noon prayers. Return at 14:00 and inshallah the station you called at 11:00 is still there. Call him again at 14:05. Your visit to the Mosque is rewarded, you QSO the station, and the QSO is logged. What is the QSO start time logged? 14:05? Ha! You wish.

SeventyThree(s).


On 11/01/2020 12:25 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just
dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all
other info is the same (call, band, mode), this import should be
considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the
program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Re: Import

Bob <k4cy@...>
 

Question 1: No.
Question 2: You are not the only one, and I have asked for the WSJT developers to fix the problem.

Anything else? SeventyThree(s).

On 11/01/2020 2:48 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Thanks Bob, but you are not answering my questions...
Attached is a screen shot. The dupes are the results of
1/ logging live, direct and automatic "import" from JTDX into L32,
without me doing anything (besides proper setup of course)
2/ import the JTDX adif file (which is supposed to be the same) as such.

My import created 700+ dupes, which I do not plan on deleting one by one...

The second question was : is there a way to tell L32 to ignore import of
a QSO if it is a dupe (same call/band/mode) if the time if off by x
minutes ?
I think not, but can you confirm ?

Why don't the developpers of both programs work on solving this import
issue (unless I am the only one with it) ?

Thanks +73
Paul

Le 01/11/2020 à 18:52, Bob a écrit :
Paul, this has been written/discussed here many times ... UDP QSO logged messages from WSJT/JTDX include both the QSO start/end times. That is what Logger32 uses to log the QSO. Because the QSO start time is imaginary, there is an option on the UDP BandMap to log the QSOs start time to be the same as QSO end time.

Why do I say the QSO start time is imaginary? Try this. At 11:30 call a station. Call once and click Halt Tx. Go to the Mosque for noon prayers. Return at 14:00 and inshallah the station you called at 11:00 is still there. Call him again at 14:05. Your visit to the Mosque is rewarded, you QSO the station, and the QSO is logged. What is the QSO start time logged? 14:05? Ha! You wish.

SeventyThree(s).


On 11/01/2020 12:25 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just
dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all
other info is the same (call, band, mode), this import should be
considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the
program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Re: Import

Paul F6EXV
 

Thanks Bob, but you are not answering my questions...
Attached is a screen shot. The dupes are the results of
1/ logging live, direct and automatic "import" from JTDX into L32, without me doing anything (besides proper setup of course)
2/ import the JTDX adif file (which is supposed to be the same) as such.

My import created 700+ dupes, which I do not plan on deleting one by one...

The second question was : is there a way to tell L32 to ignore import of a QSO if it is a dupe (same call/band/mode) if the time if off by x minutes ?
I think not, but can you confirm ?

Why don't the developpers of both programs work on solving this import issue (unless I am the only one with it) ?

Thanks +73
Paul

Le 01/11/2020 à 18:52, Bob a écrit :
Paul, this has been written/discussed here many times ... UDP QSO logged messages from WSJT/JTDX include both the QSO start/end times. That is what Logger32 uses to log the QSO. Because the QSO start time is imaginary, there is an option on the UDP BandMap to log the QSOs start time to be the same as QSO end time.

Why do I say the QSO start time is imaginary? Try this. At 11:30 call a station. Call once and click Halt Tx. Go to the Mosque for noon prayers. Return at 14:00 and inshallah the station you called at 11:00 is still there. Call him again at 14:05. Your visit to the Mosque is rewarded, you QSO the station, and the QSO is logged. What is the QSO start time logged? 14:05? Ha! You wish.

SeventyThree(s).


On 11/01/2020 12:25 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just
dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all
other info is the same (call, band, mode), this import should be
considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the
program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Re: L32LogSync real time download LOTW

f5idj2001 valéry Pierson
 

Thank you Rick  and thank you for the ham radio softwares.
Best regards
valéry
Re: Import

Bob <k4cy@...>
 

Paul, this has been written/discussed here many times ... UDP QSO logged messages from WSJT/JTDX include both the QSO start/end times. That is what Logger32 uses to log the QSO. Because the QSO start time is imaginary, there is an option on the UDP BandMap to log the QSOs start time to be the same as QSO end time.

Why do I say the QSO start time is imaginary? Try this. At 11:30 call a station. Call once and click Halt Tx. Go to the Mosque for noon prayers. Return at 14:00 and inshallah the station you called at 11:00 is still there. Call him again at 14:05. Your visit to the Mosque is rewarded, you QSO the station, and the QSO is logged. What is the QSO start time logged? 14:05? Ha! You wish.

SeventyThree(s).

On 11/01/2020 12:25 PM Paul F6EXV <f6exv@hotmail.com> wrote:


Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just
dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all
other info is the same (call, band, mode), this import should be
considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the
program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Import

Paul F6EXV
 

Hello all
I have made a few QSO with JTDX without being "connected" to L32.
So I had to import that adif log. (global log over 8000 QSOs, just dozens without being connected))
It creates hundreds of dupes, just 1, 2 , 3 sometimes 4 minutes apart.
Once and for all, which is the time being imported ? Start or finish ?
Is there a way to tell L32 that if the time is off by x minutes, all all other info is the same (call, band, mode), this import should be considered a dupe and therefore ignored ?
Now, I want to exit without saving, and cannot find where to tell the program not to save on exit (just for this time)

Help !
Thanks + 73
Paul F6EXV



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Re: Logging from WSJT-X issue

Bob <k4cy@...>
 

Jim, when logging QSOs from WSJT/JTDX UDP messages, the band the QSO is logged as is derived from the frequency. This process does use you BandPlan to figure out the band, but the mode is not part of the equation. In your example (where the frequency is 14.0761) as long as 14.0761 is covered somewhere in 20m, the QSO will be logged accordingly.

You need to check carefully that there are no holes in the BandPlan. When setting up my BandPlan, I set CW from 14.000 to 14.350. That way there ate no holes in the band.

Also, if you FT8 defined on another band, you can test my logic. Remove the FT8 row in your 20m BandPlan and QSOs will still be logged as 20m as long as 14.074 to 14.076 is covered on some mode somewhere in 20m.

 SeventyThree(s).

On 11/01/2020 11:20 AM Jim Ciurczak <nfjimc@...> wrote:


This happens to me once in a great while and I discovered it is because the actual xmt frequency is outside the frequency I have set in the Band Set Up. If I have FT8 set to 14.07400 to 14.07600 in the Band Set Up fort 20m and the actual xmt frequency ends up being 14.0761 or some other frequency higher than 14.076 it will get logged but the Band will be blank.

Jim K2QB

Re: L32LogSync real time download LOTW

Rick Ellison
 

L32logsync does not have that capability.. It would require to Always keep checking LOTW for new confirmations. A big waste of bandwidth and probably discouraged by the LOTW folks for banging away at their already busy server..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of f5idj2001 valéry Pierson
Sent: Sunday, November 1, 2020 11:05 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] L32LogSync real time download LOTW

 

Hello Dave and Steve,
Yes I agree with you !
I wish to know if L32Logsync can auto update my log in Logger 32 as soon as the QSL confirmation shows up in LOTW and, if yes, how to do it ?
thank you
73
valéry


Virus-free. www.avast.com

Re: Logging from WSJT-X issue

Jim K2QB
 

This happens to me once in a great while and I discovered it is because the actual xmt frequency is outside the frequency I have set in the Band Set Up. If I have FT8 set to 14.07400 to 14.07600 in the Band Set Up fort 20m and the actual xmt frequency ends up being 14.0761 or some other frequency higher than 14.076 it will get logged but the Band will be blank.

Jim K2QB
Re: L32LogSync real time download LOTW

f5idj2001 valéry Pierson
 

Hello Dave and Steve,
Yes I agree with you !
I wish to know if L32Logsync can auto update my log in Logger 32 as soon as the QSL confirmation shows up in LOTW and, if yes, how to do it ?
thank you
73
valéry
Re: L32LogSync real time download LOTW

Steve VE3RX
 

LOTW only confirms once both stations have uploaded their files, and the LOTW server has processed those files. Right after some big weekend contests, the LOTW server can be as much as 8 hours behind in processing all the uploaded files. So if you upload during that time, your file will be 8 hours behind in the processing queue. There is no "real time" LOTW confirmations, it is all "batch" orientated.

73
Steve
Re: Error on autoupdate

John
 

That did it! Thank you so much Bob.....

 

I'm back in business and will now back up to different media :-)

73
John k5Mo
Re: L32LogSync real time download LOTW

Dave Colliau
 

You will only get confirmation after the station you worked does an upload and it gets in the system.
Dave N8DC

--
Sent from Yahoo Email App for Android

Sunday, 01 November 2020, 07:57AM -05:00 from f5idj2001 valéry Pierson f5idj2008@...:

Hello,

does the real time download QSO from LOTW works ?
Is-it possible to get confirmation of a QSO just after I upload it ?
I chechek the auto upload to LOTW, it works great but can't find the way for download.
Thank you for your help
valéry, f5idj

2041 - 2060 of 83481