Date   
Re: UDP BandMap

Dennis
 

I’m new to FT8, but I’m a long time user of Logger32. I tried the UDP feature and found it interesting. I don’t know if I had it working right, but I was learning more about WSJT-X and Logger32 trying to figure it out.  The very next day an update removed it Please put this feature back so I can continue to experiment and learn.  It looked promising and could save some time switching between programs trying to log FT8 contacts. Thanks to all who develop and continue to update Logger32 it is a great program and I use it daily.

 

Pete K1OYQ

Re: Logger32 Auto-update 339

Stewart Rolfe
 

I've been using Logger32 now for probably 15 years. It's a sign of it's reliability and usefulness that I never really think about it. It's there for day to day logging and it's there for me to import my contest logs from N1MM; I suppose I just take it for granted.

So I'm guilty of not giving sufficient gratitude and acknowledgment to the folk that keep this complicated piece of software going. So I'm now giving them a big thumbs up and hopefully making amends a little. Sadly you only seem to read the bad stuff like on the TV news, human nature I suppose.

I know nothing about these latest issues as I don't use FT8 etc. Tried it and got bored after 10 minutes......

73,
Stew, GW0ETF


---In hamlogger@..., <thomasgwylie@...> wrote :

Spot on Jim

Tom

GM4FDM

On 9 Nov 2017 10:31 pm, "'Jim Hargrave' w5ifp@... [hamlogger]" <hamlogger@...> wrote:
 

Let me set the record straight.

Bob Furzer / K4CY is the sole owner / programmer for Logger32. As such, he makes all decisions on Logger32 functionality.

The Development/Beta team, along with several volunteer users, have spent countless hours the past 3 weeks testing/debugging the JT interface into Logger32.

It is very disturbing to see unfounded negative reports, posted for the world to see, during an intensive development effort. Quiet often functions are removed / rewritten and re-instated during the development / de-bug effort. The JT effort is still on-going. Please be patient, a new auto-update will be forthcoming.

Bottom line: If you can’t say something good about a FREE program, please just ask for your money back and buy another program or, better yet, program your own masterpiece.

73, Jim – w5ifp@...

From: hamlogger@... [mailto:hamlogger@yahoogroups. com]
Sent: Thursday, November 9, 2017 11:13 AM
To: hamlogger@...
Subject: Re: [hamlogger] Re: Logger32 Auto-update 339

Well,

My post as it appears was not finished but it seems a part has been removed.

Anyway,

Let's just add that there was a very polite mail traffic with Rick and me until he did not answer anymore.

Rick obviously was pissed with my questions for more info and removed the UDP functionality.

Like G4DWV stated, I was surprised that Rick spoiled it for everyone. The Logger32 users do not deserve that. However, I cannot feel responsible for Rick’s decision. He simply lost his cool I guess.

I hope for all you guys he will re-implement the UDP function.

As for me, I can’t rely on software managed in such an impulsive way. I lost my confidence.

I just wanted you to know what happened. No more, no less.

But apparently I'm not aloud to give the full story.

So be it.

73,

Bruno

ON6AB

[Non-text portions of this message have been removed]

Re: Logger32 Auto-update 339

w4lde
 

Mike,
The TCP when setup with SOCAT will allow you to use all the positive features of WSJT-x and JTAlert with auto logging to Logger32.
Stay tune for a help file update soon.  Both UDP and TCP  com’s provide significant benefits 
73 de Ron W4LDE




On Nov 9, 2017, at 10:54 AM, michael@... [hamlogger] <hamlogger@...> wrote:

 

Why does the UDP function need to be removed?  Why not just close the UDP port in Logger32 if you are using JTAlert?  I am running version .337 and can use either L32 or JTAlert with WSJT-X, (not both at the same time) by either opening or closing the UDP socket in L32..  What I like about connecting to L32 is it will automatically log the contact when I log it in WSJT-X.

