Roadster 2.x TPMS Tool

[markwj]

@markwj - We received the TPMS board last week and installed/configured it today. Our OVMS did require a jumper. Installation was fairly straight forward with your instructions. We verified it's operation with the "TPMS read" command. Everything works! Thanks again!!

Very cool. You are, I think, the first from the production batch. Glad the shipping wasn't too messed up.

The picture will be helpful for those others who require that jumper.

 

[markwj]

Okay, I just watched this video here and it doesn't look too bad. I need to get a more precision tip for my soldering iron though. @markwj can you confirm I have the correct pins circled below? Also, what gauge insulated wire should I use?

Looks like your DA26 pin is wrong. Please refer to Nvbob's earlier post, for his picture of the correct pin. This is probably one of the easiest soldering jobs you would ever have to do.

 

[Roadster]

I'll definitely give it a try. To avoid any confusion, @TEG / mods, pls delete the annotated photo I uploaded to my previous post here so no one inadvertently solders the jumper to the wrong DA26 pin using that as a reference, thx.

 

[TEG]

I'll definitely give it a try. To avoid any confusion, @TEG / mods, pls delete the annotated photo I uploaded to my previous post here so no one inadvertently solders the jumper to the wrong DA26 pin using that as a reference, thx.

I removed the photo from that post. Hopefully it is the way you want it now.

 

[Roadster]

Perf, thx @TEG.

@markwj - just received the TPMS board today. I'll make sure to follow @Nvbob's jumper installation to the correct pins.

 

[Nvbob]

Before soldering I noticed the surface of the OVMS module was "shiny" due to the clear surface applied to it. I took a very small piece of 330 grit sandpaper and removed the clear coating on the connectors. I then referred to @Roadster's link to soldering to make sure there were no issues. I tinned both the connectors (DB9 & DA26) and the wire ends prior to soldering the wires on. After that, soldering the wire to the connectors was a piece of cake.

 

[Roadster]

