<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6487.1">
<TITLE>Re: New Request for findU... Mic-E Decoding</TITLE>
</HEAD>
<BODY dir=ltr>
<DIV>Maybe I'm missing something...</DIV>
<DIV> </DIV>
<DIV>I'm looking at the find.cgi page. My truck (KF4OTN-14) is sending
Mic-E packets. I can't tell if the status text is ENROUTE, IN SERVICE,
EMERGENCY, etc. Maybe I'm using the wrong word to describe that... I
also do not see my lat/long.</DIV>
<DIV> </DIV>
<DIV>Just food for thought... </DIV>
<DIV> </DIV>
<DIV>Eric</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT size=2>-----Original Message----- <BR><B>From:</B> Steve Dimse
[mailto:k4hg@tapr.org] <BR><B>Sent:</B> Sun 05-Dec-04 16:53 <BR><B>To:</B>
Christensen, Eric <BR><B>Cc:</B> aprssig@lists.tapr.org <BR><B>Subject:</B>
Re: New Request for findU... Mic-E Decoding<BR><BR></FONT></DIV>
<P><FONT size=2>On 12/5/04 at 4:16 PM Christensen, Eric
<CHRISTENSENE@MAIL.ECU.EDU> sent:<BR><BR>>Hope this isn't too late
for development purposes, but can you have findU<BR>decode<BR>>the Mic-E
packets on position requests so it shows the lat/long, status,
etc<BR>>along with the raw packet?<BR><BR>Not sure I understand, findU
already decodes the lat/lon, the comment (not<BR>status, which is sent as a
separate packet starting with '>') is plain text<BR>visible in the raw
packet. If you are asking to see the lat/lon of reports, that<BR>is available
through posit.cgi. If you are asking to see lat/lon in text form
on<BR>find.cgi, that would be meaningless clutter to the vast majority of
people<BR>viewing that page. If it is something else, please explain
more...<BR><BR>Steve K4HG<BR></FONT></P></BLOCKQUOTE>
</BODY>
</HTML>