Date   

Re: manual calling from bandmap

Matthias Bellmann
 

Bob: Oh my God! What would i do without your help! Thanks

73 Matthias


Am 07.01.2020 um 17:14 schrieb Bob:

You must configure WSJT-X to allow it to receive UDP Reply messages. Then WSJT-X will accept commands from Logger32 and call the station. SeventyThree(s).

On January 7, 2020 at 10:25 AM Matthias Bellmann <Dk4wd@...> wrote:


NEED HELP:

wsjt-bandmap ist running and shows any active call.

I (right) click on a wanted call, the call  is surrounded by a red box

According to the help-file my ft8 should send a message after the wanted
call ha finished the qso (73, RRR) or has called CQ. So i exspect.

BUT: The wanted statiion terminates its qso, the red box disappears, but
nmothing happend with my wsjtx.

There must be a step i have missed out or misunderstodd.

What must i do?







Re: manual calling from bandmap

Bob
 

You must configure WSJT-X to allow it to receive UDP Reply messages. Then WSJT-X will accept commands from Logger32 and call the station. SeventyThree(s).

On January 7, 2020 at 10:25 AM Matthias Bellmann <Dk4wd@...> wrote:


NEED HELP:

wsjt-bandmap ist running and shows any active call.

I (right) click on a wanted call, the call  is surrounded by a red box

According to the help-file my ft8 should send a message after the wanted
call ha finished the qso (73, RRR) or has called CQ. So i exspect.

BUT: The wanted statiion terminates its qso, the red box disappears, but
nmothing happend with my wsjtx.

There must be a step i have missed out or misunderstodd.

What must i do?







Re: LOTW Sent flag

Bob
 

On completion of the Export LoTW file process you are prompted with message box something like this:



Click YES and QSOs are marked a SENT and the SEND fied is removed. SeventyThre(s).

On January 7, 2020 at 8:57 AM Marvin Stern <marbern@...> wrote:

Thanks for the prompt reply Bob. I used the Export LOTW file routine, LOTW accepts it, but Logger does not flag the QSO as sent. I'll try the N2AMG routine next.
73's, Marv W2AOC 

 


Re: Previous QSO

Bob
 

Yes, I can duplicate this test. I have broken something and importing ADIF records is not automatically updating the statistics. QRX while I investigate. SeventyThree(s).

On January 7, 2020 at 8:14 AM "Gianfranco via Groups.Io" <tog-franco@...> wrote:

OK Bob you are right and this also happens here.

Now I export 2 existing QSOs with the date 06 Jan, change the date of both in Jan 05 and again in Jan 07....Import the 4 new QSOs ...

In the Previous QSOs  window I only see the original 2 QSOs with the date Jan 06 and not the newones imported.
I hope to be clear.

ik3ogn GFranco


Il 07/01/2020 11:41, Bob ha scritto:
I can not duplicate this. I made a dummy QSO with IK3OGN. I see one IK3OGN QSO in the Logbook Page Window. I made a dummy ADIF file and imported a QSO with IK3OGN. I now see two IK3OGN QSOs in the Previous QSOs Window. I made another dummy QSO with IK3OGN. I now see three IK3OGN QSOs in the Previous QSOs Window. SeventyThree(s).
On January 7, 2020 at 1:21 AM "Gianfranco via Groups.Io" <tog-franco@...> wrote:

I apologize but I want to specify that only the imported QSOs do not appear in the "Previous QSOs" window.
They are shown regularly only
after the statistical recalculation.
For normal QSOs logged in via "DX Spot" everything is ok

ik3ogn GFranco

Il 07/01/2020 06:36, Gianfranco via Groups.Io ha scritto:


I have a problem with displaying previous QSO’s.

The "Previous QSOs" window shows only the qso logged before the update to the latest version 404.

ik3ogn GFranco


 

 


manual calling from bandmap

Matthias Bellmann
 

NEED HELP:

wsjt-bandmap ist running and shows any active call.

I (right) click on a wanted call, the call  is surrounded by a red box

According to the help-file my ft8 should send a message after the wanted
call ha finished the qso (73, RRR) or has called CQ. So i exspect.

BUT: The wanted statiion terminates its qso, the red box disappears, but
nmothing happend with my wsjtx.

There must be a step i have missed out or misunderstodd.

What must i do?


Re: LOTW Sent flag

Marvin Stern <marbern@...>
 

