Date   

Re: Logger 32 / CW Machine

Dave Colliau
 

Easy Bob . I see your blood pressure rising  !
Dave N8DC

On 07/25/2020 12:00 PM Bob <k4cy@...> wrote:


How can we help you if you won't help yourself? You said:  Logger 32 for some reason will not allow me to use this device. What do you see, what do you not see? Does Logger32 see the port? Can you open the port? Maybe my biorhythms are at a low right now, but I find your description of the problem unhelpful. SeventyThree(s)
On 07/25/2020 11:21 AM n3bud <n3bud@...> wrote:


Guys I have tried all the above to no avail.   Logger 32 for some reason will not allow me to use this device.   Is anyone else using it and if so how did you configure it?  It works perfectly with N1MM.   I was hoping to use it when in our motor home.  Space is always tight and I could eliminate the paddles if it worked.  Hate to change logging programs.


Re: Name not being logged when using WSJT-X

Bob
 

Phil, yes you quoted me accurately. However to keep it in contest, I also said something like 'I haven't tested in a long time', or 'when I last tested' ... So yes, it appears WSJT-X has in their latest release addressed the issue of premature dropping of TxEnabled (which of course they denied as being problematic when I raised (no pun intended) the issue with them.

If you have the UDP BandMap option to LOG ADDITIONAL INFO FROM THE LOGBOOK ENTRY WINDOW checked, and the name field in the Logbook Entry Window when the QSO is logged, then the same cut/paste text from the Cherry-picker event viewer should adequately reveal the sequence of events.

SeventyThree(s).

On 07/25/2020 11:25 AM Phill Morris (G6EES) <phill.morris@...> wrote:


Bob

 

That’s very good news that your L32 is logging the operator name for a QSO via WSJT-X

 

In a reply you gave to me on Monday 20th you said I think you'll find the when using WSJT none of the additional information is logged.” So based on your test results below, L32 does not work the way you described on July 20th (which is very good news).

 

But me and other people don’t experience the same result as you (i.e. for us, the name is not stored)

 

Is there some kind of diagnostic or debug file(s) that I can send you so that you could see what is different in the way my setup is working. Maybe I could also send you a file containing the configuration of both L32 and WSJT-X.

Hopefully you will then be able to see what is set wrong (or different) in my system

 

If there are such files, then please tell me how to enable them and where each are stored.

I will then do the same tests as you and then forward these files to you

 

Hope this is OK with you

 

Thanks again

 

Phill G6EES

________________________.

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 25 July 2020 15:08
To: hamlogger@groups.io
Subject: [hamlogger] Name not being logged when using WSJT-X


 

 

I installed WSJT-X v2.2.2 and made some 20M FT8 contacts. I see this:

 

13:24:57 Cherry-picking AK4AG started
AK4AG sent: CQ AK4AG FM18
AK4AG not worked on 20M/FT8
13:24:57 Sent message to WSJT-X to call AK4AG
13:25:00 WSJT-X is transmitting to AK4AG
13:25:29 WSJT-X is transmitting to AK4AG
13:25:59 WSJT-X is transmitting to AK4AG
13:26:26 AK4AG replied: K4CY AK4AG -02
13:26:30 WSJT-X is transmitting to AK4AG
13:26:56 AK4AG replied: K4CY AK4AG RR73
13:27:00 WSJT-X is transmitting to AK4AG
13:27:04 AK4AG QSO logged
13:28:03 WSJT-X has stopped calling
13:28:03 Cherry-picking AK4AG ended *12
13:28:03 Sent Tx Halt message to WSJT-X

 

This contact was logged with name, but you will notice that after receiving the RR73 from AK4AG WSJT-X logged the QSO (Logger32 automatically clicked the Log QSO prompt window) sent 73 and took a lunch break. This contact was with TX1 enabled.

 

