Date   

Re: TM-D710 support

Lynn Deffenbaugh
 

James,

Nice writeup and capture of the D710 data. Now, if someone could provide an indefinite loan of a TM-D710 that I could use for testing my implementation? ;)

No, I'll see what I can do about having an interleaved GPS/TEXT mode port. Do you know if the D710 will transmit any packets that I supply? I'm suspecting not since it's in CMD mode. And I assume that if I change it to KISS, the GPS data quits coming out. Maybe I'll call it a D7x0 port...

As for relaying a reconstructed $GPRMC out another port, I'll have to think on that one. In the UI-View function, did it ignore incoming data on that port or do something with it. And how did the data get into the other programs? Were you running one of the virtual serial port drivers that provided a loop-back?

Lynn (D) - KJ4ERJ

James Ewen wrote:

Lynn,

I have finally found some time to sit and contemplate, while sitting
in my truck with the AvMap G5 and Kenwood TM-D710 staring at me.

I pulled out my interface cable, and slapped it into the D710 control
head. I have the D710 configured to spit out copies of the APRS
information received through the com port. Using Teraterm, I captured
a few packets...

The D710 forwards the current GPS information out the port constantly,
but in a $PKWDPOS string rather than the usual RMC, GGA, or GLL
strings.

I believe this is how it breaks down...


$PKWDPOS,185227,A,4142.9135,N,08743.6903,W,0.0,295,160208,163.9*10

185227 : time 6:52:27 PM

A : Valid Satellite fix

4142.9135 : 41 degrees 42.9135 minutes

N : North

08743.6903 : 87 degrees 43.6903 minutes

W : West

0.0 : 0 knots

295 : heading WNW

160208 : 16th February, 2008

163.9 : Altitude (metres)

*10 : Checksum
Interleaved into the GPS data is the actual APRS data...

Below is a capture of some data while I sat still. I had my D7 send a
couple packets to show the APRS data interleaved. After an APRS packet
is displayed, the cmd: prompt pops up.


$PKWDPOS,170006,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1E
$PKWDPOS,170008,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*10
$PKWDPOS,170011,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*18
$PKWDPOS,170013,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1A
$PKWDPOS,170015,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1C
VE6SRV-7>UVTVSW,WIDE1-1,WIDE2-2:''5 l [/>

$PKWDPOS,170017,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1E

cmd:$PKWDPOS,170018,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*11
$PKWDPOS,170021,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1B
$PKWDPOS,170023,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*19
VE6SRV-7>UVTVSW,WIDE1-1,WIDE2-2:''5 l [/>


cmd:$PKWDPOS,170025,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1F
$PKWDPOS,170027,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1D
$PKWDPOS,170028,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*12


I also had to enable incoming CR+LF in Teraterm to get the display to
scroll. I would guess that the lines only end in <CR>, with no <LF>
character.

If APRSISCE could digest the $PKWDPOS GPS data, I could run the
program hanging off the D710's com port, and use it as an alternate
supplementary display without needing to disable the APRS software in
the D710, and run in KISS mode. What do you think about supporting
that mode? Kai on the D710 forum has some in depth knowledge of the
communications out the back of the D710 control head.

Also, another thing that UI-View could do that was handy, was to strip
the GPS information out of the incoming mixed GPS/APRS streams from
the Kenwoods, and send pseudo GPS strings out another port. I would
daisy chain UI-View into other programs such as Net Stumbler, or
RadioMobile. These programs both want location information internally,
and being able to daisy chain them onto UI-View was great, as I got to
use both UI-View and the other program concurrently, sharing the GPS
data being passed through the D710. I believe UI-View recreated the
$GPRMC string from the data available.

James
VE6SRV


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

Yahoo! Groups Links





Phone home

Eric Söderman
 

Hi,

I found these messeages: http://aprs.fi/?c=message&call=KJ4ERJ&limit=50


I was just curious to know what they mean. I understand that my client
reports it´s version and position to KJ4ERJ in some way which then
sends it over APRS to KJ4ERJ-12.

Lynn, what can you tell more about this behavior? :-)

BR

Eric SA5BKE


Re: Possible issue with Locked Tracking

Lynn Deffenbaugh
 

Bummer, I believe you caught one condition I didn't test for! I'll see about getting that fixed before I take my "spring break". Thanks for catching (and reporting) it! Problems that are reported with the steps necessary to reproduce are easy to fix. It's reports like "it did something strange" that are difficult (like the white map screens that I finally fixed in today's release).

Lynn (D) - KJ4ERJ

Gary Sanders wrote:

Lynn, there seems to be a small issue with Locked Tracking on aprsisce32.

When you start the program and it was previously in the locked mode, it will display "Awaiting WB0ABC-2" as is should.

If the program is shut down before receiving the station, (in other words, while still displaying "Awaiting WB0ABC-2"), when it is subsequently restarted the bottom of the circle displays "Panning", and will not begin to track the station when a position is received.

