Date   

Activating IS

Ron Wenig <rwenig@...>
 

Lynn,

After I sent the message to the group yesterday asking about transmitting over IS it started to work. Now I am trying to help someone else with their APRSISCE and they are having the same problem. Is there a waiting period before you can start transmitting on IS. He is receiving things ok.

73, Ron ny3j


Re: KISS TNC Running

Stan Leeds <srkleeds@...>
 

Thanks Lynn, I'll finish reading up on your links.

I see were you have sent me a couple or three messages via "RF", I've sent replies, but they sit there "Pending". I'm still using low power and an antenna sitting by the window, so not sure how well I'm getting out. However no problem using the email messaging or messaging with local stations.

So, in summary, the test with a radio "just sitting there" I'm going to chalk up complete. The next test is to put it one of my laptops with WinXP (have another with Vista I'll check also), prefetch some maps, connect a GPS, then this radio and take it out for a spin.

I ran a UI-View IGATE for a couple of years before the winter, but a limb took out the antenna and since then I have had a case of "motivational antenna installation" syndrome. It was bi-directional and I would gate 2 or 3 mobiles to RF when they went back and forth to Florida and others during vacation. Guess I need to get a remedy for my "lazyness"...

I've seen were you may be working on other external mapping programs (PMaps?) and D-710 interfacing, I'm also interested in those.

Cheers and 73,
Stan/KC7EHJ-4

Lynn W. Deffenbaugh wrote:


Stan Leeds wrote:
I do have some comments/questions:
When looking at my messages on findu.com, I saw these...
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another
BITS.11111111,Battery State Tracking
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another
EQNS.0,1,0,0,1,0,0,1,0,0,1,0,0,1,0
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another
UNIT.Percent,Charge/On/Off,Sats/On/Off,N/A,N/A,On,Yes,On,N/A,N/A,N/A,N/A,N/A
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another
PARM.Battery,Charging/AC,GPS+Sat,A4,A5,A/C,Charging,GPS,B4,B5,B6,B7,B8
Are these actually from me to me?
Yes, they actually are. And I just put an entry on the Wiki today that
describes them! They're the messages that set up telemetry. You can
read the following pages for details:

http://aprsisce.wikidot.com/telemetry <http://aprsisce.wikidot.com/telemetry>

http://www.aprs.net/vm/DOS/TELEMTRY.HTM <http://www.aprs.net/vm/DOS/TELEMTRY.HTM>

http://wiki.argentdata.com/index.php/Telemetry <http://wiki.argentdata.com/index.php/Telemetry>

Also I see my call with the * on the end which I believe that I was
digi'd.
But my call KC7EHJ-4 was originally just black lettering, then I saw
black lettering with a red highlight, then white lettering and red
highlight. I've looked, but i have either missed the explanation or
couldn't find it.
I have a ToDo to explain the colors, but they're showing how far away
the station is. Black means we don't know where the station is. Green
are far away, Red are close by. Reverse video is for someone in your
filter as a Buddy. Yellow background are other stations running
APRSISCE/32. Ping background is a packet that APRSISCE/32 considers as
probably invalid (moving too fast, duplilcate, or beaconing too quickly).

Now low priority wish list for the small time I have playing with it. A
lot of other folks has brought most of the main options carried over
from UI-View.
I would like to see (for Windows) is when zooming with a mouse wheel
that the display centers were the mouse pointer is..
.


Re: TT4

Robin Williams <phonetech@...>
 

Hi Lynn,
I think I prefer it to show the station rather than the Digi.
I just had a look at my display (RF only) and it only shows the igate call.
If connected to the I/S it shows the station call and I would look at that
and then centre on a particular call.
Just my 10c worth.
Cheers,
Robin.

(The scrolling station log is simply there to show that traffic is coming in
from the stations being displayed. The actual object name is placed on the
map and is also available if you click on a station in the scrolling display
to learn more about what it said, not just the fact that it said something.
I would have to say that what's most important to the observer isn't that
they heard about an object, but they'll scan the map to find the closest
antenna object and click it to get the details.)