What I like about JTAlert is it shows needed state info whereas L32 only seems to show needed DX info.  In the JTAlert settings under Logging -> Last QSO API it states, "JTAlert will automatically... transmit an ascii UDP packet of the ADIF record."  It is set for UDP port 52001 by default.  Would it be possible to allow the UDP port in L32 to be changed to port 52001 for the purpose of logging the contact while using JTAlert for the actual alerts?  Or does this get into the database issuse?

Mike
KIØHA


---In hamlogger@..., wrote :

Hi all,


It seems I’m the “bad apple” posting the 2/5 review on eHam.

Here’s what happened:

Let me first say that I was using version  335 of Logger32, so without the UDP function.

I’m using Logger32 for more than 10 years (see my review on eHam om February 11  2005).

Also, I did not find any  wiki about how to connect WSJT-X to Logger32 so I was not aware .

I also did not see any version history/changes on the website. Nor was there a helpfile explaining  the WSJT functionality. The latest online helpfile is for version 336 Beta 1. It even is marked as “NEW”.

Despite all the above, it is a fact that the majority of all FT8 users use JTAlert to communicate with their logging program and that Logger32 is not able to do so.


What I found on the internet was the following statement from Laurie VK3AMA, the author of JTAlert:


Sorry, there is no workaround for Logger32.

Logger32 is not supported by JTAlert as there is no way to read the Logger32 Log. It uses a proprietary format with no public documentation of its file or database structure.

JTAlert needs to be able to run queries against a log in order to perform real-time B4 checks, QSO history lookups and log scans to update the various Wanted Lists. None of this is possible with Logger32 because its log file cannot be read directly.

de Laurie VK3AMA



I was very disappointed I could not use the JTAlert functionality on Logger32 and I was afraid, considering the huge FT8 boom, that Logger 32 would be left in the dust like so many other logging software lacking to keep up to date with new technology. That’s when I posted my review.




Re: Logger32 Auto-update 339

Tom Wylie
 

Spot on Jim

Tom

GM4FDM

On 9 Nov 2017 10:31 pm, "'Jim Hargrave' w5ifp@... [hamlogger]" <hamlogger@...> wrote:
 

Let me set the record straight.

Bob Furzer / K4CY is the sole owner / programmer for Logger32. As such, he makes all decisions on Logger32 functionality.

The Development/Beta team, along with several volunteer users, have spent countless hours the past 3 weeks testing/debugging the JT interface into Logger32.

It is very disturbing to see unfounded negative reports, posted for the world to see, during an intensive development effort. Quiet often functions are removed / rewritten and re-instated during the development / de-bug effort. The JT effort is still on-going. Please be patient, a new auto-update will be forthcoming.

Bottom line: If you can’t say something good about a FREE program, please just ask for your money back and buy another program or, better yet, program your own masterpiece.

73, Jim – w5ifp@...

From: hamlogger@... [mailto:hamlogger@yahoogroups.com]
Sent: Thursday, November 9, 2017 11:13 AM
To: hamlogger@...
Subject: Re: [hamlogger] Re: Logger32 Auto-update 339

Well,

My post as it appears was not finished but it seems a part has been removed.

Anyway,

Let's just add that there was a very polite mail traffic with Rick and me until he did not answer anymore.

Rick obviously was pissed with my questions for more info and removed the UDP functionality.

Like G4DWV stated, I was surprised that Rick spoiled it for everyone. The Logger32 users do not deserve that. However, I cannot feel responsible for Rick’s decision. He simply lost his cool I guess.

I hope for all you guys he will re-implement the UDP function.

As for me, I can’t rely on software managed in such an impulsive way. I lost my confidence.

I just wanted you to know what happened. No more, no less.

But apparently I'm not aloud to give the full story.

So be it.

73,

Bruno

ON6AB

[Non-text portions of this message have been removed]

Re: Logger32 Auto-update 339

Jim Hargrave
 

Let me set the record straight.



Bob Furzer / K4CY is the sole owner / programmer for Logger32. As such, he makes all decisions on Logger32 functionality.



