Custom USB tyre pressure monitoring interface

**Enforcer** · 07-11-2008, 06:29 AM

remove "spare" from the tooltips.

**allypally** · 07-11-2008, 06:52 AM

Originally Posted by Enforcer

remove "spare" from the tooltips.

I was under the impression the the "Left" and "spare" were just comments. How would that effect the display?

**Enforcer** · 07-11-2008, 07:36 AM

The tooltips/comments are also used for alignments, so left in there aligns a label to the left, right aligns it to the right, center centres it.

However having something unexpected in the might cause a problem and it is more likely with an extension plugin label than a standard label.

**allypally** · 07-11-2008, 07:40 AM

Thanks for the explanation. I will give it a try

**Enforcer** · 07-11-2008, 07:42 AM

BTW It's only a suggestion not a definite solution

**Robby BMW** · 07-11-2008, 07:52 AM

As Enforcer said, there are some errors in your skin, try this one:

RoadRunner Skin
RRScreen "TMS"

TMS_OFF.jpg,TMS_OFF.jpg,TMS_ON.jpg,TMS_DOWN.jpg

I01,204,327,115,153,"TMS_ALERT_FL:B"
I02,73,269,98,138,"TMS_ALERT_FR:B"
I03,497,273,63,99,"TMS_ALERT_RL:B"
I04,363,236,56,89,"TMS_ALERT_RR:B"
I05,644,28,138,161,"TMS_ALERT"
I06,694,514,25,15,"TMS_SILENT:B"

B01,630,507,97,86,"TMS_SILENT",""
B02,727,507,67,86,"EXIT",""

L01,433,37,173,28,255,120,0,28,"BMW-E36","TMS_PRESSURE_RR","LEFT"
L02,430,80,123,28,255,120,0,28,"BMW-E36","TMS_TEMPERATURE_RR","LEFT"
L03,30,37,173,28,255,120,0,28,"BMW-E36","TMS_PRESSURE_FR","LEFT"
L04,30,80,123,28,255,120,0,28,"BMW-E36","TMS_TEMPERATURE_FR","LEFT"
L05,433,491,173,29,255,120,0,28,"BMW-E36","TMS_PRESSURE_RL","LEFT"
L06,433,535,123,28,255,120,0,28,"BMW-E36","TMS_TEMPERATURE_RL","LEFT"
L07,30,491,173,29,255,120,0,28,"BMW-E36","TMS_PRESSURE_FL","LEFT"
L08,30,535,123,28,255,120,0,28,"BMW-E36","TMS_TEMPERATURE_FL","LEFT"
L09,623,251,173,28,255,120,0,28,"BMW-E36","TMS_PRESSURE_ST","LEFT"
L010,626,289,117,28,255,120,0,28,"BMW-E36","TMS_TEMPERATURE_ST","LEFT"

Y01,"SLIDER_BATTERY\SLIDER_*.gif"

S01,559,77,47,34,559,77,47,34,H,01,"",0,"TMS_BATTE RY_RR",""
S02,156,77,47,34,156,77,47,34,H,01,"",0,"TMS_BATTE RY_FR",""
S03,559,532,47,34,559,532,47,34,H,01,"",0,"TMS_BAT TERY_RL",""
S04,156,532,47,34,156,532,47,34,H,01,"",0,"TMS_BAT TERY_FL",""
S05,748,289,47,34,559,77,47,34,H,01,"",0,"TMS_BATT ERY_ST",""

END

**Robby BMW** · 07-11-2008, 09:47 AM

Originally Posted by bes51659

I know now that sensors have unique id's (explained in message format description in ..hrm.. post 1) and that id 1-5 labeled sensors can be used in any combination without getting a conflict. The id tag is only a way of remembering which wheel goes where.

LTHDPS quote "If you use the TPMS Doctor, you should be able to see what the sensor IDs are after you teach them."

Q1) So the sensor id 1-5 is stored in the sensor? I did not see the ID in the message description. When is it sent? So the teaching process involves writing to EEProm in sensor? And it does not envolve saving info in PC register or similar? Learning is sensor only and PC is stupid as ever?

Q2) Since I have not seen or preformed the learning process yet I just want to get confirmation that learning is not a pairing of ID 1-5 and wheel position. It is pairing of unique serialno and wheel position. The wheel position is what gets stored in the sensor. Correct?

Q3) I got contact with one sensor (id1) on TMPS doctor 1.2. Why did I get sensor data from one sensor in ambient pressure and not the others?

Q4) I will use RR but I am currently just testing the hardware. Is there a standalone app/skin that will work and look as the RR skin?

***********

PS. Should maybe a thread be started in the "own inventions" subforum or a sticky? I am sure everything has been asked more than once. But finding it is like searching for a needle in a hairstack.

Just to do a bit of clarity on the topic:

Each sensor has a unique internal code (ID) 32 bit long (something like: 12-F5-A3-BC) and doesn't exist two sensors in the world with the same code.

This code is "written" internally in the sensor and can not be changed in any way.

The numbering from 1 to 5 are purely indicative, and has the unique purpose to provide a simple reference to know in which tire has been installed each sensor.

When you perform the "learning procedure", by using the "Configuration Tool" provided with the RoadRunner plugin or by the Centrafuse plugin, the PIC microcontroller stores the sensor ID inside its E2PROM (a non volatile memory), so it is a PIC internal process that doesn't involve in any way the PC.

Also, the device (PIC) will not save any identical sensor ID, so it is possible to replace any sensor with a new one, but not with a sensor already stored, this is just to prevent to store the same sensor in two different positions.

However, if necessary, you can erase the PIC memory through "TPMS Doctor" and repeat the whole "learnig procedure" (if you don't know how to do it, I will explain).

**Lok** · 07-11-2008, 02:09 PM

It looks like a bunch of you are interested in the complete kit, I already have 5 people on the list in just 24hrs

. I would post the link to the waiting list but don't want to risk another infraction...

**Blankstar85** · 07-11-2008, 07:51 PM

Also, the device (PIC) will not save any identical sensor ID, so it is possible to replace any sensor with a new one, but not with a sensor already stored, this is just to prevent to store the same sensor in two different positions.

However, if necessary, you can erase the PIC memory through "TPMS Doctor" and repeat the whole "learnig procedure" (if you don't know how to do it, I will explain). "

Robby

So then how does tire rotation work?? Do i have to delete the PIC and renter or is there a way to switch it, or possibly a way to write it in the plugin, like a check box?