Re: L32 Updating Database?
I would usually only see it when I was checking DXCC, etc. It happened while I was logging a QSO and not checking any awards. Just wondered.
Thanks Bob.
Tony
toggle quoted message
Show quoted text
On Nov 21, 2024, at 11:58 AM, Bob via groups.io <k4cy@...> wrote:
If you mean the top right corner of the main Logger32 window, to the tight of the toolbar. That is a progress bar and the only user setting is what color you want it to be.?To see it in action, look at the DXCC award. You will see it showing the progress of loading the award data.
?
There are some QSO logging activities where the progress bar is visible, but most?do not show it. Logging a QSO is very quick, and?there would be nothing to see. Changing a previously logged QSO prefix (for example) is relatively slow, and the progress bar is visible so that you can actually see that something is happening.
?
No, the progress bar does not slow down the logging process, it is only made visible for things that are relatively slow. Eye candy only.
?
Or something like that. SeventyThree(s).
On 11/21/2024 11:41 AM EST Anthony Buscaglia via groups.io < gihamgeek@...> wrote:
?
?
I have noticed at times that a green bar go across the top if the L32 window.
I may I have some automatic setting that I am not aware. It ] slows down the logging process.
I have over 300k Q¡¯s in the log. Anything I am missing?
?
73
Tony
K2NV
?
?
?
|
Re: L32 Updating Database?
If you mean the top right corner of the main Logger32 window, to the tight of the toolbar. That is a progress bar and the only user setting is what color you want it to be.?To see it in action, look at the DXCC award. You will see it showing the progress of loading the award data.
?
There are some QSO logging activities where the progress bar is visible, but most?do not show it. Logging a QSO is very quick, and?there would be nothing to see. Changing a previously logged QSO prefix (for example) is relatively slow, and the progress bar is visible so that you can actually see that something is happening.
?
No, the progress bar does not slow down the logging process, it is only made visible for things that are relatively slow. Eye candy only.
?
Or something like that. SeventyThree(s).
On 11/21/2024 11:41 AM EST Anthony Buscaglia via groups.io < gihamgeek@...> wrote:
?
?
I have noticed at times that a green bar go across the top if the L32 window.
I may I have some automatic setting that I am not aware. It ] slows down the logging process.
I have over 300k Q¡¯s in the log. Anything I am missing?
?
73
Tony
K2NV
?
?
?
|
I have noticed at times that a green bar go across the top if the L32 window.
I may I have some automatic setting that I am not aware. It ] slows down the logging process.
I have over 300k Q¡¯s in the log. Anything I am missing?
73
Tony
K2NV
|
Hi all
"Can't open the UDP socket. Error : the requested address is a broadcast address, but flag is not set"...
How do I deal with that, as my JTDX QSO do not get ipmported automatically ?
TU + 73
Paul F6EXV
|
Re: new installation crashing
Wow.. yes.. All right! Nice. ? CMd ?¡. ?? bcdi.exe ?. Tank you.? 73 chris?
toggle quoted message
Show quoted text
Le 21 nov. 2024 ¨¤ 16:07, Bob via groups.io <k4cy@...> a ¨¦crit?:
?
Look at Https://www.logger32.net/files/Logger32_v4_User_Manual.pdf?
page 68. SeventyThree(s).
On 11/21/2024 9:43 AM EST jean-Christophe via groups.io <fe5ind@...> wrote:
?
?
<IMG_4468.png> hello
new installation (version 4.0.307)on new computer.
when opening, the program always stops at the same time.
when the progress bar reaches "setup radio interface".
on this computer, there is no interface connected.
do you have any idea?
Tank you so much.?
f5ind chris?
|
Re: new installation crashing
Look at Https://www.logger32.net/files/Logger32_v4_User_Manual.pdf?
page 68. SeventyThree(s).
On 11/21/2024 9:43 AM EST jean-Christophe via groups.io <fe5ind@...> wrote:
?
?
 hello
new installation (version 4.0.307)on new computer.
when opening, the program always stops at the same time.
when the progress bar reaches "setup radio interface".
on this computer, there is no interface connected.
do you have any idea?
Tank you so much.?
f5ind chris?
|
new installation crashing
 hello new installation (version 4.0.307)on new computer. when opening, the program always stops at the same time. when the progress bar reaches "setup radio interface". on this computer, there is no interface connected.