Re: KISS TNC Running

Lynn Deffenbaugh
 

Stan Leeds wrote:
I do have some comments/questions:
When looking at my messages on findu.com, I saw these...
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another BITS.11111111,Battery State Tracking
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another EQNS.0,1,0,0,1,0,0,1,0,0,1,0,0,1,0
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another UNIT.Percent,Charge/On/Off,Sats/On/Off,N/A,N/A,On,Yes,On,N/A,N/A,N/A,N/A,N/A
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another PARM.Battery,Charging/AC,GPS+Sat,A4,A5,A/C,Charging,GPS,B4,B5,B6,B7,B8
Are these actually from me to me?
Yes, they actually are. And I just put an entry on the Wiki today that describes them! They're the messages that set up telemetry. You can read the following pages for details:

http://aprsisce.wikidot.com/telemetry

http://www.aprs.net/vm/DOS/TELEMTRY.HTM

http://wiki.argentdata.com/index.php/Telemetry

Also I see my call with the * on the end which I believe that I was digi'd.
But my call KC7EHJ-4 was originally just black lettering, then I saw black lettering with a red highlight, then white lettering and red highlight. I've looked, but i have either missed the explanation or couldn't find it.
I have a ToDo to explain the colors, but they're showing how far away the station is. Black means we don't know where the station is. Green are far away, Red are close by. Reverse video is for someone in your filter as a Buddy. Yellow background are other stations running APRSISCE/32. Ping background is a packet that APRSISCE/32 considers as probably invalid (moving too fast, duplilcate, or beaconing too quickly).

Now low priority wish list for the small time I have playing with it. A lot of other folks has brought most of the main options carried over from UI-View.
I would like to see (for Windows) is when zooming with a mouse wheel that the display centers were the mouse pointer is..
Sorry, not happening anytime too soon. Centering the map is one of my hot spots. I NEVER pay attention to where the mouse pointer is when I spin the wheel and actually despise things that pan the map when I didn't tell them to.

A closed fist/hand when dragging the map around.
I'm a simple person, if Windows doesn't do it automatically, I don't usually bother with eye candy. I'm more focused on basic functionality. I'll add it to the list, though, for sometime I'm bored and want to learn how to do something new.

Thanks for all the hard work and look forward to more.
Keep up the suggestions, even when I respond negatively the first time. Sometimes I can come around after thinking about it for a while...

Lynn (D) - KJ4ERJ

73,
Stan/KC7EHJ



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

Yahoo! Groups Links





Re: TT4

Lynn Deffenbaugh
 

Broncus wrote:
It seems the only equipment that show the objects name are Kenwoods (at least the D7). My T2 puts the originator on the LCD but the object name on the GPS display. For an object, the D7 actually shows the the object name and in the comment field the comment. For a repeater, the object name is the frequency and the status will give tone and range. For example, see objects on APRS.FI from PNRDVL. There are 3 of them. Actually 4, but one is not currently being updated.

Here is one of the objects:
Source callsign: PNRDVL APRS object: 147.135NH
Comment: T100 r20m S.Uncan MT

The question is, what information is the most useful to an observer? Is it the originator of the object or the object itself?
The scrolling station log is simply there to show that traffic is coming in from the stations being displayed. The actual object name is placed on the map and is also available if you click on a station in the scrolling display to learn more about what it said, not just the fact that it said something. I would have to say that what's most important to the observer isn't that they heard about an object, but they'll scan the map to find the closest antenna object and click it to get the details.

The D710 allows the user to set the radio to a repeater object if it is properly formed. I actually would like the repeater objects to be stored in a separate file for access by software that can program my FT857D. It would sure be handy when travelling to areas other than my own.
Got any specs on that "separate file" that FT857D programming software can access. I've certainly not heard of such software, but then, I don't own an FT857D either!

Lynn (D) - KJ4ERJ - The best thing about being an author is that I get to do it MY way! (But I'd like that way to work for others as well!)

Ah, more food for thought! :)

Best regards,
Fred



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