Thanks for the prompt reply Bob. I used the Export LOTW file routine, LOTW accepts it, but Logger does not flag the QSO as sent. I'll try the N2AMG routine next.
73's, Marv W2AOC 


Re: LOTW Sent flag

Marvin Stern <marbern@...>
 

Tnx for the reply Arturo. 73 Marv


Re: Previous QSO

Gianfranco
 

... I run "Recalculate statistic" and all 6 QSOs (3 and 3) are visible.

ik3ogn GFranco


Il 07/01/2020 14:14, Gianfranco via Groups.Io ha scritto:

OK Bob you are right and this also happens here.

Now I export 2 existing QSOs with the date 06 Jan, change the date of both in Jan 05 and again in Jan 07....Import the 4 new QSOs ...

In the Previous QSOs  window I only see the original 2 QSOs with the date Jan 06 and not the newones imported.
I hope to be clear.

ik3ogn GFranco


Il 07/01/2020 11:41, Bob ha scritto:
I can not duplicate this. I made a dummy QSO with IK3OGN. I see one IK3OGN QSO in the Logbook Page Window. I made a dummy ADIF file and imported a QSO with IK3OGN. I now see two IK3OGN QSOs in the Previous QSOs Window. I made another dummy QSO with IK3OGN. I now see three IK3OGN QSOs in the Previous QSOs Window. SeventyThree(s).
On January 7, 2020 at 1:21 AM "Gianfranco via Groups.Io" <tog-franco@...> wrote:

I apologize but I want to specify that only the imported QSOs do not appear in the "Previous QSOs" window.
They are shown regularly only
after the statistical recalculation.
For normal QSOs logged in via "DX Spot" everything is ok

ik3ogn GFranco

Il 07/01/2020 06:36, Gianfranco via Groups.Io ha scritto:


I have a problem with displaying previous QSO’s.

The "Previous QSOs" window shows only the qso logged before the update to the latest version 404.

ik3ogn GFranco


 


Re: Previous QSO

Gianfranco
 

OK Bob you are right and this also happens here.

Now I export 2 existing QSOs with the date 06 Jan, change the date of both in Jan 05 and again in Jan 07....Import the 4 new QSOs ...

In the Previous QSOs  window I only see the original 2 QSOs with the date Jan 06 and not the newones imported.
I hope to be clear.

ik3ogn GFranco


Il 07/01/2020 11:41, Bob ha scritto:
I can not duplicate this. I made a dummy QSO with IK3OGN. I see one IK3OGN QSO in the Logbook Page Window. I made a dummy ADIF file and imported a QSO with IK3OGN. I now see two IK3OGN QSOs in the Previous QSOs Window. I made another dummy QSO with IK3OGN. I now see three IK3OGN QSOs in the Previous QSOs Window. SeventyThree(s).
On January 7, 2020 at 1:21 AM "Gianfranco via Groups.Io" <tog-franco@...> wrote:

I apologize but I want to specify that only the imported QSOs do not appear in the "Previous QSOs" window.
They are shown regularly only
after the statistical recalculation.
For normal QSOs logged in via "DX Spot" everything is ok

ik3ogn GFranco

Il 07/01/2020 06:36, Gianfranco via Groups.Io ha scritto:


I have a problem with displaying previous QSO’s.

The "Previous QSOs" window shows only the qso logged before the update to the latest version 404.

ik3ogn GFranco


 


Re: Previous QSO

Bob
 

I can not duplicate this. I made a dummy QSO with IK3OGN. I see one IK3OGN QSO in the Logbook Page Window. I made a dummy ADIF file and imported a QSO with IK3OGN. I now see two IK3OGN QSOs in the Previous QSOs Window. I made another dummy QSO with IK3OGN. I now see three IK3OGN QSOs in the Previous QSOs Window. SeventyThree(s).

On January 7, 2020 at 1:21 AM "Gianfranco via Groups.Io" <tog-franco@...> wrote:

I apologize but I want to specify that only the imported QSOs do not appear in the "Previous QSOs" window.
They are shown regularly only
after the statistical recalculation.
For normal QSOs logged in via "DX Spot" everything is ok

ik3ogn GFranco

Il 07/01/2020 06:36, Gianfranco via Groups.Io ha scritto:


I have a problem with displaying previous QSO’s.

The "Previous QSOs" window shows only the qso logged before the update to the latest version 404.

ik3ogn GFranco


 


Re: Previous QSO

Gianfranco
 

