Ok, I found these using the Orbit Parameter Monitor
![[Image: image.png]](https://i.postimg.cc/nLpdGLRM/image.png)
Orbit displays 4856 as ~353V in the parameter monitor, and it drops by ~2V if I put some strain on the electric motor.
353V divided by 96 cells = 3.677V per cell, which seems reasonable at the current ~55% SoC displayed in the car.
If I query it using Send Cmd, I get
Not entirely sure how to decode this.
Closest I can get to is assuming I have to divide by 8. 0b30 hex is 2864 dec. 2864/8 would be 358V.
Not far off 353V, but a bit too much to ignore it...
How does Orbit calculate the voltage value from what the car sends? Is there some ADC reference correction thing taken into account, or is there some more crooked factor instead of 1/8?
Orbit displays 4856 as ~353V in the parameter monitor, and it drops by ~2V if I put some strain on the electric motor.
353V divided by 96 cells = 3.677V per cell, which seems reasonable at the current ~55% SoC displayed in the car.
If I query it using Send Cmd, I get
Quote:Command sent to ECU: 224856
Response from ECU: 6248560b30
Not entirely sure how to decode this.
Closest I can get to is assuming I have to divide by 8. 0b30 hex is 2864 dec. 2864/8 would be 358V.
Not far off 353V, but a bit too much to ignore it...
How does Orbit calculate the voltage value from what the car sends? Is there some ADC reference correction thing taken into account, or is there some more crooked factor instead of 1/8?