13:43:27 Cherry-picking TI2ALF started
TI2ALF sent: CQ TI2ALF EJ79
TI2ALF not worked on 20M/FT8
13:43:27 Sent message to WSJT-X to call TI2ALF
13:43:29 WSJT-X is transmitting to TI2ALF
13:43:56 TI2ALF replied: K4CY TI2ALF -12
13:43:59 WSJT-X is transmitting to TI2ALF
13:44:26 TI2ALF replied: K4CY TI2ALF RR73
13:44:29 WSJT-X is transmitting to TI2ALF
13:44:32 TI2ALF QSO logged
13:45:29 TI2ALF sent: WN2E TI2ALF -07
13:45:29 Not even time for a quick 73?
13:45:29 Sent Tx Halt message to WSJT-X
13:45:29 Cherry-picking TI2ALF ended *1

 

Again, with this contact after receipt of RR7 from TI2ALF WSJT-X logged the QSO, sent 73, and took a siesta. Name was logged. Again, for this contact, Logger32 clicked the Log QSO prompt  and TX1 enabled on WSJT-X. Lets try some contacts with TX1 disabled (my preferred operation setting).

 

13:52:27 Cherry-picking K4PRO started
K4PRO sent: CQ K4PRO EL87
K4PRO not worked on 20M/FT8
13:52:27 Sent message to WSJT-X to call K4PRO
13:52:29 WSJT-X is transmitting to K4PRO
13:52:59 WSJT-X is transmitting to K4PRO
13:53:26 K4PRO sent: K6JDC K4PRO RR73
13:53:29 WSJT-X is transmitting to K4PRO
13:53:56 K4PRO replied: K4CY K4PRO R+01
13:53:59 WSJT-X is transmitting to K4PRO
13:54:02 K4PRO QSO logged
13:54:26 K4PRO replied: K4CY K4PRO 73
13:54:26 Sent Tx Halt message to WSJT-X
13:54:26 Cherry-picking K4PRO ended with 73

 

For this contact, with TX1 disabled, WSJT-X behaved as I would expect, after receiving R+01 it replied with RR73, logged the QSO (Logger32 clicked the Log QSO window) and waited for the final 73 from K4PRO. The name was logged.

 

3:54:59 Cherry-picking W5W started
W5W sent: CQ W5W EL29
W5W not worked on 20M/FT8
13:54:59 Sent message to WSJT-X to call W5W
13:54:59 WSJT-X is transmitting to W5W
13:55:29 WSJT-X is transmitting to W5W
13:55:56 W5W replied: K4CY W5W R-13
13:55:59 WSJT-X is transmitting to W5W
13:56:26 W5W replied: K4CY W5W 73
13:56:26 Sent Tx Halt message to WSJT-X
13:56:26 Cherry-picking W5W ended with 73

 

Again, this contact followed the sequence I would expect. No lunch break, and name was logged.

 

Test concluded. WSJT-X uninstalled. SeventyThree(s).



Re: Logger 32 / CW Machine

Bob
 

How can we help you if you won't help yourself? You said:  Logger 32 for some reason will not allow me to use this device. What do you see, what do you not see? Does Logger32 see the port? Can you open the port? Maybe my biorhythms are at a low right now, but I find your description of the problem unhelpful. SeventyThree(s)

On 07/25/2020 11:21 AM n3bud <n3bud@...> wrote:


Guys I have tried all the above to no avail.   Logger 32 for some reason will not allow me to use this device.   Is anyone else using it and if so how did you configure it?  It works perfectly with N1MM.   I was hoping to use it when in our motor home.  Space is always tight and I could eliminate the paddles if it worked.  Hate to change logging programs.


Re: Logger 32 / CW Machine

Dave Colliau
 

If it works in N1MM it sure should work in Logger 32 ?  comport and use dedicated serial port and rts or dtr keying.use ptt to switch to transmit.  Make sure you dont have 2 programs trying to use the port at the same time .
Dave N8DC


Re: Name not being logged when using WSJT-X

Phill Morris (G6EES)
 

Bob

 

That’s very good news that your L32 is logging the operator name for a QSO via WSJT-X

 