I apologize but I want to specify that only the imported QSOs do not appear in the "Previous QSOs" window.
They are shown regularly only
after the statistical recalculation.
For normal QSOs logged in via "DX Spot" everything is ok

ik3ogn GFranco

Il 07/01/2020 06:36, Gianfranco via Groups.Io ha scritto:


I have a problem with displaying previous QSO’s.

The "Previous QSOs" window shows only the qso logged before the update to the latest version 404.

ik3ogn GFranco


Previous QSO

Gianfranco
 


I have a problem with displaying previous QSO’s.

The "Previous QSOs" window shows only the qso logged before the update to the latest version 404.

ik3ogn GFranco


Re: LOTW Sent flag

Arturo LU6ETB
 

If you wish to automatically flag your QSOs for QSLing, then this may be setup using the right click menu from the Logbook Entry window.

Setup -> QSLing & QSO Export -> Flag QSOs for LoTW

73 de Arturo, LU6ETB


Re: Logger32 RadioInfo UDP Broadcasts

Terry Glagowski / W1TR / AFA1DI
 

I would like to suggest that you make the periodic transmission more like 5 seconds or 10…

 

73, Terry / W1TR  :  )

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Monday, January 06, 2020 18:08
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 RadioInfo UDP Broadcasts

 

Too late for auto-update 3.50.404, it was released this morning. The next version (in a few weeks) will have this format

 

            '<?xml version="1.0" encoding="utf-8"?>
            '<app>Logger32</app>
            '<RadioInfo>
            '   <Freq>2120000</Freq> ' Note format is like 1420000
            '</RadioInfo>



and will broadcast the current frequency at least every 4 minutes - that way you can safely put your out-to-lunch timer at 5 minutes ... I'll add that tomorrow. SeventyThree(s).



SeventyThree(s).

On January 6, 2020 at 5:30 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:

Bob,

Thanks for creating a UDP broadcast in Logger32 so that other applications can piggyback off the Logger32 Rig Control…

The HFAUTO APP uses these UDP broadcasts to preset the ATU L/C Element Tuning Solution to track the TX VFO so that an AutoTune cycle is unnecessary.

 

There are now 3 applications that I know of which broadcast a <RadioInfo> UDP Packet in XML Document Format, each one a little different.

N1MM has the most comprehensive set of radio properties, including both a <Freq> and <TXFreq> element and <RadioNr>, <FocusRadioNr>,<ActiveRadioNr> elements, plus a few more.

DXLAB has these as well, but not a <FocusRadioNr>,<ActiveRadioNr>

If an APP works with multiple transceivers, it is important to indicate which one should be used as a TX VFO source to set the L/C Tuning Solution.

It cannot be jumping around from radio to radio since the HF-AUTO has continuously tunable L/C components, not relay switched ones.

 

The HFAUTO app can receive any number of UDP packets in XML Document format on any number of UDP ports for IPAddr=0.0.0.0.

It’s a good thing that all the APPs don’t send the exact same <RadioInfo> UDP packet because I could not then tell which APP is the source.

My preference would be that each application use a different XML Document Name…

The FLDIGI_UDP helper program uses XML Document  <FLDIGI>

OR… if there were an element in the <RadioInfo> packet that identified the APP, such as <APP>Logger32</APP>

 

Another thing that can be an issue is that Logger32 only broadcasts the <RadioInfo> UDP Packet when there is a change in frequency.

The HFAUTO APP uses a timeout to determine when CAT control has been lost due to a terminated application… this is adjustable in HFAUTO and can be shut off (CAT TMO=0)

It would be really great to have a UDP packet every few seconds (5, 10, 20 seconds) even if there is no change, to confirm that CAT control is still active.

N1MM does this, also DXLAB…  currently FLDIGI_UDP (my APP) does so every 200 ms whether there is a change or not, but maybe this is wasteful of bandwidth.

 

I’m not sure how Logger32 handles SPLIT operation, but the other APPs have both a <Freq> and <TXFreq> element in the UDP, the HFAUTO needs the <TXFreq>…

If one is not received, HFAUTO assumes <TXFreq> = <Freq> and transceiver mode without split is being used.

The HFAUTO APP does not make use of MODE information, but N1MM, DXLAB, and FLDIGI all have a <Mode> element.

Other APPs might need this information.

 

Kudos on using a decimal point to get the Hz digit… I always wondered why N1MM didn’t use a number in Hz instead of 10 Hz count!

Earlier radios did not use 1 Hz resolution, but good systems engineering would have predicted that they would someday!

 

