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


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





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




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


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


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