And now for the rest of the story...

The same thing happens with received objects. The ID in the scrolling station log will be the originator of the object (or the IGate if the object was 3rd party gated, a rare occurrence) but the right click menu will be for the object itself. You see this a lot with repeater frequency objects that are beaconed.

Lynn (D) - KJ4ERJ

Robin Williams wrote:

Hi Lynn,
That was quick.
"Do you mean ones that were gated from -IS to RF by an iGate?"
Yep.
Your explanation says it all.
Thanks,
Robin.
-----Original Message-----
From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
Of Lynn W. Deffenbaugh
Sent: Sunday, 7 March 2010 3:07 p.m.
To: aprsisce@yahoogroups.com
Subject: Re: [aprsisce] TT4

Robin Williams wrote:

I have my laptop (zl3rew-8) hooked up to a TT4 running in kiss mode.
Seems to TX and RX fine.
The only issue is in the station pane on the left.
If a station is received via an iGate it shows the igate callsign not the stations callsign.
The stations appear on the map ok as normal.
Something i have done wrong?
I'm not sure what you mean "received via an iGate". Do you mean ones that
were gated from -IS to RF by an iGate? The scrolling station display shows
the fromCall of the actual received packet, be it from -IS or RF. In the
case of an -IS to RF gated packet, the iGate is actually the sender that you
received. The originator of the packet is contained behind the 3rd party
header. It will show properly both in the popup and on the map.

I intended the scrolling log to be a snapshot of the station's you're
actually hearing. The * means you've heard THAT station via RF, not
necessarily the packet originator which could become very misleading if I'd
put a * beside that callsign. You'd think you've gotten some extreme DX
reception via RF.

Lynn (D) - KJ4ERJ





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

Yahoo! Groups Links





APRS-IS Not Sending

Ron Wenig <rwenig@...>
 

HI Lynn and All,

I have APRSIS32 set up with APRS-IS enabled, using the password that I received when I registered UIView32. When I hit transmit and check with another instance of APRSIS32 or when I check findu I don't see the posit. It does transmit ok on RF and that posit shows up.

Also, should I be seeing messages from other stations. All I see is No Msg on the top right corner.

73, Ron ny3j


KISS TNC Running

Stan Leeds <srkleeds@...>
 

This was one of the quickest config to a TNC I have done. Pretty much in under five minutes I had the program downloaded and connected/receivimg via RF only with a DR-135/T2-135 setup. This is with low power and a mg mount antenna by the window. KC7EHJ-4

Lynn,
When I sent the RF only message to you, I had only been up for about 10 minutes.

I do have some comments/questions:
When looking at my messages on findu.com, I saw these...
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another BITS.11111111,Battery State Tracking
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another EQNS.0,1,0,0,1,0,0,1,0,0,1,0,0,1,0
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another UNIT.Percent,Charge/On/Off,Sats/On/Off,N/A,N/A,On,Yes,On,N/A,N/A,N/A,N/A,N/A
KC7EHJ-4 KC7EHJ-4 03/07 02:18:55z Send another PARM.Battery,Charging/AC,GPS+Sat,A4,A5,A/C,Charging,GPS,B4,B5,B6,B7,B8
Are these actually from me to me?

Also I see my call with the * on the end which I believe that I was digi'd.
But my call KC7EHJ-4 was originally just black lettering, then I saw black lettering with a red highlight, then white lettering and red highlight. I've looked, but i have either missed the explanation or couldn't find it.

Now low priority wish list for the small time I have playing with it. A lot of other folks has brought most of the main options carried over from UI-View.
I would like to see (for Windows) is when zooming with a mouse wheel that the display centers were the mouse pointer is..
A closed fist/hand when dragging the map around.


Thanks for all the hard work and look forward to more.

73,
Stan/KC7EHJ


Re: TT4

Fred Hillhouse
 

