You must run the config tool alone without Road Runner.
It is important, to ensure at the Config Tool exclusive access to the device.
It means that the sensor has not been yet paired.
The data should be already updated after the pairing procedure.
You must run the config tool alone without Road Runner.
It is important, to ensure at the Config Tool exclusive access to the device.
It means that the sensor has not been yet paired.
The data should be already updated after the pairing procedure.
_______________________________________
Car installation 95% [■■■■■■■■■■■■■■■■■■■■]
Current project: Parking sensor USB interface
_______________________________________
Car installation 95% [■■■■■■■■■■■■■■■■■■■■]
Current project: Parking sensor USB interface
Ok Robby, thats what I thought. I have a feeling that I damaged the receiver board when I chopped it off of the 3rd eye.
If I order a new 3rd eye and connect the jp2 pin to the data pin on the 3rd eye wire harness, I don't use the config tool to learn the sensors right? Because I just do the learn procedure through the 3rd eye and the data is just sent to the PIC via jp2?
Ok, never mind.
I just read this:
Robby, Dejan or anyone else...
So I have built the interface and paired sensors and I have initial values for the sensors but today I went to adjust my tire air pressures and the values using the TPMS Doctor, did not change and have not changed at all! Whats going on? Why isn't it refreshing with new values?
_______________________________________
Car installation 95% [■■■■■■■■■■■■■■■■■■■■]
Current project: Parking sensor USB interface
Thanks, Robby. Probably it is what happened: I connected the device before starting the software.
Anyway, I'm testing the kit using the "garden" method suggested by Glitchinthesyst (thanks!) and I'm having confusing results.
The learning procedure (done via the Centrafuse plugin by Wolfgang) looks like complete successfully, but then I don't get data from the sensors.
In two cases I get data which apparently did not belong to the correct sensor. I mean I was working with the yellow sensor and TPMS Doctor showed data coming from the green one (apparently the data was correct). In another situation the CF plugin raised an alarm for a low pressure on the 5th tire sensor (that I don't own!).
What can be wrong ?
Can the TPMS Doctor perform the learning procedure ? I would rather use a single tool just to avoid confusion in the confusion!
Thanks,
Diego.-.
Ok, in this case, check this two things:
1) The connection to the display must be done as in the picture below.
2) The display must be powered at least trough the RED and the BLACK cables.
Now, launch the configuration tool (without RoadRunner) and perform the learning procedure for each sensor, as described in the program.
_______________________________________
Car installation 95% [■■■■■■■■■■■■■■■■■■■■]
Current project: Parking sensor USB interface
Robby,
I could not find where is described the TPMS Doctor learning procedure, could you please shade some lights on this subject?
Thanks,
Diego.-
[EDIT]
Do you refer by chance to the RRTMS Config Tool? Do the registration did with it works even with the Centrafuse plugin?
[/EDIT]
Is a power cable needed for people that decide just to use the USB board and reciever and not the LCD screen? I figured that the USB port is what supplied power.
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.
Bookmarks