Message-ID: <19980929191732.15040.qmail@www08.netaddress.usa.net>
Date: Tue, 29 Sep 1998 19:17:32
From: Dan Schaefer <dfschaefer@usa.net>
To: lancair.list@olsusa.com
Subject: Another potential date problem for some GPS units
Mime-Version: 1.0

          <<<<<<<<<<<<<<<<--->>>>>>>>>>>>>>>>
          <<  Lancair Builders' Mail List  >>
          <<<<<<<<<<<<<<<<--->>>>>>>>>>>>>>>> 
>>
While looking around the Allied Signal Web site for any data on the 
Y2K and Date roll-over problems, I came across Service Memo #359, 
apparently published this month, with the Subject line referring to
"Leap Year Date Anomaly - Jan 32". The jist of the SM says that on 
February 1 of any leap year, including year 2000, the units will 
display a "System Error" and WILL BE INOPERATIVE FOR THAT DAY. (Their
emphasis). The SM explains that it's a software glitch causing an 
incorrect leap year calculation resulting in computing that date as
January 32. The SM also states that the anomaly will correct itself
the next day and operate normally on Feb 2.
The units affected are their KLX 135 and KLX 135A with specific 
Software mod levels installed. The SM also states that the same 
receivers with later S/W mod levels are not affected and that the two
receivers can be upgraded to the later mod level. To be sure to 
get the straight poop on the various S/W versions, if you have one of
these GPS's in your panel, as I do, you should check out the SM at:

"http://www.alliedsignal.com"

and then follow the buttons to the Service Memo.

There was one thing that the SM seemed a bit confused on and that was
identifying the KLX 135 as a GPS/Comm. I'm sure that one is GPS only
while the KLX 135A includes the Comm Tranceiver. Doesn't matter much
to the GPS section but I intend to ask about it anyway, and will post
what I hear.

Cheers,

Dan Schaefer


____________________________________________________________________
Get free e-mail and a permanent address at http://www.netaddress.com/?N=1