I've hit a wall with soliciting the battery block voltages and resistances. Not sure if I'm sending the correct command or I'm missing something but this is the issue. I can send 7e3 2 21 cf and I get the correct reply of 7eb 10 12 61 cf..... I *think* I need to send the command of 7e3 30 7..... and then I should get back 7eb 21...., 7eb 22...., 7eb 23.... and 7eb 24.... There are two problems I can't get my brain to understand. 1. When I send 7e3 30 7, I get two replies of 7e3 04 30 81 00 06 55 55 55 and then I get 7eb 02 70 81 00 00 00 00 00. This is not what I was expecting. 2. Regarding the response, do the block voltages, block resistances and other battery information fall under byte D0 (21) or is the information a sequential response from 7e3 2 21 d0/cf/ce? In other words, even if byte D0 is 21, can it be different information? (if that makes sense)
I am not handling the acknowledgement myself but looking at the log I see that OBDLink is sending 7E3 30 00 00 00 00 00 00 00 not 7E3 30 7 .... You may give that a try. Good luck!
I think I tried that last night and had no luck. During the day I'm going to write the code for a sequential response, which I believe it is. On my way home from work today I'll try it out and let you know if it works.
Hi FirstFlight, I have already done this using mmBasic V4.0 with CAN commands. The frame to send is 7E3 30 00 01 00 00 00 00 00 , this is what my miniVCI uses. However 7E3 30 00 00 00 00 00 00 00 also works. Must send all eight bytes of data. Answer is received at 7EB.
I have one issue that I need to resolve. Maybe someone else has had this issue too. All of the battery block voltages work correctly but on occasion (once every 3-4 seconds) the block voltages for 8, 9 and 10 will show -327 and then on the next update go back to normal. Anyone else ever seen this issue?
I haven't paid much attention to the block voltages but I just plotted up the log from a recent trip and didn't see the abnormal value.
