Hello,
i have a strange situation, on older 3/Y Batteries the 352 will decoded correct, but on new one and on the S/X Plaid (Refresh) models the frame 352 has only wrong values.
Did anyone know where i can find the correct data or description of the new battery can communication?
How to decode frame 352 from S/X Plaid battery?
-
- Posts: 772
- Joined: Tue Sep 17, 2019 8:33 pm
- Location: Raleigh, NC, USA
- Has thanked: 96 times
- Been thanked: 96 times
Re: How to decode frame 352 from S/X Plaid battery?
Sounds like once again Tesla has randomly changed things. You may have to try to figure out the new data/offset/gain. In fact, you may have more info on this than anyone else, unfortunately.
If at first you don't succeed, buy a bigger hammer.
1940 Chevrolet w/ Tesla LDU - "Shocking Chevy" - Completed 2023 Hot Rod Drag Week
1940 Chevrolet w/ Tesla LDU - "Shocking Chevy" - Completed 2023 Hot Rod Drag Week
Re: How to decode frame 352 from S/X Plaid battery?
yes - tesla did change anything, i have one tesla model 3 and one plaid battery with other decoding of this adresses - but the rest looks simular. For the refresh X/S you have more modules and you can query this simular like the smaller 3/Y ones. but on this address i think tesla did it completly other than before. a simple right/left shifting of bits did not bring me to a positiv result.
-
- Posts: 772
- Joined: Tue Sep 17, 2019 8:33 pm
- Location: Raleigh, NC, USA
- Has thanked: 96 times
- Been thanked: 96 times
Re: How to decode frame 352 from S/X Plaid battery?
If you can share some of the data/logs, folks might be able to assist.OOP wrote: ↑Wed Nov 15, 2023 4:13 pm yes - tesla did change anything, i have one tesla model 3 and one plaid battery with other decoding of this adresses - but the rest looks simular. For the refresh X/S you have more modules and you can query this simular like the smaller 3/Y ones. but on this address i think tesla did it completly other than before. a simple right/left shifting of bits did not bring me to a positiv result.
If at first you don't succeed, buy a bigger hammer.
1940 Chevrolet w/ Tesla LDU - "Shocking Chevy" - Completed 2023 Hot Rod Drag Week
1940 Chevrolet w/ Tesla LDU - "Shocking Chevy" - Completed 2023 Hot Rod Drag Week
Re: How to decode frame 352 from S/X Plaid battery?
here is a example:
Timestamp: 1702038482.047673 ID: 0352 S Rx DL: 8 01 00 23 01 00 00 ba 0a Channel: can0
Timestamp: 1702038482.047673 ID: 0352 S Rx DL: 8 01 00 23 01 00 00 ba 0a Channel: can0
- uhi22
- Posts: 601
- Joined: Mon Mar 14, 2022 3:20 pm
- Location: Ingolstadt/Germany
- Has thanked: 91 times
- Been thanked: 412 times
Re: How to decode frame 352 from S/X Plaid battery?
How does this change, depending on temperature, current, voltage, soc?
Just guessing: 23 01 may be 0x0123 is 291 maybe 291 volts.
Or ba 0a may be 0x0aba is 2746 maybe 274.6 volts.
Just guessing: 23 01 may be 0x0123 is 291 maybe 291 volts.
Or ba 0a may be 0x0aba is 2746 maybe 274.6 volts.
Github: http://github.com/uhi22 --- Patreon: https://www.patreon.com/uhi22
- muehlpower
- Posts: 575
- Joined: Fri Oct 11, 2019 10:51 am
- Location: Germany Fürstenfeldbruck
- Has thanked: 12 times
- Been thanked: 103 times
Re: How to decode frame 352 from S/X Plaid battery?
I have two DBC files. They both say the same thing. In the second 64|4 cannot be correct
Code: Select all
BO_ 850 ID352BMS_energyStatus: 8 VehicleBus
SG_ BMS_energyBuffer : 55|8@1+ (0.1,0) [0|25.4] "KWh" Receiver
SG_ BMS_energyToChargeComplete : 44|11@1+ (0.1,0) [0|204.6] "KWh" Receiver
SG_ BMS_expectedEnergyRemaining : 22|11@1+ (0.1,0) [0|204.6] "KWh" Receiver
SG_ BMS_fullChargeComplete : 63|1@1+ (1,0) [0|1] "" Receiver
SG_ BMS_idealEnergyRemaining : 33|11@1+ (0.1,0) [0|204.6] "KWh" Receiver
SG_ BMS_nominalEnergyRemaining : 11|11@1+ (0.1,0) [0|204.6] "KWh" Receiver
SG_ BMS_nominalFullPackEnergy : 0|11@1+ (0.1,0) [0|204.6] "KWh" Receiver
Code: Select all
BO_ 850 BMS_energyStatus: 8 VEH
SG_ BMS_energyBuffer: 55|8@1+ (0.1,0) [0|0] "KWh" X
SG_ BMS_energyCounter: 64|4@1+ (1,0) [0|0] "" X
SG_ BMS_energyToChargeComplete: 44|11@1+ (0.1,0) [0|0] "KWh" X
SG_ BMS_expectedEnergyRemaining: 22|11@1+ (0.1,0) [0|0] "KWh" X
SG_ BMS_idealEnergyRemaining: 33|11@1+ (0.1,0) [0|0] "KWh" X
SG_ BMS_nominalEnergyRemaining: 11|11@1+ (0.1,0) [0|0] "KWh" X
SG_ BMS_nominalFullPackEnergy: 0|11@1+ (0.1,0) [0|0] "KWh" X
SG_ BMS_fullyCharged : 63|1@1+ (1,0) [0|1] "" X
Re: How to decode frame 352 from S/X Plaid battery?
The SOC is wrong too at this pack - i dont know why. i thin the expected and the normal full value is the problem at this condition.
i calculate the SOC with this 2 values:
soc = round(expected_energy_remaining / nominal_full_pack_energy * 100)
But a 0 of the BMS_nominalFullPackEnergy can not be true.
i calculate the SOC with this 2 values:
soc = round(expected_energy_remaining / nominal_full_pack_energy * 100)
But a 0 of the BMS_nominalFullPackEnergy can not be true.
Re: How to decode frame 352 from S/X Plaid battery?
right now i have a simular BMS that writes confusing data:
Timestamp: 1704294961.760159 ID: 0352 S Rx DL: 8 01 00 24 01 24 01 80 09 Channel: can0
If i check the voltages, the battery should be very full, but the SOC writes a totaly diffrent value.
Timestamp: 1704294961.760159 ID: 0352 S Rx DL: 8 01 00 24 01 24 01 80 09 Channel: can0
Code: Select all
[01]4.0588V [02]4.0593V [03]4.0579V [04]4.0592V [05]4.057V [06]4.0588V [07]4.0588V [08]4.0599V [09]4.0594V [10]4.06V [11]4.0601V [12]4.0649V
[13]4.0648V [14]4.065V [15]4.0647V [16]4.0647V [17]4.0647V [18]4.0648V [19]4.0648V [20]4.0648V [21]4.065V [22]4.0652V [23]4.065V [24]4.0653V
[25]4.0653V [26]4.0655V [27]4.0642V [28]4.0655V [29]4.0657V [30]4.0653V [31]4.0656V [32]4.0659V [33]4.0656V [34]4.0659V [35]4.0656V [36]4.0631V
[37]4.0631V [38]4.0631V [39]4.0632V [40]4.0632V [41]4.0629V [42]4.0628V [43]4.0628V [44]4.0628V [45]4.0628V [46]4.0624V [47]4.062V [48]4.0624V
[49]4.0576V [50]4.058V [51]4.0573V [52]4.0578V [53]4.058V [54]4.058V [55]4.058V [56]4.0588V [57]4.0589V [58]4.0586V [59]4.0587V [60]4.0591V
[61]4.0605V [62]4.0607V [63]4.0609V [64]4.0604V [65]4.0606V [66]4.0608V [67]4.0606V [68]4.0606V [69]4.0604V [70]4.0604V [71]4.0606V [72]4.0605V
[73]4.0607V [74]4.0577V [75]4.0575V [76]4.058V [77]4.0576V [78]4.0576V [79]4.0578V [80]4.0579V [81]4.058V [82]4.058V [83]4.058V [84]4.0572V
[85]4.0565V [86]4.0557V [87]4.0563V [88]4.0564V [89]4.056V [90]4.0558V [91]4.0556V [92]4.055V [93]4.0546V [94]4.0535V [95]4.0535V [96]4.0533V
battery_voltage : 389.27 V battery_amps : 0.0 A battery_charge_time_remaining : 409.5 min
min_voltage : 240.70 V max_discharge_current : 0.0 KW max_charge_current : 0.0 A
max_voltage : 402.68 V regenerative_limit : 0.0 KWh discharge_limit : 0.0 KWh
max_heat_park : 0.0 KWh hvac_max_power : 0.0 KWh soc_max : 16.0 %
soc_ave : 12.6 % soc_vi : 10.0 % soc_min : 11.8 %
bms_bat_temp_pct : 33.2 C bat_beginning_of_life : 77.8 KWh high_voltage : 9.5214 V
low_voltage : 14.218 V output_current : 0.0 A soc : 400 %
energy_buffer : 1.9000 KWh energy_to_charge_complete : 0.0 KWh expected_energy_remaining : 0.4 KWh
full_charge_complete : 0 ideal_energy_remaining : 14.600 KWh nominal_energy_remaining : 115.2 KWh
nominal_full_pack_energy : 0.1 KWh total_discharge : 24157. KWh total_charge : 24902. KWh
ac_charge_total_module3 : 3813.7 KWh dc_charge_total_module3 : 699.50 KWh discharge_total_module4 : 5897.3 KWh
charge_total_module4 : 6059.6 KWh ac_charge_total_module4 : 3639.0 KWh dc_charge_total_module4 : 664.02 KWh
ac_charger_total : 14896. KWh dc_charger_total : 2726.1 KWh regen_charge_total : 7280.0 KWh
drive_discharge_total : 21093. KWh discharge_total_module1 : 5897.2 KWh charge_total_module1 : 6060.7 KWh
ac_charge_total_module1 : 3639.1 KWh dc_charge_total_module1 : 663.99 KWh discharge_total_module2 : 6228.0 KWh
charge_total_module2 : 6399.5 KWh ac_charge_totalmodule2 : 3814.0 KWh dc_charge_total_module2 : 699.64 KWh
discharge_total_module3 : 6227.4 KWh charge_total_module3 : 6398.3 KWh