Diagnostic Port and Data Access

  • SUPPORT THE SITE AND ENJOY A PREMIUM EXPERIENCE!
    Welcome to Tesla Owners Online, five years young! For a low subscription fee, you will receive access to more features on the site. We now offer yearly memberships too! For more information visit this page:
    https://teslaownersonline.com/account/upgrades

    SUBSCRIBE TO OUR YOUTUBE CHANNEL!
    Did you know we have a YouTube channel that's all about Tesla? Lots of Tesla information, fun, vlogs, product reviews, and a weekly Tesla Owners Online Podcast as well!

kornerz

Active member
Joined
Sep 27, 2017
Messages
74
Location
Kyiv
Country
Country
Tesla Owner
Model 3
Does anyone know the updated definition of ID3F2, BMSCounters?
I've noticed that on recent firmware the index (BMSCountersIndex3F2) is now 4-bit wide instead of 3, and overall there are 12 values in this message instead of 4 described in the DBC here: https://github.com/joshwardell/model3dbc/blob/master/Model3CAN.dbc#L2898

Values sample:

Code:
 (1613970959.816149)  can0  3F2   [8]  00 8A 42 40 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 0,
    BMStotalACcharge3F2: 4211.338 KWh
)
(1613970960.816584)  can0  3F2   [8]  01 0D D0 01 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 1,
    BMStotalDCcharge3F2: 118.797 KWh
)
(1613970961.816518)  can0  3F2   [8]  02 54 B0 12 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 2,
    BMStotalRegenCharge3F2: 1224.788 KWh
)
(1613970962.816044)  can0  3F2   [8]  03 36 61 40 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 3,
    BMStotalDriveDischarge3F2: 4219.19 KWh
)
(1613970963.815376)  can0  3F2   [8]  04 DA 87 14 D0 11 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 4
(1613970964.816724)  can0  3F2   [8]  05 F4 10 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 5
(1613970965.814835)  can0  3F2   [8]  06 C7 87 14 20 18 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 6
(1613970966.814765)  can0  3F2   [8]  07 47 11 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 7
(1613970967.814462)  can0  3F2   [8]  08 F5 87 14 90 15 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 8
(1613970968.814413)  can0  3F2   [8]  09 26 11 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 9
(1613970969.814359)  can0  3F2   [8]  0A D7 87 14 10 16 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 10
(1613970970.814391)  can0  3F2   [8]  0B 2C 11 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 11
 

JWardell

TOO Master Member
TOO Sponsor Vendor
Joined
May 9, 2016
Messages
4,737
Location
Boston
Country
Country
Tesla Owner
Model 3
Does anyone know the updated definition of ID3F2, BMSCounters?
I've noticed that on recent firmware the index (BMSCountersIndex3F2) is now 4-bit wide instead of 3, and overall there are 12 values in this message instead of 4 described in the DBC here: https://github.com/joshwardell/model3dbc/blob/master/Model3CAN.dbc#L2898

Values sample:

Code:
 (1613970959.816149)  can0  3F2   [8]  00 8A 42 40 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 0,
    BMStotalACcharge3F2: 4211.338 KWh
)
(1613970960.816584)  can0  3F2   [8]  01 0D D0 01 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 1,
    BMStotalDCcharge3F2: 118.797 KWh
)
(1613970961.816518)  can0  3F2   [8]  02 54 B0 12 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 2,
    BMStotalRegenCharge3F2: 1224.788 KWh
)
(1613970962.816044)  can0  3F2   [8]  03 36 61 40 00 00 00 00 ::
ID3F2BMSCounters(
    BMSCountersIndex3F2: 3,
    BMStotalDriveDischarge3F2: 4219.19 KWh
)
(1613970963.815376)  can0  3F2   [8]  04 DA 87 14 D0 11 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 4
(1613970964.816724)  can0  3F2   [8]  05 F4 10 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 5
(1613970965.814835)  can0  3F2   [8]  06 C7 87 14 20 18 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 6
(1613970966.814765)  can0  3F2   [8]  07 47 11 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 7
(1613970967.814462)  can0  3F2   [8]  08 F5 87 14 90 15 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 8
(1613970968.814413)  can0  3F2   [8]  09 26 11 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 9
(1613970969.814359)  can0  3F2   [8]  0A D7 87 14 10 16 53 01 :: expected multiplexer id 0, 1, 2 or 3, but got 10
(1613970970.814391)  can0  3F2   [8]  0B 2C 11 10 30 40 07 00 :: expected multiplexer id 0, 1, 2 or 3, but got 11

Not sure this is entirely up to date:

BO_ 1010 ID3F2BMSCounters: 8 VehicleBus
SG_ BMS_kwhCounter_Id M : 0|4@1+ (1,0) [0|0] "" Receiver
SG_ BMS_kwhDcChargeTotalModule3 m9 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhChargeTotalModule2 m6 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDcChargeTotalModule2 m7 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhChargeTotalModule4 m10 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDcChargeTotalModule4 m11 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDcChargeTotalModule1 m5 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhChargeTotalModule1 m4 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhChargeTotalModule3 m8 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhAcChargeTotalModule3 m9 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDischargeTotalModule2 m6 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhAcChargeTotalModule2 m7 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDischargeTotalModule4 m10 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhAcChargeTotalModule4 m11 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhAcChargeTotalModule1 m5 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDriveDischargeTotal m3 : 8|32@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_dcChargerKwhTotal m1 : 8|32@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDischargeTotalModule1 m4 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_acChargerKwhTotal m0 : 8|32@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhRegenChargeTotal m2 : 8|32@1+ (0.001,0) [0|0] "KWh" Receiver
SG_ BMS_kwhDischargeTotalModule3 m8 : 8|28@1- (0.001,0) [0|0] "KWh" Receiver
 

kornerz

Active member
Joined
Sep 27, 2017
Messages
74
Location
Kyiv
Country
Country
Tesla Owner
Model 3
Not sure this is entirely up to date:

BO_ 1010 ID3F2BMSCounters: 8 VehicleBus
SG_ BMS_kwhCounter_Id M : 0|4@1+ (1,0) [0|0] "" Receiver
SG_ BMS_kwhDcChargeTotalModule3 m9 : 36|28@1+ (0.001,0) [0|0] "KWh" Receiver
...
Thanks, looks up to date for me at 48.3.5

Edit: that split of charge stats into 4 module details look like a preparation for the Semi, where 4 modules are charged separately and it will make sense to track each
 
Last edited:
  • Like
Reactions: JWardell

JWardell

TOO Master Member
TOO Sponsor Vendor
Joined
May 9, 2016
Messages
4,737
Location
Boston
Country
Country
Tesla Owner
Model 3
Thanks, looks up to date for me at 48.3.5

Edit: that split of charge stats into 4 module details look like a preparation for the Semi, where 4 modules are charged separately and it will make sense to track each

Oh, good point. And two for the roadster perhaps. They should send me one for development purposes :) Maybe we can use Trev's extra...
 
  • Agree
Reactions: Roci

Madmolecule

Top-Contributor
Green Level Supporter
Joined
Oct 7, 2018
Messages
515
Location
Duluth, GA
Country
Country
Tesla Owner
Model 3
I’ll bit off topic as usual but has anyone tried to split the display cable to run two displays? I don’t really see any safety concerns as it would be impossible to enter something on both screens simultaneously. Karaoke would be a lot better with the rear display.
 
  • Like
Reactions: Achooo

Madmolecule

Top-Contributor
Green Level Supporter
Joined
Oct 7, 2018
Messages
515
Location
Duluth, GA
Country
Country
Tesla Owner
Model 3
I have added a second instrument cluster display. The set up is done by using various different finger combinations on the main display. Is this finger information available on the can server? It could be usefull to change display modes on the micro display

example from the setup
  • 2 UI styles. Hold down the central touchscreen with four fingers to change the display from current style to another style.
  • Hold down the central touchscreen with five fingers to reset the trip.
  • Instead of total estimated driving distance available, you can hold down the central touchscreen with six fingers to display the percentage of battery energy remaining.
  • Hold down the central touchscreen with seven fingers to change the language. (English or Simplified Chinese)
  • Brightness sync with the central touchscreen
 
  • Like
Reactions: Mike

pyjamasam

Active member
Joined
Feb 24, 2020
Messages
36
Location
Ontario, Canada
Country
Country
Tesla Owner
Model 3
I have added a second instrument cluster display. The set up is done by using various different finger combinations on the main display. Is this finger information available on the can server? It could be usefull to change display modes on the micro display

example from the setup
  • 2 UI styles. Hold down the central touchscreen with four fingers to change the display from current style to another style.
  • Hold down the central touchscreen with five fingers to reset the trip.
  • Instead of total estimated driving distance available, you can hold down the central touchscreen with six fingers to display the percentage of battery energy remaining.
  • Hold down the central touchscreen with seven fingers to change the language. (English or Simplified Chinese)
  • Brightness sync with the central touchscreen
UI_FalseTouchCounter in ID00CUI_status is the touch count. Combine that with some timers and you should be able to mimic the behaviour you specified.

UI_displayBrightnessLevel in ID273UI_vehicleControl would be the brightness level of the display.

chris.
 

Madmolecule

Top-Contributor
Green Level Supporter
Joined
Oct 7, 2018
Messages
515
Location
Duluth, GA
Country
Country
Tesla Owner
Model 3
Created a quick bezel for the micro displays and they mount pretty nice on the base of my Chinese display. I have not been able to find some right angle power connectors that would work properly and be more discrete. It still looks pretty good. Once I added the swivel to the screen it lowered it, so it made more sense to move in on top of the main display. I like the look there also.

9BFB791A-57E8-47C2-A9A4-DB55F586B293.jpeg
AA17BDCE-9E43-4BE9-B749-00EFEA8153CA.jpeg
CB333054-0B1C-4745-B27A-7F590556E5CC.jpeg
 
