Date   

Re: Logger32 Macros Icom 756 Pro III

Hew Lines
 

Yup. Sure is. Just look in the Helpfile, in the "MACROs" section !!

73 -Hew

VA7HU



On 2017-07-08 1:47 PM, mmaynard1@... [hamlogger] wrote:
 

I have used rig control for sometime with Logger32 but I just started working with macros today. Is there a list of the basic macros (mode, VFO,) available? 



Logger32 Macros Icom 756 Pro III

mmaynard1@...
 

I have used rig control for sometime with Logger32 but I just started working with macros today. Is there a list of the basic macros (mode, VFO,) available? 


Re: Incorrect mode in LOTW

Jan
 

ARRL makes no difference in RTTY, PSK JT65 or other digital modes. It's all data.

73
Jan
PA4JJ

Op 8-7-2017 om 08:50 schreef 'Darren Collins (G0TSM)' daz@... [hamlogger]:
 

Good Morning.

When I upload into LOTW via Rick's LOTW/EQSL Utility the QSOs are being
listed as DATA. I haven't tried to upload a CW QSO but below are three
dummy QSOs for RTTY, JT65 and SSB. An additional MODE field has been
added at the end of the record which I presume is causing the problem.

Could this be caused by a broken index that was mentioned regarding
another export issue?

73 Darren G0TSM

5150.44 20M AA1TTT WCY at 2200 :
SFI 76, A 12, K 2, R 16 NA 5 291
14.076000 8 RTTY G0TSM AA1
Y Y 20170707
223549 599 599 020
2 223549 76 12
Y 54244 PSK

63.47 6M G1AAA WCY at 2200 : SFI
76, A 12, K 2, R 16 EU 14 223 50.276000
27 JT65 G0TSM G1
Y Y 20170708
063549 -01 -01 2
063549 76 12 Y
54246 PSK

63.47 6M G1AAA WCY at 2200 : SFI
76, A 12, K 2, R 16 EU 14 223 50.176000
27 SSB G0TSM G1
Y Y 20170708
063810 59 59 2
063810 76 12 Y
54247 PSK


-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388


Incorrect mode in LOTW

Darren Collins (G0TSM)
 

Good Morning.

When I upload into LOTW via Rick's LOTW/EQSL Utility the QSOs are being listed as DATA. I haven't tried to upload a CW QSO but below are three dummy QSOs for RTTY, JT65 and SSB. An additional MODE field has been added at the end of the record which I presume is causing the problem.

Could this be caused by a broken index that was mentioned regarding another export issue?

73 Darren G0TSM



<DISTANCE:7>5150.44 <BAND:3>20M <CALL:6>AA1TTT <COMMENT:37>WCY at 2200 : SFI 76, A 12, K 2, R 16 <CONT:2>NA <CQZ:1>5 <DXCC:3>291 <FREQ:9>14.076000 <ITUZ:1>8 <MODE:4>RTTY <OPERATOR:5>G0TSM <PFX:3>AA1 <APP_LOGGER32_eQSL:1>Y <APP_LOGGER32_LoTW:1>Y <QSO_DATE:8:D>20170707 <TIME_ON:6>223549 <RST_RCVD:3>599 <RST_SENT:3>599 <STX:3>020 <K_INDEX:1>2 <TIME_OFF:6>223549 <SFI:2>76 <A_INDEX:2>12 <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:5>54244 <MODE:3>PSK <EOR>


<DISTANCE:5>63.47 <BAND:2>6M <CALL:5>G1AAA <COMMENT:37>WCY at 2200 : SFI 76, A 12, K 2, R 16 <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:9>50.276000 <ITUZ:2>27 <MODE:4>JT65 <OPERATOR:5>G0TSM <PFX:2>G1 <APP_LOGGER32_eQSL:1>Y <APP_LOGGER32_LoTW:1>Y <QSO_DATE:8:D>20170708 <TIME_ON:6>063549 <RST_RCVD:3>-01 <RST_SENT:3>-01 <K_INDEX:1>2 <TIME_OFF:6>063549 <SFI:2>76 <A_INDEX:2>12 <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:5>54246 <MODE:3>PSK <EOR>