Soldering complete (I hope ) and TPMS board is attached. Now...what should the switch (#1) and dial (#2) be set to for a 2.5 RS?

 

[drewski]

Hmm,

maybe i do need to break out the soldering iron.

"Error: TPMS IDs could not be read from the vehicle (or not implemented)"

Soldering complete (I hope ) and TPMS board is attached. Now...what should the switch (#1) and dial (#2) be set to for a 2.5 RS?

View attachment 571236

i left them in those default positions.
Tesla Roadster — Open Vehicles documentation

 

[Roadster]

Ah, thx @drewski. BTW, I believe you said your main board was from July 2018 which means you shouldn't have to solder so hopefully it's something else

Pasting the info from the link below for future reference (hope you don't mind @markwj):

TPMS Option
Reading and writing TPMS wheel sensor IDs from/to the Baolong TPMS ECU is supported in v2.x Tesla Roadsters using the optional OVMS K-Line Expansion Board. You will need a v3.2 module (or v3.1 module labelled on board as July 2018 or later, with K-line pin connected), and an OVT1 vehicle cable (clearly labelled with “OVT1” on the cable).

The optional OVMS K-line Expansion Board should be configured with SW1 set to position #2 (LDO 5v), and S1 in to OFF position (away from the ON label).

To read the current wheel sensor IDs from the Baolong TPMS ECU, ensure that the ignition switch is ON (so instrument panel lights are on), and issue the ‘tpms read’ command in OVMS.

Similarly, to write wheel sensor IDs to the Baolong TPMS ECU, ensure that the ignition switch is ON (so instrument panel lights are on), and issue the ‘tpms write’ command in OVMS.

Note that this functionality will not work with v1.5 Tesla Roadsters (that use a different TPMS ECU to the v2.x cars).​

 

[drewski]

Ah, thx @drewski. BTW, I believe you said your main board was from July 2018 so you should be fine with no need to solder

<snip>

yep. installed this evening and working OK!

i thought i might have to solder until i found the manual and saw i needed to turn the ignition ON!

 

[JohnGarziglia]

Cable Available: 9665972 OVMS Data Cable for Early Teslas official OVMS parts / Tesla Roadster v1.x/v2.x/v3.x & early Model S compatible.

I received my board this week and will be installing it later today or tomorrow. I also ordered the new cable with the OVT1 label on it as I was unable to get under my dash to see what cable I actually had before ordering. Turns out I already have the OVT1 cable in my roadster from the last time I upgraded my OVMS.

The cable cost me $15.05. If you need it and you are in the US, I will send it First Class mail to you if you PayPal me $15.05 (or make an offer). Please PM me. Otherwise, it will just sit in a parts bin and not be used.

 

[Roadster]

@markwj / @Nvbob - I’m getting the error msg show below when initiating the “tpms read” command. I just updated to 3.2.013 as well so thoughts on what might be wrong?

ERROR: TPMS IDs could not be read for the vehicle (or not implemented)

 

[JohnGarziglia]

Hi,

I need help with the tpms write' command.

The command tpms read command works great. I had found that when previously inserted the numbers using the temporary TPMS tool, I reversed the LR and RR so I am now trying to correct that, switching around 0806685d and 08066929.

-- I get an error message of "Tyre set .... not found" with 'tpms write' (see red text). What am I doing wrong.

-- Also, to clarify, should the order of the TPMS sensors be: LF,RF,RR,LR or have I got that wrong?

-- And while on this subject, what is the function of the "list" and the "set" commands - can our TPMS now have different tire sets and be able to switch between them?

Usage: tpms delete|list|read|set|status|write

I (899485) webcommand: HttpCommandStream[0x3fa40f0c]: 1872464 bytes free, executing: tpms read
OVMS# tpms read
TPMS read as 08066968,080668e2,0806685d,08066929
I (901935) housekeeping: 2020-08-02 16:09:52 EDT (RAM: 8b=79628-81732 32b=24840)
I (936445) webserver: HTTP POST /api/execute
I (936455) webcommand: HttpCommandStream[0x3fa4c5dc]: 1881884 bytes free, executing: tpms write 08066968,080668e2,08066929,0806685d
OVMS# tpms write 08066968,080668e2,08066929,0806685d
Error: Tyre set '08066968,080668e2,08066929,0806685d' not found
I (942845) ovms-server-v2: Send MP-0 S94.0,M,0,0,stopped,standard,159,147,70,0,0,20,2,21,0,0,0,0,136.33,0,0,0,0,0,0,0,0,0,0,0,0,0.00,0.00,81
I (942855) ovms-server-v2: Send MP-0 D204,32,5,29,28,28,3124,1054586,0,0,28,3,1,1,13.17,0,11.5,0,29,0,0
I (942865) ovms-server-v2: Send MP-0 F3.2.013/ota_0/eap (build idf v3.3-beta3-775-gdc1ca69 May 31 2020 17:27:06),5YJRE1A18B1001243,0,1,TR2N,CI523
I (979005) webserver: HTTP POST /api/execute
I (979015) webcommand: HttpCommandStream[0x3fa3d468]: 1889936 bytes free, executing: tpms write
OVMS# tpms write
Usage: tpms write <set>
I (993895) webserver: HTTP POST /api/execute
I (993905) webcommand: HttpCommandStream[0x3fa4c614]: 1881060 bytes free, executing: tpms write 08066968,080668e2,08066929,0806685d
OVMS# tpms write 08066968,080668e2,08066929,0806685d
Error: Tyre set '08066968,080668e2,08066929,0806685d' not found
I (1003845) ovms-server-v2: Send MP-0 S94.0,M,0,0,stopped,standard,159,147,70,0,0,20,2,21,0,0,0,0,136.33,0,0,0,0,0,0,0,0,0,0,0,0,0.00,0.00,81
I (1003855) ovms-server-v2: Send MP-0 D204,32,5,29,28,28,3124,1054586,0,0,28,3,1,1,13.16,0,11.5,0,29,0,0
I (1003865) ovms-server-v2: Send MP-0 F3.2.013/ota_0/eap (build idf v3.3-beta3-775-gdc1ca69 May 31 2020 17:27:06),5YJRE1A18B1001243,0,1,TR2N,CI523
I (1017185) webserver: HTTP POST /api/execute
I (1017195) webcommand: HttpCommandStream[0x3fa414b0]: 1870004 bytes free, executing: tpms read
OVMS# tpms read
TPMS read as 08066968,080668e2,0806685d,08066929
I (1034335) ovms-server-v2: Incoming Msg: MP-0 AFA
I (1034335) ovms-server-v2: Send MP-0 a
I (1051925) webserver: HTTP POST /api/execute
I (1051935) webcommand: HttpCommandStream[0x3fa459f8]: 1881332 bytes free, executing: tpms write <08066968,080668e2,08066929,0806685d>
OVMS# tpms write <08066968,080668e2,08066929,0806685d>
Error: Tyre set '<08066968,080668e2,08066929,0806685d>' not found
I (1064845) ovms-server-v2: Send MP-0 S94.0,M,0,0,stopped,standard,159,147,70,0,0,20,2,21,0,0,0,0,136.33,0,0,0,0,0,0,0,0,0,0,0,0,0.00,0.00,81
I (1064855) ovms-server-v2: Send MP-0 D204,32,5,29,28,28,3124,1054586,0,0,28,3,1,1,13.15,0,11.5,0,29,0,0
I (1064865) ovms-server-v2: Send MP-0 F3.2.013/ota_0/eap (build idf v3.3-beta3-775-gdc1ca69 May 31 2020 17:27:06),5YJRE1A18B1001243,0,1,TR2N,CI523​

 

[Nvbob]

@markwj / @Nvbob - I’m getting the error msg show below when initiating the “tpms read” command. I just updated to 3.2.013 as well so thoughts on what might be wrong?


View attachment 571750

Turn the key to the "on" position (so the instrument panel lights are on) and then try your read command. If it comes back with the same result, . . . @markwj would need to assist.

I get the same Error when I do a "tpms read" with the key in the "off" position. With it "on" the read command works as it should.

 

[Roadster]

Yeah, I had already tried both ignition positions "I" and "II" but to no avail Adding a photo of my copycat solder job for comparison to yours @Nvbob (see below). Pretty certain I have the correct pins jumped.

Everything else on the OVMS app works as expected from before I added the TPMS module. Are there any other SMS commands I should try to see if there are bigger problems? Sorry, still an OVMS n00b and could use as much help as I can get, thx.

*UPDATE*
I just tried issuing a number of basic SMS commands (see photo below) and got the same "Unrecognised command" for all fo them so I think I have bigger problems... or I've missed a simple setting somewhere... or worse?

 

[Nvbob]

Yeah, I had already tried both ignition positions "I" and "II" but to no avail Adding a photo of my copycat solder job for comparison to yours @Nvbob (see below). Pretty certain I have the correct pins jumped.

Everything else on the OVMS app works as expected from before I added the TPMS module. Are there any other SMS commands I should try to see if there are bigger problems? Sorry, still an OVMS n00b and could use as much help as I can get, thx.

View attachment 571821

*UPDATE*
I just tried issuing a number of basic SMS commands (see photo below) and got the same "Unrecognised command" for all fo them so I think I have bigger problems... or I've missed a simple setting somewhere... or worse?

View attachment 571822

@Roadster

Your soldering looks ok to me but I would do continuity checks from the db9 pin#1 to the da26 pin#21, 20, & 22 just to make sure that nothing got crossed. Also, what's the mfg date on your OVMS (before or after July 2018 - before requires the jumper)? Are the switches set - SW1 set to #2 (LDO 5v) and S1 set to off (away from the ON label)?

Your SMS commands, try using lower case and put a space between the commands and the question mark (module ?, server ?, etc.). Use the "help" command to get a quick help. Use the "?" to get a full list of commands available. I did not see a "gprs" nor a "diag" in the list when accessing from my OVMS app.

The "Feature 15 1" is a feature setting - In the OVMS app on your phone, go to "settings" (at the bottom right), touch the right arrow next to your vehicle, touch "control" at the very top right, select "Features", scroll down to "#15: CAN Write", touch the "#15: CAN Write" and change the value to "1". Once you are done touch "<Control" at the very top left (next to "Features" to get out of that screen, then touch "Back", then touch "<Cars", and you are back on your car with the "Status/Car/Location/Messages/Settings" screen.

Anything beyond that would require @markwj.

Hope this helps!

 

[markwj]

I need help with the tpms write' command.

The new TPMS subsystem in OVMS works off the concept of 'tyre sets'. You can read into a set with:
tpms read summer
(for a set called 'summer'). If you don't specify the set name, 'tpms read' will simply show you the IDs (and not save them in a set).

You can also manually define sets with
tpms write winter 11111111 22222222 33333333 44444444
You'll need to drop by a garage with a TPMS tool to get the values for those IDs.

The order of IDs is vehicle dependent. For Tesla Roadster 2.x it is FL, FR, RL, RR.

You can write back IDs with:
tpms write winter
(for a set called 'winter').

The 'tpms list' command will show you what sets you have defined.

Regards, Mark.

 

[markwj]

@markwj / @Nvbob - I’m getting the error msg show below when initiating the “tpms read” command. I just updated to 3.2.013 as well so thoughts on what might be wrong?

A rough checklist:

1. You have a 2.x roadster (not 1.5, which uses a different TPMS system).
2. You have the Tesla Baolong TPMS system installed in your car (some don't, as this was an optional extra).
   
3. You have an OVMS v3.2 module (or v3.1 module labelled on board as July 2018 or later), or have made the jump-wire modification.
4. You are using a cable labelled "OVT1".
5. You have the K-line expansion board installed in OVMS (and double check the pins fit nicely, with nothing loose/bent).
6. SW1 is set to position #2 (LDO 5v).
7. S1 is set to the OFF position (away from the ON label).
8. The car key is turned fully on, with the car in Park.

There was some discussion that the read/write command needs to be run within a minute or so of turning on the ignition. I haven't seen that myself, or been able to reproduce the issue, but perhaps some version of the Baolong TPMS ECU requires that.

Regards, Mark.

 

[Roadster]

Thx @Nvbob and @markwj! Some replies...

1. You have a 2.x roadster (not 1.5, which uses a different TPMS system). Yes, 2011 2.5 RS.
2. You have the Tesla Baolong TPMS system installed in your car (some don't, as this was an optional extra). I'm not actually sure. Is there a way to check without dismounting the tires?
   
3. You have an OVMS v3.2 module (or v3.1 module labelled on board as July 2018 or later), or have made the jump-wire modification. 2018.03.05 build and jump-wire done. However, I haven't tested for continuity as I don't own a multimeter. Guess it's time to get a new toy for the toolbox Any recommendations? I've been looking at Fluke but there are so many!
4. You are using a cable labelled "OVT1". Yes, confirmed.
5. You have the K-line expansion board installed in OVMS (and double check the pins fit nicely, with nothing loose/bent). Yes, confirmed.
6. SW1 is set to position #2 (LDO 5v). Yes, confirmed.
7. S1 is set to the OFF position (away from the ON label). Yes, confirmed.
8. The car key is turned fully on, with the car in Park. Yes, confirmed.

Your SMS commands, try using lower case and put a space between the commands and the question mark (module ?, server ?, etc.). Use the "help" command to get a quick help. Use the "?" to get a full list of commands available.

This worked thx (see below)!

The "Feature 15 1" is a feature setting - In the OVMS app on your phone, go to "settings" (at the bottom right), touch the right arrow next to your vehicle, touch "control" at the very top right, select "Features", scroll down to "#15: CAN Write", touch the "#15: CAN Write" and change the value to "1".

Confirming this was set accordingly, thx.

I attempted to issue the "tpms list" command and it seems to have worked even though I haven't configured any tire sets with the "tpms write" command (see image below). Does this mean the TPMS board is responding correctly or is that just a default reply?

 

[JohnGarziglia]

The new TPMS subsystem in OVMS works off the concept of 'tyre sets'. You can read into a set with:
tpms read summer
(for a set called 'summer'). If you don't specify the set name, 'tpms read' will simply show you the IDs (and not save them in a set).

You can also manually define sets with
tpms write winter 11111111 22222222 33333333 44444444
You'll need to drop by a garage with a TPMS tool to get the values for those IDs.

The order of IDs is vehicle dependent. For Tesla Roadster 2.x it is FL, FR, RL, RR.

You can write back IDs with:
tpms write winter
(for a set called 'winter').

The 'tpms list' command will show you what sets you have defined.

Regards, Mark.

Mark, thanks so much! Exactly what I needed to know.

Thx @Nvbob and @markwj!
I attempted to issue the "tpms list" command and it seems to have worked even though I haven't configured any tire sets with the "tpms write" command (see image below). Does this mean the TPMS board is responding correctly or is that just a default reply?

For Roadster, I would start with asking does your VMS display tire pressures, and does your OVMS likewise display tire pressures. I am assuming both do but if not, it would appear your issue is not with OVMS but possibly with the TPMS system itself. Just a thought.