It seems the only equipment that show the objects name are Kenwoods (at least the D7). My T2 puts the originator on the LCD but the object name on the GPS display. For an object, the D7 actually shows the the object name and in the comment field the comment. For a repeater, the object name is the frequency and the status will give tone and range. For example, see objects on APRS.FI from PNRDVL. There are 3 of them. Actually 4, but one is not currently being updated.

Here is one of the objects:
Source callsign: PNRDVL
APRS object: 147.135NH
Comment: T100 r20m S.Uncan MT

The question is, what information is the most useful to an observer? Is it the originator of the object or the object itself?

The D710 allows the user to set the radio to a repeater object if it is properly formed. I actually would like the repeater objects to be stored in a separate file for access by software that can program my FT857D. It would sure be handy when travelling to areas other than my own.

Ah, more food for thought! :)

Best regards,
Fred

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

And now for the rest of the story...

The same thing happens with received objects. The ID in the scrolling
station log will be the originator of the object (or the IGate if the
object was 3rd party gated, a rare occurrence) but the right click menu
will be for the object itself. You see this a lot with repeater
frequency objects that are beaconed.

Lynn (D) - KJ4ERJ

Robin Williams wrote:
Hi Lynn,
That was quick.
"Do you mean ones that were gated from -IS to RF by an iGate?"
Yep.
Your explanation says it all.
Thanks,
Robin.

-----Original Message-----
From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
Of Lynn W. Deffenbaugh
Sent: Sunday, 7 March 2010 3:07 p.m.
To: aprsisce@yahoogroups.com
Subject: Re: [aprsisce] TT4

Robin Williams wrote:

I have my laptop (zl3rew-8) hooked up to a TT4 running in kiss mode.
Seems to TX and RX fine.
The only issue is in the station pane on the left.
If a station is received via an iGate it shows the igate callsign not
the stations callsign.
The stations appear on the map ok as normal.
Something i have done wrong?
I'm not sure what you mean "received via an iGate". Do you mean ones that
were gated from -IS to RF by an iGate? The scrolling station display shows
the fromCall of the actual received packet, be it from -IS or RF. In the
case of an -IS to RF gated packet, the iGate is actually the sender that you
received. The originator of the packet is contained behind the 3rd party
header. It will show properly both in the popup and on the map.

I intended the scrolling log to be a snapshot of the station's you're
actually hearing. The * means you've heard THAT station via RF, not
necessarily the packet originator which could become very misleading if I'd
put a * beside that callsign. You'd think you've gotten some extreme DX
reception via RF.

Lynn (D) - KJ4ERJ


Re: TT4

Lynn Deffenbaugh
 

And now for the rest of the story...

The same thing happens with received objects. The ID in the scrolling station log will be the originator of the object (or the IGate if the object was 3rd party gated, a rare occurrence) but the right click menu will be for the object itself. You see this a lot with repeater frequency objects that are beaconed.

Lynn (D) - KJ4ERJ

Robin Williams wrote:

Hi Lynn,
That was quick.
"Do you mean ones that were gated from -IS to RF by an iGate?"
Yep.
Your explanation says it all.
Thanks,
Robin.
-----Original Message-----
From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
Of Lynn W. Deffenbaugh
Sent: Sunday, 7 March 2010 3:07 p.m.
To: aprsisce@yahoogroups.com
Subject: Re: [aprsisce] TT4

Robin Williams wrote:

I have my laptop (zl3rew-8) hooked up to a TT4 running in kiss mode.
Seems to TX and RX fine.
The only issue is in the station pane on the left.
If a station is received via an iGate it shows the igate callsign not the stations callsign.
The stations appear on the map ok as normal.
Something i have done wrong?
I'm not sure what you mean "received via an iGate". Do you mean ones that
were gated from -IS to RF by an iGate? The scrolling station display shows
the fromCall of the actual received packet, be it from -IS or RF. In the
case of an -IS to RF gated packet, the iGate is actually the sender that you
received. The originator of the packet is contained behind the 3rd party
header. It will show properly both in the popup and on the map.

I intended the scrolling log to be a snapshot of the station's you're
actually hearing. The * means you've heard THAT station via RF, not
necessarily the packet originator which could become very misleading if I'd
put a * beside that callsign. You'd think you've gotten some extreme DX
reception via RF.