In a reply you gave to me on Monday 20th you said I think you'll find the when using WSJT none of the additional information is logged.” So based on your test results below, L32 does not work the way you described on July 20th (which is very good news).

 

But me and other people don’t experience the same result as you (i.e. for us, the name is not stored)

 

Is there some kind of diagnostic or debug file(s) that I can send you so that you could see what is different in the way my setup is working. Maybe I could also send you a file containing the configuration of both L32 and WSJT-X.

Hopefully you will then be able to see what is set wrong (or different) in my system

 

If there are such files, then please tell me how to enable them and where each are stored.

I will then do the same tests as you and then forward these files to you

 

Hope this is OK with you

 

Thanks again

 

Phill G6EES

________________________.

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 25 July 2020 15:08
To: hamlogger@groups.io
Subject: [hamlogger] Name not being logged when using WSJT-X

 

 

 

I installed WSJT-X v2.2.2 and made some 20M FT8 contacts. I see this:

 

13:24:57 Cherry-picking AK4AG started
AK4AG sent: CQ AK4AG FM18
AK4AG not worked on 20M/FT8
13:24:57 Sent message to WSJT-X to call AK4AG
13:25:00 WSJT-X is transmitting to AK4AG
13:25:29 WSJT-X is transmitting to AK4AG
13:25:59 WSJT-X is transmitting to AK4AG
13:26:26 AK4AG replied: K4CY AK4AG -02
13:26:30 WSJT-X is transmitting to AK4AG
13:26:56 AK4AG replied: K4CY AK4AG RR73
13:27:00 WSJT-X is transmitting to AK4AG
13:27:04 AK4AG QSO logged
13:28:03 WSJT-X has stopped calling
13:28:03 Cherry-picking AK4AG ended *12
13:28:03 Sent Tx Halt message to WSJT-X

 

This contact was logged with name, but you will notice that after receiving the RR73 from AK4AG WSJT-X logged the QSO (Logger32 automatically clicked the Log QSO prompt window) sent 73 and took a lunch break. This contact was with TX1 enabled.

 

13:43:27 Cherry-picking TI2ALF started
TI2ALF sent: CQ TI2ALF EJ79
TI2ALF not worked on 20M/FT8
13:43:27 Sent message to WSJT-X to call TI2ALF
13:43:29 WSJT-X is transmitting to TI2ALF
13:43:56 TI2ALF replied: K4CY TI2ALF -12
13:43:59 WSJT-X is transmitting to TI2ALF
13:44:26 TI2ALF replied: K4CY TI2ALF RR73
13:44:29 WSJT-X is transmitting to TI2ALF
13:44:32 TI2ALF QSO logged
13:45:29 TI2ALF sent: WN2E TI2ALF -07
13:45:29 Not even time for a quick 73?
13:45:29 Sent Tx Halt message to WSJT-X
13:45:29 Cherry-picking TI2ALF ended *1

 

Again, with this contact after receipt of RR7 from TI2ALF WSJT-X logged the QSO, sent 73, and took a siesta. Name was logged. Again, for this contact, Logger32 clicked the Log QSO prompt  and TX1 enabled on WSJT-X. Lets try some contacts with TX1 disabled (my preferred operation setting).

 

13:52:27 Cherry-picking K4PRO started
K4PRO sent: CQ K4PRO EL87
K4PRO not worked on 20M/FT8
13:52:27 Sent message to WSJT-X to call K4PRO
13:52:29 WSJT-X is transmitting to K4PRO
13:52:59 WSJT-X is transmitting to K4PRO
13:53:26 K4PRO sent: K6JDC K4PRO RR73
13:53:29 WSJT-X is transmitting to K4PRO
13:53:56 K4PRO replied: K4CY K4PRO R+01
13:53:59 WSJT-X is transmitting to K4PRO
13:54:02 K4PRO QSO logged
13:54:26 K4PRO replied: K4CY K4PRO 73
13:54:26 Sent Tx Halt message to WSJT-X
13:54:26 Cherry-picking K4PRO ended with 73

 

