Date   

Re: Anyone using a TNC and have it working?

Lynn Deffenbaugh
 

Looks like I need to bump up the priority of supporting the UI-View command files for KISS and TEXT mode Interfaces, huh? It'll dovetail nicely with the effort of generalizing the interfaces in order to support multiple channels through AGW.

Lynn (D) - KJ4ERJ

M1ARF wrote:

See below.



I did realize though, that my TNC is apparently not
communicating with the program. When I enable on the RF
side, I see nothing at all. I'm running text mode, so maybe
I will try KISS to see if that does it. Since I never was
able to get UI-View to run on Win7 either, I'm not sure how
this will turn out. I hope I can solve this problem, because
I want to use APRSIS32 all the time. I guess I will have to
hook the TNC up to the old machine to get it into KISS mode,
and then try it. This com port issue has been aggravating.

Kenny

Hi Kenny,

I had the same problem, put the TNC into KISS mode first then connect with APRSIS32.
Likewise use the setup string from UI-Veiw to put the TNC into host mode then use TEXT mode in APRSIS32.

Good luck,

Derek M1ARF


Re: Anyone using a TNC and have it working?

M1ARF <m1arf@...>
 

See below.


I did realize though, that my TNC is apparently not
communicating with the program. When I enable on the RF
side, I see nothing at all. I'm running text mode, so maybe
I will try KISS to see if that does it. Since I never was
able to get UI-View to run on Win7 either, I'm not sure how
this will turn out. I hope I can solve this problem, because
I want to use APRSIS32 all the time. I guess I will have to
hook the TNC up to the old machine to get it into KISS mode,
and then try it. This com port issue has been aggravating.

Kenny

Hi Kenny,

I had the same problem, put the TNC into KISS mode first then connect with APRSIS32.
Likewise use the setup string from UI-Veiw to put the TNC into host mode then use TEXT mode in APRSIS32.

Good luck,

Derek M1ARF


Re: Minor details.

James Ewen
 

On Tue, Mar 2, 2010 at 10:30 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

I remember that now!  Cycle map doesn't zoom very close
Hmm, you can zoom in as close as Mapnik... I don't have tiles rendered
right down to the full zoom in my area. Cycle Map renders tiles as
requested by the users. If no one has asked for the tiles, you'll zoom
in, and see blanks, but give it a bit, and the tiles will be rendered.

and is rather
boring in Florida.  The hazards of where I live!
Well, not much I can do about that. Even in my area, there's not a lot
of interesting appeal, but there are areas where I would like to have
the topo information as part of the map. I'd rather have the Cycle Map
as the tiles for use in RadioMobile, as RadioMobile is all about 3D
propagation modelling.

James
VE6SRV


Re: Top left rectangle

James Ewen
 

On Tue, Mar 2, 2010 at 9:59 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

A side line of my APRS work is analyzing and visualizing nationwide APRS
traffic.  Sometimes it can be hard to tell the difference between an
alias in a path and a station using some sort of tactical callsign.
Especially up in the NorthWest.
Hey, that's close to home... What paths could be confused with a
tactical callsign?

British Columbia uses BCn-N, Alberta uses ABn-N, Washington uses
WAn-N, Idaho uses IDn-N, Oregon uses ORn-N, Montana uses MTn-N.
Tactical callsign look like EVNBRG, WHTCRT, EDMNTN, PIGEON, ROCKYD,
HRYHIL, and ANTLER. Regular WIDEn-N paths are pretty easy to pick out.

Tactical callsigns make it much easier to visualize where the packets
have traveled as the tactical callsigns are chosen to represent the
area that digipeater is located. When I see WHTCRT,EVNBRG in the path
portion, I know it has come from Whitecourt through Evansburg to me.
Much easier to decode than trying to figure out where VE6PP and VE6YER
are located.

James
VE6SRV


Re: Minor details.

Lynn Deffenbaugh
 

I remember that now! Cycle map doesn't zoom very close and is rather boring in Florida. The hazards of where I live!

Lynn (D) - KJ4ERJ

James Ewen wrote:

On Tue, Mar 2, 2010 at 9:09 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:


What is their license like and do you have a URL? Are they on-line
available for on-demand download? If the URL is compatible with the
Slippy Map server, you could try just changing the proper settings in
the XML and see what happens!
I dunno... I just play with this stuff! I can't keep up with
downloading the latest version of APRSISCE! My employer seems to think
that I should be working during the day.

Go to www.openstreetmap.org, and click on the little blue + on the
right side of the map screen. Click on CycleMap under data layers, and
you'll see the result. Other people might like the Osmarender version
of the map.

