“You can click N to exit to Scan Mx-Sensor page and then press Up or Down button to return to the main page.”    I already went back to 2.68, but exiting other program functions only require pressing the ‘N’ button.  So having to also use the up or down button to exit is not very intuitive for the user.   Not a big deal, since I don’t plan on ever using any MX-sensors.

“I am sorry, because there will be something wrong if the tyre pressure showing in the tyre like following picture, so in the new version, we have removed it. Please understand.”    I think that must be a marketing decision, as I see no technical reason for not providing the pressure results on the graphic suddenly now, when it was provided on earlier firmware versions.  I’m not likely to buy your more advanced tool just to get this feature.  Very disappointed.

These TPMS tools seem to be targeting the commercial businesses like tire/brake shops.  I was thinking about making my own Personal TPMS tool.  It looks easy to do for a couple cars using the Infineon TDA5235 radio chip which has FSK, ASK, and Manchester decoding.  For a personal TPMS decoding tool, I’d want to have features like:  For each car’s data set, user input of calibration offset settings for pressure and temperature at each wheel. Also would be nice to have for each wheel, cold tire pressures estimated at each wheel based on current sensor temperature readings.

Billy,

No, they are keeping the graphic image of the car which shows the progress of each wheel.  What they have removed is the actual pressure read by each wheel which was previously shown in a smaller font.  You can still see the results of all four wheels in a two page tabular format by pressing the ‘Y’ button.

They didn’t say, but it could be that the firmware programmer is running short of program space (flash memory) of the TS401.  Before they were using two font sizes, now they are only using one. The more fonts they store, the less space is left for adding more program features. Font characters are usually stored in program memory as bit-mapped data.  If memory is running low, they could store the fonts in compressed format using 4 or 8-bit run-length encoding.  

If they are not very proficient in programming, there is plenty of space on the display for the pressure at each wheel using three characters (kPa) with the font size in use, they just need to narrow the car graphic image slightly.