For this contact, with TX1 disabled, WSJT-X behaved as I would expect, after receiving R+01 it replied with RR73, logged the QSO (Logger32 clicked the Log QSO window) and waited for the final 73 from K4PRO. The name was logged.

 

3:54:59 Cherry-picking W5W started
W5W sent: CQ W5W EL29
W5W not worked on 20M/FT8
13:54:59 Sent message to WSJT-X to call W5W
13:54:59 WSJT-X is transmitting to W5W
13:55:29 WSJT-X is transmitting to W5W
13:55:56 W5W replied: K4CY W5W R-13
13:55:59 WSJT-X is transmitting to W5W
13:56:26 W5W replied: K4CY W5W 73
13:56:26 Sent Tx Halt message to WSJT-X
13:56:26 Cherry-picking W5W ended with 73

 

Again, this contact followed the sequence I would expect. No lunch break, and name was logged.

 

Test concluded. WSJT-X uninstalled. SeventyThree(s).


Re: Logger 32 / CW Machine

n3bud
 

Guys I have tried all the above to no avail.   Logger 32 for some reason will not allow me to use this device.   Is anyone else using it and if so how did you configure it?  It works perfectly with N1MM.   I was hoping to use it when in our motor home.  Space is always tight and I could eliminate the paddles if it worked.  Hate to change logging programs.


Name not being logged when using WSJT-X

Bob
 



I installed WSJT-X v2.2.2 and made some 20M FT8 contacts. I see this:

13:24:57 Cherry-picking AK4AG started
AK4AG sent: CQ AK4AG FM18
AK4AG not worked on 20M/FT8
13:24:57 Sent message to WSJT-X to call AK4AG
13:25:00 WSJT-X is transmitting to AK4AG
13:25:29 WSJT-X is transmitting to AK4AG
13:25:59 WSJT-X is transmitting to AK4AG
13:26:26 AK4AG replied: K4CY AK4AG -02
13:26:30 WSJT-X is transmitting to AK4AG
13:26:56 AK4AG replied: K4CY AK4AG RR73
13:27:00 WSJT-X is transmitting to AK4AG
13:27:04 AK4AG QSO logged
13:28:03 WSJT-X has stopped calling
13:28:03 Cherry-picking AK4AG ended *12
13:28:03 Sent Tx Halt message to WSJT-X


This contact was logged with name, but you will notice that after receiving the RR73 from AK4AG WSJT-X logged the QSO (Logger32 automatically clicked the Log QSO prompt window) sent 73 and took a lunch break. This contact was with TX1 enabled.

13:43:27 Cherry-picking TI2ALF started
TI2ALF sent: CQ TI2ALF EJ79
TI2ALF not worked on 20M/FT8
13:43:27 Sent message to WSJT-X to call TI2ALF
13:43:29 WSJT-X is transmitting to TI2ALF
13:43:56 TI2ALF replied: K4CY TI2ALF -12
13:43:59 WSJT-X is transmitting to TI2ALF
13:44:26 TI2ALF replied: K4CY TI2ALF RR73
13:44:29 WSJT-X is transmitting to TI2ALF
13:44:32 TI2ALF QSO logged
13:45:29 TI2ALF sent: WN2E TI2ALF -07
13:45:29 Not even time for a quick 73?
13:45:29 Sent Tx Halt message to WSJT-X
13:45:29 Cherry-picking TI2ALF ended *1

Again, with this contact after receipt of RR7 from TI2ALF WSJT-X logged the QSO, sent 73, and took a siesta. Name was logged. Again, for this contact, Logger32 clicked the Log QSO prompt  and TX1 enabled on WSJT-X. Lets try some contacts with TX1 disabled (my preferred operation setting).

