Date   

Re: DX Spots Map not displaying spots.

Mark Tetrault <mdtetrault@...>
 

Room L206
Cost a little over $1100, total. Each

On Sun, May 19, 2019, 8:45 AM David Leckie <djcleckie@...> wrote:
Hi

"Sometimes View DX causes a crash with a “Invalid Call to Procedure” message."
Currently I cannot reproduce the above crash it stopped happening when the DX spots started to appear.
Its all now working perfectly and I have made no changes at my end.
Puzzled but happy.
tnx es 73
Dave
GM4NFI


Re: DX Spots Map not displaying spots.

David Leckie
 

Hi

"Sometimes View DX causes a crash with a “Invalid Call to Procedure” message."
Currently I cannot reproduce the above crash it stopped happening when the DX spots started to appear.
Its all now working perfectly and I have made no changes at my end.
Puzzled but happy.
tnx es 73
Dave
GM4NFI


Re: 3.50.386 auto-update ...

Bob
 

Rich, draw your own conclusions. SeventyThree(s).


From the FT4_protocol.pdf document at https://www.physics.princeton.edu/pulsar/K1JT/wsjtx.html


Modulation uses 4-tone frequency-shift keying at approximately 23.4 baud, with tones separated by the baud rate


From the Brief Description of the FT8 Protocol at http://physics.princeton.edu/pulsar/k1jt/ft8.txt


The mode name "FT8" stands for "Franke and Taylor, 8-FSK modulation".

On May 19, 2019 at 8:25 AM "richard Quick via Groups.Io" <rich.w4rq@...> wrote:

FT4 is different than FT8, JT65 etc. thus the designation is different.
I’m no guru, but where FT8 switches frequencies, FT 4 sweeps from frequency to frequency. Someone else can describe it better than I, I’m sure. But they are different. 

Rich - W4RQ


 


 


Re: 3.50.386 auto-update ...

richard Quick <rich.w4rq@...>
 

FT4 is different than FT8, JT65 etc. thus the designation is different.
I’m no guru, but where FT8 switches frequencies, FT 4 sweeps from frequency to frequency. Someone else can describe it better than I, I’m sure. But they are different. 

Rich - W4RQ


Re: DX Spots Map not displaying spots.

Bob
 

Dave, the painting of DX Spots on the map is done at the lowest possible priority - When Logger32 has absolutely nothing better to do. When the PC is busy, it's not uncommon new DX Spots to not appear on the map for a second or three (but not an hour late).  Now, let's address the error you get with VIEW DX. Tell me how to duplicate this. SeventyThree(s).

On May 19, 2019 at 7:55 AM David Leckie <djcleckie@...> wrote:

Hi

Its showing "Show all DX Spots".

However after no spots appearing in an hour and me having made no changes I left it running over lunch and suddenly the spots have started to appear on the map.

Its working but I have no idea why it has started to work.

TNX fer advice
73
Dave
GM4NFI


Re: DX Spots Map not displaying spots.

David Leckie
 

I cleared the DX Spots window and the map cleared as expected.

Within a minute 3 new DX Spots appeared and these IMMEDIATELY appeared on the map with no delay.
No changes here working fine.
73
Dave
GM4NFI


Re: DX Spots Map not displaying spots.

David Leckie
 

Hi

Its showing "Show all DX Spots".

However after no spots appearing in an hour and me having made no changes I left it running over lunch and suddenly the spots have started to appear on the map.

Its working but I have no idea why it has started to work.

TNX fer advice
73
Dave
GM4NFI


Re: DX Spots Map not displaying spots.

Bob
 

Dave, select the DX SPOTS tab of the tracking Window. Right click on the map somewhere. Click the FILTER DX SPOTS ON MAP menu. What option have you selected? SeventyThree(s).

On May 19, 2019 at 7:18 AM David Leckie <djcleckie@...> wrote:

Running V3.50.385

Win10 Pro 64 bit.

Telnet connected to GB7UJS and logged in OK.

