Date   
Mac user ...

Bob
 

Radhames, There are many Mac users using Logger32. The last message I saw from a Mac user, he was using Parallels. Today, I don't know what the best option would be. So, for you, there is good news and bad news ... The good news is that many users are running Logger32 on a Mac. The bad news is that there is one way skip on this reflector ... Everyone asks questions here, very few answer them here ... C'est la vie ... SeventyThree(s).

On September 28, 2019 at 7:54 PM HI3B Radhames <hi3b@...> wrote:

I come from the Mac world and  Logger32 is the main reason to use Windows, with which I have a few tangles.
 I have no intention of using another logbook.
I appreciate in advance who can give me some remote help.
I think  should not bother the group with posts if someone in his spare time could help me.   
I feel honest I must say that "the more I know Window, the more I love my Mac.
Thank you for being understanding.
Radhames, HI3B


 


--
HI3B


 

Who use TeamViewer?

HI3B Radhames
 

I come from the Mac world and  Logger32 is the main reason to use Windows, with which I have a few tangles.
 I have no intention of using another logbook.
I appreciate in advance who can give me some remote help.
I think  should not bother the group with posts if someone in his spare time could help me.   
I feel honest I must say that "the more I know Window, the more I love my Mac.
Thank you for being understanding.
Radhames, HI3B

--
HI3B

UDP shortcuts commands

Vytas LY3BG <ly3bg@...>
 


Hi!

Version 396 does but execute not all UDP shortcuts commands, does not change frequency.
Recorded commands are the same. In 395 all is OK.

V. 396

V. 395


-- 
73  Vytas LY3BG

Re: W10 New PC install File Registration problems

Jim Hargrave
 

Paul,

Just a suggestion…

You can save a lot of time loading  paper QSO’s by using “Fast Log Entry” by DF3CB.

It produces an ADIF file that you can import into Logger32.

 

https://www.df3cb.com/fle/

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Paul Bigwood
Sent: Saturday, September 28, 2019 8:44 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] W10 New PC install File Registration problems

 

OK now working after using paper logging for a while.

I realised that I had not read you reply correctly. Running the application first time as an administrator is critical with the protection that Windows puts on everything these days.

Now installed and busy reloading my QSO database.

Thanks for the help and I must read a bit more carefully!

73 de Pau; G3WYW

Re: W10 New PC install File Registration problems

Paul Bigwood <paul@...>
 

OK now working after using paper logging for a while.

I realised that I had not read you reply correctly. Running the application first time as an administrator is critical with the protection that Windows puts on everything these days.

Now installed and busy reloading my QSO database.

Thanks for the help and I must read a bit more carefully!

73 de Pau; G3WYW

Re: QSL via lotW and eQsl

IZ5ILJ Lenio
 

Hi Steph and Jim,

tnx so much, I've allready installed this great utility of Rich and I've enabled the HRDLOG.net that sends the qsl to LotW and eQsl and for this reason I asked if it was possible to make some settings directly on Logger32 to indicate how already sent the qsls.

73's de Lenio - IZ5ILJ - #69.


Il 26/09/2019 21:16, Jim Hargrave ha scritto:

Lenio,

The procedure for setting up Logger32 to do this is outlined in the Logger32 help file under “Tips, Tricks and  Troubleshooting, paragraph 1.13”

Once you have setup Logger32, then install N2AMG’s L32 Log sync program to do the work.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of IZ5ILJ Lenio
Sent: Thursday, September 26, 2019 12:25 PM
To: hamlogger@groups.io
Subject: [hamlogger] QSL via lotW and eQsl

 

Hi guys,

with my bad english I don't know if I will be able to explain myself: is it possible to put some settings so that all the qsos that I put in log are set as qsl sent via lotw and eqsl?

 

TNX in advance, greetings

73's de Lenio - IZ5ILJ - #69.

 

Re: QSL via lotW and eQsl

Bob
 

... but first you should detup Logger32. On the Logbook Entry Window, Right click on the CALLSIGN field. Move the mouse to SETUP. Then click on QSLING & QSO EXPORT. You will see this menu:




CHECK the EQSL and LOTW options. Now new QSOs can be exported with the N2AMG utility. SeventyThree(s).

On September 26, 2019 at 1:59 PM "Steph Collas via Groups.Io" <f5nzy@...> wrote:

Yes, it is…

 

You need to use the great L32LogSync, available from Rich’s site : https://www.n2amg.com/

 

73 de Steph, F5NZY

 

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de IZ5ILJ Lenio
Envoyé : jeudi 26 septembre 2019 19:25
À : hamlogger@groups.io
Objet : [hamlogger] QSL via lotW and eQsl

 

Hi guys,

with my bad english I don't know if I will be able to explain myself: is it possible to put some settings so that all the qsos that I put in log are set as qsl sent via lotw and eqsl?

 

TNX in advance, greetings

73's de Lenio - IZ5ILJ - #69.
     

 

 



 


 

Re: QSL via lotW and eQsl

Jim Hargrave
 

Lenio,

The procedure for setting up Logger32 to do this is outlined in the Logger32 help file under “Tips, Tricks and  Troubleshooting, paragraph 1.13”

Once you have setup Logger32, then install N2AMG’s L32 Log sync program to do the work.

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of IZ5ILJ Lenio
Sent: Thursday, September 26, 2019 12:25 PM
To: hamlogger@groups.io
Subject: [hamlogger] QSL via lotW and eQsl

 

Hi guys,

with my bad english I don't know if I will be able to explain myself: is it possible to put some settings so that all the qsos that I put in log are set as qsl sent via lotw and eqsl?

 

TNX in advance, greetings

73's de Lenio - IZ5ILJ - #69.

 

Re: QSL via lotW and eQsl

Steph Collas <f5nzy@...>
 

Yes, it is…

 

You need to use the great L32LogSync, available from Rich’s site : https://www.n2amg.com/

 

73 de Steph, F5NZY

 

 

 

De : hamlogger@groups.io <hamlogger@groups.io> De la part de IZ5ILJ Lenio
Envoyé : jeudi 26 septembre 2019 19:25
À : hamlogger@groups.io
Objet : [hamlogger] QSL via lotW and eQsl

 

Hi guys,

with my bad english I don't know if I will be able to explain myself: is it possible to put some settings so that all the qsos that I put in log are set as qsl sent via lotw and eqsl?

 

TNX in advance, greetings

73's de Lenio - IZ5ILJ - #69.

 

QSL via lotW and eQsl

IZ5ILJ Lenio
 

Hi guys,

with my bad english I don't know if I will be able to explain myself: is it possible to put some settings so that all the qsos that I put in log are set as qsl sent via lotw and eqsl?

TNX in advance, greetings
73's de Lenio - IZ5ILJ - #69.

Complete stats...

Steph Collas <f5nzy@...>
 

Re: ROTOR problem

Jim Hargrave
 

Jim,

 

Yes…Send me your “LOGGER32.INI”  & “MYBANDMODE.DB” to w5ifp@....

Is your Logger32 located in default folder “C\Logger32”? If different, tell me your folder setup and I’ll duplicate it here

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Cox
Sent: Wednesday, September 25, 2019 7:20 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Rotator works fine with spots from the dx band spots.  Only the UDP map.  Nothing is sent to the rotator according to the rotator debug screen.  I also have my delay at 3 seconds.

This started several months ago.  Will be happy to send you my logger32.ini if that would help.   73s Jim K4JAF

 

From: Jim Hargrave

Sent: Tuesday, September 24, 2019 8:47 PM

Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Jim,

I cannot duplicate your condition  Logger32 commands the Rotor to target as soon as the preset delay expires.

 

I have my command delay set to 3 second This allows sufficient  time for on-line call lookups.

If you have poor internet response, try extending the delay time.

 

Be sure you have the correct rotor number identified in the band plan.

 

Logger32 should compute direction based on (1)Call area > refined to  (2)Grid (If available). .

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Cox
Sent: Tuesday, September 24, 2019 8:13 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Yep, finally woke up from afternoon nap.  Us old people need our beauty rest.......

That turn rotor on DX spot is marked, works fine on spots from the DX spots map.  I believe it worked ok in the past on most jtdx spots too but quit working a while ago and since others have no problem, must be on my end.  Just not sure what is happening but see no rotator commands in rotor debug but they are fine just clicking on a DX spot entry...  Not sure what is happening..

73s Jim K4JAF

 

From: Bob

Sent: Tuesday, September 24, 2019 7:29 PM

Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Jim, you woke up from your afternoon nap? Try this:

 

 

