[kornerz]

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:

 (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]

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:

 (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]

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

 

[JWardell]

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...

 

[kornerz]

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

"Anyone has CAN message IDs for cold gas thrusters?"

 

[Madmolecule]

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.

 

[Madmolecule]

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

 

[pyjamasam]

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]

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.

 

[dimitar.ns]

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]

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]

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.

 

[All About Jake]

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]

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:

  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

 

[tyuo9980]

Does anyone know if you can write to the canbus with the obdlink mx+?

 

[JWardell]

Does anyone know if you can write to the canbus with the obdlink mx+?

Yes you can, with the right commands. I wouldn't recommend it, because your Tesla will most likely detect the unexpected data.

 

[jj92]

Hello all,

I am still quite new here and have but directly a question regarding a Model Y.
I'm looking for some info on where to find the can bus in the Model Y.
I have already notebook with can interface to record what is on the bus.

Would be great if someone knows, maybe even with a photo or where I can get more info.

Greetings

 

[JWardell]

Hello all,

I am still quite new here and have but directly a question regarding a Model Y.
I'm looking for some info on where to find the can bus in the Model Y.
I have already notebook with can interface to record what is on the bus.

Would be great if someone knows, maybe even with a photo or where I can get more info.

Greetings

(Are there Model Ys in Germany??)
The Y is the same and the 3, so the best place to access CAN is in the back of the center console, with an OBD harness.

 

[jj92]

(Are there Model Ys in Germany??)
The Y is the same and the 3, so the best place to access CAN is in the back of the center console, with an OBD harness.

No, but I have access to a us version of model y.
Have you ever tried to connect directly to the wire of the can?

 

[likandoo]

Hello,

I am hoping to get help on this Forum I am trying to get the OBDLink MX+ to work in my Model 3 connected to a MacBook Pro.
I bought the OBDLink MX+ because everyone said its the best with the best compatibility. But now I found out that apparently it does not officially support MacOS is that right?

Because I have the problem that I cannot get it connected to my Macbook via Bluetooth.

The Dongle is connected and has Power and also shows up in MacOS with the right name. When I click connect it takes 2 seconds and then it says "Connected" however on the Dongle the Bluetooth indication LED is still flashing blue instead of constant blue. And after about 5-10 seconds it says disconnected again in the MacOS Bluetooth Panel.

What am I doing wrong as it connects flawlessly on my iPhone and also on a Android Device.

But I need it to connect to MacOS Bluetooth as it is my development environment there.

I hope someone ran into the same problem here and found a solution.

(btw tried it on two different MacBooks with Catalina and BigSur)