Date   

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


Feature Set Request - self awareness

Fred Hillhouse
 

Hi Lynn,

I did look through the ToDo List and hopefully am not repeating something I missed.

My location (determined by GPS) - something other than the ICON in CONFIG. A simple dot would suffice.

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.

A question, is the self tracking with the little square where a beacon was generated? If not, that could be useful.


Thanks!

Fred n7fmh


Re: /32 and Mobile Use Problem (Maybe)

Lynn Deffenbaugh
 

David Shrum wrote:


I will offer an opinion and Lynn will correct me if I am wrong. You need a different Yourcall-SSID for each copy that you use; otherwise it wont know where you are for sure if they are running at the same time.
You are absolutely correct and thanks for jumping in! As the use of the client grows, I'm counting on others like yourself to jump in as the message traffic increases! If all goes as I plan with the Wiki, it might be as simple as just dropping a URL in response to FAQs as the first part of this one was.

P.S. found from earlier messages Re: [aprsisce] 2 instances:

(Lynn (D) - KJ4ERJ wrote)

EVERY SINGLE APRS-IS CLIENT MUST HAVE A UNIQUE -SSID! These -SSIDs do NOT have to be between 00-15 and don't even need to be numeric. I use -AL for my full (ALL) feed, -AP for my APW* watcher, and various others as well.
That response was specifically for APRS-IS (Internet) ONLY connected stations. If you're running APRSISCE/32 connected directly to any sort of RF port (KISS, TEXT, or AGW), the -00 -15 numeric restriction applies. I need to update the -SSID page to make that distinction (added to the ToDo list!)

Lynn (D) - KJ4ERJ



*From:* aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com] *On Behalf Of *K3RWN
*Sent:* Saturday, March 06, 2010 10:08 AM
*To:* aprsisce@yahoogroups.com
*Subject:* [aprsisce] /32 and Mobile Use Problem (Maybe)




I am not sure if this is a /32 problem or a lack of APRS setup knowledge on my part. I have /32 running great on the laptop in my vehicle, however there is one issue. Under Config I have the Mycall-SSID set to K3RWN-9 (the same as MYCALL in the TT4). The problem is I cannot track myself. The program thinks I am at the South Pole and does not update per my GPS position. If I change /32 Mycall to K3RWN-1 and leave the TT4 as K3RWN-9 it tracks great.

Am I missing something in the APRS setup or the /32 setup or is that how it works?

Rich




No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2726 - Release Date: 03/06/10 02:39:00




Re: /32 and Mobile Use Problem (Maybe)

K3RWN
 

I will offer an opinion and Lynn will correct me if I am wrong.  You need a different Yourcall-SSID for each copy that you use; otherwise it won’t know where you are for sure if they are running at the same time.

 

Dave N8PU

 

P.S. found from earlier messages “Re: [aprsisce] 2 instances”:

(Lynn (D) - KJ4ERJ wrote)

EVERY SINGLE APRS-IS CLIENT MUST HAVE A UNIQUE -SSID!  These -SSIDs do NOT have to be between 00-15 and don't even need to be numeric.  I use -AL for my full (ALL) feed, -AP for my APW* watcher, and various others as well.

 

From: aprsisce@... [mailto:aprsisce@...] On Behalf Of K3RWN
Sent: Saturday, March 06, 2010 10:08 AM
To: aprsisce@...
Subject: [aprsisce] /32 and Mobile Use Problem (Maybe)

 



I am not sure if this is a /32 problem or a lack of APRS setup knowledge on my part.  I have /32 running great on the laptop in my vehicle, however there is one issue.  Under Config I have the Mycall-SSID set to K3RWN-9 (the same as MYCALL in the TT4). The problem is I cannot track myself.  The program thinks I am at the South Pole and does not update per my GPS position.  If I change /32 Mycall to K3RWN-1 and leave the TT4 as K3RWN-9 it tracks great.

 

Am I missing something in the APRS setup or the /32 setup or is that how it works?

 

Rich



 

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2726 - Release Date: 03/06/10 02:39:00



Re: /32 and Mobile Use Problem (Maybe)

Lynn Deffenbaugh
 

Rich,

First, as a general rule, each APRS packet generating "thing" should have its own unique -SSID. There's lots of complex reasons for this, but the bottom line is that things can get very confusing if -SSIDs are shared. (http://aprsisce.wikidot.com/ssids)

I'm looking at your RAW packets at aprs.fi:

http://aprs.fi/?c=raw&call=K3RWN-1
http://aprs.fi/?c=raw&call=K3RWN-9&limit=300

You've only actually transmitted 2 packets as K3RWN-1 (at least, that's all that made it to APRS-IS) and neither of those was a position packet. Do you have a GPS configured into APRSIS32? I suspect not, so you might want to just disable tracking on it as it would only support manual position updates of that station.

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.

Which brings me to the next topic. APRSIS32 doesn't have good code to put TNCs into KISS mode. It blindly fires out a few commands that work with some TNC, but not the TT4. For a TT4, it is best to pre-configure the PC's port into KISS mode and tell APRSIS32 to speak KISS over that COM port. According to what I see in -9's raw packets, it looks like you had the TT4 is some sort of Unproto mode where the TT4 added an AX.25 header in front of the fully-formed packet received from APRSIS32. This doesn't work and also implies that you had APRSIS32's TEXT port configured to talk to the TT4. You can do this, but you have to configure the TT4 to not put any additional headers on the packet.

Bottom line: Use different -SSIDs, put the TT4 and APRSIS32 into KISS mode, track the TT4's -SSID (and probably Screen / Tracking / Locked).

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

PS. APRSIS32 fires the following commands when a KISS port is enabled or the program starts. You're TT4 transmitted the commands! If it had been already in KISS mode, it would have ignored them.

2010-03-06 14:37:29 UTC: K3RWN-9>APTT4,W3PIE-3*,WIDE1,WIDE2-1,qAR,N3WWN-3:XFLOW OFF [Unsupported packet format]
2010-03-06 14:37:29 UTC: K3RWN-9>APTT4,W3PIE-3*,WIDE1,WIDE2-1,qAR,N3WWN-3:KISS ON [Unsupported packet format]
2010-03-06 14:37:29 UTC: K3RWN-9>APTT4,W3PIE-3*,WIDE1,WIDE2-1,qAR,N3WWN-3:RESTART [Unsupported packet format]

Here's the packets from APRSIS32 that were put into the body of the TT4's added header:

2010-03-06 14:42:08 UTC: K3RWN-9>APTT4,W3EXW,WIDE1*,WIDE2-1,qAR,N3DXC-1:K3RWN-9>APWW00,WIDE1-1,WIDE2-1:T#003,86,95,2,0,0,11000000 [Unsupported packet format]

2010-03-06 14:47:10 UTC: K3RWN-9>APTT4,W3EXW,WIDE1*,WIDE2-1,qAR,K3WOW-5:K3RWN-1>APWW00,WIDE1-1,WIDE2-1:T#004,89,95,2,0,0,11000000 [Unsupported packet format]

2010-03-06 14:47:11 UTC: K3RWN-9>APTT4,W3EXW,WIDE1*,WIDE2-1,qAR,K3WOW-5:K3RWN-1>APWW00,WIDE1-1,WIDE2-1:<IGATE,CLOSED [Unsupported packet format]

2010-03-06 14:47:44 UTC: K3RWN-9>APTT4,W3EXW,WIDE1*,WIDE2-1,qAR,N3DXC-1:K3RWN-1>APWW00,WIDE1-1,WIDE2-1:<IGATE,MSG_CNT=0,LOC_CNT=1,DIR_CNT=0,RF_CNT=1 [Unsupported packet format]


It appears that you MAY have put APRSIS32 into KISS mode here, but since the TT4 was not in KISS mode, it just transmitted the raw KISS packets as binary body data.



2010-03-06 14:47:21 UTC: K3RWN-9>APTT4,W3EXW,WIDE1,W3PIE-3*,WIDE2,qAR,N3WWN-3:[ binary data ] [Unsupported packet format]

2010-03-06 14:47:25 UTC: K3RWN-9>APTT4,W3EXW,WIDE1,WIDE2*,qAR,K3WOW-5:?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? [Unsupported packet format]

2010-03-06 14:47:30 UTC: K3RWN-9>APTT4,W3EXW,WIDE1,WIDE2*,qAR,K3WOW-5:K3RWN@ARRL.NET [Unsupported packet format]


Finally, you might want to add an > to the front of your comment text or upgrade the TT4 to the latest firmware which I think does this for you automatically.

2010-03-06 14:57:29 UTC: K3RWN-9>APTT4,W3VC-1,WIDE1*,WIDE2-1,qAR,K3WOW-5:K3RWN@ARRL.NET [Unsupported packet format]

