On Wed, Oct 12, 2011 at 11:50:42PM -0600, we recorded a bogon-computron 
collision of the <[email protected]> flavor, containing:
> On Wed, Oct 12, 2011 at 11:28:59PM -0600, we recorded a bogon-computron 
> collision of the <[email protected]> flavor, containing:
> > On Thu, Oct 13, 2011 at 01:26:00AM -0400, we recorded a bogon-computron 
> > collision of the <[email protected]> flavor, containing:
> > > If the o/ISS doesn't get it (I've had mixed luck with non-9-character 
> > > object names, maybe o/ISS*?), try a b/KJ4ERJ-15 which is the source of 
> > > the object.  They're going out every 2 minutes, but you won't see them 
> > > at aprs.fi as Hessu seems to be having some sort of backlog issue with 
> > > his Raw packet display.
> > 
> > I'm using a connection to rotate.aprs.net port 14580.  Just switched the 
> > filter to b/KJ4ERJ-15.  Will let you know.
> > 
> 
> There we go, I just started getting the ISS objects.  Sad to say, none of the 
> multiline data showed up on screen.
> 
[...]
> 
> According to the spec, object comments can only be 43 characters long, and
> if you strip off the " }k1k" that describe the line type, color, and scale,
> and the "{sssss" characters for sequence, that leaves only 32, enough for
> 16 lat/lon pairs.  Your strings have 38 chars (19 lat/lon pairs) there.

I see where this confusion might come from.  The Multiline page makes a claim
that there is room for 46 characters of point data, but the APRS spec 1.0.1
page 58 clearly states that only 43 characters *total* are available for
objects without data extension.

Xastir is clearly not accepting more than 43, as when your packets are parsed
the sequence is stripped off, making it not recognizable as multiline.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 "One man alone can be pretty dumb sometimes, but for real bona fide
 stupidity, there ain't nothin' can beat teamwork." - Edward Abbey

_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Reply via email to