The menu item Screen | Tracking | Locked is still checked.

I have aprsisce32 installed on 2 machines, and the same behavior is seen on both.

Gary Sanders
WB0BZR


Re: Minor details.

Lynn Deffenbaugh
 

Fred Hillhouse wrote:
Assuming your map engine is reusable, whether you use the Mapnik tiles or Cycle Map tiles or Osmarender it should be transparent except for storage space. By allowing the user the option they can make the decision whether there is too much clutter or not and whether or not there is not enough tiles. I myself would use the Cycle Maps immediately.
Agreed. See the definitions of "immediately" below!

In two packages I have run, when a tile is not available or there is a server error, they fill it in with a homemade tile that might be just a X from corner to corner. Or they just leave the space blank. Then when the user re-visits the area when running a separate instance, it tries for the tile again. In the case of APRSCIS32, you use an adjacent zoom tile. I suspect that would be fine.
I'm anxious to hear how expanding the Cycle Map tiles turns out looking. When I played with the alternate renderings from OSM, I didn't have that feature implemented. I still want to force-load the 0, 1, or 2 zoom level just to make sure I HAVE a cached tile for expansion. More scaling work will be occurring when I get to the UI-View map support.

Again, in the other map packages, there are key sequences to switch between map sources. And, whatever map type was up at shutdown is what is used again at startup.
You can play with this today, if you'd like. Just save a copy of your XML file and edit the following entries: (See also: http://aprsisce.wikidot.com/editing-xml-configuration)

<OSM.Server>tile.openstreetmap.org</OSM.Server>
<OSM.Port>80</OSM.Port>
<OSM.URLPrefix>/</OSM.URLPrefix>

The program connects to the OSM.Port on the OSM.Server and does an HTTP GET operation on the OSM.URLPrefix for the slippy-map-standard (http://wiki.openstreetmap.org/wiki/Slippy_map_tilenames#Tiles) named tile (/zoom/x/y.png). As you can see in that table,

http://tile.openstreetmap.org/12/2047/1362.png
http://tah.openstreetmap.org/Tiles/tile/12/2047/1362.png
http://andy.sandbox.cloudmade.com/tiles/cycle/12/2047/1362.png

These are all the same tile in different renderings. APRSISCE/32's default configuration builds the first URL as you can see by my values above. Any URL without a :port would use the standard 80 for a web server.

Over time, I suspect more topo maps will become available. I don't know how to request rendering of tiles yet. I have been looking but not been successful.
Until you arrive at a plan, I will be patient, like a kid in a candy store. ;)
I just opened Pandora's jar for you, let us know if it really works! Maybe I'll add a ToDo to support multiple map configurations and a Map cascading menu to switch between them....Hmmm....

Enjoy you time with the kids! Mine isn't coming home for break. :( She is the one in Arkansas.
Will do, I stepped down from volunteering at a FIRST Regional Robotics competition to be available while they're here. I'm certain we'll be having some fun together.

Lynn (D) - KJ4ERJ

Best regards,
Fred

------------------------------------------------------------------------
*From:* aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com]
*On Behalf Of *Lynn W. Deffenbaugh
*Sent:* Wednesday, March 03, 2010 10:17
*To:* aprsisce@yahoogroups.com
*Subject:* Re: [aprsisce] Re: Minor details.


Just play around with the SlippyMap browser at
http://www.openstreetmap.org/ <http://www.openstreetmap.org/> with
Cycle Map selected on the upper right
corner and you'll see why I don't have that as a publicized
option. WAY
too many chunks of the country that simply disappear into white tiles
when you zoom in. Just SW of Winston Salem in the Carolinas as
well as
the East Coast of Florida just don't seem to exist at the lower
levels
of Cycle Map.

I also discounted Osmarender due to the density of "stuff" on the
map.
The APRS stations just got lost in the clutter.

I'll see about providing configuration assistance to switch the tile
server and URLs to these various options, but I'll be keeping
Mapnik as
the default option.

Lynn (D) - KJ4ERJ

Fred Hillhouse 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.
>
> Do they get rendered on the fly or is it done through some sort of
> communication?
>
> This would be a sweet option! That would be my default. There is
> something about contours that are just plain attractive.
>
> > > 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.
>
> When I lived in Utah I bought every 7min map of the Moab area and
> several other areas I visited. I have a large collection of paper.


TM-D710 support

James Ewen
 

Lynn,

I have finally found some time to sit and contemplate, while sitting
in my truck with the AvMap G5 and Kenwood TM-D710 staring at me.

I pulled out my interface cable, and slapped it into the D710 control
head. I have the D710 configured to spit out copies of the APRS
information received through the com port. Using Teraterm, I captured
a few packets...

The D710 forwards the current GPS information out the port constantly,
but in a $PKWDPOS string rather than the usual RMC, GGA, or GLL
strings.

I believe this is how it breaks down...