Lynn (D) - KJ4ERJ


Re: TT4

Robin Williams <phonetech@...>
 

Hi Lynn,
That was quick.
"Do you mean ones that were gated from -IS to RF by an iGate?"
Yep.
Your explanation says it all.
Thanks,
Robin.

-----Original Message-----
From: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] On Behalf
Of Lynn W. Deffenbaugh
Sent: Sunday, 7 March 2010 3:07 p.m.
To: aprsisce@yahoogroups.com
Subject: Re: [aprsisce] TT4

Robin Williams wrote:
I have my laptop (zl3rew-8) hooked up to a TT4 running in kiss mode.
Seems to TX and RX fine.
The only issue is in the station pane on the left.
If a station is received via an iGate it shows the igate callsign not
the stations callsign.
The stations appear on the map ok as normal.
Something i have done wrong?
I'm not sure what you mean "received via an iGate". Do you mean ones that
were gated from -IS to RF by an iGate? The scrolling station display shows
the fromCall of the actual received packet, be it from -IS or RF. In the
case of an -IS to RF gated packet, the iGate is actually the sender that you
received. The originator of the packet is contained behind the 3rd party
header. It will show properly both in the popup and on the map.

I intended the scrolling log to be a snapshot of the station's you're
actually hearing. The * means you've heard THAT station via RF, not
necessarily the packet originator which could become very misleading if I'd
put a * beside that callsign. You'd think you've gotten some extreme DX
reception via RF.

Lynn (D) - KJ4ERJ


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

Yahoo! Groups Links


Re: TT4

Lynn Deffenbaugh
 

Robin Williams wrote:
I have my laptop (zl3rew-8) hooked up to a TT4 running in kiss mode.
Seems to TX and RX fine.
The only issue is in the station pane on the left.
If a station is received via an iGate it shows the igate callsign not the stations callsign.
The stations appear on the map ok as normal.
Something i have done wrong?
I'm not sure what you mean "received via an iGate". Do you mean ones that were gated from -IS to RF by an iGate? The scrolling station display shows the fromCall of the actual received packet, be it from -IS or RF. In the case of an -IS to RF gated packet, the iGate is actually the sender that you received. The originator of the packet is contained behind the 3rd party header. It will show properly both in the popup and on the map.

I intended the scrolling log to be a snapshot of the station's you're actually hearing. The * means you've heard THAT station via RF, not necessarily the packet originator which could become very misleading if I'd put a * beside that callsign. You'd think you've gotten some extreme DX reception via RF.

Lynn (D) - KJ4ERJ


TT4

Robin Williams <phonetech@...>
 

Hi All,
I have my laptop (zl3rew-8) hooked up to a TT4 running in kiss mode.
Seems to TX and RX fine.
The only issue is in the station pane on the left.
If a station is received via an iGate it shows the igate callsign not the stations callsign.
The stations appear on the map ok as normal.
Something i have done wrong?
Cheers,
Robin.


Re: TM-D710 support

Lynn Deffenbaugh
 

James Ewen wrote:
On Sat, Mar 6, 2010 at 12:22 AM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:


If you put the D710 into Converse mode, do the monitor and GPS packets
continue to come out? That should eliminate the CMD: prompt and allow
APRSISCE/32 to transmit beacons, messages, and telemetry.
I'm not sure if you can get to converse mode in that mode. It's
designed as an output port from the APRS application, not really an
interactive port. Converse mode would mean that the TNC is in Packet
mode.
I was under the impression that you were in normal TNC mode hence the Cmd: prompt that kept interleaving with the data. I pulled the Kenwood documentation before asking the question. I'll keep this on the ToDo list and work with you when I get closer to it.

Lynn (D) - KJ4ERJ


Re: TM-D710 support

James Ewen
 

On Sat, Mar 6, 2010 at 12:22 AM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

