Date   
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.

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

Jim Hargrave
 

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: STOP calling after clicking a call in UDP band map

Bob <k4cy@...>
 

Jim, I have no rotor (truth be known, I don't even have an antenna), so I'm out of my depth on this subject .Jim <W5IFP> is the resident guru on the subject, I'll leave it up to him to get you squared away. 73.

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

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: STOP calling after clicking a call in UDP band map

Jim Cox
 

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: Logger32 to SOCAT interface to JTAlert/WSJT-x

Bob <k4cy@...>
 

Ron, you're on you're own on this one (WARNING: the reflector has one way skip). This is way above my paygrade - I have never heard of SOCAT. I have heard of JTAlert, but have no idea what it is/does. I'll pass on this thread. Good luck, 73.

On September 24, 2019 at 8:28 PM w4lde <W4LDE@...> wrote:

For a log time I was running SOCAT that provides a TCP to UPD conversion so I could automatically log completed QSO's on any mode from WSJT-x through JTAlert.  Worked great until I had (and may still have ) a disk / Win10 issue.

Had to do a reformat and a reinstall of the latest Win10.  During this period there's been several updates so I'm not sure which one if any has caused the following trouble.

For the reference you can view the setup for the above in the Logger32 help file "TCP".  When I load SOCAT from JTAlert or via a direct command line using the stated attributes the Socat windows opens and then quickly closes.

I do run Win10 version 1903, WSJT-x 2.0.1, JTAlert 2.3 and Logger32 3.50.395 and SOCAT 1.7.3.0

Anyone currently running that combination and still working OK?  SOCAT is a old program and mayhave outlived its effectivness with all of the WIN10 changes.

Any other recommendations for a UDP to TCP port conversion program, Ive looked on the Internet but havent found something.

Thanks for your input and PS - through all of the troubles with HD crashes, reinstalls, ect, logger32 was the most stable and with the auto backups plus the ability to also do in manually my logs are all A-OK

73 de Ron W4LDE



Virus-free. www.avast.com


 


 

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

Bob <k4cy@...>
 

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
 

 

 


 


 


 


 

Logger32 to SOCAT interface to JTAlert/WSJT-x

w4lde
 

For a log time I was running SOCAT that provides a TCP to UPD conversion so I could automatically log completed QSO's on any mode from WSJT-x through JTAlert.  Worked great until I had (and may still have ) a disk / Win10 issue.

Had to do a reformat and a reinstall of the latest Win10.  During this period there's been several updates so I'm not sure which one if any has caused the following trouble.

For the reference you can view the setup for the above in the Logger32 help file "TCP".  When I load SOCAT from JTAlert or via a direct command line using the stated attributes the Socat windows opens and then quickly closes.

I do run Win10 version 1903, WSJT-x 2.0.1, JTAlert 2.3 and Logger32 3.50.395 and SOCAT 1.7.3.0

Anyone currently running that combination and still working OK?  SOCAT is a old program and mayhave outlived its effectivness with all of the WIN10 changes.

Any other recommendations for a UDP to TCP port conversion program, Ive looked on the Internet but havent found something.

Thanks for your input and PS - through all of the troubles with HD crashes, reinstalls, ect, logger32 was the most stable and with the auto backups plus the ability to also do in manually my logs are all A-OK

73 de Ron W4LDE



Virus-free. www.avast.com

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

Jim Cox
 

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: STOP calling after clicking a call in UDP band map

Bob <k4cy@...>
 

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