Does that work for you? SeventyThree(s).

On September 24, 2019 at 8:21 PM Jim Cox <jcox123@...> wrote:

I don’t see any rotator commands sent in the rotator debug screen after I click on  a spot in the udp band map.   Nothing at all, unless I manually click on the world map, then the rotator command appears in the rotator debug screen  73s Jim K4JAF

 

From: Bob

Sent: Tuesday, September 24, 2019 5:56 PM

Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Olivier, I think I have asked you before to look at the rotor debug window to see when Logger32 sends commands to the rotor to turn. Send me the information I need that would help me understand what you see. 73.

On September 24, 2019 at 6:39 PM Olivier F4FQH <unit365@...> wrote:

Hi all and Bob

 

When i click a call in the UDP band map, it’s very hard to stop the system calling.

I delete the call in operator, i click on CLEAR DX in JTDX, and if i’ve not clicked on another call in the UDP bm, the system call again and there is no more call in logger and JTDX....

How to stop the system calling without clicking on another call in DX spots windows ?

 

Bob, for the rotor, i still have some issues.

The problem too, is when i click on a call in the UDP bm, call is filling operator windows, but the rotor don’t move, it moving when the system call after 73 or CQ.

If the antenna is in oposite direction, i must click on the map to turn it in the good direction.

I think it should be interesting the antena turn when we click on UDP bm call for first time.

Maybe it’s due to the last mods you made for the rotor bug.

 

thanks

 

73s

Olivier

F4FQH

 


 


 


 


 


 


 

Re: FT4 Mode

Gerry VE6LB
 

This is also incorrect . The adif tag have wrong character counts.


On September 25, 2019 2:19:26 a.m. MDT, ja1nlx <ayoshida0205@...> wrote:

Charles

<MODE:3>FT4 is not correct.

It should be replaced with <MODE:4>MFSK<SUBMODE:3>FT4

You can change this using text editor. If you have a problem to change then send me

whole BAD.adi.

73

On 2019/09/25 17:11, Charles &#39;OXO&#39; wrote:
Thanks Aki-San,

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:5>M0IYI <CONT:2>EU <COUNTRY:7>England <CQZ:2>14 <DISTANCE:7>276.000 <DXCC:3>223 <FORCE_INIT:1>0 <GRIDSQUARE:6>IO94io <ITUZ:2>27 <K_INDEX:3>2.0 <LAT:11>N054 36.250 <LON:11>W001 17.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:7>Malcolm <PFX:2>M0 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:10>Billingham <RST_RCVD:3>-06 <RST_SENT:3>-01 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>120900 <TIME_ON:6>120900 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:6>PD0JMH <CONT:2>EU <COUNTRY:11>Netherlands <CQZ:2>14 <DISTANCE:7>338.000 <DXCC:3>263 <FORCE_INIT:1>0 <GRIDSQUARE:6>JO32cd <ITUZ:2>27 <K_INDEX:3>2.0 <LAT:11>N052 08.750 <LON:11>E006 12.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:3>Jos <PFX:3>PD0 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:7>Zutphen <RST_RCVD:3>-05 <RST_SENT:3>-14 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>120300 <TIME_ON:6>120200 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:5>K2TQC <CONT:2>NA <COUNTRY:13>United States <CQZ:1>5 <DISTANCE:8>5586.000 <DXCC:3>291 <FORCE_INIT:1>0 <GRIDSQUARE:6>FN13xa <ITUZ:1>8 <K_INDEX:3>2.0 <LAT:11>N043 01.250 <LON:11>W076 02.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:7>William <PFX:2>K2 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:10>Jamesville <RST_RCVD:3>+01 <RST_SENT:3>-16 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>115900 <TIME_ON:6>115800 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.



On Wed, Sep 25, 2019 at 9:09 AM ja1nlx <ayoshida0205@...> wrote:

Charles

Please show me a part of BAD.adi.

73

On 2019/09/25 17:04, Charles &#39;OXO&#39; wrote:

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: STOP calling after clicking a call in UDP band map

Jim Cox
 

Rotator works fine with spots from the dx band spots.  Only the UDP map.  Nothing is sent to the rotator according to the rotator debug screen.  I also have my delay at 3 seconds.
This started several months ago.  Will be happy to send you my logger32.ini if that would help.   73s Jim K4JAF
 