If you put the D710 into Converse mode, do the monitor and GPS packets
continue to come out?  That should eliminate the CMD: prompt and allow
APRSISCE/32 to transmit beacons, messages, and telemetry.
I'm not sure if you can get to converse mode in that mode. It's
designed as an output port from the APRS application, not really an
interactive port. Converse mode would mean that the TNC is in Packet
mode.

One problem with making an application, is that the users might not
always want your application to do what you think it should be doing.

James
VE6SRV


Re: TM-D710 support

James Ewen
 

On Thu, Mar 4, 2010 at 1:22 PM, Lynn W. Deffenbaugh <kj4erj@arrl.net> wrote:

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...
I don't believe you can easily feed packets back at the D710 in that
mode. Kai made a wedge that would allow you to run UI-View attached in
this configuration, I think... I have to do more digging back in the
archives.

I'll have to play for a while to learn more about putting the unit
into KISS mode, and what data is presented out the port.

The reason for my interest in this type of operation is to be able to
have an enhanced D710 display. The D710 does a pretty good job all by
itself. There are a few things that I would like to see added into it
to make it better, but that means convincing Kenwood of the usefulness
of the enhancement, and then getting them to add the functions into
the firmware.

I believe the D710 has to be in APRS mode to send $KWDWPL strings to
the GPS, which puts the APRS icons on the GPS. Putting the D710 into
KISS mode means that all the smarts in the D710 are turned off. We
lose the GPS attached to the D710, and no icons are passed to the GPS.

Adding APRSISCE/32 onto the com port of the D710 would allow the D710
to do everything that it currently does, but also gives additional
features, such as using the OSM map, tracking of stations, and
hopefully viewing of the raw packets. (I'm not sure why so many client
authors think that raw packets contain no useful information... the
path information is very useful in observing the health of the APRS
network)

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?
I don't know if it would do anything with incoming data. Most likely
not, but I never tried sending data back. Most other applications are
RX only. Not many applications send information back to the GPS in
real time like APRS. I sent the data to a virtual serial port driver,
which looped back to the other application.

James
VE6SRV


Re: Feature Set Request - self awareness

Fred Hillhouse
 

Broncus wrote:
My location (determined by GPS) - something other than the ICON in
CONFIG.
A simple dot would suffice.
This could go hand-in-hand with one I just put on the list which was to
make the
"Me" icon completely disappear. Maybe I'll add a configuration for a
"local display"
symbol which can be blank to be gone and otherwise configured as you
desire,
including your suggested simple dot. I could also add a "Me" (and/or
tracking)
scale factor which will increase (+) or shrink (-) the size of the "Me"
or tracked
station making it disappear or become more visible. Good idea!
I figure that if I am centered on the GPS position, then it must be ME at
the center too.

I think one of the APRS symbols is a dot. I would have to check. That would
suffice.

Of course a line depicting direction of travel (GPS base information) would
be useful to. Actually, when hunting a Geocache I found that useful. There
are a couple of PDA based applications (CetusGPS and GeoNiche) that provided
just a point and a short line (half the range circle).


Display my returned beacon with the ICON. The T2 sends my returned beacon
to the GPS but I am thinking to remove my current GPS and replace it with a
mouse type and leave all the display functions up to APRSIS32.

I'm not clear on what this one means. Can you elaborate a bit more?
My system is a T2, GPS, radio, and of late, added APRSIS/32. But prior to
adding /32, I could see my own "digi echoed" symbol on the GPS display and
on the T2 LCD. That means I can see where my beacon did a complete 'out and
back'.

T2, GPS, radio (N7FMH-9)
APRSIS/32 = N7FMH-12

Is "returned beacon" hearing your own beacon digipeated?
Yes

That will put a * beside your name in the scrolling station list. Boxes
around
the icon in the scrolling station list (subtle) mean that the station was
heard
direct via an RF channel.
I saw that, but where was it received? I have to look at the GPS to see
N7FMH-12. I do see N7FMH-9 on the GPS even though the T2 sent it out.
Basically I think that all received position beacons should be on the map
(with a exception for any filtered out).

