So I set up my Hex-Net to log transmission temperature and started a gps track recording at the same time and drove over a mountain pass. Transmission temp is pathological obsession of us Eurovan owners. Then I wrote some code to merge those logs into a kml file for Google Earth. That's done, but there were some issues. My complete log is here https://s3.amazonaws.com/docbucketjmb/VegasLog.csv If you have Google Earth installed on a computer, the kml file I created is here: https://s3.amazonaws.com/docbucketjmb/atflog.kmz . Anyway, these are the issues:
- values are separated by spaces, not commas
Each entry looks like:
Code:,1743.63,070 009 005 057 003 080 093 104 112 120,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
- temperature values seem implausibly low
I assume the first value in the group of ten is the ATF temp in degrees C. My code converts to F for the kml file. The entry I show above is the highest value in the log. Consensus in the Eurovan Owners Unite! facebook group is that this seems too low to be valid. Are you guys sure you're reading the right sensor? Everybody seems to agree that this scangauge setting is right. I'll be doing some tests later comparing hex-net to my old scangauge.