The Development/Beta team, along with several volunteer users, have spent countless hours the past 3 weeks testing/debugging the JT interface into Logger32.



It is very disturbing to see unfounded negative reports, posted for the world to see, during an intensive development effort. Quiet often functions are removed / rewritten and re-instated during the development / de-bug effort. The JT effort is still on-going. Please be patient, a new auto-update will be forthcoming.



Bottom line: If you can’t say something good about a FREE program, please just ask for your money back and buy another program or, better yet, program your own masterpiece.



73, Jim – w5ifp@...



From: hamlogger@... [mailto:hamlogger@...]
Sent: Thursday, November 9, 2017 11:13 AM
To: hamlogger@...
Subject: Re: [hamlogger] Re: Logger32 Auto-update 339





Well,



My post as it appears was not finished but it seems a part has been removed.

Anyway,



Let's just add that there was a very polite mail traffic with Rick and me until he did not answer anymore.



Rick obviously was pissed with my questions for more info and removed the UDP functionality.

Like G4DWV stated, I was surprised that Rick spoiled it for everyone. The Logger32 users do not deserve that. However, I cannot feel responsible for Rick’s decision. He simply lost his cool I guess.

I hope for all you guys he will re-implement the UDP function.

As for me, I can’t rely on software managed in such an impulsive way. I lost my confidence.



I just wanted you to know what happened. No more, no less.

But apparently I'm not aloud to give the full story.



So be it.



73,

Bruno

ON6AB












[Non-text portions of this message have been removed]

Re: Logger32 Auto-update 339

Rick Ellison
 

No I have not replied to you as I have just been too busy to sit in front of my computer. WE are expecting snow in the next few days and that means there is a lot of outdoor stuff that needs to get done before the snow comes. It’s more important to get ready for winter that type on the computer..

 

I did not have any doings in removing the UDP in Logger32. That was all Bob himself.

But he has re-enabled the UDP and I would imagine it will be in an auto update soon. He is working on something on the WSJT communications side and once that is done I would imagine he will make it back public again..

 

73 Rick N2AMG

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Thursday, November 9, 2017 11:07 AM
To: hamlogger@...
Subject: Re: [hamlogger] Re: Logger32 Auto-update 339

 




Hi all,

 

It seems I’m the “bad apple” posting the 2/5 review on eHam.

Here’s what happened:

Let me first say that I was using version  335 of Logger32, so without the UDP function.

I’m using Logger32 for more than 10 years (see my review on eHam om February 11  2005).

Also, I did not find any  wiki about how to connect WSJT-X to Logger32 so I was not aware .

I also did not see any version history/changes on the website. Nor was there a helpfile explaining  the WSJT functionality. The latest online helpfile is for version 336 Beta 1. It even is marked as “NEW”.

Despite all the above, it is a fact that the majority of all FT8 users use JTAlert to communicate with their logging program and that Logger32 is not able to do so.

 

What I found on the internet was the following statement from Laurie VK3AMA, the author of JTAlert:

 

Sorry, there is no workaround for Logger32.

Logger32 is not supported by JTAlert as there is no way to read the Logger32 Log. It uses a proprietary format with no public documentation of its file or database structure.

JTAlert needs to be able to run queries against a log in order to perform real-time B4 checks, QSO history lookups and log scans to update the various Wanted Lists. None of this is possible with Logger32 because its log file cannot be read directly.

de Laurie VK3AMA

 

 

I was very disappointed I could not use the JTAlert functionality on Logger32 and I was afraid, considering the huge FT8 boom, that Logger 32 would be left in the dust like so many other logging software lacking to keep up to date with new technology. That’s when I posted my review.

 

 

Shortly after, I reveived following mail from Rick:

2017-11-07 4:34 GMT+01:00 Rick Ellison <rellison@...>:

 

