hamlogger@groups.io

Re: CW machine and IC-7610

Dave Colliau

#74016

As you probably know your Icom has 2 serial ports . Use the 2nd port and check the use dedicated port for cw and the use radio command PTT override is checked on mine in the keyer setup. In the 7610 under usb send keying set usb keying cw to DTR. Same for RTTY also . Usb send should be RTS.

Mine works fine

73

Dave N8DC

Show quoted text

On April 7, 2018 at 7:34 AM Mike Doe <ch25@...> wrote:

Hi, can anyone tell me how to configure cw machine and radio to be able to send CW from CW machine?
Thanks, Mike

CW machine and IC-7610

Mike

#74015

Hi, can anyone tell me how to configure cw machine and radio to be able to send CW from CW machine?
Thanks, Mike

Logger32

ANDREW KERSEY <g0ibn1@...>

#74014

I am unable to make an ADI file without the notes being included, can anyone help ?

Andy G0IBN

Re: Invalid operation

Jose EA7BJ

#74013

I have the same problem since the .348 version.
I have returned to the .347 version and the problems disappeared.
I have noticed that the problem does not appear in all the out-of-band spots, only in some.
My band plan is optimized only for the cw segment.
The "View | Enable out of band messages" is uncheck.

73 Jose.

Logger32

Yuriy Veselov

#74012

HI Mailer-Demon.

Re: Clublog Validation

David Stout

#74011

This issue was corrected with the latest L32 Update.

Thanks to Dan N3ND for investigating it and the L32 team for fixing it.

KY3W

Re: Error with Auto Update to version 3.50.352

Gerald Boutin

#74010

On Fri, Apr 6, 2018 at 07:26 pm, Steve Gorecki wrote:

I just tried the update, it failed with less bytes than expected in the download...

Steve VE3RX

Steve,

It worked OK here. I think the error you got indicates a download timeout. Try again.

--
Gerald, VE1DT

Re: Error with Auto Update to version 3.50.352

Steve VE3RX

#74009

I just tried the update, it failed with less bytes than expected in the download...

Steve VE3RX

Re: USA prefixes...

Larry Fravel

#74008

I use the prefix updates from Club Log every day when I turn on the logging computer.

Larry K8YYY

"Never interrupt some one doing something you said couldn't be done"
Amelia Earhart

This email has been checked for viruses by AVG antivirus software.
www.avg.com

Re: L32 LogSync and LOTW Problem - Solved

Makoto Tanaka

#74007

Dave,

Thanks to your update, I have solved the same
problem and LoTW works well now.

73s, Shin JR1NHD

Show quoted text

On 2018/04/07 0:08, gw8szl via Groups.Io wrote:
Hi All,

Just an update on my problem with LOTW crashing Windows 7 Professional
for you.

I downloaded L32LogSync ver 2.0.0.2 and tried enabling LOTW from the
Program Setup menu as before and it crashed once again.

I then had a look at the L32Lotw_eQSL_Utility.ini file from the
previous version and noticed the line:

TQSLPath=C:\Program Files\TrustedQSL\tqsl.exe

I added this manually to the new L32LogSync.ini file along with LOTW=
True and now i can access the LOTW Setup menu. I have just got to
enter all my details now.

Just thought i would let you know how i have managed to get it working
as it could help others with the same problem.

73

Dave GW8SZL

Error with Auto Update to version 3.50.352

w4lde

#74006

1st time Ive had any problem with Logger32 Auto Update, but after downloading and trying to imitate the update I got two warnings which are:

#302 - The central header offset was incorrect, and

#319 - The zip file reported more files than found in the central directory.

Anyone else seeing these two alerts?

Thanks for any feedback

73 - Ron W4LDE

Virus-free. www.avast.com

Re: USA prefixes...

akira yoshida <ayoshida@...>

#74005

This works as expected. I use Country database exceptions from ClubLog.

73 de aki ja1nlx

Show quoted text

On 2018/04/07 3:49, Steph Collas via Groups.Io wrote:

Hello,

I use the very last update of Logger32.

If I hit, for exemple, AA4AK, which is an OM from USA, the Logger32's data base does not recognize it as USA (see print screen: Unknown prefix).

I recalculate statistics... same issue.

Any idea?

73 de Steph, F5NZY

--

73 de aki ja1nlx

Re: USA prefixes...

Mike

#74004

Works for me. Shows W NA 05 for me.
Mike

Re: USA prefixes...

Steph Collas <f5nzy@...>

#74003

We are at least two, Larry...

Waiting for response...

73 de Steph, F5NZY

Le 06/04/2018 à 23:05, Larry Fravel a écrit :

Show quoted text

Been having this problem for over a week now on various prefixes. All seem to be near the end of the alphabet. Asked about it last week but got no response. thought maybe I was the only one having it.

Larry K8YYY

"Never interrupt some one doing something you said couldn't be done"
Amelia Earhart

This email has been checked for viruses by AVG antivirus software.
www.avg.com

Re: USA prefixes...

Larry Fravel

#74002

Been having this problem for over a week now on various prefixes. All seem to be near the end of the alphabet. Asked about it last week but got no response. thought maybe I was the only one having it.

Larry K8YYY