<DISTANCE:5>63.47 <BAND:2>6M <CALL:5>G1AAA <COMMENT:37>WCY at 2200 : SFI 76, A 12, K 2, R 16 <CONT:2>EU <CQZ:2>14 <DXCC:3>223 <FREQ:9>50.176000 <ITUZ:2>27 <MODE:3>SSB <OPERATOR:5>G0TSM <PFX:2>G1 <APP_LOGGER32_eQSL:1>Y <APP_LOGGER32_LoTW:1>Y <QSO_DATE:8:D>20170708 <TIME_ON:6>063810 <RST_RCVD:2>59 <RST_SENT:2>59 <K_INDEX:1>2 <TIME_OFF:6>063810 <SFI:2>76 <A_INDEX:2>12 <LOTW_QSL_SENT:1>Y <APP_LOGGER32_QSO_NUMBER:5>54247 <MODE:3>PSK <EOR>


Re: Runtime error

M0BKV
 

sorted - all to do wit utility program VE7CC. Working now thanks.


Re: Runtime error

M0BKV
 

All overcome. To do with utility program VE7CC.


Re: Runtime error

M0BKV
 

I've overcome this 30010 problem but now get TABCTL32.OCX runtime error 339. I expect I'l solve it but every little helps. Just had to reinstall windows 10 due to update problems.


Re: Cannot export Files to LoTW and eQSL

gboutin@...
 

Andy,

Try exporting your log as ADIF and then create a new logbook and import the ADIF file.

> Gerald, VE1DT


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

Same problem has happened here, been using it for years with no problems.

So far I have tried recalculating statistics, reformat qsl numbers. 

Have even tried a new install of logger32 and still it won't find any log to upload.

It is ticked to flag to lotw etc so no issue there.

Last thing to try is to delete the utility program and reinstall that and try.

Andy
M0NKR



On 6 Jul 2017, at 18:45, cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@... [hamlogger] <hamlogger@...> wrote:

 

Thanks to everyone for the many suggestions.  I decided to uninstall/reinstall. 

First, I copied the entire Loger32 folder into a new one named "Logger32 Save" as backup if something went wrong. 

I then went to the Logger32 website and downloaded the program again.  The screens in the downloaded program were in the default formats, as expected.  Then I opened the program in the "Logger32 Save" folder to copy the .INI files to the new downloaded folder in order to reformat the screens.   But first I decided to try the "Export LoTW file" again ... to my surprise it worked!  Not sure why.  Maybe copying the files to another folder did something.  It also works in the newly downloaded program.  I then copied the .INI files to the newly downloaded program and all screens were restored to the configurations I had before all this happened.

So I'm back in action!

Thanks again to all for your suggestions and comments.

This is a great logging program and I'm very thankful to those responsible for keeping it updated.

73  Tony  KU4NY


Runtime error

M0BKV
 

The Runtime Error 30010   Invalid Colume Value   When Installing Logger32 from scratch   If I remember correctly I have to delete something but can't remember what?


Re: Cannot export Files to LoTW and eQSL

Andy M0NKR
 

Same problem has happened here, been using it for years with no problems.

So far I have tried recalculating statistics, reformat qsl numbers. 

Have even tried a new install of logger32 and still it won't find any log to upload.

It is ticked to flag to lotw etc so no issue there.

Last thing to try is to delete the utility program and reinstall that and try.

Andy
M0NKR



On 6 Jul 2017, at 18:45, cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@... [hamlogger] <hamlogger@...> wrote:

 

Thanks to everyone for the many suggestions.  I decided to uninstall/reinstall. 

First, I copied the entire Loger32 folder into a new one named "Logger32 Save" as backup if something went wrong. 

I then went to the Logger32 website and downloaded the program again.  The screens in the downloaded program were in the default formats, as expected.  Then I opened the program in the "Logger32 Save" folder to copy the .INI files to the new downloaded folder in order to reformat the screens.   But first I decided to try the "Export LoTW file" again ... to my surprise it worked!  Not sure why.  Maybe copying the files to another folder did something.  It also works in the newly downloaded program.  I then copied the .INI files to the newly downloaded program and all screens were restored to the configurations I had before all this happened.

So I'm back in action!

Thanks again to all for your suggestions and comments.