From: Jim Hargrave
Sent: Tuesday, September 24, 2019 8:47 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map
 

Jim,

I cannot duplicate your condition  Logger32 commands the Rotor to target as soon as the preset delay expires.

 

I have my command delay set to 3 second This allows sufficient  time for on-line call lookups.

If you have poor internet response, try extending the delay time.

 

Be sure you have the correct rotor number identified in the band plan.

 

Logger32 should compute direction based on (1)Call area > refined to  (2)Grid (If available). .

 

Jim – w5ifp-

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Jim Cox
Sent: Tuesday, September 24, 2019 8:13 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Yep, finally woke up from afternoon nap.  Us old people need our beauty rest.......

That turn rotor on DX spot is marked, works fine on spots from the DX spots map.  I believe it worked ok in the past on most jtdx spots too but quit working a while ago and since others have no problem, must be on my end.  Just not sure what is happening but see no rotator commands in rotor debug but they are fine just clicking on a DX spot entry...  Not sure what is happening..

73s Jim K4JAF

 

From: Bob

Sent: Tuesday, September 24, 2019 7:29 PM

To: hamlogger@groups.io

Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Jim, you woke up from your afternoon nap? Try this:

 

 

Does that work for you? SeventyThree(s).

On September 24, 2019 at 8:21 PM Jim Cox <jcox123@...> wrote:

I don’t see any rotator commands sent in the rotator debug screen after I click on  a spot in the udp band map.   Nothing at all, unless I manually click on the world map, then the rotator command appears in the rotator debug screen  73s Jim K4JAF

 

From: Bob

Sent: Tuesday, September 24, 2019 5:56 PM

To: hamlogger@groups.io

Subject: Re: [hamlogger] STOP calling after clicking a call in UDP band map

 

Olivier, I think I have asked you before to look at the rotor debug window to see when Logger32 sends commands to the rotor to turn. Send me the information I need that would help me understand what you see. 73.

On September 24, 2019 at 6:39 PM Olivier F4FQH <unit365@...> wrote:

Hi all and Bob

 

When i click a call in the UDP band map, it’s very hard to stop the system calling.

I delete the call in operator, i click on CLEAR DX in JTDX, and if i’ve not clicked on another call in the UDP bm, the system call again and there is no more call in logger and JTDX....

How to stop the system calling without clicking on another call in DX spots windows ?

 

Bob, for the rotor, i still have some issues.

The problem too, is when i click on a call in the UDP bm, call is filling operator windows, but the rotor don’t move, it moving when the system call after 73 or CQ.

If the antenna is in oposite direction, i must click on the map to turn it in the good direction.

I think it should be interesting the antena turn when we click on UDP bm call for first time.

Maybe it’s due to the last mods you made for the rotor bug.

 

thanks

 

73s

Olivier

F4FQH

 


 


 


 


 


 


 

Re: FT4 Mode

ja1nlx
 

Charles

<MODE:3>FT4 is not correct.

It should be replaced with <MODE:4>MFSK<SUBMODE:3>FT4

You can change this using text editor. If you have a problem to change then send me

whole BAD.adi.

73

On 2019/09/25 17:11, Charles &#39;OXO&#39; wrote:
Thanks Aki-San,

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:5>M0IYI <CONT:2>EU <COUNTRY:7>England <CQZ:2>14 <DISTANCE:7>276.000 <DXCC:3>223 <FORCE_INIT:1>0 <GRIDSQUARE:6>IO94io <ITUZ:2>27 <K_INDEX:3>2.0 <LAT:11>N054 36.250 <LON:11>W001 17.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:7>Malcolm <PFX:2>M0 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:10>Billingham <RST_RCVD:3>-06 <RST_SENT:3>-01 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>120900 <TIME_ON:6>120900 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:6>PD0JMH <CONT:2>EU <COUNTRY:11>Netherlands <CQZ:2>14 <DISTANCE:7>338.000 <DXCC:3>263 <FORCE_INIT:1>0 <GRIDSQUARE:6>JO32cd <ITUZ:2>27 <K_INDEX:3>2.0 <LAT:11>N052 08.750 <LON:11>E006 12.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:3>Jos <PFX:3>PD0 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:7>Zutphen <RST_RCVD:3>-05 <RST_SENT:3>-14 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>120300 <TIME_ON:6>120200 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:5>K2TQC <CONT:2>NA <COUNTRY:13>United States <CQZ:1>5 <DISTANCE:8>5586.000 <DXCC:3>291 <FORCE_INIT:1>0 <GRIDSQUARE:6>FN13xa <ITUZ:1>8 <K_INDEX:3>2.0 <LAT:11>N043 01.250 <LON:11>W076 02.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:7>William <PFX:2>K2 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:10>Jamesville <RST_RCVD:3>+01 <RST_SENT:3>-16 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>115900 <TIME_ON:6>115800 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.