Not sure what the GPS has to do with this request, either. And who would
be
getting the mouse-type GPS, the T2 or APRSIS32?
Either or both, depends on how I want to re-allocate resources. Basically, I
am missing some satellite information because of how I have things wired and
if there is a laptop running then I really don't need a display on the GPS
which means the GPS can be a mouse type.

A question, is the self tracking with the little square where a beacon was
generated? If not, that could be useful.
Yes, the little squares are drawn at the actual points where beacons were
generated (or received if you're tracking someone else). I only draw a few
of the most recent points for display performance considerations.

I thought that might be what I was seeing. Cool! Although, an option to turn
them all on might be useful to tune beacon settings. That is mostly what
drove the question.

Best regards,
Fred


Telemetry

Lynn Deffenbaugh
 

Someone asked a while back about what Telemetry values are used in APRSISCE/32. I can't find the e-mail to reply, but here's the answer.

First, you can view two of my station's telemetry at:

http://aprs.fi/telemetry/KJ4ERJ-1?range=day
http://aprs.fi/telemetry/KJ4ERJ-12?range=day

KJ4ERJ-1 is APRSIS32 as my HF IGate talking to an NMEA Bluetooth GPS from my Dell laptop
KJ4ERJ-12 is APRSISCE on my AT&T Tilt phone

As you can see, there are three telemetry values and three bits. They are:

Battery: Graphs the battery percentage. APRSISCE sends an update on each transition notification from Windows Mobile. APRSIS32 polls the battery periodically to generate telemetry (and graph the battery bar on the right edge of the screen). (Yes, the battery IS bad in KJ4ERJ-1, at least, Windows 7 says it is!)

Charging/AC: 2% is running on battery, 48% is running on A/C, 95% is running on A/C and charging. I chose those numbers because 0, 50, 100 was hard to see on the lines at aprs.fi.

GPS+Sat: Tracks the GPS Enable/Disable and satellite in use count. 2=Disabled, 50=Enabled, >50 = 50+SatellitesInUse*5 max 95)

Bits show A/C connected, Charging or not, and GPS enabled.

So, how did aprs.fi know about these categories? I'm glad you asked! APRSISCE/32 send the following APRS messages addressed to itself when it thinks it needs to:

"PARM.Battery,Charging/AC,GPS+Sat,A4,A5,A/C,Charging,GPS,B4,B5,B6,B7,B8", /* Channel names */
"UNIT.Percent,Charge/On/Off,Sats/On/Off,N/A,N/A,On,Yes,On,N/A,N/A,N/A,N/A,N/A",/* Units */
"EQNS.0,1,0,0,1,0,0,1,0,0,1,0,0,1,0", /* (a*v^2 + b*v + c) 5 times! */
"BITS.11111111,Battery State Tracking" /* Bit sense and project name */

It does this once per telemetry format change and keeps track of what telemetry version it last transmitted in the XML file under <TelemetryDefined>. Telemetry is transmitted based on <TelemetryInterval> as expressed in minutes. If your station doesn't have the proper labels on your telemetry page, or if you'd like telemetry to send more (or less) often, edit the config file and change these values. Note that APRSISCE is still going to send Telemetry on every battery state change, regardless of the value of the <TelemetryInterval>.

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


Re: Feature Set Request - self awareness

Lynn Deffenbaugh
 

Broncus wrote:
My location (determined by GPS) - something other than the ICON in CONFIG. A simple dot would suffice.
This could go hand-in-hand with one I just put on the list which was to make the "Me" icon completely disappear. Maybe I'll add a configuration for a "local display" symbol which can be blank to be gone and otherwise configured as you desire, including your suggested simple dot. I could also add a "Me" (and/or tracking) scale factor which will increase (+) or shrink (-) the size of the "Me" or tracked station making it disappear or become more visible. Good idea!