$PKWDPOS,185227,A,4142.9135,N,08743.6903,W,0.0,295,160208,163.9*10

185227 : time 6:52:27 PM

A : Valid Satellite fix

4142.9135 : 41 degrees 42.9135 minutes

N : North

08743.6903 : 87 degrees 43.6903 minutes

W : West

0.0 : 0 knots

295 : heading WNW

160208 : 16th February, 2008

163.9 : Altitude (metres)

*10 : Checksum
Interleaved into the GPS data is the actual APRS data...

Below is a capture of some data while I sat still. I had my D7 send a
couple packets to show the APRS data interleaved. After an APRS packet
is displayed, the cmd: prompt pops up.


$PKWDPOS,170006,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1E
$PKWDPOS,170008,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*10
$PKWDPOS,170011,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*18
$PKWDPOS,170013,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1A
$PKWDPOS,170015,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1C
VE6SRV-7>UVTVSW,WIDE1-1,WIDE2-2:''5 l [/>

$PKWDPOS,170017,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1E

cmd:$PKWDPOS,170018,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*11
$PKWDPOS,170021,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1B
$PKWDPOS,170023,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*19
VE6SRV-7>UVTVSW,WIDE1-1,WIDE2-2:''5 l [/>


cmd:$PKWDPOS,170025,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1F
$PKWDPOS,170027,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*1D
$PKWDPOS,170028,A,5646.372,N,11125.042,W,000.0,174,040310,246.1*12


I also had to enable incoming CR+LF in Teraterm to get the display to
scroll. I would guess that the lines only end in <CR>, with no <LF>
character.

If APRSISCE could digest the $PKWDPOS GPS data, I could run the
program hanging off the D710's com port, and use it as an alternate
supplementary display without needing to disable the APRS software in
the D710, and run in KISS mode. What do you think about supporting
that mode? Kai on the D710 forum has some in depth knowledge of the
communications out the back of the D710 control head.

Also, another thing that UI-View could do that was handy, was to strip
the GPS information out of the incoming mixed GPS/APRS streams from
the Kenwoods, and send pseudo GPS strings out another port. I would
daisy chain UI-View into other programs such as Net Stumbler, or
RadioMobile. These programs both want location information internally,
and being able to daisy chain them onto UI-View was great, as I got to
use both UI-View and the other program concurrently, sharing the GPS
data being passed through the D710. I believe UI-View recreated the
$GPRMC string from the data available.

James
VE6SRV


Possible issue with Locked Tracking

Gary Sanders
 

Lynn, there seems to be a small issue with Locked Tracking on aprsisce32.

When you start the program and it was previously in the locked mode, it will display "Awaiting WB0ABC-2" as is should.

If the program is shut down before receiving the station, (in other words, while still displaying "Awaiting WB0ABC-2"), when it is subsequently restarted the bottom of the circle displays "Panning", and will not begin to track the station when a position is received.

The menu item Screen | Tracking | Locked is still checked.

I have aprsisce32 installed on 2 machines, and the same behavior is seen on both.

Gary Sanders
WB0BZR


Re: Minor details.

Fred Hillhouse
 

Hi Lynn,
 
Assuming your map engine is reusable, whether you use the Mapnik tiles or Cycle Map tiles or Osmarender it should be transparent except for storage space. By allowing the user the option they can make the decision whether there is too much clutter or not and whether or not there is not enough tiles. I myself would use the Cycle Maps immediately.
 
In two packages I have run, when a tile is not available or there is a server error, they fill it in with a homemade tile that might be just a X from corner to corner. Or they just leave the space blank. Then when the user re-visits the area when running a separate instance, it tries for the tile again. In the case of APRSCIS32, you use an adjacent zoom tile. I suspect that would be fine.
 
Again, in the other map packages, there are key sequences to switch between map sources. And, whatever map type was up at shutdown is what is used again at startup.
 
Over time, I suspect more topo maps will become available. I don't know how to request rendering of tiles yet. I have been looking but not been successful.
 
Until you arrive at a plan, I will be patient, like a kid in a candy store. ;)
 
Enjoy you time with the kids! Mine isn't coming home for break. :( She is the one in Arkansas.
 
Best regards,
Fred
 
 
 


From: aprsisce@... [mailto:aprsisce@...] On Behalf Of Lynn W. Deffenbaugh
Sent: Wednesday, March 03, 2010 10:17
To: aprsisce@...
Subject: Re: [aprsisce] Re: Minor details.

 

Just play around with the SlippyMap browser at
http://www.openstreetmap.org/ with Cycle Map selected on the upper right
corner and you'll see why I don't have that as a publicized option. WAY
too many chunks of the country that simply disappear into white tiles
when you zoom in. Just SW of Winston Salem in the Carolinas as well as
the East Coast of Florida just don't seem to exist at the lower levels
of Cycle Map.

I also discounted Osmarender due to the density of "stuff" on the map.
The APRS stations just got lost in the clutter.

I'll see about providing configuration assistance to switch the tile
server and URLs to these various options, but I'll be keeping Mapnik as
the default option.

Lynn (D) - KJ4ERJ

Fred Hillhouse 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.
>
> Do they get rendered on the fly or is it done through some sort of
> communication?
>
> This would be a sweet option! That would be my default. There is
> something about contours that are just plain attractive.
>
> > > 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.
>
> When I lived in Utah I bought every 7min map of the Moab area and
> several other areas I visited. I have a large collection of paper.
>
>
>


Re: One more cool thing

kb0npw <kenny@...>
 

Lynn, thanks so much for all the hard work. I left UI-View for this and don't plan on looking back. Every day I find a new feature that I didn't know was there, or a new one that you've added.

Today my goal is to get TeraTerm downloaded and see if I can get my TNC talking with the software.

73 from Missouri

Kenny

--- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@...> wrote:

If you've got a copy of the client running (most likely APRSIS32)
drawing from a full feed (port 10152) or with a HUGE range, try fading
out the OSM maps the whole way (left arrow). When the map disappears,
the client quits doing a Mercator Projection and reverts to plotting
stations based on distance and bearing from the center of the screen.
Well, the new version actually plots Lat/Lon lines every 10 degrees when
it enters this mode. Zoom out and then drag the screen around. It's
quite....interesting. Especially if you've got stations in the US,
Europe, Japan, Australia, and New Zealand!

Lynn (D) - KJ4ERJ

PS. The kids are home on spring break starting this weekend and through
next weekend, so the updates will probably slow to a crawl....Unless I
really broke something!


One more cool thing

Lynn Deffenbaugh
 

If you've got a copy of the client running (most likely APRSIS32) drawing from a full feed (port 10152) or with a HUGE range, try fading out the OSM maps the whole way (left arrow). When the map disappears, the client quits doing a Mercator Projection and reverts to plotting stations based on distance and bearing from the center of the screen. Well, the new version actually plots Lat/Lon lines every 10 degrees when it enters this mode. Zoom out and then drag the screen around. It's quite....interesting. Especially if you've got stations in the US, Europe, Japan, Australia, and New Zealand!

Lynn (D) - KJ4ERJ

PS. The kids are home on spring break starting this weekend and through next weekend, so the updates will probably slow to a crawl....Unless I really broke something!


Yep, another new release!

Lynn Deffenbaugh
 

Trust me, they'll start slowing down, but here's the skinny on this one:

The real reason for the quick release is that I found and fixed a bug in the map drawing on Windows Mobile. Under some circumstances, you could end up staring at a white screen. The menus and everything worked, it just wouldn't SHOW you anything. It is fixed.

Also, if you disable your GPS just as Genius Beaconing is about to transmit, the client will begin beaconing at the configured Min Time rate, typically 10 or 15 seconds. This is decidedly NOT good, so please upgrade to this version!

Added some AGW diagnostics on startup. Anyone running AGW, particularly a multi-channel installation, please send a copy of your APRSIS32.LOG file to KJ4ERJ@arrl.net. It should show the configuration and recently heard station list as well as the AGW version. This is a test, it is only a test, of new communications to AGW.

The GPS Fix box (lower right corner) now disappears completely if a GPS is not configured. Also, if you have a GTRANS cable, it will now say Fix or Fix(D) rather than No Fix which was caused by not getting $GPGSA or $GPGSV strings from the GTRANS. (See below for the sentences now supported by NMEA thanks to Fred N7FMH).

If a message exhausts its retries, it will now wait for a beacon from the intended recipient. When that happens, a new set of retries is initiated, but only once. (One additional set, not just one more transmission). If you look at the Pending Messages, it will say Final if it exhausted once, or FINAL if it retried a second set.

Popup menus with a single station have been re-configured so you do not need to cascade them. The station ID is now the option for Info in this case.

You'll see a new View / Symbols submenu with Mobile and Weather filters. These are based on the station symbol. Eventually you'll be able to make your own custom symbol filter set as well.

Finally, thanks to Bradley, KC9GQR, the Screen / Tracking submenu now shows checks if a tracked station or Me is at the center. Note that if Locked is checked, the others may be checked as well pending receipt of the next position update. The bottom of the screen is still more reliable at telling you what you're really doing.

Enjoy!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

http://groups.yahoo.com/group/aprsisce/files/20100304%20APRSISCE%20Notes.txt

http://groups.yahoo.com/group/aprsisce/files/APRSIS32100304.zip

http://groups.yahoo.com/group/aprsisce/files/APRSISCE6P100304.zip


PS. The short version looks longer than the long version!

Shuffled one line of code in painting the maps that should result in less time staring at whitespace in certain circumstances.

Send AGW a Version request, Heard stations list, and Port list command at startup to learn more about talking to it.

Remove the GPS Fix box (lower right corner) if a GPS isn't even configured (Win32-only)

Change Tracking(xxxxx-n) and Awaiting(xxxx-n) to Track() and Await() to fit on small Windows Mobile screens (both versions)

Retransmit messages on beacon reception, but only ONE addition retry set (Final vs FINAL)

Corrected a high-speed (Genius / Min Time Rate) beacon if GPS is disabled while moving, now drops back to Max Time rate while disabled

In the absence of a $GPGSA NMEA string (like from a GTRANS cable) to provide 2D or 3D fix type, the Fix pane (lower right) will display Fix or Fix(D) if coordinates are available instead of the "No Fix" it was displaying. APRSISCE/32 interprets the following NMEA strings: RMC, GGA, GSA, GSV and now (hopefully) GLL (Fred N7FMH)

Expanded the Fix pane width to fit Fix(D). Previously it barely fit 3D(D)...

If a popup menu has only one station, it is stacked instead of cascaded. The station ID is the same as Info in the cascade.

Correct s subtle bug when the OSM tile bitmap (in memory) cache gets flushed to zero. Was causing a heap memory corruption on Windows Mobile...

Remove a completely unused path from messages gated from IS to RF. Still reading on the proper approach to the 3rd party packet.

Changed default Station.MinAge from 60 to 80 minutes and Station.MaxAge from 0 (unlimited) to 120 per http://www.aprs.org/aprs11.html. This will not affect existing installations, but ony new installations. Stations fade out between Min and Max age, but may disappear abruptly beyond MinAge if Stations.MaxCount is exceeded. If MaxAge is 0, stations don't fade, but will be removed when Stations.MaxCount is reached.

If you fade the OSM maps completely out (left arrow a bunch), it now draws Lat/Lon lines at 10 degree intervals. If you have a global feed, the effect is quite interesting.

Support View/Symbols/(Custom/Mobile/Weather) as additional filters per symbol definitions on http://www.aprs.org/aprs11.html. Custom will be configurable in the future, both primary and alternate table symbols, but NOT overlays.

Check the appropriate entry in Tracking menu for Center (other) or Me (me/center) (Bradley KC9GQR)


SSn-N Values

Lynn Deffenbaugh
 

James,

Very well stated and it matches my understanding of the paradigm as well. Rest easy, the reason I'm looking for such a list has nothing to do with APRSISCE/32!

As I mentioned in an earlier post, I also tinker around with analyzing the APRS infrastructure by watching packets from all over North America and trying to make sense out of the paths. Your standard of putting the aliases into the beacon status text is really good for humans looking for what is supported in a given area. However, software doesn't have the reading ability of a 2 year old let alone the ability to interpret the various ways operators code such information for humans.

Consider a digiS that uses tactical callsigns of CNABAR, HARIN, LEWIS, PEQUOP, and VIC. Suppose further that someone decides to use an SSn-N alias of PIPEn-N (anywhere from 1-1 through 7-7 as in your example). And to complicate matters, someone half-way around the world decides to call their special event stations PIPE1, PIPE2, ..., PIPE7, PIPE8, and PIPE9 (maybe they're a pipe-rolling event). Consider the paths of packets that have gone through the various digis and gotten marked used, especially the SSn-N aliases that are used up.

How can you tell the difference between
.....>.....,CNABAR,HARIN,PIPE2*.... and
....>.....,PIPE2*,WIDE2-1..... especially when PIPE2 IDs itself as
PIPE2>APXXXX:

Did the first packet really go through PIPE2 the station or is there really a PIPEn-N running around?

My analysis software had this trouble even with WIDE1 and WIDE2 when people mis-configure their stations and accidentally make that their MyCall. I finally decided that WIDEn-N is well known and coded around it. I am now trying to determine if the SSn-N aliass have a "well known" list somewhere or whether they're only local word-of-mouth information. Apparently, it's more the latter (except that it's word-of-digi-comment).

Anyway, I'll let the list get back onto APRSISCE/32 topics now that I've chased this rabbit into the briar patch...

Lynn (D) - KJ4ERJ - Author of APRSISCE/32 and APRS Infrastructure Visualizer

PS. I finally decided that I'll just ignore "impossibly long" digi paths and let the rest of the routes land where they fall.

PPS. To see some of the graphs of which I speak, go to

http://tinyurl.com/APRSAct24 or http://tinyurl.com/APRSAct00



James Ewen wrote:

On Wed, Mar 3, 2010 at 12:45 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:


We've all become familiar with WIDE1-1 and WIDE2-1 or WIDE2-2, but the
SSn-N path aliases don't seem to have any other description other than
on that page (at least, from what I've been able to find).
What exactly are you looking for Lynn? A list of specified values for
SS? There isn't one. The concept is to use the two letter abbreviation
for the state/province. In some areas they use a 3 letter
abbreviation, such as Northern California (NCA).

If one wanted to, they could organize a group of digipeaters that
responded to a totally unique SS value, such as BOINKn-N... as long as
the alias fits the packet name type properly, it's good. It would be
up to the locals to publish the local SSn-N path to use, as they see
fit.

That's why we send that information in the position packets from our
digipeaters around here. W3, ABn, Edmonton, VE6SBR is what the main
digipeater in Edmonton sends, telling people that it supports up to 3
hops via WIDEn-N, the local SS alias is AB, the digipeater is in
Edmonton, and the IC assigned callsign is VE6SBR.

The value of SS doesn't even need to be supported by all the
digipeaters in a specific area. It could be possible to implement a
pipeline of digipeaters between two areas that respond to a special
alias, which would allow people to send packets between to very
disparate areas along a specialized path, without having to flood the
whole area. I could conceivably set up a string of digipeaters between
Edmonton, and Seattle that use an SS alias of PIPE. By sending a
packet with a path of PIPE7-7, I could get that packet to follow the
route on the specific digipeaters that respond to PIPEn-N, getting the
packet to the far end without lighting up any other digipeaters
between Edmonton and Seattle.

So, having said that, I'm still wondering why you are looking for a
definitive list of SS values.

James
VE6SRV


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

Yahoo! Groups Links





Re: Top left rectangle

James Ewen
 

On Wed, Mar 3, 2010 at 12:45 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

We've all become familiar with WIDE1-1 and WIDE2-1 or WIDE2-2, but the
SSn-N path aliases don't seem to have any other description other than
on that page (at least, from what I've been able to find).
What exactly are you looking for Lynn? A list of specified values for
SS? There isn't one. The concept is to use the two letter abbreviation
for the state/province. In some areas they use a 3 letter
abbreviation, such as Northern California (NCA).

If one wanted to, they could organize a group of digipeaters that
responded to a totally unique SS value, such as BOINKn-N... as long as
the alias fits the packet name type properly, it's good. It would be
up to the locals to publish the local SSn-N path to use, as they see
fit.

That's why we send that information in the position packets from our
digipeaters around here. W3, ABn, Edmonton, VE6SBR is what the main
digipeater in Edmonton sends, telling people that it supports up to 3
hops via WIDEn-N, the local SS alias is AB, the digipeater is in
Edmonton, and the IC assigned callsign is VE6SBR.

The value of SS doesn't even need to be supported by all the
digipeaters in a specific area. It could be possible to implement a
pipeline of digipeaters between two areas that respond to a special
alias, which would allow people to send packets between to very
disparate areas along a specialized path, without having to flood the
whole area. I could conceivably set up a string of digipeaters between
Edmonton, and Seattle that use an SS alias of PIPE. By sending a
packet with a path of PIPE7-7, I could get that packet to follow the
route on the specific digipeaters that respond to PIPEn-N, getting the
packet to the far end without lighting up any other digipeaters
between Edmonton and Seattle.

So, having said that, I'm still wondering why you are looking for a
definitive list of SS values.

James
VE6SRV


Re: Top left rectangle

franmargue <f.guerra@...>
 

You can see a little reference in http://www.apritch.myby.co.uk/uiview_newn-n.htm
Here, in Portugal, some station use unproto "APRS,POR2-2" or "WIDE1-1,POR2-2" as UK stations use ...GBRn-n.
So aprs stations are repeated only in those countries.

(Francisco Guerra - CT1AKV)

--- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@...> wrote:

Francisco,

Thanks for the input, but -SSID standards, I've got a handle on
(http://aprsisce.wikidot.com/ssids). That reference is newer than Bob's
2004 page.

My comment was on SSn-N standards which are regional extensions to the
WIDEn-N paradigm (http://www.aprs.org/fix14439.html). Look for:

*_Fix #4: THE NEW STATE SSn-N PATH FOR STATE/SECTIONS or REGIONS:
_*
We've all become familiar with WIDE1-1 and WIDE2-1 or WIDE2-2, but the
SSn-N path aliases don't seem to have any other description other than
on that page (at least, from what I've been able to find).

Lynn (D) - KJ4ERJ

franmargue wrote:
About SSIDs standards:
The last standard I found from Bob is in http://www.aprs.org/aprs11/SSIDs.txt
But in IARU Region I there is a recomendation to use a similar approach in document "CT08_C5_33 NRRL Common standards for APRS".
A copy of that doc is my page http://ct1akv.cidadevirtual.pt/CT08_C5_33%20NRRL%20Common%20standards%20for%20APRS.pdf.
The recomendation is:
"Although in the early 1990's there were some specific SSID definitions for raw NMEA GPS data, those SSID's are no long needed. However, the APRS community has found it useful to encourage users to consider a few simple SSID's as it makes rapid callsign recognition possible. The most commonly used are:
SSID Function
-6 Satellite or special applications
-7 TH-D7 or other handheld applications
-8 Boats (Maritime Mobile)
-9 Stations primarily mobile
-10 Internet only applications
-11 Balloons
-14 Large multi-wheel trucks
Remarks:
- SSID -1 to -4 are normally used when having more ports/frequencies on the same Digipeater or home callsign.
- A standalone Digipeater does not require a SSID, as the assigned callsign would normally clearly indicate what kind of installation we are talking about"

(Francisco Guerra - CT1AKV)

--- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@> 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@
<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)


Re: Top left rectangle

Lynn Deffenbaugh
 

Francisco,

Thanks for the input, but -SSID standards, I've got a handle on (http://aprsisce.wikidot.com/ssids). That reference is newer than Bob's 2004 page.

My comment was on SSn-N standards which are regional extensions to the WIDEn-N paradigm (http://www.aprs.org/fix14439.html). Look for:

*_Fix #4: THE NEW STATE SSn-N PATH FOR STATE/SECTIONS or REGIONS:
_*
We've all become familiar with WIDE1-1 and WIDE2-1 or WIDE2-2, but the SSn-N path aliases don't seem to have any other description other than on that page (at least, from what I've been able to find).

Lynn (D) - KJ4ERJ

franmargue wrote:

About SSIDs standards:
The last standard I found from Bob is in http://www.aprs.org/aprs11/SSIDs.txt
But in IARU Region I there is a recomendation to use a similar approach in document "CT08_C5_33 NRRL Common standards for APRS".
A copy of that doc is my page http://ct1akv.cidadevirtual.pt/CT08_C5_33%20NRRL%20Common%20standards%20for%20APRS.pdf.
The recomendation is: "Although in the early 1990's there were some specific SSID definitions for raw NMEA GPS data, those SSID's are no long needed. However, the APRS community has found it useful to encourage users to consider a few simple SSID's as it makes rapid callsign recognition possible. The most commonly used are:
SSID Function
-6 Satellite or special applications
-7 TH-D7 or other handheld applications
-8 Boats (Maritime Mobile)
-9 Stations primarily mobile
-10 Internet only applications
-11 Balloons
-14 Large multi-wheel trucks
Remarks:
- SSID -1 to -4 are normally used when having more ports/frequencies on the same Digipeater or home callsign.
- A standalone Digipeater does not require a SSID, as the assigned callsign would normally clearly indicate what kind of installation we are talking about"

(Francisco Guerra - CT1AKV)

--- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@...> 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@...
<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)


Re: Top left rectangle

franmargue <f.guerra@...>
 

Oh! Sorry; you're talking about SSn-N and I read SSID!
(Francisco Guerra - CT1AKV)

--- In aprsisce@yahoogroups.com, "franmargue" <f.guerra@...> wrote:

About SSIDs standards:
The last standard I found from Bob is in http://www.aprs.org/aprs11/SSIDs.txt
But in IARU Region I there is a recomendation to use a similar approach in document "CT08_C5_33 NRRL Common standards for APRS".
A copy of that doc is my page http://ct1akv.cidadevirtual.pt/CT08_C5_33%20NRRL%20Common%20standards%20for%20APRS.pdf.
The recomendation is:
"Although in the early 1990's there were some specific SSID definitions for raw NMEA GPS data, those SSID's are no long needed. However, the APRS community has found it useful to encourage users to consider a few simple SSID's as it makes rapid callsign recognition possible. The most commonly used are:
SSID Function
-6 Satellite or special applications
-7 TH-D7 or other handheld applications
-8 Boats (Maritime Mobile)
-9 Stations primarily mobile
-10 Internet only applications
-11 Balloons
-14 Large multi-wheel trucks
Remarks:
- SSID -1 to -4 are normally used when having more ports/frequencies on the same Digipeater or home callsign.
- A standalone Digipeater does not require a SSID, as the assigned callsign would normally clearly indicate what kind of installation we are talking about"

(Francisco Guerra - CT1AKV)

--- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@> 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@
<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: Top left rectangle

franmargue <f.guerra@...>
 

About SSIDs standards:
The last standard I found from Bob is in http://www.aprs.org/aprs11/SSIDs.txt
But in IARU Region I there is a recomendation to use a similar approach in document "CT08_C5_33 NRRL Common standards for APRS".
A copy of that doc is my page http://ct1akv.cidadevirtual.pt/CT08_C5_33%20NRRL%20Common%20standards%20for%20APRS.pdf.
The recomendation is:
"Although in the early 1990's there were some specific SSID definitions for raw NMEA GPS data, those SSID's are no long needed. However, the APRS community has found it useful to encourage users to consider a few simple SSID's as it makes rapid callsign recognition possible. The most commonly used are:
SSID Function
-6 Satellite or special applications
-7 TH-D7 or other handheld applications
-8 Boats (Maritime Mobile)
-9 Stations primarily mobile
-10 Internet only applications
-11 Balloons
-14 Large multi-wheel trucks
Remarks:
- SSID -1 to -4 are normally used when having more ports/frequencies on the same Digipeater or home callsign.
- A standalone Digipeater does not require a SSID, as the assigned callsign would normally clearly indicate what kind of installation we are talking about"

(Francisco Guerra - CT1AKV)

--- In aprsisce@yahoogroups.com, "Lynn W. Deffenbaugh" <kj4erj@...> 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@...
<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: Feature from uiview I'd like to see in aprsisce32

Lynn Deffenbaugh
 

I did catch that suggestion / request embedded in there. I've got it on the ToDo list under "Cool Features".

Thanks for making sure I caught it. I've been known to miss things like that!

Lynn (D) - KJ4ERJ

Gary Sanders wrote:

Lynn, I had posted the following as part of another unrelated message
previously, but it was tucked in toward the bottom of the message and it
was easy to miss, so I thought I'd repeat it here with it's own subject (and a few edits for clarity).........


You had asked in another post what features from uiview people would like to see. One that I use constantly is an add-in for uiview called "Station Movement Alarm". If a received station moves more than "X" (programmable in yards) from it's previous position, a user-selectable sound file is played. I have it play a chime. The user selects which stations to monitor for movement.

I have the distance set to 30 yards. So when the received station is parked, no alert chime sounds. If the next position is more than 30 yards from the last one, the chime sounds. Simple, and unbelievably convenient.

It would be nice if something like this could be optionally added to the
"Locked Tracking" feature.

Gary Sanders
WB0BZR


Feature from uiview I'd like to see in aprsisce32

Gary Sanders
 

Lynn, I had posted the following as part of another unrelated message
previously, but it was tucked in toward the bottom of the message and it
was easy to miss, so I thought I'd repeat it here with it's own subject (and a few edits for clarity).........


You had asked in another post what features from uiview people would like to see. One that I use constantly is an add-in for uiview called "Station Movement Alarm". If a received station moves more than "X" (programmable in yards) from it's previous position, a user-selectable sound file is played. I have it play a chime. The user selects which stations to monitor for movement.

I have the distance set to 30 yards. So when the received station is parked, no alert chime sounds. If the next position is more than 30 yards from the last one, the chime sounds. Simple, and unbelievably convenient.

It would be nice if something like this could be optionally added to the
"Locked Tracking" feature.

Gary Sanders
WB0BZR


Re: Can't see other stations using RF only through an Internet connection

Lynn Deffenbaugh
 

Craig,

First, if you connect to the TT4 in text mode with a terminal emulator, is it decoding and displaying packets?

When you say you've checked aprs.fi and see that you are beaconing, is that the TT4 beaconing, APRSIS32 beaconing via the TT4, or APRSIS32 beaconing directly to the Internet? What -SSID are you doing this testing with?

Finally, if you can do the following and send me the APRSIS32.LOG file, I can see what might be going on.

1) Set up all of the appropriate configurations and enables for the test (APRS-IS disabled, KISS or TEXT configured and Enabled as appropriate)
2) Turn on Enables / Debug Logging
3) Close the client
4) Restart the client
5) Wait a suitable time for things to happen. You can click Transmit once or twice as desired.
6) After beacons should have been received (and apparently were not), Turn off Enables / Debug Logging
7) Close the client
8) Email the APRSIS32.LOG file to KJ4ERJ@arrl.net. Grab a copy BEFORE restarting the client as it will be renamed on each client restart.