In the Telnet window the DX spots are scrolling along fine.  Tab is labelled GB7UJS

DX Spots window is active and displaying the data from the Telnet window correctly.

Its also scrolling away as the DX spots come in.

So far so good.

The problem is with the DX Spots map.

Setup DX Spots is setup exactly the same as in the Help File.

Now if I go to View>Show Tracking Window the window displays OK.

If I select DX Spots it says 0 stations in 0 countries.  After 1 hour still no spots shown.

If I select IOTA it gives 0 unique Iota stations.  Now there is an EA6 and an EA8 in the DX spots window.  These being IOTA only prefixes they should show in the IOTA window?

Show all DX spots is selected.

Persistence is set to 30 minutes.

Greyline seems fine - moving slowly west as time passes.

Satellite seems fine.

Sometimes View DX causes a crash with a “Invalid Call to Procedure” message.

In previous versions of logger32 I have had this working OK but I am unsure of exactly when the issue started.

I have read the help files and searched the groups.io site but cannot see any help.

As no one else  has posted this issue it must be something to do with my setup but what?

73

Dave

GM4NFI


Re: 3.50.386 auto-update ...

Barry GM4GIF
 

In total agreement with that one Bob. Now, where’s my fishing gear 👍

On Sun, 19 May 2019 at 11:37, Bob <k4cy@...> wrote:



Barry, another quotable quote for you. I am a great fan of Oscar Wilde, an while he is probably not the originator of the quote, I do my best to not take life seriously (especially where ham radio is concerned). SeventyThree(s).

On May 19, 2019 at 3:59 AM Barry Lyons <gm4gif@...> wrote:

Gary/Bob
We certainly do appreciate it, however we grownups leave the amusing comments to the ‘Chattering Classes’ hi
Keep quaffing the Grouse Bob, helps my pension pot !!!

73
Barry / gm4gif


On Sun, 19 May 2019 at 06:55, Gary Hinson < Gary@...> wrote:

😊

 

Thanks, Bob, for second-guessing the ADIF-meisters …. and, well, for everything really.

 

I wonder how many L32 users appreciate just how much painstaking work goes on behind the scenes to maintain and enhance the software, fix bugs, tweak stuff and all for free. 

 

You’re “awesome” as we Kiwis say.

73

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 19 May 2019 14:17
To: hamlogger@groups.io
Subject: [hamlogger] 3.50.386 auto-update ...

 

 

Johann was a wise man. In todays wired world, he may well have said "Life is too short to drink bad wine, or wait for ADIF to make public their decision as to what exactly FT4 is - a mode or submode". My buddy Julian Assange tells me it has been decreed that FT4 is a submode of MFSK. A closely held secret apparently. Pure speculation on my part, but I suggest they are reluctant to make any public proclamation as it would be a tacit acknowledgement that they screwed up big time when FT8 was given the much coveted mode status ... but wait, the subterfuge has just begun ... how will they undo all the other incorrectly assigned modes/submodes and maintain even a modicum of credibility? ... the spin doctors will be out in force ...

 