13:52:27 Cherry-picking K4PRO started
K4PRO sent: CQ K4PRO EL87
K4PRO not worked on 20M/FT8
13:52:27 Sent message to WSJT-X to call K4PRO
13:52:29 WSJT-X is transmitting to K4PRO
13:52:59 WSJT-X is transmitting to K4PRO
13:53:26 K4PRO sent: K6JDC K4PRO RR73
13:53:29 WSJT-X is transmitting to K4PRO
13:53:56 K4PRO replied: K4CY K4PRO R+01
13:53:59 WSJT-X is transmitting to K4PRO
13:54:02 K4PRO QSO logged
13:54:26 K4PRO replied: K4CY K4PRO 73
13:54:26 Sent Tx Halt message to WSJT-X
13:54:26 Cherry-picking K4PRO ended with 73

For this contact, with TX1 disabled, WSJT-X behaved as I would expect, after receiving R+01 it replied with RR73, logged the QSO (Logger32 clicked the Log QSO window) and waited for the final 73 from K4PRO. The name was logged.

3:54:59 Cherry-picking W5W started
W5W sent: CQ W5W EL29
W5W not worked on 20M/FT8
13:54:59 Sent message to WSJT-X to call W5W
13:54:59 WSJT-X is transmitting to W5W
13:55:29 WSJT-X is transmitting to W5W
13:55:56 W5W replied: K4CY W5W R-13
13:55:59 WSJT-X is transmitting to W5W
13:56:26 W5W replied: K4CY W5W 73
13:56:26 Sent Tx Halt message to WSJT-X
13:56:26 Cherry-picking W5W ended with 73

Again, this contact followed the sequence I would expect. No lunch break, and name was logged.

Test concluded. WSJT-X uninstalled. SeventyThree(s).


Re: Logger 32 / CW Machine

Barry GM4GIF
 

Crikey!, now I know why I use a straight key, plug in and go!
73 de Barry/gm4gif


Re: Logger 32 / CW Machine

Bob
 

... and Google wont tell me if the gizmo actually toggles PTT, so you'll need to experiment with that by turning on your VOX (if your radio can operate CW PTT that way). SeventyThree(s).

On 07/25/2020 8:48 AM Bob <k4cy@...> wrote:


... and Google tells me it uses RTS keying.

So, with the gizmo unplugged, open the CW Machine. Select Software keyer. Open the Keyer setup. List the serial ports Logger32 can see. Now Close the Keyer setup window and plug in the gizmo. Open the keyer setup window an list the serial ports again. See the new one? That's the port you want. Select it. Now check the dedicated serial port and and standard keying options. Click apply. SeventyThree(s).
On 07/25/2020 7:30 AM ja1nlx <ayoshida0205@...> wrote:


Mike

I think you need to select "Software mode" and select proper serial port in CW machine.
The serial port is created when the device is connected to PC.

73

On 2020/07/25 20:14, n3bud wrote:
I was trying to get CW Machine in Logger 32 to control a USB to CW device.   Device works fine with N1MM but I can't get it to work with Logger 32's CW Machine.   The device is a LD-C103 and simulates a serial port.  Any one have a solution?
Thanks,
Mike, N3BUD 
--
73 de aki
JA1NLX


Re: Logger 32 / CW Machine

Bob
 

... and Google tells me it uses RTS keying.

So, with the gizmo unplugged, open the CW Machine. Select Software keyer. Open the Keyer setup. List the serial ports Logger32 can see. Now Close the Keyer setup window and plug in the gizmo. Open the keyer setup window an list the serial ports again. See the new one? That's the port you want. Select it. Now check the dedicated serial port and and standard keying options. Click apply. SeventyThree(s).

On 07/25/2020 7:30 AM ja1nlx <ayoshida0205@...> wrote:


Mike

I think you need to select "Software mode" and select proper serial port in CW machine.
The serial port is created when the device is connected to PC.

73

On 2020/07/25 20:14, n3bud wrote:
I was trying to get CW Machine in Logger 32 to control a USB to CW device.   Device works fine with N1MM but I can't get it to work with Logger 32's CW Machine.   The device is a LD-C103 and simulates a serial port.  Any one have a solution?
Thanks,
Mike, N3BUD 
--
73 de aki
JA1NLX


Re: Logger 32 / CW Machine

ja1nlx
 

Mike

I think you need to select "Software mode" and select proper serial port in CW machine.
The serial port is created when the device is connected to PC.