Once I get the .LOG file, I'll try to guess what's going on, but with the TT4, the decoding or not decoding is usually the biggest first hurdle.

Lynn (D) - KJ4ERJ

Craig Leventhal wrote:

If I use APRSIS32 on my laptop connected to the Internet I can see other APRS staions but if I use it offline - Laptop conected to a Byonics TT4 throug a USB adapter and null modem cable, GPS and rig, I don't receive any stations. I verified on aprs.fi that I am beconing, I can use terminal software to connect and configure my TT4, and I've tried changing both APRSIS32 and the TT4 both set for TEXT and KISS mode. The TT4 is set for 19200,n,8,1 and so is APRSIS32. Any suggestions why the APRSSI32 and laptop aren't talking to the TT4?


Thanks in advance and 73

Craig - KI6WLP


Re: Minor details.

Lynn Deffenbaugh
 

Just play around with the SlippyMap browser at http://www.openstreetmap.org/ with Cycle Map selected on the upper right corner and you'll see why I don't have that as a publicized option. WAY too many chunks of the country that simply disappear into white tiles when you zoom in. Just SW of Winston Salem in the Carolinas as well as the East Coast of Florida just don't seem to exist at the lower levels of Cycle Map.

I also discounted Osmarender due to the density of "stuff" on the map. The APRS stations just got lost in the clutter.

I'll see about providing configuration assistance to switch the tile server and URLs to these various options, but I'll be keeping Mapnik as the default option.

Lynn (D) - KJ4ERJ

Fred Hillhouse 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.
Do they get rendered on the fly or is it done through some sort of communication?
This would be a sweet option! That would be my default. There is something about contours that are just plain attractive.

> > 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.
When I lived in Utah I bought every 7min map of the Moab area and several other areas I visited. I have a large collection of paper.