|
OK, then ignore my Subject 2 answer. SeventyThree(s).
On 11/13/2022 7:52 AM Jim Altman <jaltman636@...> wrote:
Regarding Subject 2, both my Kenwood and my Yeasu return to the frequency they started with when i close JTDX from the start/stop menu.
73
Jim
|
|
|
Regarding Subject 2, both my Kenwood and my Yeasu return to the frequency they started with when i close JTDX from the start/stop menu.
73
Jim
|
|
|
Hi Bob
Thanks for the answer.
I found something checked in the misc menu of JTDX: hide FT8 dupe message.
But don’t know what is mean exactly.
Nothing in the JTDX manual or missed it.
i tried to uncheck it and will see if it change something.. I don’t know if
it’s checked in the basic JTDX configuration, as the manual is not up to date
with all news features.
For closing JTDX i use stop in the UDP band map menu and same issue. I
don’t close the UDP band map, sometime i close JTDX with the standart “X” to
closes all windows but it’s the also the same issue. Just done it at the second
i write this message.
I changed in JTDX the CAT COM from 2 to 1, 1 is the COM set in logger32.
Same issue
But i lost now something. When i click on a spot in logger32 the TRX don’t
change frequency. That’s why i use the COM2 for 2nd CAT in JTDX.
This story make me crazy since long time until now i have no more ideas in
the bag... That’s why i ask for.
Maybe there is just a little thing but don’t find it.
Ciao
Thanks for the help as usual.
Don’t know if Lou solved his problem.
73s
Olivier
F4FQH
toggle quoted message
Show quoted text
From: Bob
Sent: Sunday, November 13, 2022 10:51 AM
To: hamlogger@groups.io ; F4FQH Olivier
Subject: Re: [hamlogger] QSO not sent in the log
Subject 1. There is code in
Logger32 to prevent logging a contact twice. one after another. It happens often
that a contact is logged by me, but not by the other station so he attempts to
get a RR73 from me and JTDX send me another LogQSO message. If Logger32 has just
logged that station the second LogQSO message is ignored. After lots of coffee,
I will check the code to see if that is why your second TT8ZZ contact was not
logged.
Subject 2. I think you will find
that if you close JTDX by closing the UDP BandMap the radio is reset where it
was when JTDX was started. If you stop JTDX by the start/stop menu on the UDP
BandMap, JTDX is stopped and Logger32 assumes radio control without resetting
the frequency/mode. The choice is yours.
SeventyThree(s).
On 11/12/2022 8:10 PM F4FQH Olivier <unit365@...> wrote:
As i wrote on the beta tester JTDX list, i have
this bug since 2 or 3 versions of JTDX/logger32
Seem to be more on logger because with the JTDX
rc2, i had also the bug, of course we can’t say we are sure.
Started my PC, opened logger and lauched JTDX via
logger.
Made QSO with TT8ZZ on the 30m. Logged
corectly
As logger have disabled the RADIO PORT i
reactivated it, i clicked on the TT8ZZ 40m spot.
As i was one of the first arrived on the 7.056 i
made QSO quickly.
AND.............after RR73 he did not go in
logger32 log.
So yes this bug exist, and why it happen not all
the time....that is the question...
And still not understand why when i close JTDX my
rig (and all the rest) come back to the frequency (but more frustrating, the
BAND) set in logger just before opening JTDX.
I should be interesting to remove this in the code
(JTDX or logger32)
I close JTDX sometime because i change to CW or
SSB.
I have the steppir which is become crazy, and this
is the best way to destroy the antenna.
Some would say me to disable autotrack, but then,
what is autotrack and VSC made for ?
Some others would say me also i’m the only
one...yes but this happen ! maybe there is others case than me who have this
issue and say nothing.
I will continue to investigate this issues, tried
many things but nothing positive for the moment.
|
|
|
I did not receive a copy of this message, so I will resend. 73.
On 11/13/2022 5:52 AM Bob <k4cy@...> wrote:
Subject 1. I have checked the code, and made numerous simulated contacts with the same station on two different bands in quick succession and both contacts were logged in Logger32. The Logger32 code to detect duplicate UDP logging requests checks for logged contacts within the last 5 minutes with the same station on the same band and mode. It's easy to test using the JTDX main window to enter callsigns in the DX Call field, the Log QSO button to log the contact, and the Band dropdown to change the Band. No voodoo required. SeventyThree(s).
On 11/13/2022 4:51 AM Bob <k4cy@...> wrote:
Subject 1. There is code in Logger32 to prevent logging a contact twice. one after another. It happens often that a contact is logged by me, but not by the other station so he attempts to get a RR73 from me and JTDX send me another LogQSO message. If Logger32 has just logged that station the second LogQSO message is ignored. After lots of coffee, I will check the code to see if that is why your second TT8ZZ contact was not logged.
Subject 2. I think you will find that if you close JTDX by closing the UDP BandMap the radio is reset where it was when JTDX was started. If you stop JTDX by the start/stop menu on the UDP BandMap, JTDX is stopped and Logger32 assumes radio control without resetting the frequency/mode. The choice is yours.
SeventyThree(s).
On 11/12/2022 8:10 PM F4FQH Olivier <unit365@...> wrote:
As i wrote on the beta tester JTDX list, i have this bug since 2 or 3 versions of JTDX/logger32
Seem to be more on logger because with the JTDX rc2, i had also the bug, of course we can’t say we are sure.
Started my PC, opened logger and lauched JTDX via logger.
Made QSO with TT8ZZ on the 30m. Logged corectly
As logger have disabled the RADIO PORT i reactivated it, i clicked on the TT8ZZ 40m spot.
As i was one of the first arrived on the 7.056 i made QSO quickly.
AND.............after RR73 he did not go in logger32 log.
So yes this bug exist, and why it happen not all the time....that is the question...
And still not understand why when i close JTDX my rig (and all the rest) come back to the frequency (but more frustrating, the BAND) set in logger just before opening JTDX.
I should be interesting to remove this in the code (JTDX or logger32)
I close JTDX sometime because i change to CW or SSB.
I have the steppir which is become crazy, and this is the best way to destroy the antenna.
Some would say me to disable autotrack, but then, what is autotrack and VSC made for ?
Some others would say me also i’m the only one...yes but this happen ! maybe there is others case than me who have this issue and say nothing.
I will continue to investigate this issues, tried many things but nothing positive for the moment.
|
|
|
Subject 1 (more ...) Logger32 records all UDP Logging requests in a file cryptically named UDP Logging requesta.txt. This file is in the Logger32 directory and records details of each logging request and how it was processed. The file is flushed every time Logger32 is started. SeventyThree(s).
On 11/13/2022 5:52 AM Bob <k4cy@...> wrote:
Subject 1. I have checked the code, and made numerous simulated contacts with the same station on two different bands in quick succession and both contacts were logged in Logger32. The Logger32 code to detect duplicate UDP logging requests checks for logged contacts within the last 5 minutes with the same station on the same band and mode. It's easy to test using the JTDX main window to enter callsigns in the DX Call field, the Log QSO button to log the contact, and the Band dropdown to change the Band. No voodoo required. SeventyThree(s).
On 11/13/2022 4:51 AM Bob <k4cy@...> wrote:
Subject 1. There is code in Logger32 to prevent logging a contact twice. one after another. It happens often that a contact is logged by me, but not by the other station so he attempts to get a RR73 from me and JTDX send me another LogQSO message. If Logger32 has just logged that station the second LogQSO message is ignored. After lots of coffee, I will check the code to see if that is why your second TT8ZZ contact was not logged.
Subject 2. I think you will find that if you close JTDX by closing the UDP BandMap the radio is reset where it was when JTDX was started. If you stop JTDX by the start/stop menu on the UDP BandMap, JTDX is stopped and Logger32 assumes radio control without resetting the frequency/mode. The choice is yours.
SeventyThree(s).
On 11/12/2022 8:10 PM F4FQH Olivier <unit365@...> wrote:
As i wrote on the beta tester JTDX list, i have this bug since 2 or 3 versions of JTDX/logger32
Seem to be more on logger because with the JTDX rc2, i had also the bug, of course we can’t say we are sure.
Started my PC, opened logger and lauched JTDX via logger.
Made QSO with TT8ZZ on the 30m. Logged corectly
As logger have disabled the RADIO PORT i reactivated it, i clicked on the TT8ZZ 40m spot.
As i was one of the first arrived on the 7.056 i made QSO quickly.
AND.............after RR73 he did not go in logger32 log.
So yes this bug exist, and why it happen not all the time....that is the question...
And still not understand why when i close JTDX my rig (and all the rest) come back to the frequency (but more frustrating, the BAND) set in logger just before opening JTDX.
I should be interesting to remove this in the code (JTDX or logger32)
I close JTDX sometime because i change to CW or SSB.
I have the steppir which is become crazy, and this is the best way to destroy the antenna.
Some would say me to disable autotrack, but then, what is autotrack and VSC made for ?
Some others would say me also i’m the only one...yes but this happen ! maybe there is others case than me who have this issue and say nothing.
I will continue to investigate this issues, tried many things but nothing positive for the moment.
|
|
|
Subject 1. I have checked the code, and made numerous simulated contacts with the same station on two different bands in quick succession and both contacts were logged in Logger32. The Logger32 code to detect duplicate UDP logging requests checks for logged contacts within the last 5 minutes with the same station on the same band and mode. It's easy to test using the JTDX main window to enter callsigns in the DX Call field, the Log QSO button to log the contact, and the Band dropdown to change the Band. No voodoo required. SeventyThree(s).
On 11/13/2022 4:51 AM Bob <k4cy@...> wrote:
Subject 1. There is code in Logger32 to prevent logging a contact twice. one after another. It happens often that a contact is logged by me, but not by the other station so he attempts to get a RR73 from me and JTDX send me another LogQSO message. If Logger32 has just logged that station the second LogQSO message is ignored. After lots of coffee, I will check the code to see if that is why your second TT8ZZ contact was not logged.
Subject 2. I think you will find that if you close JTDX by closing the UDP BandMap the radio is reset where it was when JTDX was started. If you stop JTDX by the start/stop menu on the UDP BandMap, JTDX is stopped and Logger32 assumes radio control without resetting the frequency/mode. The choice is yours.
SeventyThree(s).
On 11/12/2022 8:10 PM F4FQH Olivier <unit365@...> wrote:
As i wrote on the beta tester JTDX list, i have this bug since 2 or 3 versions of JTDX/logger32
Seem to be more on logger because with the JTDX rc2, i had also the bug, of course we can’t say we are sure.
Started my PC, opened logger and lauched JTDX via logger.
Made QSO with TT8ZZ on the 30m. Logged corectly
As logger have disabled the RADIO PORT i reactivated it, i clicked on the TT8ZZ 40m spot.
As i was one of the first arrived on the 7.056 i made QSO quickly.
AND.............after RR73 he did not go in logger32 log.
So yes this bug exist, and why it happen not all the time....that is the question...
And still not understand why when i close JTDX my rig (and all the rest) come back to the frequency (but more frustrating, the BAND) set in logger just before opening JTDX.
I should be interesting to remove this in the code (JTDX or logger32)
I close JTDX sometime because i change to CW or SSB.
I have the steppir which is become crazy, and this is the best way to destroy the antenna.
Some would say me to disable autotrack, but then, what is autotrack and VSC made for ?
Some others would say me also i’m the only one...yes but this happen ! maybe there is others case than me who have this issue and say nothing.
I will continue to investigate this issues, tried many things but nothing positive for the moment.
|
|
|
Subject 1. There is code in Logger32 to prevent logging a contact twice. one after another. It happens often that a contact is logged by me, but not by the other station so he attempts to get a RR73 from me and JTDX send me another LogQSO message. If Logger32 has just logged that station the second LogQSO message is ignored. After lots of coffee, I will check the code to see if that is why your second TT8ZZ contact was not logged.
Subject 2. I think you will find that if you close JTDX by closing the UDP BandMap the radio is reset where it was when JTDX was started. If you stop JTDX by the start/stop menu on the UDP BandMap, JTDX is stopped and Logger32 assumes radio control without resetting the frequency/mode. The choice is yours.
SeventyThree(s).
On 11/12/2022 8:10 PM F4FQH Olivier <unit365@...> wrote:
As i wrote on the beta tester JTDX list, i have this bug since 2 or 3 versions of JTDX/logger32
Seem to be more on logger because with the JTDX rc2, i had also the bug, of course we can’t say we are sure.
Started my PC, opened logger and lauched JTDX via logger.
Made QSO with TT8ZZ on the 30m. Logged corectly
As logger have disabled the RADIO PORT i reactivated it, i clicked on the TT8ZZ 40m spot.
As i was one of the first arrived on the 7.056 i made QSO quickly.
AND.............after RR73 he did not go in logger32 log.
So yes this bug exist, and why it happen not all the time....that is the question...
And still not understand why when i close JTDX my rig (and all the rest) come back to the frequency (but more frustrating, the BAND) set in logger just before opening JTDX.
I should be interesting to remove this in the code (JTDX or logger32)
I close JTDX sometime because i change to CW or SSB.
I have the steppir which is become crazy, and this is the best way to destroy the antenna.
Some would say me to disable autotrack, but then, what is autotrack and VSC made for ?
Some others would say me also i’m the only one...yes but this happen ! maybe there is others case than me who have this issue and say nothing.
I will continue to investigate this issues, tried many things but nothing positive for the moment.
|
|
|
As i wrote on the beta tester JTDX list, i have this bug since 2 or 3
versions of JTDX/logger32
Seem to be more on logger because with the JTDX rc2, i had also the
bug, of course we can’t say we are sure.
Started my PC, opened logger and lauched JTDX via
logger.
Made QSO with TT8ZZ on the 30m. Logged corectly
As logger have disabled the RADIO PORT i reactivated it, i clicked on
the TT8ZZ 40m spot.
As i was one of the first arrived on the 7.056 i made QSO
quickly.
AND.............after RR73 he did not go in logger32
log.
So yes this bug exist, and why it happen not all the time....that is
the question...
And still not understand why when i close JTDX my rig (and all the
rest) come back to the frequency (but more frustrating, the BAND) set in logger
just before opening JTDX.
I should be interesting to remove this in the code (JTDX or
logger32)
I close JTDX sometime because i change to CW or
SSB.
I have the steppir which is become crazy, and this is the best way to
destroy the antenna.
Some would say me to disable autotrack, but then, what is autotrack
and VSC made for ?
Some others would say me also i’m the only one...yes but this happen
! maybe there is others case than me who have this issue and say
nothing.
I will continue to investigate this issues, tried many things but
nothing positive for the moment.
|
|
|
.jpg)