73

On 2020/07/25 20:14, n3bud wrote:
I was trying to get CW Machine in Logger 32 to control a USB to CW device.   Device works fine with N1MM but I can't get it to work with Logger 32's CW Machine.   The device is a LD-C103 and simulates a serial port.  Any one have a solution?
Thanks,
Mike, N3BUD 
--
73 de aki
JA1NLX


Logger 32 / CW Machine

n3bud
 

I was trying to get CW Machine in Logger 32 to control a USB to CW device.   Device works fine with N1MM but I can't get it to work with Logger 32's CW Machine.   The device is a LD-C103 and simulates a serial port.  Any one have a solution?
Thanks,
Mike, N3BUD 


Re: Name missing in L32Lookups

Phill Morris (G6EES)
 

Pete

 

Perhaps you could do some tests when you get a moment (L32 + WSJT-X) and let me know if and when it stores the name etc

 

Thanks

 

Phill G6EES

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of G4RRM Pete
Sent: 25 July 2020 10:17
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

 

Thanks for the explanation Phil. I’m sure I have seen exactly the same behaviour with WSJTx, sometimes carrying over the Name / QTH info and other times not.

 

I’ll watch the thread for any pointers.

73

Pete

G4RRM



On 25 Jul 2020, at 10:01, Phill Morris (G6EES) <Phill.morris@...> wrote:



Pete

 

Yes, thats exactly the same problem (when using WSJT-X). Its only when WSJT-X automatically stores the QSO.

 

If i manually store a QSO,  by pressing enter key when in the L32 LogEntry window, then the name and QTH is stored in the logbook. But thats not the correct way to use WSJT-X and shouldn't be necessary.

 

Bob (L32 Guru) says that L32 only stores what WSJT-X passes to it (and WSJT-X doesn't give name) 

BUT.......

 

1. Some people report here that their L32/WSJT-X set up does store the name.

 

2. On some (rare) occasions, my setup also stores the name, without me operating or using L32/WSJT-X in any different way - Why?

 

Its all very strange. 

Its not the end of the world if course, especially as you can manually add the name etc to the log after the QSO is stored, but that is a LOT of QSOs to manually update, especially with the high QSO rate of WSJT-X 

 

I have tried both programs and prefer WSJT-X to JTDX. Both have their problems, so JTDX isn't any better from that point of view

 

Phill G6EES

 

 

 

 

-------- Original message --------

From: G4RRM Pete <pete@...>

Date: 25/07/2020 09:27 (GMT+00:00)

Subject: Re: [hamlogger] Name missing in L32Lookups

 

Hi Phil

 

I’m late to this thread, but curious of the answer.

 

I use JTDX and have it set to carry over Name & QTH from L32 (Using Ham QTH) and all works fine.

But if I use WSJT-x and L32 (I use this on VHF radio) nothing carries over from the Name / QTH info.                 

 

Is that the same issue you’re having?

 

73

Pete

G4RRM

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Phill Morris (G6EES)
Sent: 25 July 2020 08:58
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

 

Steph

 

You say it is working normally again.

 

Do you use WSJT-X with Logger32?

 

If yes, is the name recorded in your L32 logbook when the QSO is automatically recorded by WSJT-X?

 

Phill G6EES

 

 

 

 

-------- Original message --------

From: "Steph, F5NZY" <f5nzy@...>

Date: 25/07/2020 08:52 (GMT+00:00)

Subject: Re: [hamlogger] Name missing in L32Lookups

 

Thanks to Rick, everything is working normally again.

I downloaded the L32LookupInstall.msi file from Rick's site.

http://www.n2amg.com/software/l32lookups-for-logger32/

73 de Steph, F5NZY

--
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)



Re: Name missing in L32Lookups

G4RRM Pete
 

Thanks for the explanation Phil. I’m sure I have seen exactly the same behaviour with WSJTx, sometimes carrying over the Name / QTH info and other times not.

I’ll watch the thread for any pointers.

73
Pete
G4RRM

