The TPMS Doctor doesn't include the learning procedure, but you can use the configuration tool provided with the RoadRunner plugin.
It works with any front end, because the learnig procedure is an internal proces to the PIC, independent from any external software.
Simply launch the application and perform the learning procedure, ignoring everything else that refers to the configuration of the plug-in for RoadRunner.
_______________________________________
Car installation 95% [■■■■■■■■■■■■■■■■■■■■]
Current project: Parking sensor USB interface
If you don't like cables, you can use some alkaline batteries
I joke
The USB port provides the power supply to the receiver only if it is removed from the original display and installed on the TMS-USB board, but if it keeps inside the original display, a power cable is needed.
_______________________________________
Car installation 95% [■■■■■■■■■■■■■■■■■■■■]
Current project: Parking sensor USB interface
HiJackZX1 w/ The Tobiathin Core PC system!
ZOTAC GF9300-G-E
INTEL E8200
4 Gigs
OCZ Vertex 2 SSD
OPUS 320
1 Lilliput, 1 MTSVO-SC K301, 4 VM70 screens, 1 Eonon 19in
Starting Raspberry Pi multizone project.
Just ordered the last TPMS from Viva that they had in stock.. Coupon code still works though =]
cashtexts - Earn money for receiving text messaged offers
cashtexts review not a scam
Space Navigator - 6 Axis input device: Take it apart - Driver App
RRCam - Video/webcam capture, text overlay, and recording: 2.0 Stable
Robby,
I've completed the learning procedure using the RRTMS config tool and now the sensors are correctly coupled with their respective colors. As you may know I was using the "garden" method to wake up the sensor because I still don't have them mounted in the car wheels (thanks Glitchinthesyst for the idea).
[Note for others that are in the same situation: I inserted each sensor in plastic container and put it under pressure while the other sensors were placed in a isolated metal box, just to be sure;I then fired the learning procedure on the software and at the same time lowered the pressure in the cointainer to let the sensor send its data and register it.]
After having registered all the sensors I've tested them putting them all togheter in the plastic container and then raising and lowering the pressure just to be sure everything was okay.
In this situation I've noticed that in some cases the data showed by the TPMS Doctor was not consistent. I mean that sometime the pressure values from the sensors where not equal (they were supposed to be equal because they were in the same container!): some of them remained for a long time at the old value, sometime it was only for 10 or 15 seconds, sometime for much more time (I could probably dare to say for ever, at least minutes!).
As you may understand this is pretty important as I would like to be notified of a pressure change as soon as it happens!
Do you believe that this problem is related to having all sensors at short distance (inside the container) and thus could their radio transmission be jammed by each other? Or could it be that the firmware on the PIC does not handle batch of changes all at the same time (in a real situation I suppose this is not common)...
Thanks for your comments.
Diego.-
I powered up my TPMS to check the function...
Prior to it learning the sensors, does it read 'dead' on pressure, temp and battery? Specifically, the battery...I need to know (before going to the tire shop) that the batteries are okay in the sensors...
Can this only be accomplished after the learn function?
Thanks
Hey Delta...how'd you pressurize this 'container'? Would a large mouth Coke bottle work if I just applied pressure with my mouth over the opening?
Yes, as far as I know you have to "learn" the sensors before you can read any of the values.
I've used a garden hand sprayer with a wide filler mouth like this:
The mouth is big enough to insert the sensor.
I don't think the coke bottle will work because you would need to apply a fairly large amount of pressure.
The problem is not due to the short distance of the sensors, but to the simultaneous transmission.
The PIC firmware analyzes any signal coming from the receiver, in the same way the original display does, but if there are more transmissions at the same time, the result is the sum of the various signals, then garbled data. It is a physical fact.
About the issue that you had during the learnig procedure with the Centrafuse plugin, there is a new update that should solve that problem. Take a look here: http://forums.fluxmedia.net/showthread.php?t=2356
_______________________________________
Car installation 95% [■■■■■■■■■■■■■■■■■■■■]
Current project: Parking sensor USB interface
So this is a design limitation, am I correct? Anyway I suppose it does not happen in the real world, unless you drive an F.1 car and have 4 mechanics working at the 4 wheels at the same time
About the Centrafuse plugin I've already noted and installed the new release by Wolfgang, thanks. It's a nice piece of software!
Bye,
Diego.-
Bookmarks