Re: Strange Position Reports
On Mon, Jan 6, 2020 at 06:32 PM, James Ewen wrote:
There are no real mysteries in APRS, just answers that you have looked for yet.
?
So, the real problem is with the operators of BAMBAM and NICOLI, and YAAC is simply demonstrating the "Garbage In, Garbage Out" reality of computer technology. ? Which clears up my concerns about BAMBAM -- I routinely see it "co-located" on YAAC with my digipeater (WA2WA), which is about 130 miles away. ?I had wondered what the issue was. ?The operator (KI7RUS, from the status text) should add the lat/lon to his beacon and edit the WIDE1-1 setting. Thanks for that explanation. ? But I am puzzled about one matter concerning aprs.fi -- do you know if aprs.fi plots the position for BAMBAM using CWOP data? ?I ask because the FCC registered address for KI7RUS is in Vancouver, WA (no where near Goldendale). ?The CWOP database (http://wxqa.com/sss/search1.cgi?keyword=bambam) does have a lat/lon, which resolves to the same location shown on aprs.fi. 73, Jeff AL1Q?
|
Re: Strange Position Reports
There's a pretty good way to remove the mysteries of APRS...
Look at the packets being sent by a station and received by your station.
I can't see the packets being received by your station unless you show them to me, but I can look at what is being sent...
?
2020-01-06 18:32:15 MST:?>APTT4,WIDE1-1,WIDE2-2,qAR,:T#420,125,070,255,105,083,000010112020-01-06 18:37:18 MST:?>APTT4,WIDE1-1,WIDE2-2,qAR,:>KI7RUS-13?Cliffside?Launch?HP?WX
All BAMBAM is sending is status packets and telemetry...?
It's just a noise maker... there's an i-gate within simplex range that can gate the WX packets, and the 3 hop status messaging is just a waste of resources.
??
The position report that heard may have been heard years ago. stores information for a very long time. You can send your telemetry definitions once, and will keep them in memory for years.
Transient stations that come on every so often don't have that long term memory. BAMBAM is also very naughty, using a WIDE1-1 path, especially when it is located less than a mile from the JUNIPER digipeater. Why is it asking for assistance from a home fill-in digipeater to get heard by a main digipeater less than a mile away? Especially when there is evidence that ALAKES locates over 200 km away can hear BAMBAM direct?
NICOLI sends out positions reports via local only, and telemetry via a single hop.
??
2020-01-06 17:57:18 MST:?>APRS,WIDE2-1,qAR,:T#050,189,098,005,055,173,00000000
2020-01-06 18:06:24 MST:?>APRS,qAR,:!4605.21N/12327.31W#PHG2830W2,?ORn-N,?Fill-in?/?NA7Q?14.2V?76.2F??
YAAC is telling you that you heard the telemetry and/or status packets via the W7SRA digipeater, and with no location information, the best it can do is tell you that the W7SRA digipeater handled the packets.? NICOLI is operating in a much more network friendly manner than BAMBAM... it causes far less load on the system with conservative path settings. Most packets aren't going any further than onto the local airwaves.
??
Pretty tough to expect the computer to provide an accurate position for where the digipeaters are located with no position reports heard by your station.
There are no real mysteries in APRS, just answers that you have looked for yet.
On Sun, Jan 5, 2020 at 9:06 PM Michael WA7SKG < wa7skg@...> wrote: My station = WA7SKG in Dallas, OR
Digipeater = W7SRA about 20 miles SE of me, about 10 miles south of
Salem, OR
Digipeater = NICOLI about 90 miles NW of me near Westport,OR
Digipeater = BAMBAM about 130 miles NE of me near Goldendale, WA
(These digipeaters show up in their proper locations on )
The NICOLI and BAMBAM digipeaters routinely show up with gray icons with
red question marks in a small area about 2-3 miles radius of W7SRA
digipeater.
Michael WA7SKG
Andrew P. wrote on 1/5/20 6:30 PM:
> Hmmm... vicinity plotting can also work in the opposite direction to guesstimate the position of "stealth" digipeaters (those that do not transmit position reports of their own, and only meet their legal station identification regulations by UITRACE-inserting their callsign into digipeat paths). When a regular station's position report is digipeated by a "stealth" digipeater, YAAC attempts to approximate the position of the digipeater as being in the centroid of all the stations it has been heard to digipeat.
>
> How do you know these digipeater positions are incorrect? How are you checking this?
>
> Please provide some callsigns of the participating stations so others can help you interpret what is going on.
>
> Andrew, KA2DDO
> author of YAAC
> ________________________________________
> From: [email protected] <[email protected]> on behalf of Michael WA7SKG <wa7skg@...>
> Sent: Saturday, January 4, 2020 11:51 PM
> To: [email protected]
> Subject: Re: [yaac-users] Strange Position Reports
>
> Still confused. The two items I see most are digipeaters. They show up
> on my map near (varying in about a five mile radius) a local digi, but
> one is actually 90 miles away and the other is 130 miles away with
> significant terrain between them and the local digi. They are persistent
> in that they move around a little bit, but are shown for days at a time
> in the same area. I do have "vicinity plotting" turned off, yet they
> still show up. They never show up in their actual locations.
>
> I only have RF items on my map. Nothing from the Internet is displayed.
>
> Just another of those APRS mysteries I guess.
>
> Michael WA7SKG
>
>
> Andrew P. wrote on 1/4/20 6:47 PM:
>> The question mark icon is for stations with unknown positions. A station
>> that sends a status message, telemetry, or positionless weather report
>> first (as far as your station newly listening is concerned) means that
>> YAAC doesn't know where to plot it or what its symbol is. So YAAC
>> guesses the station's location by assuming it's near its first
>> digipeater (assuming the digipeater's position report has been heard).
>> This feature is called "vicinity plotting".
>>
>> Once YAAC hears an actual position report with an APRS symbol code from
>> the station, it will change the icon and move it to the correct location
>> on the map.
>>
>> While the station's actual position is not known, and either it wasn't
>> digipeated and heard by an I-Gate whose position isn't known, or
>> digipeated by a digipeater whose position isn't known, the position
>> remains at latitude/longitude (0,0). The button on the map toolbar with
>> a big 0 on it will jump the map to that location.
>>
>> Note that, if you don't like it, you can turn vicinity plotting off in
>> the expert-mode configuration dialog.
>>
>> Hope this helps.
>>
>> Andrew, KA2DDO
>> author of YAAC
>>
>>>
>> -------- Original message --------
>> From: Michael WA7SKG <wa7skg@...>
>> Date: 1/4/20 15:36 (GMT-05:00)
>> To: [email protected]
>> Subject: [yaac-users] Strange Position Reports
>>
>> I see periodic objects show up with the icon of a gray circle with a red
>> question mark. They are many miles from their actual location. Clicking
>> on the icon gives me a box of either seemingly garbage characters or
>> just a blank in the comments field. Many of these are fixed sites, so I
>> know the location is not correct. Some are mobile, but when I talk to
>> them later, they were never in the area.
>>
>> What's up with that?
>>
>> Michael WA7SKG
|
Per another user's bug report, I have found and fixed the issue with the mini-webserver, as of build#144 (05-Jan-2020).
However, due to the internal design of the graphics code in the Java runtime, you need to be running in graphical mode to be able to generate the map images on the webserver, as they are copied from the map display in the graphical UI of YAAC.
|
Let me know if you still have issues with the blacklist using build#144 (05-Jan-2020).
|
Re: next beta build#144 of YAAC, created 2020-Jan-05
Thank you Andrew!
toggle quoted message
Show quoted text
On 1/5/2020 8:59 PM, Andrew P. wrote: next beta build#144 of YAAC ("Yet Another APRS Client"), created 2020-Jan-05
downloadable from
or
changes and updates include:
1. properly generate standard APRS packets in locales where a comma is used
instead of a period as the numeric decimal point. also fix where
executing KML files or CSV files of lat/lon data.
2. fix null pointer exception when using GPSD with a non-moving station or
station that doesn't currently have a valid GPS fix.
3. shorten outgoing text message panel's text field for the message body
to cut down on field loss when someone shrinks the desktop window
too small (typically under 965 pixels in width of the map window,
depending on font choice).
4. fix ClassCastException accidentally introduced by a refactoring to
resolve a findbugs issue.
5. fix hang in mini-webserver caused by using buffered input in an
invalid context.
6. fix null pointer exception and HTTP server error in mini-webserver
when viewing the stations page on a system that is still rapidly
growing its station list.
7. fix incorrect map direction rotation in repeater finder plugin, and
handle fitting on small screens by using fullscreen mode and no
window title bar.
--
Michael Cozzi
cozzicon@...
kd8tut@...
269-519-2389
|
Small world :-)
According to the doc available at the link above, javaAPRSSrvr
supports linux kernel ax25 networking, so in theory it should be
able to share a serial port / TNC with another APRS app. Once a
serial port is configured to be an ax25 interface it can be shared
by any app that supports kernel ax25 networking.
I've never used javaAPRSSrvr, but I wouldn't expect an APRSIS
server to need to connect to a serial port at all - unless it was
doubling as an IGate.
73,
Lee K5DAT
Hi.
Unless the attached TNC is multi-threading, in respect to the
different clients connected to it via the single physical port,
you could get into bad trouble if one application changes the
configuration to suit it, but another application is confused by
the changes.
For pure RX only, probably not a problem, but if you have two
app's sending and receiving, hmmmm....
A KISS mode TNC is probably less troublesome than some, but
still not a good thing to do.
The same holds true when "sharing" a radio between data and
logging app's.? The fact that it can seem to work OK for many,
does not mean it is the correct way to do things.?? Put Hamlib or
Omnirig in the middle (for rig control) and it's much more
reliable, but you can still get into trouble if careless.
Regards.
??? Dave G8KBV
--
Created on and sent from a Unix like PC running and using free and open source software:
|
Re: Strange Position Reports
My station = WA7SKG in Dallas, OR
Digipeater = W7SRA about 20 miles SE of me, about 10 miles south of Salem, OR
Digipeater = NICOLI about 90 miles NW of me near Westport,OR
Digipeater = BAMBAM about 130 miles NE of me near Goldendale, WA
(These digipeaters show up in their proper locations on aprs.fi)
The NICOLI and BAMBAM digipeaters routinely show up with gray icons with red question marks in a small area about 2-3 miles radius of W7SRA digipeater.
Michael WA7SKG
Andrew P. wrote on 1/5/20 6:30 PM:
toggle quoted message
Show quoted text
Hmmm... vicinity plotting can also work in the opposite direction to guesstimate the position of "stealth" digipeaters (those that do not transmit position reports of their own, and only meet their legal station identification regulations by UITRACE-inserting their callsign into digipeat paths). When a regular station's position report is digipeated by a "stealth" digipeater, YAAC attempts to approximate the position of the digipeater as being in the centroid of all the stations it has been heard to digipeat.
How do you know these digipeater positions are incorrect? How are you checking this?
Please provide some callsigns of the participating stations so others can help you interpret what is going on.
Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Michael WA7SKG <wa7skg@...>
Sent: Saturday, January 4, 2020 11:51 PM
To: [email protected]
Subject: Re: [yaac-users] Strange Position Reports
Still confused. The two items I see most are digipeaters. They show up
on my map near (varying in about a five mile radius) a local digi, but
one is actually 90 miles away and the other is 130 miles away with
significant terrain between them and the local digi. They are persistent
in that they move around a little bit, but are shown for days at a time
in the same area. I do have "vicinity plotting" turned off, yet they
still show up. They never show up in their actual locations.
I only have RF items on my map. Nothing from the Internet is displayed.
Just another of those APRS mysteries I guess.
Michael WA7SKG
Andrew P. wrote on 1/4/20 6:47 PM:
The question mark icon is for stations with unknown positions. A station
that sends a status message, telemetry, or positionless weather report
first (as far as your station newly listening is concerned) means that
YAAC doesn't know where to plot it or what its symbol is. So YAAC
guesses the station's location by assuming it's near its first
digipeater (assuming the digipeater's position report has been heard).
This feature is called "vicinity plotting".
Once YAAC hears an actual position report with an APRS symbol code from
the station, it will change the icon and move it to the correct location
on the map.
While the station's actual position is not known, and either it wasn't
digipeated and heard by an I-Gate whose position isn't known, or
digipeated by a digipeater whose position isn't known, the position
remains at latitude/longitude (0,0). The button on the map toolbar with
a big 0 on it will jump the map to that location.
Note that, if you don't like it, you can turn vicinity plotting off in
the expert-mode configuration dialog.
Hope this helps.
Andrew, KA2DDO
author of YAAC
-------- Original message --------
From: Michael WA7SKG <wa7skg@...>
Date: 1/4/20 15:36 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Strange Position Reports
I see periodic objects show up with the icon of a gray circle with a red
question mark. They are many miles from their actual location. Clicking
on the icon gives me a box of either seemingly garbage characters or
just a blank in the comments field. Many of these are fixed sites, so I
know the location is not correct. Some are mobile, but when I talk to
them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
Re: Strange Position Reports
Hmmm... vicinity plotting can also work in the opposite direction to guesstimate the position of "stealth" digipeaters (those that do not transmit position reports of their own, and only meet their legal station identification regulations by UITRACE-inserting their callsign into digipeat paths). When a regular station's position report is digipeated by a "stealth" digipeater, YAAC attempts to approximate the position of the digipeater as being in the centroid of all the stations it has been heard to digipeat. How do you know these digipeater positions are incorrect? How are you checking this? Please provide some callsigns of the participating stations so others can help you interpret what is going on. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Michael WA7SKG <wa7skg@...> Sent: Saturday, January 4, 2020 11:51 PM To: [email protected]Subject: Re: [yaac-users] Strange Position Reports Still confused. The two items I see most are digipeaters. They show up on my map near (varying in about a five mile radius) a local digi, but one is actually 90 miles away and the other is 130 miles away with significant terrain between them and the local digi. They are persistent in that they move around a little bit, but are shown for days at a time in the same area. I do have "vicinity plotting" turned off, yet they still show up. They never show up in their actual locations. I only have RF items on my map. Nothing from the Internet is displayed. Just another of those APRS mysteries I guess. Michael WA7SKG Andrew P. wrote on 1/4/20 6:47 PM: The question mark icon is for stations with unknown positions. A station
that sends a status message, telemetry, or positionless weather report
first (as far as your station newly listening is concerned) means that
YAAC doesn't know where to plot it or what its symbol is. So YAAC
guesses the station's location by assuming it's near its first
digipeater (assuming the digipeater's position report has been heard).
This feature is called "vicinity plotting".
Once YAAC hears an actual position report with an APRS symbol code from
the station, it will change the icon and move it to the correct location
on the map.
While the station's actual position is not known, and either it wasn't
digipeated and heard by an I-Gate whose position isn't known, or
digipeated by a digipeater whose position isn't known, the position
remains at latitude/longitude (0,0). The button on the map toolbar with
a big 0 on it will jump the map to that location.
Note that, if you don't like it, you can turn vicinity plotting off in
the expert-mode configuration dialog.
Hope this helps.
Andrew, KA2DDO
author of YAAC
-------- Original message --------
From: Michael WA7SKG <wa7skg@...>
Date: 1/4/20 15:36 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Strange Position Reports
I see periodic objects show up with the icon of a gray circle with a red
question mark. They are many miles from their actual location. Clicking
on the icon gives me a box of either seemingly garbage characters or
just a blank in the comments field. Many of these are fixed sites, so I
know the location is not correct. Some are mobile, but when I talk to
them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
next beta build#144 of YAAC, created 2020-Jan-05
next beta build#144 of YAAC ("Yet Another APRS Client"), created 2020-Jan-05
downloadable from
or
changes and updates include:
1. properly generate standard APRS packets in locales where a comma is used
instead of a period as the numeric decimal point. also fix where
executing KML files or CSV files of lat/lon data.
2. fix null pointer exception when using GPSD with a non-moving station or
station that doesn't currently have a valid GPS fix.
3. shorten outgoing text message panel's text field for the message body
to cut down on field loss when someone shrinks the desktop window
too small (typically under 965 pixels in width of the map window,
depending on font choice).
4. fix ClassCastException accidentally introduced by a refactoring to
resolve a findbugs issue.
5. fix hang in mini-webserver caused by using buffered input in an
invalid context.
6. fix null pointer exception and HTTP server error in mini-webserver
when viewing the stations page on a system that is still rapidly
growing its station list.
7. fix incorrect map direction rotation in repeater finder plugin, and
handle fitting on small screens by using fullscreen mode and no
window title bar.
|
Looks like there's enough demand for access to the Linux native AX.25 stack for me to add support for it to YAAC.? ;-)
Another item on the to-do list....
Andrew, KA2DDO
author of YAAC
Sent from my Verizon 4G LTE smartphone
toggle quoted message
Show quoted text
-------- Original message --------
From: K5DAT <kilo5dat@...>
Date: 1/5/20 10:45 (GMT-05:00)
To: [email protected]
Subject: Re: [yaac-users] ax25 kiss tnc
Hi Ken,
Small world :-)
According to the doc available at the link above, javaAPRSSrvr supports linux kernel ax25 networking, so in theory it should be able to share a serial port / TNC with another APRS app. Once a serial port is configured to be an ax25 interface it can be
shared by any app that supports kernel ax25 networking.
I've never used javaAPRSSrvr, but I wouldn't expect an APRSIS server to need to connect to a serial port at all - unless it was doubling as an IGate.
73,
Lee K5DAT
On Sun, Jan 5, 2020 at 7:39 AM Ken G7VJA < ken@...> wrote:
Hi Lee
In all my year of running a javAPRSSrvr (formerly T2England) i have never heard of it sharing a serial port,
Question for Pete on the javAPRSSrvr io group.
73 Ken G7VJA
mb7ufo-js
|
Hi Ken,
Small world :-)
According to the doc available at the link above, javaAPRSSrvr supports linux kernel ax25 networking, so in theory it should be able to share a serial port / TNC with another APRS app. Once a serial port is configured to be an ax25 interface it can be shared by any app that supports kernel ax25 networking.
I've never used javaAPRSSrvr, but I wouldn't expect an APRSIS server to need to connect to a serial port at all - unless it was doubling as an IGate.
73, Lee K5DAT
On Sun, Jan 5, 2020 at 7:39 AM Ken G7VJA < ken@...> wrote: Hi Lee
In all my year of running a javAPRSSrvr (formerly T2England) i have never heard of it sharing a serial port,
Question for Pete on the javAPRSSrvr io group.
73 Ken G7VJA
mb7ufo-js
|
Hi Lee
In all my year of running a javAPRSSrvr (formerly T2England) i have never heard of it sharing a serial port,
Question for Pete on the javAPRSSrvr io group.
73 Ken G7VJA
mb7ufo-js
|
Re: Strange Position Reports
Still confused. The two items I see most are digipeaters. They show up on my map near (varying in about a five mile radius) a local digi, but one is actually 90 miles away and the other is 130 miles away with significant terrain between them and the local digi. They are persistent in that they move around a little bit, but are shown for days at a time in the same area. I do have "vicinity plotting" turned off, yet they still show up. They never show up in their actual locations.
I only have RF items on my map. Nothing from the Internet is displayed.
Just another of those APRS mysteries I guess.
Michael WA7SKG
Andrew P. wrote on 1/4/20 6:47 PM:
toggle quoted message
Show quoted text
The question mark icon is for stations with unknown positions. A station that sends a status message, telemetry, or positionless weather report first (as far as your station newly listening is concerned) means that YAAC doesn't know where to plot it or what its symbol is. So YAAC guesses the station's location by assuming it's near its first digipeater (assuming the digipeater's position report has been heard). This feature is called "vicinity plotting".
Once YAAC hears an actual position report with an APRS symbol code from the station, it will change the icon and move it to the correct location on the map.
While the station's actual position is not known, and either it wasn't digipeated and heard by an I-Gate whose position isn't known, or digipeated by a digipeater whose position isn't known, the position remains at latitude/longitude (0,0). The button on the map toolbar with a big 0 on it will jump the map to that location.
Note that, if you don't like it, you can turn vicinity plotting off in the expert-mode configuration dialog.
Hope this helps.
Andrew, KA2DDO
author of YAAC
-------- Original message --------
From: Michael WA7SKG <wa7skg@...>
Date: 1/4/20 15:36 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Strange Position Reports
I see periodic objects show up with the icon of a gray circle with a red
question mark. They are many miles from their actual location. Clicking
on the icon gives me a box of either seemingly garbage characters or
just a blank in the comments field. Many of these are fixed sites, so I
know the location is not correct. Some are mobile, but when I talk to
them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
Alas, this is a bug. It will be fixed in the next build of YAAC (to be released next week).
Andrew, KA2DDO
author of YAAC
toggle quoted message
Show quoted text
-------- Original message --------
From: "w5agm via Groups.Io" <w5agm@...>
Date: 1/2/20 17:04 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Blacklist
New YAAC user here, so pardon me if this is a repeat or common question.? In the blacklist function, I added a station to this list.? After adding the station, I am unable to delete the station from the list.? I've tried clicking on the callsign in the blacklist
as well as using arrows and tabs, but the "Delete Callsign" option always remains grayed out or unavailable.? I have shutdown, rebooted the pi and restarted YAAC with no changes.? I've also cleared all filters.? Any thoughts on how to remove a callsign from
the blacklist?? I'm running the 23-Dec-2019 version on a pi4 w/ buster.
Great software, Andrew!
Thanks in advance,
W5AGM
|
Hello
Jean-Pierre,
There is a program called ldsped that can connect to your ax25 interface and provide an AGWPE compatible interface that YAAC can use. Ldsped would share the serial port in this case with javaARPSSrvr at the ax25 layer.? Other apps like XASTIR support ax25 natively and can share the TNC as a result, but I expect ldsped to work with YAAC.
It's been a long time, but I once used Ldsped on a Raspberry Pi and was able to share the serial port with aprx on the Pi.? Other apps not on the Pi could also share the TNC via the home wifi network thanks to the AGW interface provided by ldsped.
73, Lee K5DAT
Note that you can't share the TNC between YAAC and javAPRSSrvr; only one program can own the serial port connected to the TNC.
Assuming you're going to have YAAC control the TNC, create a port of type Serial_TNC and specify the serial port device name connected to the TNC, your callsign-SSID, and the correct baud rate. You don't connect the TNC and YAAC to the Linux AX.25 kernel;
all the AX.25 logic is in YAAC so you don't use kissattach or /etc/axports.
If you want YAAC to forward the received packets to javAPRSSrvr, also create a port of type APRS-IS and connect it to your local javAPRSSrvr's client port.
Hope this helps.
Andrew, KA2DDO
author of YAAC
Sent from my Verizon 4G LTE smartphone
-------- Original message --------
From: Jean-Pierre Desilets < jeanpierredesilets@...>
Date: 1/4/20 12:56 (GMT-05:00)
To: ka2ddo@...
Subject: ax25 kiss tnc
Hi Andreew
i have? install YAAC on? my Ubuntu 18.04 machine running javAPRSSrvr??
and? ax25 tnc? in kiss? mode .
How to connect? this tnc to? YAAC? ?? ( In aprx? , interface is
ax25-device? ve2se-3? )
tnx de Jean-Pierre? ve2se
|
New YAAC user here, so pardon me if this is a repeat or common question.? In the blacklist function, I added a station to this list.? After adding the station, I am unable to delete the station from the list.? I've tried clicking on the callsign in the blacklist as well as using arrows and tabs, but the "Delete Callsign" option always remains grayed out or unavailable.? I have shutdown, rebooted the pi and restarted YAAC with no changes.? I've also cleared all filters.? Any thoughts on how to remove a callsign from the blacklist?? I'm running the 23-Dec-2019 version on a pi4 w/ buster.
Great software, Andrew!
Thanks in advance,
W5AGM
|
Re: Strange Position Reports
The question mark icon is for stations with unknown positions. A station that sends a status message, telemetry, or positionless weather report first (as far as your station newly listening is concerned) means that YAAC doesn't know where to plot it or
what its symbol is. So YAAC guesses the station's location by assuming it's near its first digipeater (assuming the digipeater's position report has been heard). This feature is called "vicinity plotting".
Once YAAC hears an actual position report with an APRS symbol code from the station, it will change the icon and move it to the correct location on the map.?
While the station's actual position is not known, and either it wasn't digipeated and heard by an I-Gate whose position isn't known, or digipeated by a digipeater whose position isn't known, the position remains at latitude/longitude (0,0). The button
on the map toolbar with a big 0 on it will jump the map to that location.
Note that, if you don't like it, you can turn vicinity plotting off in the expert-mode configuration dialog.?
Hope this helps.
Andrew, KA2DDO
author of YAAC
toggle quoted message
Show quoted text
-------- Original message --------
From: Michael WA7SKG <wa7skg@...>
Date: 1/4/20 15:36 (GMT-05:00)
To: [email protected]
Subject: [yaac-users] Strange Position Reports
I see periodic objects show up with the icon of a gray circle with a red
question mark. They are many miles from their actual location. Clicking
on the icon gives me a box of either seemingly garbage characters or
just a blank in the comments field. Many of these are fixed sites, so I
know the location is not correct. Some are mobile, but when I talk to
them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
I see periodic objects show up with the icon of a gray circle with a red question mark. They are many miles from their actual location. Clicking on the icon gives me a box of either seemingly garbage characters or just a blank in the comments field. Many of these are fixed sites, so I know the location is not correct. Some are mobile, but when I talk to them later, they were never in the area.
What's up with that?
Michael WA7SKG
|
Note that you can't share the TNC between YAAC and javAPRSSrvr; only one program can own the serial port connected to the TNC.
Assuming you're going to have YAAC control the TNC, create a port of type Serial_TNC and specify the serial port device name connected to the TNC, your callsign-SSID, and the correct baud rate. You don't connect the TNC and YAAC to the Linux AX.25 kernel;
all the AX.25 logic is in YAAC so you don't use kissattach or /etc/axports.
If you want YAAC to forward the received packets to javAPRSSrvr, also create a port of type APRS-IS and connect it to your local javAPRSSrvr's client port.
Hope this helps.
Andrew, KA2DDO
author of YAAC
Sent from my Verizon 4G LTE smartphone
toggle quoted message
Show quoted text
-------- Original message --------
From: Jean-Pierre Desilets <jeanpierredesilets@...>
Date: 1/4/20 12:56 (GMT-05:00)
To: ka2ddo@...
Subject: ax25 kiss tnc
Hi Andreew
i have? install YAAC on? my Ubuntu 18.04 machine running javAPRSSrvr??
and? ax25 tnc? in kiss? mode .
How to connect? this tnc to? YAAC? ?? ( In aprx? , interface is
ax25-device? ve2se-3? )
tnx de Jean-Pierre? ve2se
|
No, it's a code bug. YAAC is receiving the query from your browser, but the min-webserver thread is hanging instead of sending the reply. I have the fix for the next build. I hope to put the next build out this weekend, once I finish testing other bugfixes. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Paul Bramscher <pfbram@...> Sent: Thursday, January 2, 2020 7:39 PM To: [email protected]Subject: Re: [yaac-users] Mini-Webserver I'm not able to access the mini webserver either (Debian 10). I haven't tried in 1-2+ years, so I couldn't say when it became an issue on my system. Via 'netstat -tea' I see that tcp6 under port 8008 is set to LISTEN under my local (non-root) account, but I'm unable to access it. Some sort of permissions issue when running the server under an ordinary user? I have http (80) and https (443) running on that PC, but nothing on 8008. 73, KD0KZE / Paul On 12/27/2019 7:51 PM, Greg WB6ZSU wrote: Andrew...
I did a restart and didn't see anything in the startup messages or the
syslog related to an exception. I really don't see any errors. It's just
as if the web server isn't being enabled.
|
Jeff AL1Q
Michael WA7SKG