This is a great logging program and I'm very thankful to those responsible for keeping it updated.

73  Tony  KU4NY


L32 Helpfile Ver 3.50.324 Beta 1

Hew Lines
 

We are out camping with the trailer. It got too hot in the sun so I came in to the air conditioned trailer and have been working on Aki's latest changes.

Ver 3.50.324 Beta 1 has just been posted to the Github site for release.

73 - Hew
VA7HU


Re: Cannot export Files to LoTW and eQSL

cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@...
 

Thanks to everyone for the many suggestions.  I decided to uninstall/reinstall. 

First, I copied the entire Loger32 folder into a new one named "Logger32 Save" as backup if something went wrong. 

I then went to the Logger32 website and downloaded the program again.  The screens in the downloaded program were in the default formats, as expected.  Then I opened the program in the "Logger32 Save" folder to copy the .INI files to the new downloaded folder in order to reformat the screens.   But first I decided to try the "Export LoTW file" again ... to my surprise it worked!  Not sure why.  Maybe copying the files to another folder did something.  It also works in the newly downloaded program.  I then copied the .INI files to the newly downloaded program and all screens were restored to the configurations I had before all this happened.

So I'm back in action!

Thanks again to all for your suggestions and comments.

This is a great logging program and I'm very thankful to those responsible for keeping it updated.

73  Tony  KU4NY


Re: Interface IC-7600

Larry Fravel
 

Hope it worked for you.
 
73
K8YYY
 
It's easier to fool people than convince them that they've been fooled.
Mark Twain



AVG logo

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



Re: Interface IC-7600

Ron Smith <n7rd@...>
 

Tnx Larry.

73, 
Ron 

On Jul 4, 2017 12:33 PM, "'Larry R Fravel' lfravel@... [hamlogger]" <hamlogger@...> wrote:
 

Here is how I have mine set up:
 
COM3  (yours may be different)
 
Baud 9600
 
Data 8
 
Stop Bits 1
 
Parity None
 
Poling 500 MS
 
HEX  Address 7A
 
Boxes Ticked
 
Set DTR High
 
SET RTS High
 
Use Narrow CW Filter
 
ICOM Has Data ON/Off Control
 
Show VFO Split
 
Identity IC-7600
Larry K8YYY
 
It's easier to fool people than convince them that they've been fooled.
Mark Twain



AVG logo

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




Re: Logger32 with Icom 756 Pro III - Split Operation

Mike Maynard <mmaynard1@...>
 

Thanks, Jim.

Mike Maynard, KJ4FZ


On Jul 4, 2017, at 11:29 PM, 'Jim Hargrave' w5ifp@... [hamlogger] <hamlogger@...> wrote:

 

Split frequency setup is accomplished in the RCP module. Instructions are contained In the RCP section of the help file.

73, Jim – w5ifp@...

From: hamlogger@... [mailto:hamlogger@...]
Sent: Tuesday, July 4, 2017 9:39 PM
To: hamlogger@...
Subject: [hamlogger] Logger32 with Icom 756 Pro III - Split Operation

I am using the Icom 756 Pro III with Logger32. I can control the radio with no issue. Does Logger32 have split frequency capability? I use Afreet Band Master and it uses OmniRig to control the Icom 765 Pro III. I have split frequency capability with that program but not Logger32. My radio type in Logger32 is "Icom".

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


Re: Logger32 with Icom 756 Pro III - Split Operation

Jim Hargrave
 

Split frequency setup is accomplished in the RCP module. Instructions are contained In the RCP section of the help file.



73, Jim – w5ifp@gvtc.com



From: hamlogger@yahoogroups.com [mailto:hamlogger@yahoogroups.com]
Sent: Tuesday, July 4, 2017 9:39 PM
To: hamlogger@yahoogroups.com
Subject: [hamlogger] Logger32 with Icom 756 Pro III - Split Operation








I am using the Icom 756 Pro III with Logger32. I can control the radio with no issue. Does Logger32 have split frequency capability? I use Afreet Band Master and it uses OmniRig to control the Icom 765 Pro III. I have split frequency capability with that program but not Logger32. My radio type in Logger32 is "Icom".












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


Logger32 with Icom 756 Pro III - Split Operation

mmaynard1@...
 