"Never interrupt some one doing something you said couldn't be done"
Amelia Earhart

This email has been checked for viruses by AVG antivirus software.
www.avg.com

Re: New Update for L32LogSync

Rick Ellison

#74001

All depends on how you are uploading them. If you are uploading them in real-time you should not get any except if the file contains more than 1 qso in it then it will use the WebUpload routine where you will get an email from ClubLog. Turn on debug and the next time you upload to Clublog after doing so send the debug.txt file to me so I can look at how it is doing the upload..

73 Rick n2AMG

Show quoted text

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Filipe Lopes
Sent: Friday, April 6, 2018 1:09 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] New Update for L32LogSync

Hi Rick

I keep getting emails from CLUBLOG for every single QSO that I made with this v2.0.2 version, is this normal?

73's Filipe Lopes

CT1ILT - CR6K

F4VPX - TM3M

2018-04-06 3:22 GMT+02:00 Rick Ellison <rellison@...>:

I have uploaded a new version to my website. This is an update only for the
.exe file. Open the zip after downloading it and unzip the file contents
into the install directory where you have installed L32LogSync.

http://www.n2amg.com/software/l32-logsync/

This version has fixes for a bunch of bugs including eQSL and ClubLog. Also
for the TQSL path error.

73 Rick N2AMG

USA prefixes...

Steph Collas <f5nzy@...>

#74000

Hello,

I use the very last update of Logger32.

If I hit, for exemple, AA4AK, which is an OM from USA, the Logger32's data base does not recognize it as USA (see print screen: Unknown prefix).

I recalculate statistics... same issue.

Any idea?

73 de Steph, F5NZY

Re: Distance Recording as 0

Gerald Boutin

#73999

Dan,

Good try, but not the issue here. These were directly logged in L32. When I import logs from my contest logger, the Distance field is left blank.

Actually, I wish L32 did compute the distance when I import logs. I would be happy if it just used the default DXCC distance from the prefix.

--
Gerald, VE1DT

Show quoted text

On Fri, Apr 6, 2018 at 10:53 am, Dan Atchison wrote:

Had you by chance imported those Q's from a different program that doesn't compute distance? If so, L32 will not compute it for you unless you did a manual, direct entry into L32. IOW, if you imported an adif from N1MM into Logger 32 there would be no distance calculated and associated with that QSO. 73, Dan

On 4/6/2018 1:02 PM, Gerald Boutin wrote:

Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.

--
Gerald, VE1DT

On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance properly here.

Jim – w5ifp@...

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO. The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT

Re: Distance Recording as 0

Gerald Boutin

#73998

Apparently this problem has a mind of it's own. The LY28A callsign now works to store the distance. I tried different bands and different modes. I also tried logging a qso with the internet disconnected. However, nothing was conclusive. But I just tried it again now and it is working.

I also tried similar things that I did with the LY28A call with the TI5/N4YDU call, but it still resists storing the correct distance. So, I still don't know whether or not it was something I did or not.

--
Gerald, VE1DT

Show quoted text

On Fri, Apr 6, 2018 at 10:02 am, Gerald Boutin wrote:

Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.

--
Gerald, VE1DT

On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance properly here.

Jim – w5ifp@...

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO. The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT

Re: Distance Recording as 0

Dan Atchison

#73997

Had you by chance imported those Q's from a different program that doesn't compute distance? If so, L32 will not compute it for you unless you did a manual, direct entry into L32. IOW, if you imported an adif from N1MM into Logger 32 there would be no distance calculated and associated with that QSO. 73, Dan

Show quoted text

On 4/6/2018 1:02 PM, Gerald Boutin wrote:

Jim,

Double checking shows that they are, of course, correct. Logging other stations was and currently still is working correctly. Distances and bearings in the entry window also continue to be correct. So far, just this one callsign. Even LY29A and LY280A work properly.

Here is what an exported ADIF shows. It is not exactly zero, but .04. While looking there, I also found one other QSO in my log that had this problem. Logging a test qso for that call also still shows the problem.

<DISTANCE:3>.04 <BAND:3>20M <CALL:5>LY28A
<DISTANCE:3>.04 <BAND:3>40M <CALL:9>TI5/N4YDU

I have also tried recalculating statistics and restarting the program, but the issue persists. I am out of ideas as to where else to look.

--
Gerald, VE1DT

On Fri, Apr 6, 2018 at 09:21 am, Jim Hargrave wrote:

Gerald,

Check your Log Entry | Setup | My QTH settings. Make sure they a correct.

It logs Distance properly here.

Jim – w5ifp@...

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Gerald Boutin
Sent: Friday, April 6, 2018 10:42 AM
To: hamlogger@groups.io
Subject: [hamlogger] Distance Recording as 0

Logging a QSO for LY28A logs 0 km for the distance. From VE1, it should be logging 5753 km.

Typing the callsign in the entry window shows proper DXCC, bearing and distance, yet the distance is logged as 0 km. Distance logging has been working all along for other callsigns including other LY calls. I was using version 3.50.347 when I initially logged the QSO. The same problem also happens with version 3.50.351.

The LY28A callsign also shows up properly in qrz.com. Any other ideas as to why this is happening and how to get it working?

--
Gerald, VE1DT