James
VE6SRV


Re: Minor details.

James Ewen
 

On Tue, Mar 2, 2010 at 9:09 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

What is their license like and do you have a URL?  Are they on-line
available for on-demand download?  If the URL is compatible with the
Slippy Map server, you could try just changing the proper settings in
the XML and see what happens!
I dunno... I just play with this stuff! I can't keep up with
downloading the latest version of APRSISCE! My employer seems to think
that I should be working during the day.

Go to www.openstreetmap.org, and click on the little blue + on the
right side of the map screen. Click on CycleMap under data layers, and
you'll see the result. Other people might like the Osmarender version
of the map.

James
VE6SRV


Re: Self awareness feature request for /32

James Ewen
 

On Tue, Mar 2, 2010 at 9:07 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

That's the intent of the Red Dot.  Have you all read
http://aprsisce.wikidot.com/red-dot?
No... never even knew there was a Red Dot...

I need to get some time at home instead of on the road all the time. I
also need to try running the program with a GPS and TNC attached. Hmm,
I need to find time to get the latest version... I think I'm back 43
versions already!

I'll think about what you all are asking, but currently I believe the
red dot is sufficient.
Probably... sound like you have a circle of ambiguity, whereas dead
reckoning uses the last known heading to create an arc of ambiguity.
Because large deviations from the last heading will cause a new
position report, you wouldn't assume that the station can possibly be
too far left or right of the current projected path, and most
certainly not behind.

I really need to play more to see exactly what this program can do...
I've pulled back the curtain and had a peek... I need to throw it open
and have a really good look one day.

James
VE6SRV


Re: Anyone using a TNC and have it working?

Lynn Deffenbaugh
 

"Local" is within 2 used hops, regardless of the n in the WIDEn-N. I considered looking at that, but is a WIDE2* 2 used hops or 1? There's no way to know if it started as WIDE2-2 or WIDE2-1. So I just count the used hops and call 2 the limit. Eventually that'll be configurable by RF port.

"Recent" is heard via some RF port within the last 30 minutes. Again, that'll eventually be configurable.

Lynn (D) - KJ4ERJ

James Ewen wrote:

On Tue, Mar 2, 2010 at 12:25 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:


Local shows just those that the client considers "Local", and Direct
shows those heard with no used path components.
What defines local? Within a specific number of hops? Or just anything
heard via RF?

James
VE6SRV


Re: Anyone using a TNC and have it working?

James Ewen
 

On Tue, Mar 2, 2010 at 12:25 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

Local shows just those that the client considers "Local", and Direct
shows those heard with no used path components.
What defines local? Within a specific number of hops? Or just anything
heard via RF?

James
VE6SRV


Re: Top left rectangle

Lynn Deffenbaugh
 

That much I knew and had already read that reference before. What I was looking for was some list of what areas actually implemented it and what they uses.

A side line of my APRS work is analyzing and visualizing nationwide APRS traffic. Sometimes it can be hard to tell the difference between an alias in a path and a station using some sort of tactical callsign. Especially up in the NorthWest.

Check out my plots at:

http://tinyurl.com/APRSAct24

and

http://tinyurl.com/APRSAct00

Lynn (D) - KJ4ERJ

Tim Cunningham wrote:

Finding a definitive standard for SSn-N might prove challenging. It could be virtually anything any digi owner wants to specify that meets the WIDEn-N or SSSSSn-N UIFLOOD format.

Details on SSn-N can be found buried in http://www.aprs.org/fix14439.html

I once got a definition from Bob and updated the UIDIGI settings at:

http://www.qsl.net/n8deu/uidigi_eprom_settings.htm

The original basic intent was where SS represents the two letter designator of your state or SSS or longer ARRL section.

73's,
Tim - N8DEU




---- "Lynn W. Deffenbaugh" <kj4erj@arrl.net> wrote:
I'm not going to get into the political war of what's a "valid" path and what's not. I'm still trying to find a list of the SSn-N "standards".

Lynn (D) - KJ4ERJ

Fred Hillhouse wrote:

How about a color for those stations running a bogus path? Like RELAY or WIDE 3-3?
Best regards,
Fred

------------------------------------------------------------------------
*From:* aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com]
*On Behalf Of *Lynn W. Deffenbaugh
*Sent:* Tuesday, March 02, 2010 14:54
*To:* aprsisce@yahoogroups.com
*Subject:* Re: [aprsisce] Re: Top left rectangle


kb0npw wrote:
> Hmmm, I'm assuming the Win32 version is the same. If so, then
maybe I don't have my TNC communicating with the software. I don't
see any stations with an asterisk. I see many different colors
used in the listing, but no asterisk. If I just disable the
APRS-IS will that allow me to see RF only through my TNC?
>