On Wed, Sep 25, 2019 at 9:09 AM ja1nlx <ayoshida0205@...> wrote:

Charles

Please show me a part of BAD.adi.

73

On 2019/09/25 17:04, Charles &#39;OXO&#39; wrote:
Hi Aki,
          It says ''ERROR in the MODE Field''.

Its not my Log, I am trying to import a DXpedition log (for QSL Managing)

Thanks,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.



On Wed, Sep 25, 2019 at 9:02 AM ja1nlx <ayoshida0205@...> wrote:

Charles

What warning message you see in BAD.adi ?

Why you import ? Logger32 log automatically when QSO is logged in jtdx/wsjt-x ?

73

On 2019/09/25 16:51, Charles &#39;OXO&#39; wrote:
GM all,
           I am clearly missing something obvious but I am unable to get FT4 QSO's to import into the log.

I have edited the Setup Bands and Mode Table which is fine but is there somewhere else that I need to add FT4 to to stop the imported q's being thrown in the Bad file?

Thank you,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.

--
73 de aki
JA1NLX
--
73 de aki
JA1NLX
--
73 de aki
JA1NLX

Re: FT4 Mode

Charles
 

Thanks Aki-San,

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:5>M0IYI <CONT:2>EU <COUNTRY:7>England <CQZ:2>14 <DISTANCE:7>276.000 <DXCC:3>223 <FORCE_INIT:1>0 <GRIDSQUARE:6>IO94io <ITUZ:2>27 <K_INDEX:3>2.0 <LAT:11>N054 36.250 <LON:11>W001 17.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:7>Malcolm <PFX:2>M0 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:10>Billingham <RST_RCVD:3>-06 <RST_SENT:3>-01 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>120900 <TIME_ON:6>120900 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:6>PD0JMH <CONT:2>EU <COUNTRY:11>Netherlands <CQZ:2>14 <DISTANCE:7>338.000 <DXCC:3>263 <FORCE_INIT:1>0 <GRIDSQUARE:6>JO32cd <ITUZ:2>27 <K_INDEX:3>2.0 <LAT:11>N052 08.750 <LON:11>E006 12.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:3>Jos <PFX:3>PD0 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:7>Zutphen <RST_RCVD:3>-05 <RST_SENT:3>-14 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>120300 <TIME_ON:6>120200 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Error in the MODE field:  <A_INDEX:4>10.0 <ANT_AZ:3>0.0 <ANT_EL:3>0.0 <BAND:3>20m <BAND_RX:3>20m <CALL:5>K2TQC <CONT:2>NA <COUNTRY:13>United States <CQZ:1>5 <DISTANCE:8>5586.000 <DXCC:3>291 <FORCE_INIT:1>0 <GRIDSQUARE:6>FN13xa <ITUZ:1>8 <K_INDEX:3>2.0 <LAT:11>N043 01.250 <LON:11>W076 02.500 <MODE:3>FT4 <MY_CQ_ZONE:2>14 <MY_GRIDSQUARE:6>JO02PP <MY_ITU_ZONE:2>27 <MY_LAT:11>N052 38.750 <MY_LON:11>E001 17.500 <NAME:7>William <PFX:2>K2 <QSO_COMPLETE:1>Y <QSO_RANDOM:10>1246576928 <QTH:10>Jamesville <RST_RCVD:3>+01 <RST_SENT:3>-16 <RX_PWR:3>0.0 <SFI:4>66.0 <STATION_CALLSIGN:7>GB60ATG <SWL:1>0 <TIME_OFF:6>115900 <TIME_ON:6>115800 <QSO_DATE:8>20190828 <TX_PWR:6>40.000 <COMMENT:25>FT8  Sent: +00  Rcvd: -15 <EOR>

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.