73, and I appreciate your help!

 

Terry G. Glagowski, Ph.D. / W1TR

TGG Systems .
25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Home) .
(860) 617-1969 (Cell) .

(EMail) TGGsystems@ GMail.com .
(Web)  http://www.glagowski.org/TGG_Systems .

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Sunday, January 05, 2020 06:23
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 RadioInfo UDP Broadcasts

 

... and I don't have a radio with CAT control, but I simulated a VFO frequency change to 14001.234 kHz. This is broadcast:

 

<?xml version="1.0"?>
<RadioInfo>
<Freq>1400123.4</Freq>
</RadioInfo>

 

Simulated a frequency change to 14123 kHz. This is broadcast:

 

<?xml version="1.0"?>
<RadioInfo>
<Freq>1412300</Freq>
</RadioInfo>

 

SeventyThree(s)/

 

 

 

On January 5, 2020 at 5:48 AM Bob <k4cy@...> wrote:

... to setup/enable UDP Broadcast of frequency in Logger32, click SETUP | FREQUENCY and check the UDP Broadcast option. Period. That's it. No port setup, no nothing, just turn it on. SeventyThree(s).

On January 4, 2020 at 9:34 PM Bob <k4cy@...> wrote:

There's a section UDP Broadcast of DX Spots in the Logger32 Help file. SeventyThree(s).

On January 4, 2020 at 9:18 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:

Does anyone have info about UDP broadcasts from Logger32 to other APPs?

Just a topic name or location in the documentation would help.

 

Terry G. Glagowski / W1TR
HAM: W1TR / USAF MARS: AFA1DI / GRID: FN31vw / ELEV: 950 MSL / 41.924750 N, 72.190320 W.


25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Landline) .
(860) 617-1969 (Cell) .

(EMail) W1TR@... .
(Web)  http://www.Glagowski.org/Radio .

 


 


 


 

 

 


 


Re: Logger32 RadioInfo UDP Broadcasts

Bob
 

Too late for auto-update 3.50.404, it was released this morning. The next version (in a few weeks) will have this format

            '<?xml version="1.0" encoding="utf-8"?>
            '<app>Logger32</app>
            '<RadioInfo>
            '   <Freq>2120000</Freq> ' Note format is like 1420000
            '</RadioInfo>

and will broadcast the current frequency at least every 4 minutes - that way you can safely put your out-to-lunch timer at 5 minutes ... I'll add that tomorrow. SeventyThree(s).

SeventyThree(s).

On January 6, 2020 at 5:30 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:

Bob,

Thanks for creating a UDP broadcast in Logger32 so that other applications can piggyback off the Logger32 Rig Control…

The HFAUTO APP uses these UDP broadcasts to preset the ATU L/C Element Tuning Solution to track the TX VFO so that an AutoTune cycle is unnecessary.

 

There are now 3 applications that I know of which broadcast a <RadioInfo> UDP Packet in XML Document Format, each one a little different.

N1MM has the most comprehensive set of radio properties, including both a <Freq> and <TXFreq> element and <RadioNr>, <FocusRadioNr>,<ActiveRadioNr> elements, plus a few more.

DXLAB has these as well, but not a <FocusRadioNr>,<ActiveRadioNr>

If an APP works with multiple transceivers, it is important to indicate which one should be used as a TX VFO source to set the L/C Tuning Solution.

It cannot be jumping around from radio to radio since the HF-AUTO has continuously tunable L/C components, not relay switched ones.

 

The HFAUTO app can receive any number of UDP packets in XML Document format on any number of UDP ports for IPAddr=0.0.0.0.

It’s a good thing that all the APPs don’t send the exact same <RadioInfo> UDP packet because I could not then tell which APP is the source.

My preference would be that each application use a different XML Document Name…

The FLDIGI_UDP helper program uses XML Document  <FLDIGI>

OR… if there were an element in the <RadioInfo> packet that identified the APP, such as <APP>Logger32</APP>

 

Another thing that can be an issue is that Logger32 only broadcasts the <RadioInfo> UDP Packet when there is a change in frequency.

The HFAUTO APP uses a timeout to determine when CAT control has been lost due to a terminated application… this is adjustable in HFAUTO and can be shut off (CAT TMO=0)

It would be really great to have a UDP packet every few seconds (5, 10, 20 seconds) even if there is no change, to confirm that CAT control is still active.