Yes, if you disable APRS-IS, the only stations that should scroll by
will have come from one of the RF interfaces. If you do that and
nothing shows up, please turn on Enables / Debug Logging, close the
client, restart it, let it run for a while, close the client and then
e-mail the APRSIS32.LOG file to KJ4ERJ@arrl.net
<mailto:KJ4ERJ%40arrl.net>. Note that this will be
overwritten if you restart the client, so make sure you get a copy
before that.

The colors of the stations indicate how far they are from the
center of
the screen. Red is really close, Green is far away, Black has no
coordinate. Reverse video is used for callsigns in your filter
string.
Yellow background are other APRSISCE/32 stations. Pink background is
"invalid" stations that are either duplicated or too fast or
something
like that.

Lynn (D) - KJ4ERJ

> Thanks,
>
> Kenny
>
>
> --- In aprsisce@yahoogroups.com
<mailto:aprsisce%40yahoogroups.com>, "Lynn W. Deffenbaugh"
<kj4erj@...> wrote:
>
>> franmargue wrote:
>>
>>> With AGWpe enabled, I understand that '*' after a callsign
means that it was heard via a digi, and the number after that "*"
the number of digis.
>>> Am I correct?
>>>
>>>
>> Almost. The * after the callsign means it was heard over an RF
>> interface (AGW, KISS, or TEXT). The number after the *
indicates how
>> many copies of the same packet were heard, independent of path or
>> interface. In other words, if you hear the packet direct and
from 2
>> digis, it will be *3. I've got a ToDo list item (in my head if
not on
>> the list) to add a window to see the actual raw traffic on the
various
>> interfaces.
>>
>>
>>> But, when the callsign has more then 1 digit in the SSID, the
rectangle is not wide enough, and you cann't see all the information.
>>> How can you wide the rectangle?
>>>
>>>
>> If you download the latest release from last night
(2010/03/01), the
>> scrolling station list widens itself to fit the *n. I noticed
the issue
>> yesterday and corrected it.
>>
>>
>>> Thanks
>>>
>>>
>> You're welcome. Good timing on the request!
>>
>> Lynn (D) - KJ4ERJ
>>
>>
>>> (Francisco Guerra - CT1AKV)
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>





------------------------------------

Yahoo! Groups Links





Re: Up and running

Stan Leeds <srkleeds@...>
 

Darn....

Thats TEXT file...

Stan/KC7EHJ


Stan Leeds wrote:


Lynn,

So far looking great.

My plan is to get hooked up to a TNC and GPS.

I have a KPC-3 and a T2-135, but I can't see about getting it into KISS
mode. I did read in the TEST file about adding the type of support as
in UI-View.

Stan/KC7EHJ
-13


Up and running

Stan Leeds <srkleeds@...>
 

Lynn,

So far looking great.

My plan is to get hooked up to a TNC and GPS.

I have a KPC-3 and a T2-135, but I can't see about getting it into KISS mode. I did read in the TEST file about adding the type of support as in UI-View.

Stan/KC7EHJ
-13


Re: Top left rectangle

Tim Cunningham <tim_cunningham@...>
 

Finding a definitive standard for SSn-N might prove challenging. It could be virtually anything any digi owner wants to specify that meets the WIDEn-N or SSSSSn-N UIFLOOD format.

Details on SSn-N can be found buried in http://www.aprs.org/fix14439.html

I once got a definition from Bob and updated the UIDIGI settings at:

http://www.qsl.net/n8deu/uidigi_eprom_settings.htm

The original basic intent was where SS represents the two letter designator of your state or SSS or longer ARRL section.


73's,
Tim - N8DEU




---- "Lynn W. Deffenbaugh" <kj4erj@arrl.net> wrote:

I'm not going to get into the political war of what's a "valid" path and
what's not. I'm still trying to find a list of the SSn-N "standards".

Lynn (D) - KJ4ERJ

Fred Hillhouse wrote:


How about a color for those stations running a bogus path? Like RELAY
or WIDE 3-3?

Best regards,
Fred

------------------------------------------------------------------------
*From:* aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com]
*On Behalf Of *Lynn W. Deffenbaugh
*Sent:* Tuesday, March 02, 2010 14:54
*To:* aprsisce@yahoogroups.com
*Subject:* Re: [aprsisce] Re: Top left rectangle



kb0npw wrote:
> Hmmm, I'm assuming the Win32 version is the same. If so, then
maybe I don't have my TNC communicating with the software. I don't
see any stations with an asterisk. I see many different colors
used in the listing, but no asterisk. If I just disable the
APRS-IS will that allow me to see RF only through my TNC?
>