Hi..
I just read your review on Logger32. I really wish you would remove it. You
really do not know the work that has taken place behind the scenes to get
JTAlert to work with Logger32. The problem is not in Logger32. WSJT and JTDX
have a udp connection called Multicast which allows all the application that
connect to WSJT/JTDX to share the UDP port. Only problem is because of the
language that JTAlert is written in he can't support the Multicast UDP
connections. Only one application can connect to WSJT/JTDX via the normal
127.0.0.1 port. So since JTAlert has to use this port no other applications
can connect to WSJT/JTDX. I have emailed Laurie to see if he could add a
repeater port so the data that gets passed to JTAlert from WSJT/JTDX could
get forwarded out the new port I have emailed him about. I have not heard
anything back from him as of yet.

I wrote the code for Bob to use to connect to WSJT/JTDX and I am well aware
what the issues are that are taking place. Bob and I email each other a
couple of times a day about what is going on..
So because of all this I really would ask you to remove your posting...

73 Rick N2AMG

 

Rick got me curious about the interaction between Logger and WSJT. I also was surprised that Laurie claimed it was Logger’s fault and Rick claimed it was Laurie’s fault.

I answered Rick with the above comments from Laurie and with the following question:

 

 

Hello Rick,

 

If it is not via the UDP port, how are HRD, DXKeeper/DXLAB, ACLog and Log4OM communicating with JTAlert?

 

br,

 

Bruno

 

Rick Answered with following mail:

 

2017-11-07 14:09 GMT+01:00 Rick Ellison <rellison@...>:

They all use normal databases Access for DXlabs, HRD is Access or Mysql, ACLog is Sqlite,Log4om is Mysql all of these programs use databases that the specs are in the public domain. JT Alert reads those database formats for the information he uses. All of the programs you listed all have a means (messaging) that JTAlert uses to log qso’s in those databases. Dxlabs uses DDE/TCIP, HRD uses TCIP, ACLog has its own server that it logs into and passes information to ACLog. Log4OM uses TCIP. Bob wrote his own database that is  proprietary. With the new enhancements that Bob made to Logger32 with its own access to WSJT it does everything that JTAlert does but within Logger32. The issue is people are used to JTAlert and do not understand that this is now all built into Logger32.

 

73 Rick N2AMG

 

 

If Logger was indeed doing more or less everything that JTAlert does, of course I was willing to remove my post.

To be sure, I asked Rick a last question as I did not really understand how it would work then:

 

Rick,

 

If you say "With the new enhancements that Bob made to Logger32 with its own access to WSJT it does everything that JTAlert does but within Logger32."

 

How then can I interconnect WSJT-X with logger32 and how can I see like for instance which of all decoded callsigns I still need for WAS?

 

 

That was it.

No more response from Rick.

Rick obviously was pissed with my questions and removed the UDP functionality.

Like G4DWV stated, I was surprized that Rick spoiled it for everyone. The Logger32 users do not deserve that. However, I cannot feel responsible for  Rick’s decision. He simply lost his cool I guess.

I hope for all you guys he will re-implement the UDP function.

As for me, I can’t rely on software managed in such an impulsive way. I lost my confidence.

Also, I will not respond on any comments on my  posting.

I just wanted you to know what happened. No more, no less.

 

73,

Bruno

ON6AB




Re: Logger32 Auto-update 339

guy@...
 

Hi Bruno,

I also am now prepared to use software where the programmer acts in an impulsive way over ONE, so-called, negative utterance.

73 de Guy G4DWV 4X1LT

Re: Logger32 Auto-update 339

wd40konijn66@...
 

Well,

My post as it appears was not finished but it seems a part has been removed.
Anyway, 

Let's just add that there was a very polite mail traffic with Rick and me until he did not answer anymore.

Rick obviously was pissed with my questions for more info and removed the UDP functionality.

Like G4DWV stated, I was surprised that Rick spoiled it for everyone. The Logger32 users do not deserve that. However, I cannot feel responsible for  Rick’s decision. He simply lost his cool I guess.

I hope for all you guys he will re-implement the UDP function.