I am using the Icom 756 Pro III with Logger32. I can control the radio with no issue. Does Logger32 have split frequency capability? I use Afreet Band Master and it uses OmniRig to control the Icom 765 Pro III. I have split frequency capability with that program but not Logger32. My radio type in Logger32 is "Icom".



Re: Cannot export Files to LoTW and eQSL

Rick Williams - VE7TK
 

Tony before throwing in the towel try a computer shut down and reboot.

73, Rick

On Tue, Jul 4, 2017 at 14:47, cr7wp2f3ps4pyumxzlkdktztoxvftpuzudhxwb7f@... [hamlogger]
wrote:
 

Jim,

Thanks for the time and trouble suggesting possible solutions.  I have tried everything, including entering sample qso's using another operator with the Send LoTW QSL checked.  The operator still does not show up in the selection box.  I'm the only operator in the logbook and the LoTW file upload process has been working flawlessly up until very recently.  I've been using Logger32 for more than 3 years now.  At this point, I'm afraid I may have to uninstall/reinstall.  As you mentioned, it may be a broken index.

Once I get this resolved, I'll post my findings.  Let's hope I can!!

Best 73
Tony KU4NY
 


Re: Cannot export Files to LoTW and eQSL

Gary Hinson
 

I agree: it’s not normally necessary to uninstall and reinstall the program itself.  

 

A full export to ADIF is well worth doing at least once a month anyway, as a log backup (save it safely offline e.g. on USB stick or CD reserved for that purpose).  Having done that anyway, opening a new logbook and importing the ADIF is no big deal provided you’re not in too much of a hurry (it takes a while to populate its internal database and calculate the statistics).

 

Hinson tip: if you do go down the reinstall route, I recommend saving offline copies of your .INI (and .ini) files first: they store your configuration – the screen and logbook layout, colours, port settings, macros, spot filters, alarms etc.  They are plain text files, editable with Notepad or TED.  Rarely, Logger32 issues can be caused by corruption or conflict in the .INI files (usually Logger32.INI for me), in which case individual sections from the saved .INI copies can be cut-n-pasted into the fresh default .INI files that Logger32 creates if they are missing, systematically testing at each stage until you find the broken section.  Alternatively, if your setup is fairly basic with most settings still at the defaults, it’s quicker and easier to forget your .INIs and just reconfigure a fresh Logger32 install manually from scratch.

 

73  GL!

Gary  ZL2iFB

 

From: hamlogger@... [mailto:hamlogger@...]
Sent: Wednesday, 5 July 2017 10:13 a.m.
To: hamlogger@...
Subject: RE: [hamlogger] Cannot export Files to LoTW and eQSL

 

 

Tony,

 

Exporting my entire log as an ADIF file and importing it to a new, clean logbook worked here. It's easy enough to try.

 

> Gerald, VE1DT

 

 

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

Jim,

 

Thanks for the time and trouble suggesting possible solutions.  I have tried everything, including entering sample qso's using another operator with the Send LoTW QSL checked.  The operator still does not show up in the selection box.  I'm the only operator in the logbook and the LoTW file upload process has been working flawlessly up until very recently.  I've been using Logger32 for more than 3 years now.  At this point, I'm afraid I may have to uninstall/reinstall.  As you mentioned, it may be a broken index.

 

Once I get this resolved, I'll post my findings.  Let's hope I can!!

 

Best 73

Tony KU4NY

 


Re: Cannot export Files to LoTW and eQSL

gboutin@...
 

Tony,

Exporting my entire log as an ADIF file and importing it to a new, clean logbook worked here. It's easy enough to try.

> Gerald, VE1DT


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

Jim,

Thanks for the time and trouble suggesting possible solutions.  I have tried everything, including entering sample qso's using another operator with the Send LoTW QSL checked.  The operator still does not show up in the selection box.  I'm the only operator in the logbook and the LoTW file upload process has been working flawlessly up until very recently.  I've been using Logger32 for more than 3 years now.  At this point, I'm afraid I may have to uninstall/reinstall.  As you mentioned, it may be a broken index.

Once I get this resolved, I'll post my findings.  Let's hope I can!!

Best 73
Tony KU4NY
 

13441 - 13460 of 85217