Yes, if you disable APRS-IS, the only stations that should scroll by
will have come from one of the RF interfaces. If you do that and
nothing shows up, please turn on Enables / Debug Logging, close the
client, restart it, let it run for a while, close the client and then
e-mail the APRSIS32.LOG file to KJ4ERJ@arrl.net
<mailto:KJ4ERJ%40arrl.net>. Note that this will be
overwritten if you restart the client, so make sure you get a copy
before that.

The colors of the stations indicate how far they are from the
center of
the screen. Red is really close, Green is far away, Black has no
coordinate. Reverse video is used for callsigns in your filter
string.
Yellow background are other APRSISCE/32 stations. Pink background is
"invalid" stations that are either duplicated or too fast or
something
like that.

Lynn (D) - KJ4ERJ

> Thanks,
>
> Kenny
>
>
> --- In aprsisce@yahoogroups.com
<mailto:aprsisce%40yahoogroups.com>, "Lynn W. Deffenbaugh"
<kj4erj@...> wrote:
>
>> franmargue wrote:
>>
>>> With AGWpe enabled, I understand that '*' after a callsign
means that it was heard via a digi, and the number after that "*"
the number of digis.
>>> Am I correct?
>>>
>>>
>> Almost. The * after the callsign means it was heard over an RF
>> interface (AGW, KISS, or TEXT). The number after the *
indicates how
>> many copies of the same packet were heard, independent of path or
>> interface. In other words, if you hear the packet direct and
from 2
>> digis, it will be *3. I've got a ToDo list item (in my head if
not on
>> the list) to add a window to see the actual raw traffic on the
various
>> interfaces.
>>
>>
>>> But, when the callsign has more then 1 digit in the SSID, the
rectangle is not wide enough, and you cann't see all the information.
>>> How can you wide the rectangle?
>>>
>>>
>> If you download the latest release from last night
(2010/03/01), the
>> scrolling station list widens itself to fit the *n. I noticed
the issue
>> yesterday and corrected it.
>>
>>
>>> Thanks
>>>
>>>
>> You're welcome. Good timing on the request!
>>
>> Lynn (D) - KJ4ERJ
>>
>>
>>> (Francisco Guerra - CT1AKV)
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>





Re: Symbols in left pane

Tim Cunningham <tim_cunningham@...>
 

See http://www.aprs-is.net/wx/ for more detail on the NWS weather message format.

73's,
Tim - N8DEU



---- "Lynn W. Deffenbaugh" <kj4erj@arrl.net> wrote:

I suspect they're either Objects or ....strategic isn't the right
word....callsigns that are supposed to mean something to someone, like
FBALL or LEADER or some-such.

SEQFLW seems to be related to a flood warning message injector of some kind.

http://aprs.fi/?c=raw&call=SEQFLW

The scrolling station list should always show the fromCall of the
packet, but if you click on one, the popup menu should show the object
name under which the station will be displayed on the map. It gets even
more confusing with 3rd party packets, but I won't complicate matters
with those just yet.

Lynn (D) - KJ4ERJ

james_jolin wrote:
Lynn,
I'm curious as to what the "stations" are with the plus (+) symbol. They also have odd call signs like SEQFLW.
Jim wa9arb


Re: Minor details.

Lynn Deffenbaugh
 

What is their license like and do you have a URL? Are they on-line available for on-demand download? If the URL is compatible with the Slippy Map server, you could try just changing the proper settings in the XML and see what happens!

Lynn (D) - KJ4ERJ

James Ewen wrote:

On Tue, Mar 2, 2010 at 12:43 PM, Fred Hillhouse <fmhillhouse@comcast.net> wrote:


I am curious what tiles others have that might be 256x256.
I would like to use the Cyclemap tiles rather than Mapnik... you get
topomaps from Cyclemap.

James
VE6SRV


------------------------------------

Yahoo! Groups Links





Re: Self awareness feature request for /32

Lynn Deffenbaugh
 

That's the intent of the Red Dot. Have you all read http://aprsisce.wikidot.com/red-dot?

The red dot and the circle interact to show how far off and in which direction an outside observer would think you are relative to where your GPS KNOWS you are. When the red dot hits the circle (Configure / Genius / Forecast Error), a new beacon is made provided it has been at least Min Time since the last one.

I'll think about what you all are asking, but currently I believe the red dot is sufficient.

Also, if you want to know if you've been digi'd, just watch the station list to see your callsign show up with a * beside it. If there's a *N, you actually heard N copies of your last position report over RF (just a * means 1).

