|
Here's the deal ... When Logger32 positions one of those little squares on a map in the Tracking Window it records everything it knows about the DX Spot so it does not have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields are immediately obvious. It starts with the callsign of the DX Station. Next is the frequency. then country information. Notice that each field is separated with a |. Real simple/easy for your PC to extract the information.
On the bottom line, you will see Localhost|-5.5625|-119.95833. This is the source of the DX Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX Spot where (for example) the originator is not K4CY-# but K4CY-|? The unexpected | in the string means that Logger32 extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the error need to do the detective work to identify where the unexpected | is coming from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
|
|
|
... another possible/likely source if the unexpected | is someone making a DX Spot comment like this "something | something else". I haven't been able to find a cluster that causes the problem. I'll have to reply on someone experiencing the problem identifying the source. SeventyThree(s).
On 12/02/2022 9:26 AM Bob <k4cy@...> wrote:
Here's the deal ... When Logger32 positions one of those little squares on a map in the Tracking Window it records everything it knows about the DX Spot so it does not have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields are immediately obvious. It starts with the callsign of the DX Station. Next is the frequency. then country information. Notice that each field is separated with a |. Real simple/easy for your PC to extract the information.
On the bottom line, you will see Localhost|-5.5625|-119.95833. This is the source of the DX Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX Spot where (for example) the originator is not K4CY-# but K4CY-|? The unexpected | in the string means that Logger32 extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the error need to do the detective work to identify where the unexpected | is coming from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
|
|
|
Jan
Bob
This is what I see
 
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's the deal ... When Logger32 positions
one of those little squares on a map in the Tracking Window it
records everything it knows about the DX Spot so it does not
have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click
on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields
are immediately obvious. It starts with the callsign of the DX
Station. Next is the frequency. then country information.
Notice that each field is separated with a |. Real simple/easy
for your PC to extract the information.
On the bottom line, you will see
Localhost|-5.5625|-119.95833. This is the source of the DX
Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX
Spot where (for example) the originator is not K4CY-# but
K4CY-|? The unexpected | in the string means that Logger32
extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the
error need to do the detective work to identify where the
unexpected | is coming from. Then hopefully I can make a quick
fix.
Or something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
Jan, if you are seeing DX Spot markers on the map, then the latitude/longitude were read correctly. What you need to do is wait for the error to occur then look at the last DX Spot received in the Telnet (or Localhost) window. Where is the extra/unwanted |? SeventyThree(s).
On 12/02/2022 9:58 AM Jan <hamlogger@...> wrote:
Bob
This is what I see
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's the deal ... When Logger32 positions one of those little squares on a map in the Tracking Window it records everything it knows about the DX Spot so it does not have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields are immediately obvious. It starts with the callsign of the DX Station. Next is the frequency. then country information. Notice that each field is separated with a |. Real simple/easy for your PC to extract the information.
On the bottom line, you will see Localhost|-5.5625|-119.95833. This is the source of the DX Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX Spot where (for example) the originator is not K4CY-# but K4CY-|? The unexpected | in the string means that Logger32 extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the error need to do the detective work to identify where the unexpected | is coming from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
Is it possible it could be this spot? 73,
Carey Magee, K2RNY
Rochester New York
Grid: FN13ef
On Fri, Dec 2, 2022 at 10:09 AM Bob < k4cy@...> wrote:
Jan, if you are seeing DX Spot markers on the map, then the latitude/longitude were read correctly. What you need to do is wait for the error to occur then look at the last DX Spot received in the Telnet (or Localhost) window. Where is the extra/unwanted |? SeventyThree(s).
Bob
This is what I see
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's the deal ... When Logger32 positions one of those little squares on a map in the Tracking Window it records everything it knows about the DX Spot so it does not have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields are immediately obvious. It starts with the callsign of the DX Station. Next is the frequency. then country information. Notice that each field is separated with a |. Real simple/easy for your PC to extract the information.
On the bottom line, you will see Localhost|-5.5625|-119.95833. This is the source of the DX Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX Spot where (for example) the originator is not K4CY-# but K4CY-|? The unexpected | in the string means that Logger32 extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the error need to do the detective work to identify where the unexpected | is coming from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
Jan, let me correct that ... I think the DX Spot marker is put on the Tracking window map before it is written to the Telnet/Localhost window. So, next time you get the error, click OK, then look at the Telnet/Localhost window for the offending DX Spot. Either way, look around for an extra | somewhere. SeventyThree(s)
On 12/02/2022 10:08 AM Bob <k4cy@...> wrote:
Jan, if you are seeing DX Spot markers on the map, then the latitude/longitude were read correctly. What you need to do is wait for the error to occur then look at the last DX Spot received in the Telnet (or Localhost) window. Where is the extra/unwanted |? SeventyThree(s).
On 12/02/2022 9:58 AM Jan <hamlogger@...> wrote:
Bob
This is what I see
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's the deal ... When Logger32 positions one of those little squares on a map in the Tracking Window it records everything it knows about the DX Spot so it does not have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields are immediately obvious. It starts with the callsign of the DX Station. Next is the frequency. then country information. Notice that each field is separated with a |. Real simple/easy for your PC to extract the information.
On the bottom line, you will see Localhost|-5.5625|-119.95833. This is the source of the DX Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX Spot where (for example) the originator is not K4CY-# but K4CY-|? The unexpected | in the string means that Logger32 extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the error need to do the detective work to identify where the unexpected | is coming from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
That's it. I'll filter out the |s from the comments field. I will send a test version to the Beta testers shortly, but it will be a day or three before I distribute an update. In the mean time maybe you can contact of DX Spot originator and ask him to cease an desist.
There is a bullshit filter that allows you to remove garbage from the comments field, but it only applies to what shows on the Telnet/Localhost window
SeventyThree(s).
On 12/02/2022 10:12 AM Carey Magee <arsk2rny@...> wrote:
Is it possible it could be this spot?
73,
Carey Magee, K2RNY
Rochester New York
Grid: FN13ef
On Fri, Dec 2, 2022 at 10:09 AM Bob < k4cy@...> wrote:
Jan, if you are seeing DX Spot markers on the map, then the latitude/longitude were read correctly. What you need to do is wait for the error to occur then look at the last DX Spot received in the Telnet (or Localhost) window. Where is the extra/unwanted |? SeventyThree(s).
Bob
This is what I see
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's the deal ... When Logger32 positions one of those little squares on a map in the Tracking Window it records everything it knows about the DX Spot so it does not have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields are immediately obvious. It starts with the callsign of the DX Station. Next is the frequency. then country information. Notice that each field is separated with a |. Real simple/easy for your PC to extract the information.
On the bottom line, you will see Localhost|-5.5625|-119.95833. This is the source of the DX Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX Spot where (for example) the originator is not K4CY-# but K4CY-|? The unexpected | in the string means that Logger32 extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the error need to do the detective work to identify where the unexpected | is coming from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
... or, you can simply temporarily block DX Spots from G3PXT-12. SeventyThree(s).
On 12/02/2022 10:21 AM Bob <k4cy@...> wrote:
That's it. I'll filter out the |s from the comments field. I will send a test version to the Beta testers shortly, but it will be a day or three before I distribute an update. In the mean time maybe you can contact of DX Spot originator and ask him to cease an desist.
There is a bullshit filter that allows you to remove garbage from the comments field, but it only applies to what shows on the Telnet/Localhost window
SeventyThree(s).
On 12/02/2022 10:12 AM Carey Magee <arsk2rny@...> wrote:
Is it possible it could be this spot?
73,
Carey Magee, K2RNY
Rochester New York
Grid: FN13ef
On Fri, Dec 2, 2022 at 10:09 AM Bob < k4cy@...> wrote:
Jan, if you are seeing DX Spot markers on the map, then the latitude/longitude were read correctly. What you need to do is wait for the error to occur then look at the last DX Spot received in the Telnet (or Localhost) window. Where is the extra/unwanted |? SeventyThree(s).
Bob
This is what I see
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's the deal ... When Logger32 positions one of those little squares on a map in the Tracking Window it records everything it knows about the DX Spot so it does not have to recalculate everything next time the DX Spot appears.
So, what information is stored. Right click on any DX Spot marker and you see a popup window like this:
Never mind what it all means but some fields are immediately obvious. It starts with the callsign of the DX Station. Next is the frequency. then country information. Notice that each field is separated with a |. Real simple/easy for your PC to extract the information.
On the bottom line, you will see Localhost|-5.5625|-119.95833. This is the source of the DX Spot, the Lat and Long of YC8ABD.
What happens if some bright spark makes a DX Spot where (for example) the originator is not K4CY-# but K4CY-|? The unexpected | in the string means that Logger32 extracts the word Localhost as the latitude. Not nice.
So, those who are experiencing the error need to do the detective work to identify where the unexpected | is coming from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
Jan
Jus saw the spot coming from G3PXT
also
I think for the time being I will block him
73
Jan
PA4JJ
Op 2-12-2022 om 16:36 schreef Bob:
... or, you
can simply temporarily block DX Spots from G3PXT-12. SeventyThree(s).
That's it. I'll filter out the
|s from the comments field. I will send a test version to
the Beta testers shortly, but it will be a day or three
before I distribute an update. In the mean time maybe you
can contact of DX Spot originator and ask him to cease an
desist.
There is a
bullshit filter that allows you to remove garbage from the
comments field, but it only applies to what shows on the
Telnet/Localhost window
SeventyThree(s).
Is it possible it
could be this spot?
73,
Carey Magee, K2RNY
Rochester New York
Grid: FN13ef
On Fri, Dec 2, 2022 at
10:09 AM Bob < k4cy@...>
wrote:
Jan,
if you are seeing DX Spot markers on the map, then
the latitude/longitude were read correctly. What
you need to do is wait for the error to occur then
look at the last DX Spot received in the Telnet
(or Localhost) window. Where is the extra/unwanted
|? SeventyThree(s).
Bob
This is what I see
 
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's
the deal ... When Logger32 positions one of
those little squares on a map in the Tracking
Window it records everything it knows about the
DX Spot so it does not have to recalculate
everything next time the DX Spot appears.
So,
what information is stored. Right click on any
DX Spot marker and you see a popup window like
this:
Never
mind what it all means but some fields are
immediately obvious. It starts with the callsign
of the DX Station. Next is the frequency. then
country information. Notice that each field is
separated with a |. Real simple/easy for your PC
to extract the information.
On
the bottom line, you will see
Localhost|-5.5625|-119.95833. This is the source
of the DX Spot, the Lat and Long of YC8ABD.
What
happens if some bright spark makes a DX Spot
where (for example) the originator is not K4CY-#
but K4CY-|? The unexpected | in
the string means that Logger32 extracts the word
Localhost as the latitude. Not nice.
So,
those who are experiencing the error need to do
the detective work to identify where the
unexpected | is coming from. Then hopefully I
can make a quick fix.
Or
something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
Jan
Op 2-12-2022 om 16:42 schreef Jan:
Jus saw the spot coming from
G3PXT also
I think for the time being I will block him
73
Jan
PA4JJ
Op 2-12-2022 om 16:36 schreef Bob:
... or,
you can simply temporarily block DX Spots from G3PXT-12. SeventyThree(s).
That's it. I'll filter out
the |s from the comments field. I will send a test version
to the Beta testers shortly, but it will be a day or three
before I distribute an update. In the mean time maybe you
can contact of DX Spot originator and ask him to cease an
desist.
There
is a bullshit filter that allows you to remove garbage
from the comments field, but it only applies to what shows
on the Telnet/Localhost window
SeventyThree(s).
Is it possible it
could be this spot?
73,
Carey Magee, K2RNY
Rochester New York
Grid: FN13ef
On Fri, Dec 2, 2022 at
10:09 AM Bob < k4cy@...>
wrote:
Jan,
if you are seeing DX Spot markers on the map,
then the latitude/longitude were read correctly.
What you need to do is wait for the error to
occur then look at the last DX Spot received in
the Telnet (or Localhost) window. Where is the
extra/unwanted |? SeventyThree(s).
Bob
This is what I see
 