do you have any idea?
Tank you so much.?
f5ind chris?
|
Re: Problems with Logger32, JTAlert plus Socat
Hello Bob,
Sorry I'm late. Had to take care of some outdoor
activities. Anyway, here we go ...
Just to let you know that I
found the hidden frog. When following your advise to look
at the TCP event viewer
window I realized that the in "Listening on port:" entered port
number 52001 after the logging of one QSO was changed
to "Listening on port: 52007". This
port number sounded familiar to me but I could not
remember why.
I started a search for
this magic port 52007 on all in
the process participating software.
Fact is that in the past I used
for a couple of month the "Parallel Logging" feature. For?
that purpose I set the port
number of the computer in question to 52007 but deactivated
"Enable parallel logging to
another PC".?? ... Look here ...
Well, why this port now was/is used for direct logging via "socat" I
don't know.
Fact is when I changed that port back to 52001?? ... look here ...
The whole logging
procedure went back to NORMAL. Though I still don't
know what has to be
blamed for that behavior.
Anyway, thanks a lot for
giving me a hand on that matter.
73 de Peter, OE3EPW
AR? SK
Am 19.11.2024 um 15:29 schrieb Bob via
groups.io:
toggle quoted message
Show quoted text
Too many
different pieces of software. Why not simply connect JTAlert
by TCP to Logger32?
?
If you
must use socat, then look at the Logger32 TCP event viewer
window. It should be 'listening' (waiting for a connection.
The LED at the bottom right should be amber). From what you
describe (only one contact logged, then nothing)? My SWAG is
that after the first contact is logged, socat is not
disconnecting and therefor cannot reconnect to log a second
contact. You will see in the Logger32 TCP event viewer that
after the first contact is logged, the socket stays connected
(the LED at the bottom right stays green).
?
If the
Logger32 TCP socket is stuck with an open connection (anything
other than an amber LED), then it is not necessary to shut
down all the software and restart. Simply right click on the
Logger32 TCP pane on the lower status bar. Close then re-open
the socket. It will re-open 'listening'.
?
Or
something like that. SeventyThree(s).
?
On 11/19/2024 4:10 AM EST Peter Eckersberger via groups.io
<oe3epw@...>
wrote: ?
?
Hello,
Need
some help. Using for more than a year the?program
combination
"Logger32", "JTAlert" and - thanks Prasad - "Socat" v
1.7.3.0-windows master. For me
and my needs the most convenient program system.
This
system was working flawlessly until a week ago when all of a
sudden the logging via "Socat" into "Logger32" had partly
quitt. "Partly" because the very first QSO is getting logged
as expected but nothing happens with the following contacts.
Although those QSOs are still logged into the JTAlerts
"Standard ADIF file" they don't show up in "Socat" and are
therefore not transferred to "Logger32". The whole logging
control system gets stuck. Very disappointing. To get rid of
this situation I've to switch off all programs in use and
start again by loading "Logger32", followed by "JTAlerts"
"Auto-Start" feature starting "Socat", "WSJT-X" and "VE7CC".
When all needed programs are running I'm able to make ONE
qso. THIS only ONE is shown on "Socat" and gets transferred
to "Logger32", for all the following contacts .... see the
story above. Back to square one.
To
me it seems the frog is hidden somewhere in "Socat". When
googling around I realized that there is a newer
Socat-version 1.8.0.1 for Windows available. Maybe there is
a helpful person who can give me a hand on that matter. OM
Prasad maybe can make a comment on whether or not "Socat"
could be the root of my problem and if an update to the
newer Socat-version could help to overcome it.
?
73
and tnx in advance de Peter, OE3EPW
AR?
SK
?
Finally
here my program config ...
|
FT897 setting: CAT Baud rate -> 4800 CAT/LIN/TUN -> CAT
Logger32 setting: Radio -> FT897 Baudrate -> 4800 Databits -> 8 Stopbit ->2
On 2024-11-20 Ë® 5:27:45, OK2LI via groups.io <ok2li@...> wrote:
?
Hi,
?
Logger32 and Yeasu FT897
Radio settings ?
Thank you
?
73! Jiri OK2LI
?
|
?
Hi,
?
Logger32 and Yeasu FT897
Radio settings ?
Thank you
?
73! Jiri OK2LI
?
|
Re: Problems with Logger32, JTAlert plus Socat
Too many different pieces of software. Why not simply connect JTAlert by TCP to Logger32?
?
If you must use socat, then look at the Logger32 TCP event viewer window. It should be 'listening' (waiting for a connection. The LED at the bottom right should be amber). From what you describe (only one contact logged, then nothing)? My SWAG is that after the first contact is logged, socat is not disconnecting and therefor cannot reconnect to log a second contact. You will see in the Logger32 TCP event viewer that after the first contact is logged, the socket stays connected (the LED at the bottom right stays green).
?
If the Logger32 TCP socket is stuck with an open connection (anything other than an amber LED), then it is not necessary to shut down all the software and restart. Simply right click on the Logger32 TCP pane on the lower status bar. Close then re-open the socket. It will re-open 'listening'.
?
Or something like that. SeventyThree(s).
?
On 11/19/2024 4:10 AM EST Peter Eckersberger via groups.io <oe3epw@...> wrote:
?
?
Hello,
Need some help. Using for more than a year the?program combination "Logger32", "JTAlert" and - thanks Prasad - "Socat" v 1.7.3.0-windows master. For me and my needs the most convenient program system.
This system was working flawlessly until a week ago when all of a sudden the logging via "Socat" into "Logger32" had partly quitt. "Partly" because the very first QSO is getting logged as expected but nothing happens with the following contacts. Although those QSOs are still logged into the JTAlerts "Standard ADIF file" they don't show up in "Socat" and are therefore not transferred to "Logger32". The whole logging control system gets stuck. Very disappointing. To get rid of this situation I've to switch off all programs in use and start again by loading "Logger32", followed by "JTAlerts" "Auto-Start" feature starting "Socat", "WSJT-X" and "VE7CC". When all needed programs are running I'm able to make ONE qso. THIS only ONE is shown on "Socat" and gets transferred to "Logger32", for all the following contacts .... see the story above. Back to square one.
To me it seems the frog is hidden somewhere in "Socat". When googling around I realized that there is a newer Socat-version 1.8.0.1 for Windows available. Maybe there is a helpful person who can give me a hand on that matter. OM Prasad maybe can make a comment on whether or not "Socat" could be the root of my problem and if an update to the newer Socat-version could help to overcome it.
?
73 and tnx in advance de Peter, OE3EPW
AR? SK
?
Finally here my program config ...
|
Problems with Logger32, JTAlert plus Socat
Hello,
Need some help. Using for more
than a year the?program
combination "Logger32",
"JTAlert" and - thanks Prasad - "Socat" v 1.7.3.0-windows master. For me and my needs the most convenient
program system.
This system was working flawlessly
until a week ago when all of a sudden the logging via "Socat"
into "Logger32" had partly quitt. "Partly" because the very
first QSO is getting logged as expected but nothing happens with
the following contacts. Although those QSOs are still logged
into the JTAlerts "Standard ADIF file" they don't show up in
"Socat" and are therefore not transferred to "Logger32". The
whole logging control system gets stuck. Very disappointing. To
get rid of this situation I've to switch off all programs in use
and start again by loading "Logger32", followed by "JTAlerts"
"Auto-Start" feature starting "Socat", "WSJT-X" and "VE7CC".
When all needed programs are running I'm able to make ONE qso.
THIS only ONE is shown on "Socat" and gets transferred to
"Logger32", for all the following contacts .... see the story
above. Back to square one.
To me it seems the frog is hidden
somewhere in "Socat". When googling around I realized that there
is a newer Socat-version 1.8.0.1 for Windows available. Maybe
there is a helpful person who can give me a hand on that matter.
OM Prasad maybe can make a comment on whether or not "Socat"
could be the root of my problem and if an update to the newer
Socat-version could help to overcome it.
73 and tnx in advance de Peter,
OE3EPW
AR? SK
Finally here my program config ...
|
Re: Spots to control radio
toggle quoted message
Show quoted text
Look at the parallel logging configuration. There is an option there to reroute clicked-on DX Spots to the other PC. SeventyThree(s).
?
?
Several weeks ago, Logger32 lost the ability to send my radio to a dx spot frequency and to populate the entry window.? Rig control works fine and I can type a frequency in and the radio will go there.? But clicking on a DX spot doesn't do anything - the entry window flashes briefly but neither the frequency or the callsign show up.? This used to work fine and I haven't (knowingly) made any changes.? I have a second computer synced to provide backup logging - that computer will populate the entry window and the frequency shows for several seconds?(but this computer doesn't have rig control).? Looking through the manual and searching for this issue hasn't shown me anything to look at. Both computers are running the latest version and have updated several times.?
?
Any suggestions are appreciated, thanks.
?
Don
VE6JY
|
Re: Spots to control radio
Look at the parallel logging configuration. There is an option there to reroute clicked-on DX Spots to the other PC. SeventyThree(s).
On 11/18/2024 12:03 PM EST Don Moman VE6JY via groups.io <ve6jy.1@...> wrote:
?
?
Several weeks ago, Logger32 lost the ability to send my radio to a dx spot frequency and to populate the entry window.? Rig control works fine and I can type a frequency in and the radio will go there.? But clicking on a DX spot doesn't do anything - the entry window flashes briefly but neither the frequency or the callsign show up.? This used to work fine and I haven't (knowingly) made any changes.? I have a second computer synced to provide backup logging - that computer will populate the entry window and the frequency shows for several seconds?(but this computer doesn't have rig control).? Looking through the manual and searching for this issue hasn't shown me anything to look at. Both computers are running the latest version and have updated several times.?
?
Any suggestions are appreciated, thanks.
?
Don
VE6JY
|
Several weeks ago, Logger32 lost the ability to send my radio to a dx spot frequency and to populate the entry window.? Rig control works fine and I can type a frequency in and the radio will go there.? But clicking on a DX spot doesn't do anything - the entry window flashes briefly but neither the frequency or the callsign show up.? This used to work fine and I haven't (knowingly) made any changes.? I have a second computer synced to provide backup logging - that computer will populate the entry window and the frequency shows for several seconds?(but this computer doesn't have rig control).? Looking through the manual and searching for this issue hasn't shown me anything to look at. Both computers are running the latest version and have updated several times.?
Any suggestions are appreciated, thanks.
Don VE6JY
|
Re: Issue on v4.0.329 with the Quick QSL window
Alain,
it IS painful. As I cannot define the added value in that venture I had to rollback to the previous version, too...
Best regards, Alec
------ Wiadomo?? oryginalna ------
Data 17.11.2024 10:22:46
Temat Re: [hamlogger] Issue on v4.0.329 with the Quick QSL window
Yes, there were changes made that slow down the opening of the Quick QSL window, but no changes that slow down how long it takes to change whatever you wanted to change. And, the delay in opening the Quick QSL window is only the first time you open the window.
?
And why the delay? When opening the Quick QSL window you are jumping into the logbook database somewhere. Loggoer32 needs to find out exactly where you are and move the vertical scrollbar thumb (the slider on the scrollbar) to the correct position. Why do this? So that scrolling up/down works correctly.
?
To see the difference, on v4.0.328, Open the Quick QSL window on a QSO somewhere in the middle of your logbook. Now on the vertical scrollbar? click with the mouse to scroll up one row. Did it go up one row? I think not.
?
C'est la vie. SeventyThree(s).
?
On 11/17/2024 3:57 AM EST Alain F5LMJ via groups.io <f5lmj@...> wrote:
?
?
Since version v4.0.329 I have a problem with the Quick QSL window any update takes on this version very long time before applying and block any other action. On v4.0.328 the update is done instantly. So I need to rollback to 328
Does anyone have also this issue ?
Is there any change in Quick QSL window between 328 and 329 ?
?
73, Alain F5LMJ ?
|
Re: Issue on v4.0.329 with the Quick QSL window
Yes, there were changes made that slow down the opening of the Quick QSL window, but no changes that slow down how long it takes to change whatever you wanted to change. And, the delay in opening the Quick QSL window is only the first time you open the window.
?
And why the delay? When opening the Quick QSL window you are jumping into the logbook database somewhere. Loggoer32 needs to find out exactly where you are and move the vertical scrollbar thumb (the slider on the scrollbar) to the correct position. Why do this? So that scrolling up/down works correctly.
?
To see the difference, on v4.0.328, Open the Quick QSL window on a QSO somewhere in the middle of your logbook. Now on the vertical scrollbar? click with the mouse to scroll up one row. Did it go up one row? I think not.
?
C'est la vie. SeventyThree(s).
?
On 11/17/2024 3:57 AM EST Alain F5LMJ via groups.io <f5lmj@...> wrote:
?
?
Since version v4.0.329 I have a problem with the Quick QSL window any update takes on this version very long time before applying and block any other action. On v4.0.328 the update is done instantly. So I need to rollback to 328
Does anyone have also this issue ?
Is there any change in Quick QSL window between 328 and 329 ?
?
73, Alain F5LMJ ?
|
Issue on v4.0.329 with the Quick QSL window
Since version v4.0.329 I have a problem with the Quick QSL window any update takes on this version very long time before applying and block any other action. On v4.0.328 the update is done instantly. So I need to rollback to 328
Does anyone have also this issue ?
Is there any change in Quick QSL window between 328 and 329 ?
?
73, Alain F5LMJ ?
|
Only the last 10 are kept. Anything older is automatically deleted. SeventyThree(s).
On 11/16/2024 12:44 PM EST Jean-Claude ROUGE via groups.io <j-cl.rouge@...> wrote:
?
?
Hello,
On my rollback window, I have 4.0.318 to 4.0.328 possibility.
Is possible to go back to an earlier versionn (before 4.0.318), and if yes, how ?
Tks for your help and your answer.
73's.
Jean-Claude? F6HDH
|
Hello,
On my rollback window, I have 4.0.318 to 4.0.328
possibility.
Is possible to go back to an earlier versionn
(before 4.0.318), and if yes, how ?
Tks for your help and your answer.
73's.
Jean-Claude? F6HDH
|
jean-Christophe
OK2LI
Alain F5LMJ