As for me, I can’t rely on software managed in such an impulsive way. I lost my confidence.


I just wanted you to know what happened. No more, no less.

But apparently I'm not aloud to give the full story.


So be it.


73,

Bruno

ON6AB


Re: Logger32 Auto-update 339

michael@...
 

Why does the UDP function need to be removed?  Why not just close the UDP port in Logger32 if you are using JTAlert?  I am running version .337 and can use either L32 or JTAlert with WSJT-X, (not both at the same time) by either opening or closing the UDP socket in L32..  What I like about connecting to L32 is it will automatically log the contact when I log it in WSJT-X.

What I like about JTAlert is it shows needed state info whereas L32 only seems to show needed DX info.  In the JTAlert settings under Logging -> Last QSO API it states, "JTAlert will automatically... transmit an ascii UDP packet of the ADIF record."  It is set for UDP port 52001 by default.  Would it be possible to allow the UDP port in L32 to be changed to port 52001 for the purpose of logging the contact while using JTAlert for the actual alerts?  Or does this get into the database issuse?

Mike
KIØHA


---In hamlogger@..., <wd40konijn66@...> wrote :

Hi all,


It seems I’m the “bad apple” posting the 2/5 review on eHam.

Here’s what happened:

Let me first say that I was using version  335 of Logger32, so without the UDP function.

I’m using Logger32 for more than 10 years (see my review on eHam om February 11  2005).

Also, I did not find any  wiki about how to connect WSJT-X to Logger32 so I was not aware .

I also did not see any version history/changes on the website. Nor was there a helpfile explaining  the WSJT functionality. The latest online helpfile is for version 336 Beta 1. It even is marked as “NEW”.

Despite all the above, it is a fact that the majority of all FT8 users use JTAlert to communicate with their logging program and that Logger32 is not able to do so.


What I found on the internet was the following statement from Laurie VK3AMA, the author of JTAlert:


Sorry, there is no workaround for Logger32.

Logger32 is not supported by JTAlert as there is no way to read the Logger32 Log. It uses a proprietary format with no public documentation of its file or database structure.

JTAlert needs to be able to run queries against a log in order to perform real-time B4 checks, QSO history lookups and log scans to update the various Wanted Lists. None of this is possible with Logger32 because its log file cannot be read directly.

de Laurie VK3AMA



I was very disappointed I could not use the JTAlert functionality on Logger32 and I was afraid, considering the huge FT8 boom, that Logger 32 would be left in the dust like so many other logging software lacking to keep up to date with new technology. That’s when I posted my review.




Re: Logger32 Auto-update 339

wd40konijn66@...
 

Hi all,


It seems I’m the “bad apple” posting the 2/5 review on eHam.

Here’s what happened:

Let me first say that I was using version  335 of Logger32, so without the UDP function.

I’m using Logger32 for more than 10 years (see my review on eHam om February 11  2005).

Also, I did not find any  wiki about how to connect WSJT-X to Logger32 so I was not aware .

I also did not see any version history/changes on the website. Nor was there a helpfile explaining  the WSJT functionality. The latest online helpfile is for version 336 Beta 1. It even is marked as “NEW”.

Despite all the above, it is a fact that the majority of all FT8 users use JTAlert to communicate with their logging program and that Logger32 is not able to do so.


What I found on the internet was the following statement from Laurie VK3AMA, the author of JTAlert:


Sorry, there is no workaround for Logger32.

Logger32 is not supported by JTAlert as there is no way to read the Logger32 Log. It uses a proprietary format with no public documentation of its file or database structure.

JTAlert needs to be able to run queries against a log in order to perform real-time B4 checks, QSO history lookups and log scans to update the various Wanted Lists. None of this is possible with Logger32 because its log file cannot be read directly.

de Laurie VK3AMA



I was very disappointed I could not use the JTAlert functionality on Logger32 and I was afraid, considering the huge FT8 boom, that Logger 32 would be left in the dust like so many other logging software lacking to keep up to date with new technology. That’s when I posted my review.



