I loaded the 0x500 connected file. It seems like you're dropping a lot of frames for some reason. For instance, 0x332 is sometimes only coming through every 3-5 seconds. It is sent much faster than that. The 0x7D2 message that gets unlocked by sending 0x500 should be occurring every second. That's certainly not happening. It could be because the 0x70A message is spamming the bus. All of these units seem to do that. I think it's looking for the other devices in the car and spams the bus with that message to reach out to them... somehow? You don't see 0x70A being constantly sent in the full car. It gets sent sometimes for a little while but then it stops again. In your captures the 0x70A message is 3/4 of the traffic! 0x132 happens a lot too but not nearly as often.nkiernan wrote: ↑Mon May 24, 2021 1:03 pm Latest capture of the vehicle CAN with the four modules connected up to make full pack and a second CAN capture with 0x500 introduced after approx 10 seconds for comparison. As Collin said, the two extra ID's do show up here too
240521 - TM3 HV Controller - Vehicle CAN - Full Pack Connected 0x500.csv
240521 - TM3 HV Controller - Vehicle CAN - Full Pack Connected.csv
What are you using for capture? I'm almost positive that I was getting much more consistent results when I captured with a PeakCAN adapter but, alas, I did not save any captures.
Anyway, 0x332 shows this:
Min cell: 2.99v (cell 60)
Max cell: 3.15v (cell 45)
So, that pack is quite discharged. It shows about 7% SOC too.