N1MM does this, also DXLAB…  currently FLDIGI_UDP (my APP) does so every 200 ms whether there is a change or not, but maybe this is wasteful of bandwidth.

 

I’m not sure how Logger32 handles SPLIT operation, but the other APPs have both a <Freq> and <TXFreq> element in the UDP, the HFAUTO needs the <TXFreq>…

If one is not received, HFAUTO assumes <TXFreq> = <Freq> and transceiver mode without split is being used.

The HFAUTO APP does not make use of MODE information, but N1MM, DXLAB, and FLDIGI all have a <Mode> element.

Other APPs might need this information.

 

Kudos on using a decimal point to get the Hz digit… I always wondered why N1MM didn’t use a number in Hz instead of 10 Hz count!

Earlier radios did not use 1 Hz resolution, but good systems engineering would have predicted that they would someday!

 

73, and I appreciate your help!

 

Terry G. Glagowski, Ph.D. / W1TR

TGG Systems .
25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Home) .
(860) 617-1969 (Cell) .

(EMail) TGGsystems@ GMail.com .
(Web)  http://www.glagowski.org/TGG_Systems
.

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Sunday, January 05, 2020 06:23
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 RadioInfo UDP Broadcasts

 

... and I don't have a radio with CAT control, but I simulated a VFO frequency change to 14001.234 kHz. This is broadcast:

 

<?xml version="1.0"?>
<RadioInfo>
<Freq>1400123.4</Freq>
</RadioInfo>

 

Simulated a frequency change to 14123 kHz. This is broadcast:

 

<?xml version="1.0"?>
<RadioInfo>
<Freq>1412300</Freq>
</RadioInfo>

 

SeventyThree(s)/

 

 

 

On January 5, 2020 at 5:48 AM Bob <k4cy@...> wrote:

... to setup/enable UDP Broadcast of frequency in Logger32, click SETUP | FREQUENCY and check the UDP Broadcast option. Period. That's it. No port setup, no nothing, just turn it on. SeventyThree(s).

On January 4, 2020 at 9:34 PM Bob <k4cy@...> wrote:

There's a section UDP Broadcast of DX Spots in the Logger32 Help file. SeventyThree(s).

On January 4, 2020 at 9:18 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:

Does anyone have info about UDP broadcasts from Logger32 to other APPs?

Just a topic name or location in the documentation would help.

 

Terry G. Glagowski / W1TR
HAM: W1TR / USAF MARS: AFA1DI / GRID: FN31vw / ELEV: 950 MSL / 41.924750 N, 72.190320 W.


25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Landline) .
(860) 617-1969 (Cell) .

(EMail) W1TR@... .
(Web)  http://www.Glagowski.org/Radio .

 


 


 


 

 



 


Re: Logger32 RadioInfo UDP Broadcasts

Terry Glagowski / W1TR / AFA1DI
 

Bob,

Thanks for creating a UDP broadcast in Logger32 so that other applications can piggyback off the Logger32 Rig Control…

The HFAUTO APP uses these UDP broadcasts to preset the ATU L/C Element Tuning Solution to track the TX VFO so that an AutoTune cycle is unnecessary.

 

There are now 3 applications that I know of which broadcast a <RadioInfo> UDP Packet in XML Document Format, each one a little different.

N1MM has the most comprehensive set of radio properties, including both a <Freq> and <TXFreq> element and <RadioNr>, <FocusRadioNr>,<ActiveRadioNr> elements, plus a few more.

DXLAB has these as well, but not a <FocusRadioNr>,<ActiveRadioNr>

If an APP works with multiple transceivers, it is important to indicate which one should be used as a TX VFO source to set the L/C Tuning Solution.

It cannot be jumping around from radio to radio since the HF-AUTO has continuously tunable L/C components, not relay switched ones.

 

The HFAUTO app can receive any number of UDP packets in XML Document format on any number of UDP ports for IPAddr=0.0.0.0.

It’s a good thing that all the APPs don’t send the exact same <RadioInfo> UDP packet because I could not then tell which APP is the source.

My preference would be that each application use a different XML Document Name…

The FLDIGI_UDP helper program uses XML Document  <FLDIGI>

OR… if there were an element in the <RadioInfo> packet that identified the APP, such as <APP>Logger32</APP>

 

Another thing that can be an issue is that Logger32 only broadcasts the <RadioInfo> UDP Packet when there is a change in frequency.

The HFAUTO APP uses a timeout to determine when CAT control has been lost due to a terminated application… this is adjustable in HFAUTO and can be shut off (CAT TMO=0)