On 25 Jul 2020, at 10:01, Phill Morris (G6EES) <Phill.morris@...> wrote:


Pete

Yes, thats exactly the same problem (when using WSJT-X). Its only when WSJT-X automatically stores the QSO.

If i manually store a QSO,  by pressing enter key when in the L32 LogEntry window, then the name and QTH is stored in the logbook. But thats not the correct way to use WSJT-X and shouldn't be necessary.

Bob (L32 Guru) says that L32 only stores what WSJT-X passes to it (and WSJT-X doesn't give name) 
BUT.......

1. Some people report here that their L32/WSJT-X set up does store the name.

2. On some (rare) occasions, my setup also stores the name, without me operating or using L32/WSJT-X in any different way - Why?

Its all very strange. 
Its not the end of the world if course, especially as you can manually add the name etc to the log after the QSO is stored, but that is a LOT of QSOs to manually update, especially with the high QSO rate of WSJT-X 

I have tried both programs and prefer WSJT-X to JTDX. Both have their problems, so JTDX isn't any better from that point of view

Phill G6EES




-------- Original message --------
From: G4RRM Pete <pete@...>
Date: 25/07/2020 09:27 (GMT+00:00)
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

Hi Phil

 

I’m late to this thread, but curious of the answer.

 

I use JTDX and have it set to carry over Name & QTH from L32 (Using Ham QTH) and all works fine.

But if I use WSJT-x and L32 (I use this on VHF radio) nothing carries over from the Name / QTH info.                 

 

Is that the same issue you’re having?

 

73

Pete

G4RRM

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Phill Morris (G6EES)
Sent: 25 July 2020 08:58
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

 

Steph

 

You say it is working normally again.

 

Do you use WSJT-X with Logger32?

 

If yes, is the name recorded in your L32 logbook when the QSO is automatically recorded by WSJT-X?

 

Phill G6EES

 

 

 

 

-------- Original message --------

From: "Steph, F5NZY" <f5nzy@...>

Date: 25/07/2020 08:52 (GMT+00:00)

Subject: Re: [hamlogger] Name missing in L32Lookups

 

Thanks to Rick, everything is working normally again.

I downloaded the L32LookupInstall.msi file from Rick's site.

http://www.n2amg.com/software/l32lookups-for-logger32/

73 de Steph, F5NZY

--
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)




Re: Name missing in L32Lookups

Phill Morris (G6EES)
 

Pete

Yes, thats exactly the same problem (when using WSJT-X). Its only when WSJT-X automatically stores the QSO.

If i manually store a QSO,  by pressing enter key when in the L32 LogEntry window, then the name and QTH is stored in the logbook. But thats not the correct way to use WSJT-X and shouldn't be necessary.

Bob (L32 Guru) says that L32 only stores what WSJT-X passes to it (and WSJT-X doesn't give name) 
BUT.......

1. Some people report here that their L32/WSJT-X set up does store the name.

2. On some (rare) occasions, my setup also stores the name, without me operating or using L32/WSJT-X in any different way - Why?

Its all very strange. 
Its not the end of the world if course, especially as you can manually add the name etc to the log after the QSO is stored, but that is a LOT of QSOs to manually update, especially with the high QSO rate of WSJT-X 

I have tried both programs and prefer WSJT-X to JTDX. Both have their problems, so JTDX isn't any better from that point of view

Phill G6EES




-------- Original message --------
From: G4RRM Pete <pete@...>
Date: 25/07/2020 09:27 (GMT+00:00)
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

Hi Phil

 

I’m late to this thread, but curious of the answer.

 

I use JTDX and have it set to carry over Name & QTH from L32 (Using Ham QTH) and all works fine.

But if I use WSJT-x and L32 (I use this on VHF radio) nothing carries over from the Name / QTH info.                 

 

Is that the same issue you’re having?

 

73

Pete

G4RRM

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Phill Morris (G6EES)
Sent: 25 July 2020 08:58
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

 

Steph

 

You say it is working normally again.

 

Do you use WSJT-X with Logger32?

 

If yes, is the name recorded in your L32 logbook when the QSO is automatically recorded by WSJT-X?

 

Phill G6EES

 

 

 

 

-------- Original message --------

From: "Steph, F5NZY" <f5nzy@...>

Date: 25/07/2020 08:52 (GMT+00:00)

Subject: Re: [hamlogger] Name missing in L32Lookups

 

Thanks to Rick, everything is working normally again.

I downloaded the L32LookupInstall.msi file from Rick's site.

http://www.n2amg.com/software/l32lookups-for-logger32/

73 de Steph, F5NZY

--
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)