Based on the information provided by Julian (he hasn't let me down yet), I will preempt any formal announcement by ADIF, and release Logger32 v3.50.386 on Monday. SeventyThree(s).

 


 

 

--
Air 2

--
Air 2


Re: Secondary administration database column widths

David Leckie
 

Thanks for the suggestions yes its not a serious issue but I posted the comment just in case I had missed something simple.
I actually use this window quite a lot tracking "Worked all Britain" squares.  The 1st column is a 4 character reference.
73
Dave
GM4NFI


DX Spots Map not displaying spots.

David Leckie
 

Running V3.50.385

Win10 Pro 64 bit.

Telnet connected to GB7UJS and logged in OK.

In the Telnet window the DX spots are scrolling along fine.  Tab is labelled GB7UJS

DX Spots window is active and displaying the data from the Telnet window correctly.

Its also scrolling away as the DX spots come in.

So far so good.

The problem is with the DX Spots map.

Setup DX Spots is setup exactly the same as in the Help File.

Now if I go to View>Show Tracking Window the window displays OK.

If I select DX Spots it says 0 stations in 0 countries.  After 1 hour still no spots shown.

If I select IOTA it gives 0 unique Iota stations.  Now there is an EA6 and an EA8 in the DX spots window.  These being IOTA only prefixes they should show in the IOTA window?

Show all DX spots is selected.

Persistence is set to 30 minutes.

Greyline seems fine - moving slowly west as time passes.

Satellite seems fine.

Sometimes View DX causes a crash with a “Invalid Call to Procedure” message.

In previous versions of logger32 I have had this working OK but I am unsure of exactly when the issue started.

I have read the help files and searched the groups.io site but cannot see any help.

As no one else  has posted this issue it must be something to do with my setup but what?

73

Dave

GM4NFI


Re: Worked/Confirmed window: SAT qso not showing up?

Bob
 

Alessandro, As you can see by the layout of the Worked/Confirmed Window it is intended to show HF DXCC worked/confirmed statistics. I know nothing about DXCC, but it is my understanding the satellite QSOs do not count for HF DXCC. This is why they are not included in the Worked/Confirmed Window. SeventyThree(s).

On May 19, 2019 at 3:06 AM Alessandro I2SVA <i2sva@i2sva.it> wrote:


Correct Bob
This was also my understanding. When a QSO is marked SAT in prop mode it is excluded from country wkd/cfmd window BUT it is included in SAT DXCC stats and window. It looks a nonsense to me as I would expect the QSO being included also in Country wkd/cfmd window since:
- it is a real qso
- country wkd/cfmd does not shows any kind of filter
So why exclude the qso from this window?

Thanks 73



Alessandro Salvatico i2sva

Inviato da iPhone



Re: 3.50.386 auto-update ...

Bob
 



Barry, another quotable quote for you. I am a great fan of Oscar Wilde, an while he is probably not the originator of the quote, I do my best to not take life seriously (especially where ham radio is concerned). SeventyThree(s).

On May 19, 2019 at 3:59 AM Barry Lyons <gm4gif@...> wrote:

Gary/Bob
We certainly do appreciate it, however we grownups leave the amusing comments to the ‘Chattering Classes’ hi
Keep quaffing the Grouse Bob, helps my pension pot !!!

73
Barry / gm4gif


On Sun, 19 May 2019 at 06:55, Gary Hinson < Gary@...> wrote:

😊

 

Thanks, Bob, for second-guessing the ADIF-meisters …. and, well, for everything really.

 

I wonder how many L32 users appreciate just how much painstaking work goes on behind the scenes to maintain and enhance the software, fix bugs, tweak stuff and all for free. 

 

You’re “awesome” as we Kiwis say.

73

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 19 May 2019 14:17
To: hamlogger@groups.io
Subject: [hamlogger] 3.50.386 auto-update ...

 

 

Johann was a wise man. In todays wired world, he may well have said "Life is too short to drink bad wine, or wait for ADIF to make public their decision as to what exactly FT4 is - a mode or submode". My buddy Julian Assange tells me it has been decreed that FT4 is a submode of MFSK. A closely held secret apparently. Pure speculation on my part, but I suggest they are reluctant to make any public proclamation as it would be a tacit acknowledgement that they screwed up big time when FT8 was given the much coveted mode status ... but wait, the subterfuge has just begun ... how will they undo all the other incorrectly assigned modes/submodes and maintain even a modicum of credibility? ... the spin doctors will be out in force ...

 

Based on the information provided by Julian (he hasn't let me down yet), I will preempt any formal announcement by ADIF, and release Logger32 v3.50.386 on Monday. SeventyThree(s).

 


 

 

--
Air 2


Re: 3.50.386 auto-update ...

Ken McVie <kenmc@...>
 

Agree!!!

73
Ken ZL4NR

On 19/05/2019 5:55 PM, Gary Hinson wrote:

😊

 

Thanks, Bob, for second-guessing the ADIF-meisters …. and, well, for everything really.

 

I wonder how many L32 users appreciate just how much painstaking work goes on behind the scenes to maintain and enhance the software, fix bugs, tweak stuff and all for free. 

 

You’re “awesome” as we Kiwis say.

73

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 19 May 2019 14:17
To: hamlogger@groups.io
Subject: [hamlogger] 3.50.386 auto-update ...

 

 

Johann was a wise man. In todays wired world, he may well have said "Life is too short to drink bad wine, or wait for ADIF to make public their decision as to what exactly FT4 is - a mode or submode". My buddy Julian Assange tells me it has been decreed that FT4 is a submode of MFSK. A closely held secret apparently. Pure speculation on my part, but I suggest they are reluctant to make any public proclamation as it would be a tacit acknowledgement that they screwed up big time when FT8 was given the much coveted mode status ... but wait, the subterfuge has just begun ... how will they undo all the other incorrectly assigned modes/submodes and maintain even a modicum of credibility? ... the spin doctors will be out in force ...

 

Based on the information provided by Julian (he hasn't let me down yet), I will preempt any formal announcement by ADIF, and release Logger32 v3.50.386 on Monday. SeventyThree(s).



Re: 3.50.386 auto-update ...

Barry GM4GIF
 

Gary/Bob
We certainly do appreciate it, however we grownups leave the amusing comments to the ‘Chattering Classes’ hi
Keep quaffing the Grouse Bob, helps my pension pot !!!

73
Barry / gm4gif


On Sun, 19 May 2019 at 06:55, Gary Hinson <Gary@...> wrote:

😊

 

Thanks, Bob, for second-guessing the ADIF-meisters …. and, well, for everything really.

 

I wonder how many L32 users appreciate just how much painstaking work goes on behind the scenes to maintain and enhance the software, fix bugs, tweak stuff and all for free. 

 

You’re “awesome” as we Kiwis say.

73

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 19 May 2019 14:17
To: hamlogger@groups.io
Subject: [hamlogger] 3.50.386 auto-update ...

 

 

Johann was a wise man. In todays wired world, he may well have said "Life is too short to drink bad wine, or wait for ADIF to make public their decision as to what exactly FT4 is - a mode or submode". My buddy Julian Assange tells me it has been decreed that FT4 is a submode of MFSK. A closely held secret apparently. Pure speculation on my part, but I suggest they are reluctant to make any public proclamation as it would be a tacit acknowledgement that they screwed up big time when FT8 was given the much coveted mode status ... but wait, the subterfuge has just begun ... how will they undo all the other incorrectly assigned modes/submodes and maintain even a modicum of credibility? ... the spin doctors will be out in force ...

 

Based on the information provided by Julian (he hasn't let me down yet), I will preempt any formal announcement by ADIF, and release Logger32 v3.50.386 on Monday. SeventyThree(s).

--
Air 2


Re: Worked/Confirmed window: SAT qso not showing up?

Alessandro I2SVA
 

Correct Bob
This was also my understanding. When a QSO is marked SAT in prop mode it is excluded from country wkd/cfmd window BUT it is included in SAT DXCC stats and window. It looks a nonsense to me as I would expect the QSO being included also in Country wkd/cfmd window since:
- it is a real qso
- country wkd/cfmd does not shows any kind of filter
So why exclude the qso from this window?

Thanks 73



Alessandro Salvatico i2sva

Inviato da iPhone


Re: 3.50.386 auto-update ...

Gary Hinson
 

😊

 

Thanks, Bob, for second-guessing the ADIF-meisters …. and, well, for everything really.

 

I wonder how many L32 users appreciate just how much painstaking work goes on behind the scenes to maintain and enhance the software, fix bugs, tweak stuff and all for free. 

 

You’re “awesome” as we Kiwis say.

73

Gary  ZL2iFB

 

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 19 May 2019 14:17
To: hamlogger@groups.io
Subject: [hamlogger] 3.50.386 auto-update ...

 

 

Johann was a wise man. In todays wired world, he may well have said "Life is too short to drink bad wine, or wait for ADIF to make public their decision as to what exactly FT4 is - a mode or submode". My buddy Julian Assange tells me it has been decreed that FT4 is a submode of MFSK. A closely held secret apparently. Pure speculation on my part, but I suggest they are reluctant to make any public proclamation as it would be a tacit acknowledgement that they screwed up big time when FT8 was given the much coveted mode status ... but wait, the subterfuge has just begun ... how will they undo all the other incorrectly assigned modes/submodes and maintain even a modicum of credibility? ... the spin doctors will be out in force ...

 

Based on the information provided by Julian (he hasn't let me down yet), I will preempt any formal announcement by ADIF, and release Logger32 v3.50.386 on Monday. SeventyThree(s).


3.50.386 auto-update ...

Bob
 



Johann was a wise man. In todays wired world, he may well have said "Life is too short to drink bad wine, or wait for ADIF to make public their decision as to what exactly FT4 is - a mode or submode". My buddy Julian Assange tells me it has been decreed that FT4 is a submode of MFSK. A closely held secret apparently. Pure speculation on my part, but I suggest they are reluctant to make any public proclamation as it would be a tacit acknowledgement that they screwed up big time when FT8 was given the much coveted mode status ... but wait, the subterfuge has just begun ... how will they undo all the other incorrectly assigned modes/submodes and maintain even a modicum of credibility? ... the spin doctors will be out in force ...


Based on the information provided by Julian (he hasn't let me down yet), I will preempt any formal announcement by ADIF, and release Logger32 v3.50.386 on Monday. SeventyThree(s).


Re: Worked/Confirmed window: SAT qso not showing up?

on6ab
 

Hi Alessandro,

You're not doing anything wrong.
The confirmed/Worked window simply is not able to produce stats for Satellite QSO's only.

73,

Bruno


Re: Worked/Confirmed window: SAT qso not showing up?

Bob
 

... but the Worked Confirmed Window only has two axis - Band & Mode. SeventyThree(s).

On May 17, 2019 at 10:29 AM Guntram Summer <summer.guntram@...> wrote:

I think he means this:

B.13 Propagation Mode Enumeration

EnumerationDescription
ASAircraft Scatter
AUEAurora-E
AURAurora
BSBack scatter
ECHEchoLink
EMEEarth-Moon-Earth
ESSporadic E
F2F2 Reflection
FAIField Aligned Irregularities
INTERNETInternet-assisted
IONIonoscatter
IRLIRLP
MSMeteor scatter
RPTTerrestrial or atmospheric repeater or transponder
RSRain scatter
SATSatellite
TEPTrans-equatorial
TRTropospheric ducting


73, Guntram oe9dgv


Bob < k4cy@...> schrieb am Fr., 17. Mai 2019, 16:18:

Alessandro, apologies but I do not understand. The Worked/Confirmed Window has columns that show MODE (like: CW, SSB, DIGital, PHOne, etc.) and the rows are BAND (like: 20M, 30M, 40M, etc.). Is SAT a mode? See: http://www.adif.org/309/ADIF_309.htm#Mode_Enumeration for a list of ADIF modes.


SeventyThree(s).

On May 17, 2019 at 9:56 AM Alessandro I2SVA < i2sva@...> wrote:

Hi all, can anyone help with my issue, perhaps a missing configuration?
Using Logger 32 version 3.50.385 on Windows 10; all working well.
I have recently defined the 13 cm band for QO-100 satellite and I am now logging Satellite QSO without any problem; stats are enabled and I can see DXCC stats. The only issue is the Confirmed/Worked window that does not show any information is Prop mode is set to SAT. Why? How can I change this behavior?

Thanks, 73
Alessandro, I2SVA

 

 

9441 - 9460 of 85914