It would be really great to have a UDP packet every few seconds (5, 10, 20 seconds) even if there is no change, to confirm that CAT control is still active.

N1MM does this, also DXLAB…  currently FLDIGI_UDP (my APP) does so every 200 ms whether there is a change or not, but maybe this is wasteful of bandwidth.

 

I’m not sure how Logger32 handles SPLIT operation, but the other APPs have both a <Freq> and <TXFreq> element in the UDP, the HFAUTO needs the <TXFreq>…

If one is not received, HFAUTO assumes <TXFreq> = <Freq> and transceiver mode without split is being used.

The HFAUTO APP does not make use of MODE information, but N1MM, DXLAB, and FLDIGI all have a <Mode> element.

Other APPs might need this information.

 

Kudos on using a decimal point to get the Hz digit… I always wondered why N1MM didn’t use a number in Hz instead of 10 Hz count!

Earlier radios did not use 1 Hz resolution, but good systems engineering would have predicted that they would someday!

 

73, and I appreciate your help!

 

Terry G. Glagowski, Ph.D. / W1TR

TGG Systems .
25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Home) .
(860) 617-1969 (Cell) .

(EMail) TGGsystems@ GMail.com .
(Web)  http://www.glagowski.org/TGG_Systems
.

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Bob
Sent: Sunday, January 05, 2020 06:23
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32 RadioInfo UDP Broadcasts

 

... and I don't have a radio with CAT control, but I simulated a VFO frequency change to 14001.234 kHz. This is broadcast:

 

<?xml version="1.0"?>
<RadioInfo>
<Freq>1400123.4</Freq>
</RadioInfo>

 

Simulated a frequency change to 14123 kHz. This is broadcast:

 

<?xml version="1.0"?>
<RadioInfo>
<Freq>1412300</Freq>
</RadioInfo>

 

SeventyThree(s)/

 

 

 

On January 5, 2020 at 5:48 AM Bob <k4cy@...> wrote:

... to setup/enable UDP Broadcast of frequency in Logger32, click SETUP | FREQUENCY and check the UDP Broadcast option. Period. That's it. No port setup, no nothing, just turn it on. SeventyThree(s).

On January 4, 2020 at 9:34 PM Bob <k4cy@...> wrote:

There's a section UDP Broadcast of DX Spots in the Logger32 Help file. SeventyThree(s).

On January 4, 2020 at 9:18 PM Terry Glagowski / W1TR / AFA1DI <W1TR@...> wrote:

Does anyone have info about UDP broadcasts from Logger32 to other APPs?

Just a topic name or location in the documentation would help.

 

Terry G. Glagowski / W1TR
HAM: W1TR / USAF MARS: AFA1DI / GRID: FN31vw / ELEV: 950 MSL / 41.924750 N, 72.190320 W.


25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Landline) .
(860) 617-1969 (Cell) .

(EMail) W1TR@... .
(Web)  http://www.Glagowski.org/Radio .

 


 


 


 


Re: Previous QSO's Exclamation Mark - Cannot display

Bob
 

Can't stretch a child form height? Two options: 1) Push the mouse button harder, or 2) Click VIEW  and UNcheck the LOCK CHILD WINDOWS option. SeventyThree(s).

On January 6, 2020 at 4:17 PM "Anthony Buscaglia via Groups.Io" <tonybb@...> wrote:

I have a problem with displaying previous QSO’s.

Over 200k Q’s in the log.

I tried re-installing but still a problem.

Any advice appreciated.

Thanks
73
Tony
K2NV



 


Re: LOTW Sent flag

Bob
 

There is more than one way to send your QSOs to LoTW for verification. One way is to use the N2AMG application L32LogSync, another is to export an ADIF file (click FILE | EXPORT FILES | EXPORT LOTW FILE. How are you attempting it? SeventyThree(s).

On January 6, 2020 at 3:45 PM Marvin Stern <marbern@...> wrote:

After uplogging LOTW sent file to LOTW, It does not change sent flag to Y. HELP

 


Previous QSO's Exclamation Mark - Cannot display

Anthony Buscaglia
 

I have a problem with displaying previous QSO’s.

Over 200k Q’s in the log.

I tried re-installing but still a problem.

Any advice appreciated.

Thanks
73
Tony
K2NV



LOTW Sent flag

Marvin Stern <marbern@...>
 

After uplogging LOTW sent file to LOTW, It does not change sent flag to Y. HELP