Custom USB tyre pressure monitoring interface - Page 20

mrbean_phillip · 02-04-2008, 03:51 AM

Quote:

However, at the end are you were able to pair the sensors?

Yep, I made a custom pressure chamber from PVC piping, and end-caps, and use a small compressor to get the pressure to around 2bar (28psi/200kpa), and just tested one sensor, which worked very well.

Both pressure (6F=1.775bar) and temp (43=27deg C) displays proper, and battery seems fine too.

Using this little pressure chamber, I will convert it to use a simple bicycle pump to pressurise it for testing units at home before shipping them

Thanx again!

Robby BMW · 02-04-2008, 08:45 AM

Quote: Originally Posted by mrbean_phillip

Yep, I made a custom pressure chamber from PVC piping, and end-caps, and use a small compressor to get the pressure to around 2bar (28psi/200kpa), and just tested one sensor, which worked very well.

Both pressure (6F=1.775bar) and temp (43=27deg C) displays proper, and battery seems fine too.

Using this little pressure chamber, I will convert it to use a simple bicycle pump to pressurise it for testing units at home before shipping them

Thanx again!

Ahahahaha!!

Great invention!
It is exactly what I would have had to use during the firmware development.

mrbean_phillip · 02-04-2008, 03:52 PM

I could have made and shipped you one, but the Federales might think it's intended for something else - rofl.

But, on a sidenote, I will take my UTE to have the 5 sensors installed, and load the config software on the Carputer as a final test. But very happy so far.

I am just awaiting beta-release of the CentraFuse plugin Wolfgang is developing over at Fluxmedia.net, then I can go finalize the hardware side of things.

I still need to make the daughterboard for my uBlox-based deadreckonong GPS, but at least I managed to source the Gyro locally, so that can go ahead to.

Now to get the Siemens TC35 modem going for the security/tracking side of things.

Ah well, all in good time

Talk to you later.

WuNgUn · 02-04-2008, 05:54 PM

Anyone doing development with the Valet system?
I noticed the 3rd Eye is now $250? Did it come down in price?

DaveDog · 02-04-2008, 06:20 PM

Valet development is being attempted, results have not been spectacular so far...

mrbean_phillip · 02-04-2008, 11:06 PM

Hello Robby,
Ok, I have tested AllyPally's kit that I have assembled, but used my pressure sensors, and still unassembled kit, with original display, to compare values.

As you can see, the one TPMS Doctor also reads sensor 2 hex data incorrectly, but displays it proper - I have verified this against the unassembled TPMS RF Receiver - so most likely a small bug somewhere in TPMS Doctor, same as the descrepancy Fmode's had a few replies back.

Other than that, things went pretty well, and I am glad AllyPally's is now confirmed working, I have not tested/paired sensor 5, which is the spare wheel, but confirmed that yesterday with his own transducer.

Well, just thought I'd feedback, and let you know about the small descrepancy.

Take care, talk to you later again.

Br,
MrBean

Robby BMW · 02-05-2008, 09:23 AM

Quote: Originally Posted by mrbean_phillip

Hello Robby,
Ok, I have tested AllyPally's kit that I have assembled, but used my pressure sensors, and still unassembled kit, with original display, to compare values.

As you can see, the one TPMS Doctor also reads sensor 2 hex data incorrectly, but displays it proper - I have verified this against the unassembled TPMS RF Receiver - so most likely a small bug somewhere in TPMS Doctor, same as the descrepancy Fmode's had a few replies back.

Other than that, things went pretty well, and I am glad AllyPally's is now confirmed working, I have not tested/paired sensor 5, which is the spare wheel, but confirmed that yesterday with his own transducer.

Well, just thought I'd feedback, and let you know about the small descrepancy.

Take care, talk to you later again.

Br,
MrBean

Thank you for your feedback, it was very useful to found the bug in the program.
I just compiled a new release (1.10) with this issue solved and some improvements added.
It is available for the download at the same link in this post.

mrbean_phillip · 02-06-2008, 05:24 AM

Hello Robby,
Good work, the new release seems to be quicker at detecting the data once you clear the data from the PIC Eprom - maybe my imagination, but working pretty well, and I can comfirm that it is now detecting the sensor pressure data correctly, same with temperature.

The only small hiccup still is something with the battery data on sensor 3, also had this descrepancy with version 1.0.0. According to the original receiver display, all battery levels are good.

I have made this unit using the data-out pin on the RF unit, and not seperated the rf board from the system. This way I can have both original LCD, and Carputer for comparison - will still cut the board and solder it to the PIC pcb, but for now it makes for a handy comparison device.

Anyway, here is a screenshot of V1.10.

Robby BMW · 02-07-2008, 01:04 PM

Quote: Originally Posted by mrbean_phillip

Hello Robby,
Good work, the new release seems to be quicker at detecting the data once you clear the data from the PIC Eprom - maybe my imagination, but working pretty well, and I can comfirm that it is now detecting the sensor pressure data correctly, same with temperature.

The only small hiccup still is something with the battery data on sensor 3, also had this descrepancy with version 1.0.0. According to the original receiver display, all battery levels are good.

I have made this unit using the data-out pin on the RF unit, and not seperated the rf board from the system. This way I can have both original LCD, and Carputer for comparison - will still cut the board and solder it to the PIC pcb, but for now it makes for a handy comparison device.

Anyway, here is a screenshot of V1.10.

It seems that the data inside the 3rd byte are more complex then I believed, especially the battery level that seems to not be coded as expected.
I need a time to better analyze the data from sensors. I will you know.

mrbean_phillip · 02-07-2008, 03:13 PM

Thanx Robby,
After testing the CF plugin too, it exacts the same behaviour, and I think there may be a slight problem with the way the PIC reads the datastream from the RF-Receiver.

Using the original LCD-based display, all batteries seems to be accurate.

Thanx for looking

Robby BMW · 02-08-2008, 11:41 AM

No, the PIC firmware is ok, it transmits only the raw data received from sensors to the PC, and CRC confirms that the data are correct. The problem is in the PC software that doesn't convert properly the data.
I've compiled another release (1.20) (available here) that should resolve definitely the problem.
The CF plugin has the same bug because it is based on the source code of my RoadRunner plugin that is buggy too, so I have released also a new version of the RoadRunner plugin with the bug fixed.