Last edited:
  • Love It!
Reactions: JWardell

dimitar.ns

Member
Joined
Nov 11, 2020
Messages
6
Location
Bulgaria
Country
Country
Tesla Owner
Model 3
Hello guys, do you know if the trip data is calculated in the UI or it's somewhere in the CAN messages? (info like distance, time and consumption since X and since last charge)

And is anybody interested in a cable with all 3 CAN buses from the MCU for example on 3 DB9 connectors? We can produce and distribute such cables if there is demand, just let me know. DB9 can be also some other type of connector if it makes sense.
 

JWardell

TOO Master Member
TOO Sponsor Vendor
Joined
May 9, 2016
Messages
4,737
Location
Boston
Country
Country
Tesla Owner
Model 3
Hello guys, do you know if the trip data is calculated in the UI or it's somewhere in the CAN messages? (info like distance, time and consumption since X and since last charge)

And is anybody interested in a cable with all 3 CAN buses from the MCU for example on 3 DB9 connectors? We can produce and distribute such cables if there is demand, just let me know. DB9 can be also some other type of connector if it makes sense.

A single plug and play harness would be great. But my problem is, harnesses are laborious and expensive, and require a significant upfront investment, especially for the unusual connectors that tesla uses. And then it all goes out the window when Tesla choses to change the connector. As it is there are two different diagnostic connectors for S&X, and two different rear console connectors for 3&Y. So as much as I hate the giant OBDII connector, that's the one standard that harnesses are already available and made for off the shelf.

The other standard is DB9, which is standard for CAN prototyping but never production given that it is bulky and in no way secure.

My CANserver does support the standard Vector 2-bus DB9 connector. So if you were to make a harness that plugs powertrain and chassis into that one DB9, it would plug and play. That certainly would be nice.
 

All About Jake

Active member
Joined
Jul 22, 2018
Messages
68
Location
Chatham NJ
Country
Country
For those interested, I just released "tes•LAX v1.6" with some slightly revised branding. Of specific interest, support for BLE OBD-2 dongles like the OBDLink CX, and vLinker MC+, etc.

It should work with most serial ELM237 dongles over BLE... but BLE has a system of service UUIDs and characteristic UUIDs and I might not have every obscure dongle accounted for. Advanced users can add their own BLE ID's in the settings if they have something that doesn't work out of the box.

I have to say I'm impressed with the OBDLink CX, as it has good performance at its price point. The vLinker MC+ with BLE is nice too because it also has the ST-command set. But with all of these BLE dongles, keep in mind a malicious user can connect to an unpaired dongle... a pretty big security problem. (Some WiFi dongles also have this problem if they cannot be secured with a password)

Also there's a Mazda 3 profile in there from @pyjamasam, showing how you can configure tes•LAX for any vehicle with a CAN bus. If you create anything neat for another vehicle (using public-domain information), let me know and maybe I can include it in the default library of presets.
 
  • Love It!
Reactions: JWardell

All About Jake

Active member
Joined
Jul 22, 2018
Messages
68
Location
Chatham NJ
Country
Country
For those interested, I just released "tes•LAX v1.6" with some slightly revised branding. Of specific interest, support for BLE OBD-2 dongles like the OBDLink CX, and vLinker MC+, etc.

Sad to report there is a minor bug in tesLAX 1.6 that prevents the "Extra Strength" unlock from working properly for some users. I've submitted a fix to Apple and are waiting for them to approve. I apologize for the interruption in features for some users.
 

kornerz

Active member
Joined
Sep 27, 2017
Messages
74
Location
Kyiv
Country
Country
Tesla Owner
Model 3
Looks like in 2021.4.11 they've updated (or moved somewhere) ID261, 12v battery status.
Now it has a multiplexer and consists of 3 messages:
Code:
  can0  261   [8]  00 10 FE 00 99 40 50 F8
  can0  261   [8]  31 48 02 01 A4 4A 62 8D
  can0  261   [8]  F6 FE 4F 04 46 42 70 00
  can0  261   [8]  00 10 FE 00 99 40 80 28
  can0  261   [8]  31 48 0D 01 A4 4A 92 C8
  can0  261   [8]  F6 FE 4F 04 46 42 A0 30
  can0  261   [8]  00 10 FE 00 99 40 B0 58
  can0  261   [8]  31 48 0D 01 A4 4A C2 F8
  can0  261   [8]  F6 FE 4F 04 46 42 D0 60
  can0  261   [8]  00 10 FE 00 99 40 E0 88
  can0  261   [8]  31 48 CC 00 9F 4A F2 E1
  can0  261   [8]  F6 FE 4F 04 46 42 00 90
 
  • Informative
Reactions: JWardell and Mike

About us

  • Tesla Owners Online © 2015-2021. All rights reserved.
    Tesla Owners Online (TOO) is an enthusiast forum and is not affiliated with Tesla Motors or Official Tesla Owners Clubs.
    All Tesla logos are trademarks or registered trademarks of Tesla Motors.