[OZAPRS] Getting UI-VIEW to Igate ISS traffic ?

Tony Hunt wavetel at bigpond.com
Mon Mar 14 21:07:58 EST 2005

Well quite right as Andrew and others pointed out ..
Its Mic-E .. I realised that after sending the mail and reading a few other 
replies .. Flame on ..

Its just that Ive never seen it plot on a map in Ui-view and I dont go 
looking at 0 0 very often .. Its all been explained .. I am used to seeing 
Mic -E frames starting with S so it never clicked into place ..

----- Original Message ----- 
From: Noel Rowe <mailto:noel-r at clear.net.nz>
To: Tony Hunt <mailto:wavetel at bigpond.com>  ; ozaprs at marconi.ics.mq.edu.au
Sent: Monday, March 14, 2005 7:38 AM
Subject: Re: [OZAPRS] Getting UI-VIEW to Igate ISS traffic ?

Tony said:-

>These frames are the classic Poppo frames from ISS .. They dont
>contain any position info .. They are not even APRS compliant really ..
>Have a look at the destination callsign .. P0PPP0 .. Whats that ??
>It does not even start with AP ..

The APRS Protocol Reference Document, chapter 10, page 42: Mic-E Data Format 
explains that.  For mic-e the destination field get a different use.

In the case of the ISS beacon, P0PPP0 is allowable and decodable.

As previously pointed out, UI-View has a lock out for any beacon that has 
both 00 N/S and 00 E/W.  Most other programs, and the Kenwood TH-D7 and 
TM-D700 pair, will decode it.  It is a D700 sending it down to us.  If only 
they would hook up a GPS to it!

Noel, ZL3GR.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://second.aprs.net.au/pipermail/ozaprs/attachments/20050314/c7f1307f/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT06874.txt
Url: http://second.aprs.net.au/pipermail/ozaprs/attachments/20050314/c7f1307f/attachment.txt 

More information about the Ozaprs mailing list