Shortly after, I reveived following mail from Rick:

2017-11-07 4:34 GMT+01:00 Rick Ellison <rellison@...>:


Hi..
I just read your review on Logger32. I really wish you would remove it. You
really do not know the work that has taken place behind the scenes to get
JTAlert to work with Logger32. The problem is not in Logger32. WSJT and JTDX
have a udp connection called Multicast which allows all the application that
connect to WSJT/JTDX to share the UDP port. Only problem is because of the
language that JTAlert is written in he can't support the Multicast UDP
connections. Only one application can connect to WSJT/JTDX via the normal
127.0.0.1 port. So since JTAlert has to use this port no other applications
can connect to WSJT/JTDX. I have emailed Laurie to see if he could add a
repeater port so the data that gets passed to JTAlert from WSJT/JTDX could
get forwarded out the new port I have emailed him about. I have not heard
anything back from him as of yet.

I wrote the code for Bob to use to connect to WSJT/JTDX and I am well aware
what the issues are that are taking place. Bob and I email each other a
couple of times a day about what is going on..
So because of all this I really would ask you to remove your posting...

73 Rick N2AMG

 

Rick got me curious about the interaction between Logger and WSJT. I also was surprised that Laurie claimed it was Logger’s fault and Rick claimed it was Laurie’s fault.

I answered Rick with the above comments from Laurie and with the following question:



Hello Rick,

 

If it is not via the UDP port, how are HRD, DXKeeper/DXLAB, ACLog and Log4OM communicating with JTAlert?

 

br,

 

Bruno

 

Rick Answered with following mail:


2017-11-07 14:09 GMT+01:00 Rick Ellison <rellison@...>:

They all use normal databases Access for DXlabs, HRD is Access or Mysql, ACLog is Sqlite,Log4om is Mysql all of these programs use databases that the specs are in the public domain. JT Alert reads those database formats for the information he uses. All of the programs you listed all have a means (messaging) that JTAlert uses to log qso’s in those databases. Dxlabs uses DDE/TCIP, HRD uses TCIP, ACLog has its own server that it logs into and passes information to ACLog. Log4OM uses TCIP. Bob wrote his own database that is  proprietary. With the new enhancements that Bob made to Logger32 with its own access to WSJT it does everything that JTAlert does but within Logger32. The issue is people are used to JTAlert and do not understand that this is now all built into Logger32.

 

73 Rick N2AMG


 

If Logger was indeed doing more or less everything that JTAlert does, of course I was willing to remove my post.

To be sure, I asked Rick a last question as I did not really understand how it would work then:

 

Rick,

 

If you say "With the new enhancements that Bob made to Logger32 with its own access to WSJT it does everything that JTAlert does but within Logger32."

 

How then can I interconnect WSJT-X with logger32 and how can I see like for instance which of all decoded callsigns I still need for WAS?

 


That was it.

No more response from Rick.

Rick obviously was pissed with my questions and removed the UDP functionality.

Like G4DWV stated, I was surprized that Rick spoiled it for everyone. The Logger32 users do not deserve that. However, I cannot feel responsible for  Rick’s decision. He simply lost his cool I guess.

I hope for all you guys he will re-implement the UDP function.

As for me, I can’t rely on software managed in such an impulsive way. I lost my confidence.

Also, I will not respond on any comments on my  posting.

I just wanted you to know what happened. No more, no less.


73,

Bruno

ON6AB

Trabajar Logger32 desde memoria externa

YV5-JIP
 

Buenas tardes colegas, me pueden ayudar en como se trabaja con logger32 desde un pendrive de 4 GB, quiero instalarlo full en pendrive, gracias amigos y salud y vida para todos...


Good afternoon colleagues, can you help me in how you work with logger32 from a 4GB pendrive, I want to install it full on pendrive, thanks friends and health and life for all ...




Jose

YV-5-JIP

Re: Logger32 Auto-update 339

G4RRM Pete
 