Display my returned beacon with the ICON. The T2 sends my returned beacon to the GPS but I am thinking to remove my current GPS and replace it with a mouse type and leave all the display functions up to APRSIS32.
I'm not clear on what this one means. Can you elaborate a bit more? Is "returned beacon" hearing your own beacon digipeated? That will put a * beside your name in the scrolling station list. Boxes around the icon in the scolling station list (subtle) mean that the station was heard direct via an RF channel. Not sure what the GPS has to do with this request, either. And who would be getting the mouse-type GPS, the T2 or APRSIS32?

A question, is the self tracking with the little square where a beacon was generated? If not, that could be useful.
Yes, the little squares are drawn at the actual points where beacons were generated (or received if you're tracking someone else). I only draw a few of the most recent points for display performance considerations.

Lynn (D) - KJ4ERJ


Thanks!

Fred n7fmh


Re: /32 and Mobile Use Problem (Maybe)

Lynn Deffenbaugh
 

K3RWN wrote:
First off thank you all so much. Is there a good location with help or
FAQs?
There is a fledgling Wiki at http://aprsisce.wikidot.com/start The organization is non-existent, but if you click on one of the Page tags on the left you'll get an idea of the topics for which pages currently exist. My goal is that simple FAQs can be answered in this group just by providing a link to the appropriate Wiki page. When you look at the Wiki, you can tell that I'm not there yet!


I set TSWPT to TRUE this will send pos reports to /32 regardless of if my
RF was heard.
Ok, that should provide good updates for the -9 back to APRSIS32 allowing that station to track nicely.

I am not sure what command is causing the UNPROTO issue.
I don't know how the TT4 actually works in TEXT mode, so if you keep the TT4 and APRSIS32 both in KISS mode, I think you'll do fine.


I have everything setup as per your email. I guess we will see if it looks
better now. Tracking is working great. I just drove around the local
streets and everything is good.
I assume that's tracking of the -9 and visibility to it on APRSIS32? I see the > from the TT4, but you probably also want to disable tracking in APRSIS32 (uncheck Enables / Tracking Enabled). You can turn it back on and drag/Transmit your actual coordinate when you get stationary if you want.

2010-03-06 16:35:42 UTC: K3RWN-1>APWW00,W3EXW,WIDE1*,WIDE2-1,qAR,N8GD-1:@163538h0000.00N/00000.00E$APRS-IS for CE [Latitude and longitude are both 0]

Does your APRISS32 machine have mobile Internet? Just curious because if it does, you'll have a mobile IGate!

Cool! I just looked at your actual location on the map. I grew up in Johnstown PA and my high school sweetheart lived in Brentwood, juse SW of your QTH! That was a LONG time ago!

Lynn (D) - KJ4ERJ


Rich


Re: /32 and Mobile Use Problem (Maybe)

K3RWN
 

First off thank you all so much. Is there a good location with help or
FAQs?


First, as a general rule, each APRS packet generating "thing" should
have its own unique -SSID.

OK I have the /32 as -1 and the TT4 as -9
I'm looking at your RAW packets at aprs.fi:

Do you have a GPS configured into APRSIS32?

I do not have a GPS on /32 it is connected to the TT4.
To track where you are actually at and have a moving map while mobile,
I'd have APRSIS32 tracking your TT4's callsign. Also, the TT4 can be
configured to send it's own position packets back to the PC port for
just this reason. Without that turned on (I'll refer you to the manual
as I don't use my TT4 mobile), the station will only update if the
beacon's digipeat is heard or the TT4 beacon is gated to the -IS and
your APRSIS32 has mobile Internet getting the update via APRS-IS. I'm
not sure if the TT4 does this in KISS mode, TEXT mode, or both.

I set TSWPT to TRUE this will send pos reports to /32 regardless of if my
RF was heard.

Which brings me to the next topic. APRSIS32 doesn't have good code to
put TNCs into KISS mode.

I knew this and was setting the TT4 to KISS in an emulator, I changed it
this morning to TEXT when I was playing around and did not set it back
before I sent the email. It is set correctly now.



I am not sure what command is causing the UNPROTO issue.
I have everything setup as per your email. I guess we will see if it looks
better now. Tracking is working great. I just drove around the local
streets and everything is good.

Rich