Thread: Usb tpms

Although the source code for the various plugins is available I don't think the info coming in to them is time stamped.

That would probably have to be coded in the PIC, so you would need to speak to RobbyBMW about that.

Yes, lack of time stamping is indeed a drawback...You never know whether the displayed reading is 1 minute old or 1 month old. I don't think an RTC can be implemented in the existing TPMS HW without major changes.

How about the plugins add time stamp to the Temp/Pressure updates based on PC time?

Thing is, the plugin doesn't know whether it is old info or new info (unless the values have changed)

The hardware stores what it last read, and just sends that.

I had one of the sensors fail on me and realized it only when I did a data reset (which I do often now) via TPMS doctor.

A time stamp when the value changed last would also be helpful than nothing at all. If we see the time stamp which is a few hours old, it at least gives an indication that the reading is stale and it's time to check the sensors.

interesting, how many people would pay for new unit (I believe another $100-$200-$300) with time stamp ability? Count one for me

Originally Posted by DigitalVampire

I had one of the sensors fail on me and realized it only when I did a data reset (which I do often now) via TPMS doctor.

I guess I take this for granted since my tablet refreshes the receivers every time I change cars.

Originally Posted by DigitalVampire

A time stamp when the value changed last would also be helpful than nothing at all. If we see the time stamp which is a few hours old, it at least gives an indication that the reading is stale and it's time to check the sensors.

This could easily be coded into your exectbl.ini using RRCode if you're just checking if a value has changed and then you can do your own timestamp. I use something like this to monitor "Powermon" PI so my system changes state "Play/Pause" and screen off/standby/hibernate based on the change of a variable sent to RR from the PI.