Likewise Guy.

73
Pete
G4RRM

On 9 Nov 2017, at 15:18, guy@... [hamlogger] <hamlogger@...> wrote:

 

Thanks Peter. Your post was much appreciated.


Mni 73 de Guy G4DWV 4X1LT

Re: Logger32 Auto-update 339

guy@...
 

Thanks Peter. Your post was much appreciated.

Mni 73 de Guy G4DWV 4X1LT

Re: Logger32 Auto-update 339

G4RRM Pete
 

Really helpful comments!

73
Pete
G4RRM

On 9 Nov 2017, at 14:00, guy@... [hamlogger] <hamlogger@...> wrote:

 

Hi,


I had just joined the group as I was considering moving to L32.

I am very disappointed that the programmer is removing such a useful feature, that took such hard work to implement, on the basis of one bad review. 

How can a newcomer have any confidence in L32, when a useful feature can be removed in such a fashion?

73 de Guy G4DWV 4X1LT

Re: Logger32 Auto-update 339

Dan Atchison
 

I believe there was more to it than one bad review - and don't believe everything you read and hear!  I have faith it will be restored once the issues have been addressed.

There is absolutely no reason to lose confidence based upon bad or poor information. 

Dan


On 11/9/2017 9:00 AM, guy@... [hamlogger] wrote:
 

Hi,


I had just joined the group as I was considering moving to L32.

I am very disappointed that the programmer is removing such a useful feature, that took such hard work to implement, on the basis of one bad review. 

How can a newcomer have any confidence in L32, when a useful feature can be removed in such a fashion?

73 de Guy G4DWV 4X1LT

Re: Logger32 Auto-update 339

guy@...
 

Hi,

I had just joined the group as I was considering moving to L32.

I am very disappointed that the programmer is removing such a useful feature, that took such hard work to implement, on the basis of one bad review. 

How can a newcomer have any confidence in L32, when a useful feature can be removed in such a fashion?

73 de Guy G4DWV 4X1LT

Re: Marking FT8 as Digital ?

michael@...
 

Hi Rick,

I believe what you need to do is click on Tools -> Database Maintenance -> Setup phone/digital modes and check the box next to FT8 in the column for Digital statistics.

Hope this helps,

Mike
KI0HA

Marking FT8 as Digital ?

rick darwicki
 

Have FT8 QSOs that confirm on LOTW, try to mark them as GRANTED and get message to mark FT8 as digital mode. How do I do that?


Thanks,


Rick N6PE

Re: Logging automatically from WSJT-X to Logger32

NICK K. PLUMIDAKIS
 

Dear Aki Hi.

I tried to "rollback" in the .338 but for an unexplained reason my versions start from .336

Can you supply me with the .338 so I will be able to do it?

Best 73

DE

Nick

SV1VS

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Wednesday, November 08, 2017 04:39
To: hamlogger@...
Subject: RE: [hamlogger] Re: Logging automatically from WSJT-X to Logger32

 

 

Try "Rollback to a previous version" in Tools Menu. Check ver3.50.338.
Reboot Logger32 and UNCHECK "Enable auto update" temporally.

73 de aki  ja1nlx



---In hamlogger@..., <n4kh@...> wrote :

As I was just about to try it out…but I upgraded to 339. Please re-enable it.

Jim N4KH

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Tuesday, November 07, 2017 8:12 PM
To: hamlogger@...
Subject: [hamlogger] Re: Logging automatically from WSJT-X to Logger32

 

 

Just looked at update 3.50.339 and said it removed UDP!!!!
I have been waiting for this GREAT feature.
Guess I won't be updating unless there is a work around.
Very sorry to see this feature go.
73's, Bill KH6OO

Re: Logger32 Auto-update 339

Deane Walkington <dgwalkington@...>
 

Hi all Logger 32 users,

 

Bob continues to provide a great program and I fully support all who wish to see the UDP function re-installed – it was a simple and neat answer to the problem

 

Dean

VK1DW