Something is wrong with my LX9000 and outside air temperature (OAT) sensing/reporting. The OAT values in the IGC B-records are on the order of -79C. I have noticed the LX9000 was alerting below freezing temperatures every flight, but ignored the warnings up until now.
I've flown my LS8 for a year. It came to me with an LX9000/V5 that was installed in 2011. I have slowly been learning to use the LX9000 features and recently began using the IGC log files to overlay TAS on GoPro video clips taken in flight. In decoding the IGC B-records I noticed the OAT recorded in the B-records was very low, and when I added a NAVBOX to a map screen and played back one of the IGC files in LXSim, the OAT NAVBOX was indeed showing very low temps. While in the glider I had noticed the LX9000 alerted to below freezing temperature every flight but ignored the alert up until now.
The OAT sensor appears to be stuck against the lower nose skin of the glider with sealant. There is no information in the installation manual about installing this sensor and it's not in the "Packing List" in Section 3 of the user manual. The installation manual wiring diagram for the vario harness does show the OAT sensor, labeled LM335Z.
LM335Z is a Texas Instruments temperature sensor, available for less that $1.00. I doubt the sensor has failed, but I suppose it could have.
There is a "Temperature Offset" in the Vario TE Compensation section of the setup menus, but it has a maximum value of 30C, which isn't close to enough to fix the issue.
The sensor attaches to the vario harness, and must get its power via the vario and convey its temperature signal (voltage) to the vario, but I don't see if the analog signal is digitized in the vario or main unit.
The installation manual says, "When the main unit is connected to the vario and other peripheral units, we can carry out a
functionality test. After power up the vario unit should turn on. Other peripheral units have
their own visual indication, so they will be tested via the main unit."
Is there some sort of peripheral testing going on in the main unit, and if so, how do I access the results?
Has anyone had a similar problem? Was it fixed, and if so, how?
Should I just replace the existing sensor and see if that fixes the issue?
Thanks for any help with this mysterious situation.
Lon Kelly