73 Jan
PA4JJ
Op 2-12-2022 om 15:26 schreef Bob:
Here's the deal ... When Logger32
positions one of those little squares on a map
in the Tracking Window it records everything
it knows about the DX Spot so it does not have
to recalculate everything next time the DX
Spot appears.
So, what information is stored. Right
click on any DX Spot marker and you see a
popup window like this:
Never mind what it all means but some
fields are immediately obvious. It starts with
the callsign of the DX Station. Next is the
frequency. then country information. Notice
that each field is separated with a |. Real
simple/easy for your PC to extract the
information.
On the bottom line, you will see
Localhost|-5.5625|-119.95833. This is the
source of the DX Spot, the Lat and Long of
YC8ABD.
What happens if some bright spark makes
a DX Spot where (for example) the originator
is not K4CY-# but K4CY-|? The unexpected | in the string means
that Logger32 extracts the word Localhost as
the latitude. Not nice.
So, those who are experiencing the
error need to do the detective work to
identify where the unexpected | is coming
from. Then hopefully I can make a quick fix.
Or something like this, SeventyThree(s).
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
--
73
Jan
PA4JJ
______________________________________________________
My dxspider clusters running 24/7 on a raspberry pi 2
pa4jj-2 telnet 77.174.195.163 port 7300
pa4jj-3 telnet 77.174.195.163 port 7388
|
|
|