2010-03-06 15:07:29 UTC: K3RWN-9>APTT4,W3PIE-3*,WIDE1,WIDE2-1,qAR,N3WWN-3:K3RWN@ARRL.NET [Unsupported packet format]

2010-03-06 15:17:33 UTC: K3RWN-9>APTT4,WIDE1*,WIDE2-1,qAR,K3WOW-5:K3RWN@ARRL.NET [Unsupported packet format]


K3RWN wrote:



I am not sure if this is a /32 problem or a lack of APRS setup knowledge on my part. I have /32 running great on the laptop in my vehicle, however there is one issue. Under Config I have the Mycall-SSID set to K3RWN-9 (the same as MYCALL in the TT4). The problem is I cannot track myself. The program thinks I am at the South Pole and does not update per my GPS position. If I change /32 Mycall to K3RWN-1 and leave the TT4 as K3RWN-9 it tracks great.


Am I missing something in the APRS setup or the /32 setup or is that how it works?


Rich




Re: /32 and Mobile Use Problem (Maybe)

David Shrum
 

I will offer an opinion and Lynn will correct me if I am wrong.  You need a different Yourcall-SSID for each copy that you use; otherwise it won’t know where you are for sure if they are running at the same time.

 

Dave N8PU

 

P.S. found from earlier messages “Re: [aprsisce] 2 instances”:

(Lynn (D) - KJ4ERJ wrote)

EVERY SINGLE APRS-IS CLIENT MUST HAVE A UNIQUE -SSID!  These -SSIDs do NOT have to be between 00-15 and don't even need to be numeric.  I use -AL for my full (ALL) feed, -AP for my APW* watcher, and various others as well.

 

From: aprsisce@... [mailto:aprsisce@...] On Behalf Of K3RWN
Sent: Saturday, March 06, 2010 10:08 AM
To: aprsisce@...
Subject: [aprsisce] /32 and Mobile Use Problem (Maybe)

 




I am not sure if this is a /32 problem or a lack of APRS setup knowledge on my part.  I have /32 running great on the laptop in my vehicle, however there is one issue.  Under Config I have the Mycall-SSID set to K3RWN-9 (the same as MYCALL in the TT4). The problem is I cannot track myself.  The program thinks I am at the South Pole and does not update per my GPS position.  If I change /32 Mycall to K3RWN-1 and leave the TT4 as K3RWN-9 it tracks great.

 

Am I missing something in the APRS setup or the /32 setup or is that how it works?

 

Rich




No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2726 - Release Date: 03/06/10 02:39:00


/32 and Mobile Use Problem (Maybe)

K3RWN
 

I am not sure if this is a /32 problem or a lack of APRS setup knowledge on my part.  I have /32 running great on the laptop in my vehicle, however there is one issue.  Under Config I have the Mycall-SSID set to K3RWN-9 (the same as MYCALL in the TT4). The problem is I cannot track myself.  The program thinks I am at the South Pole and does not update per my GPS position.  If I change /32 Mycall to K3RWN-1 and leave the TT4 as K3RWN-9 it tracks great.

 

Am I missing something in the APRS setup or the /32 setup or is that how it works?

 

Rich


Re: Install an updated version of APRSIS32

Colin Catlin <m6xsd@...>
 

I too like the idea of automatic updates, I have about 5 different copies (for different SSIDs) with copies (Backups) on various machines.

So it would save me a lot of bother keeping track of which are up to date.

 

 

73,

Colin.

 

-----Original Message-----

From: aprsisce@... [mailto:aprsisce@...] On Behalf Of David Shrum
Sent: 06 March 2010 00:32
To: aprsisce@...
Subject: RE: [aprsisce] Install an updated version of APRSIS32

 

 

I like the automatic way of updating. :-)

Dave N8PU


Just download the .ZIP, unzip it, close the client, copy the .EXE in,
and fire it back up. Smiple.

The next revision will have an on-line way to download and apply an
update if you have APRS-IS enabled and have an Internet connection.
Simply pulling up About will tell you if you have the latest or will
offer to download the .EXE directly onto your machine or phone. It also
automatically saves the version you were running with a name that
reflects what version (release date/time) it was. That way, if
something goes worng, you can just delete the new version, rename the
earlier one, and fire it back up.

I might get a periodic automatic check implemented as well which will
send you an internal APRS message when a new version is detected
prompting you to bring up About to download it.

Lynn (D) - KJ4ERJ - On, On, On to More and More Features!

No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2722 - Release Date: 03/05/10
14:34:00


Re: TM-D710 support

Lynn Deffenbaugh
 

James,

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.

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