Re: Name missing in L32Lookups

G4RRM Pete
 

Hi Phil

 

I’m late to this thread, but curious of the answer.

 

I use JTDX and have it set to carry over Name & QTH from L32 (Using Ham QTH) and all works fine.

But if I use WSJT-x and L32 (I use this on VHF radio) nothing carries over from the Name / QTH info.                 

 

Is that the same issue you’re having?

 

73

Pete

G4RRM

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Phill Morris (G6EES)
Sent: 25 July 2020 08:58
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

 

Steph

 

You say it is working normally again.

 

Do you use WSJT-X with Logger32?

 

If yes, is the name recorded in your L32 logbook when the QSO is automatically recorded by WSJT-X?

 

Phill G6EES

 

 

 

 

-------- Original message --------

From: "Steph, F5NZY" <f5nzy@...>

Date: 25/07/2020 08:52 (GMT+00:00)

Subject: Re: [hamlogger] Name missing in L32Lookups

 

Thanks to Rick, everything is working normally again.

I downloaded the L32LookupInstall.msi file from Rick's site.

http://www.n2amg.com/software/l32lookups-for-logger32/

73 de Steph, F5NZY

--
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)




Re: Name missing in L32Lookups

Phill Morris (G6EES)
 

Steph

You say it is working normally again.

Do you use WSJT-X with Logger32?

If yes, is the name recorded in your L32 logbook when the QSO is automatically recorded by WSJT-X?

Phill G6EES




-------- Original message --------
From: "Steph, F5NZY" <f5nzy@...>
Date: 25/07/2020 08:52 (GMT+00:00)
To: hamlogger@groups.io
Subject: Re: [hamlogger] Name missing in L32Lookups

Thanks to Rick, everything is working normally again.

I downloaded the L32LookupInstall.msi file from Rick's site.

http://www.n2amg.com/software/l32lookups-for-logger32/

73 de Steph, F5NZY

--
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)





Re: Name missing in L32Lookups

Steph, F5NZY
 

Thanks to Rick, everything is working normally again.

I downloaded the L32LookupInstall.msi file from Rick's site.

http://www.n2amg.com/software/l32lookups-for-logger32/

73 de Steph, F5NZY

--
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)


Re: L32Lookup's name...

Rick Ellison
 

Hi Steph..

Go to my website and download the latest version. I posted it last week to correct a change that QRZ made to the page format. It might ask you to uninstall the current version first. It has done that on a couple of systems I have been told..

 

73 Rick N2AMG

 

From: Steph, F5NZY [mailto:f5nzy@...]
Sent: Friday, July 24, 2020 12:13 PM
To: Rick Ellison <rellison@...>
Subject: L32Lookup's name...

 

Hi Rick,

Here is what I can report :

When ckecked QRZ HTTP your name does not appearin the L32Lookup.

It does with QRZ XML.

73 de Steph, F5NZY



-- 
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)

Virus-free. www.avast.com


Re: Name missing in L32Lookups

Steph, F5NZY
 

Hi Phill and all,

Here is what I sent to Rick.

73 de Steph, F5NZY

.../...

Hi Rick,

Here is what I can report :

When ckecked QRZ HTTP your name does not appear in the L32Lookup.

It does with QRZ XML.

73 de Steph, F5NZY



-- 
-- 
Everything looks impossible to the people who never tried anything.
(Dr J-L Etienne)

2061 - 2080 of 82841