Lynn (D) - KJ4ERJ

James Ewen wrote:

On Tue, Mar 2, 2010 at 7:49 AM, Fred Hillhouse <fmhillhouse@comcast.net> wrote:


An arrow that rotates with direction would be cool! Another thought, a
dot with a line extending in the direction of travel is useful. Extending
to half the distance of the range ring might be reasonable length.
What about a diverging area of ambiguity from the last beaconed
location? Dead reckoning from the last known location, using the last
reported speed and heading gives you a growing triangular area of
uncertainty of where the station might be.

Most clients display the last reported position, and call it good.
Xastir will try dead reckon the possible location of the station.
Watching dead reckoning in action is pretty sweet, especially when the
station in question is using SmartBeaconing, which reports changes in
heading and velocity.

If you want to make a good APRS client, it needs to do dead reckoning.
Having dead reckoning displayed against your last reported position
would be pretty interesting, watching how your true location and
possible location relate.

James
VE6SRV


------------------------------------

Yahoo! Groups Links





Re: Minor details.

James Ewen
 

On Tue, Mar 2, 2010 at 12:43 PM, Fred Hillhouse <fmhillhouse@comcast.net> wrote:

I am curious what tiles others have that might be 256x256.
I would like to use the Cyclemap tiles rather than Mapnik... you get
topomaps from Cyclemap.

James
VE6SRV


Re: Self awareness feature request for /32

James Ewen
 

On Tue, Mar 2, 2010 at 7:49 AM, Fred Hillhouse <fmhillhouse@comcast.net> wrote:

An arrow that rotates with direction would be cool! Another thought, a
dot with a line extending in the direction of travel is useful. Extending
to half the distance of the range ring might be reasonable length.
What about a diverging area of ambiguity from the last beaconed
location? Dead reckoning from the last known location, using the last
reported speed and heading gives you a growing triangular area of
uncertainty of where the station might be.

Most clients display the last reported position, and call it good.
Xastir will try dead reckon the possible location of the station.
Watching dead reckoning in action is pretty sweet, especially when the
station in question is using SmartBeaconing, which reports changes in
heading and velocity.

If you want to make a good APRS client, it needs to do dead reckoning.
Having dead reckoning displayed against your last reported position
would be pretty interesting, watching how your true location and
possible location relate.

James
VE6SRV


Re: Symbols in left pane

Lynn Deffenbaugh
 

TACTICAL! They're Tactical callsigns. Amazing how re-reading your own post will trigger the memory of the word you couldn't think of earlier!

Lynn W. Deffenbaugh wrote:

I suspect they're either Objects or ....strategic isn't the right word....callsigns that are supposed to mean something to someone, like FBALL or LEADER or some-such.

SEQFLW seems to be related to a flood warning message injector of some kind.

http://aprs.fi/?c=raw&call=SEQFLW

The scrolling station list should always show the fromCall of the packet, but if you click on one, the popup menu should show the object name under which the station will be displayed on the map. It gets even more confusing with 3rd party packets, but I won't complicate matters with those just yet.

Lynn (D) - KJ4ERJ

james_jolin wrote:

Lynn,
I'm curious as to what the "stations" are with the plus (+) symbol. They also have odd call signs like SEQFLW. Jim wa9arb


Re: A Question on Locked Tracking and Track Lines

Lynn Deffenbaugh
 

Currently there's no provision for decaying the track lines. In fact, on the Mobile platform, I don't even timestamp the various points. On Win32, I've got the advantage of MoRAM, so I do buffer the timestamps. Right now I've got 3.589MB of track space over 91,872 allocated points on my full-feed instance of APRSIS32 (KJ4ERJ-AL). To clear that, just click Clear Track, or double-click the Odometer if you're running a GPS.

I'll add it to the list and it will probably get done about the same time as the feature to save any station's accumulated track as a GPX file. Of course, the time to retain the track will be configurable, but I'll probably default it to something like 24 hours or so.

Lynn (D) - KJ4ERJ

Gary Sanders wrote:

Is there a provision to decay the track line from the display after some period of time? For example, erase the oldest line segment of a given track after 30 minutes (or some programmable amount of time).

Or, if tracking all those track points would get out of hand, just do it like uiview and display the last "X" number of segments (or positions, in the case of uiview).

I'm thinking of putting aprsisce32 on my home server, running continuously in Locked Tracking mode. I need the track lines, but for a frequently repeated route, the tracks would continuously overwrite.

I currently use uiview32 this way, and the decaying of the previous positions works well for this application.

Gary Sanders
WB0BZR


------------------------------------

Yahoo! Groups Links