On Wed, Sep 25, 2019 at 9:09 AM ja1nlx <ayoshida0205@...> wrote:

Charles

Please show me a part of BAD.adi.

73

On 2019/09/25 17:04, Charles &#39;OXO&#39; wrote:
Hi Aki,
          It says ''ERROR in the MODE Field''.

Its not my Log, I am trying to import a DXpedition log (for QSL Managing)

Thanks,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.



On Wed, Sep 25, 2019 at 9:02 AM ja1nlx <ayoshida0205@...> wrote:

Charles

What warning message you see in BAD.adi ?

Why you import ? Logger32 log automatically when QSO is logged in jtdx/wsjt-x ?

73

On 2019/09/25 16:51, Charles &#39;OXO&#39; wrote:
GM all,
           I am clearly missing something obvious but I am unable to get FT4 QSO's to import into the log.

I have edited the Setup Bands and Mode Table which is fine but is there somewhere else that I need to add FT4 to to stop the imported q's being thrown in the Bad file?

Thank you,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.

--
73 de aki
JA1NLX
--
73 de aki
JA1NLX

Re: FT4 Mode

ja1nlx
 

Charles

Please show me a part of BAD.adi.

73

On 2019/09/25 17:04, Charles &#39;OXO&#39; wrote:
Hi Aki,
          It says ''ERROR in the MODE Field''.

Its not my Log, I am trying to import a DXpedition log (for QSL Managing)

Thanks,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.



On Wed, Sep 25, 2019 at 9:02 AM ja1nlx <ayoshida0205@...> wrote:

Charles

What warning message you see in BAD.adi ?

Why you import ? Logger32 log automatically when QSO is logged in jtdx/wsjt-x ?

73

On 2019/09/25 16:51, Charles &#39;OXO&#39; wrote:
GM all,
           I am clearly missing something obvious but I am unable to get FT4 QSO's to import into the log.

I have edited the Setup Bands and Mode Table which is fine but is there somewhere else that I need to add FT4 to to stop the imported q's being thrown in the Bad file?

Thank you,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.

--
73 de aki
JA1NLX
--
73 de aki
JA1NLX

Re: FT4 Mode

Charles
 

Hi Aki,
          It says ''ERROR in the MODE Field''.

Its not my Log, I am trying to import a DXpedition log (for QSL Managing)

Thanks,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.



On Wed, Sep 25, 2019 at 9:02 AM ja1nlx <ayoshida0205@...> wrote:

Charles

What warning message you see in BAD.adi ?

Why you import ? Logger32 log automatically when QSO is logged in jtdx/wsjt-x ?

73

On 2019/09/25 16:51, Charles &#39;OXO&#39; wrote:
GM all,
           I am clearly missing something obvious but I am unable to get FT4 QSO's to import into the log.

I have edited the Setup Bands and Mode Table which is fine but is there somewhere else that I need to add FT4 to to stop the imported q's being thrown in the Bad file?

Thank you,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.

--
73 de aki
JA1NLX

Re: FT4 Mode

ja1nlx
 

Charles

What warning message you see in BAD.adi ?

Why you import ? Logger32 log automatically when QSO is logged in jtdx/wsjt-x ?

73

On 2019/09/25 16:51, Charles &#39;OXO&#39; wrote:
GM all,
           I am clearly missing something obvious but I am unable to get FT4 QSO's to import into the log.

I have edited the Setup Bands and Mode Table which is fine but is there somewhere else that I need to add FT4 to to stop the imported q's being thrown in the Bad file?

Thank you,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.

--
73 de aki
JA1NLX

FT4 Mode

Charles
 

GM all,
           I am clearly missing something obvious but I am unable to get FT4 QSO's to import into the log.

I have edited the Setup Bands and Mode Table which is fine but is there somewhere else that I need to add FT4 to to stop the imported q's being thrown in the Bad file?

Thank you,

Kindest regards

Charles Wilmott (MØOXO)
60 Church Hill,
Royston, Barnsley,
South Yorkshire, S71 4NG
England, United Kingdom

Tel ; (+44) 7900 500775

The information in this internet email is copyright of Charles Wilmott, confidential and is intended solely for the addressee(s). Any views expressed in this e-mail are those of Charles Wilmott only, except where the sender specifically states these to be his own views. Access, copying, dissemination to or re-use of information in it to or by anyone else is unauthorised.