Thread: Custom USB tyre pressure monitoring interface

@ Almera: Oh, no worries - hope it works for you, sometimes the sensors needs some pressure change over a specific period of time before they will activate and send readings, otherwise they might do so when you go over a bumpy road, for example, which can/will give false readings if the sensors are not filtering these "spikes"

Let us know how you go.

@ Robby: Looking very good, I will test it when I get home the afternoon, just started the day at work Down Under - and I was pleasantly surprised to see the software ready when I loggen on

Thanx again for your efforts, it is appreciated!

Originally Posted by juve021

Wait so Robby, can I use this to test my receiver if I DO NOT have the sensors installed in my wheels?

You can test your receiver with this program outside RoadRunner, but remember that to "wake" the sensors, the pressure needs to be increased above 1.5 bars.

Basically the sensors operate in 5 different ways depending on the situation:

1. Storage mode: If the pressure is below 1.5 bar, pressure is measured every 60 seconds but no data is sent. If the pressure increases above 1.5 bars, the sensor shifts into the Initial mode.

2. Initial mode: This mode occurs if the pressure increases above 1.5 bar from Storage mode. In this mode, pressure is measured every 0.85 seconds and data is sent every 0.85 seconds. This sequence is repeated 256 times. After the sequence is repeated 256 times, the sensor shifts into the Normal mode only if pressure is above 1.5 bar. If the pressure is below 1.5 bar, the sensor will shift into the Storage mode.

3. Normal mode: Pressure is measured every 3.4 seconds and data is transmitted every 60 seconds. If the measured pressure differs by more than 200 mbar from the reference taken every 60 seconds, the sensor enters a Pressure Alert mode.

4. Pressure Alert mode: It is the same measurement and transmitting pattern as the Initial mode.

5. High Temp Alert mode: If the temperature exceeds 120°C, the sensor device enters into the same measurement and transmitting pattern as the Initial mode.

@ Petter: You can adjust the upper/lower limits at which the alarms will activate.

@ Fmode: Are you running the config tool in windows, and not having RoadRunner installed? If that's the case, it won't abort the learn - you must have Roadrunner up and running, before you can run config tool - in the above screenshot, with the test-routine, it seems all is well with your setup.

Is your 5th sensor installed in the spare tyre, or not?

Anyway, for those unsure how to do their own conversion kit, look at page 9 in my Project Log, I made a nice how-to, with plenty pics, on how to marry the 3rd EYE TPMS to Robby's USB interface board.

Post questions there if you have any.

Originally Posted by FMode

Played around with the air in my tyres but the config tools doesn't want to abort its Learn procedure... I don't know whats going on because the new tool also doesn't change any values. I only have this screenshot.
I would like to read my ID 001C40F7 sensor somewhere...

Your screenshot shows that everything is working well, the only strange thing I can see is a discrepancy between the pressure detected by the sensor number 1 and the related raw data, but it may be a bug in the program and not a problem with your setup, I have to check this.



The reason because the config tools doesn't want to terminates the learning procedure is because the system will not save any identical sensor ID, and since all your sensors are been succesful paired the first time, if you try to start the learning procedure again, the device will be waiting for a new sensor with an new ID other than the ones already stored in the PIC (this is the case when a sensor needs to be replaced with a new one).

Another important thing, unlike what most people think, is that the config tool can be used also without having RoadRunner installed.
Indeed the program is basically divided into two parts, the first is for setup the parameters in the ini file handled by the RoadRunner plugin (measurement units, warning thresholds, etc), and the second is for "the learning procedure" that is completly handled by the firmware on PIC, regardless of the software used to display the data.

Finally, the sensor IDs are stored in the E2PROM of the PIC for internal use, and there is no way to read them through the USB port, at least without make some change in the firmware, but this is not essential for the normal use of the device.

That clears a few things up, thanx Robby

So we can actually use the config without RR, which is what I first tried, but it did not do anything for me - only after having RR installed, and the app running, could config tool stop flashing abort sequence....

But, probably 99% something I have done wrong with the pairing process then, will check it out and feedback.

Thanx.