OVMS für den Soul

[^tom^]

Just a "funfact":
Driving home from work today, I drove 12.5km using 2.4kWh off the battery and recuperated 0.5kWh.
My wife just drove 20.7km using 4.9kWh off the battery and recuperated 0.7kWh.
For these two trips, we got 20% and 14% of the energy from recuperation. This is the first time I've ever seen some real figures

Great job thanks!
Max and MIn Btmp.
It takes cell #3 and cell#4 or #1 and and #4 to get this result (not 100% sure)
value of #8 never show up

Any idea what HST (I had HST=45) is for?

Charging: Perfect working. Incl. "Performance" (is CHademo) and "Standard" (Typ1 socket). True Amps even with Typ2 32A socket (shows at begining 28A (50% SoC) and goes to 24A at 99% SoC)

trip:
works fine, superb I like this command
Disch.,Recup.,Sum.: All are looking logical and true to me

Please:
Can you add
Disch.,Recup.
for the total too? Hopefully you can find the adress for it.

Outsidetmp. : Correct

PEM or McuT: Shows the OBC tmp. and or the coolant fluid and looks good to me too (raised up to 22C during charging with 6kW at two different cars)

[goev_no05]

Max and Min, in BTMP, fits the value on #1 and #2 for my car at the moment, so there is some logic there. I might be some delay or something that gives these odd results.

HST is Heatsink Temperature. I don't know the location of that heatsink. 45 is the raw byte from the car. The next OVMS version will show the actual temperature.

I can add disch. to total, but recuperation is not possible yet. There might be a number somewhere, but I don't know where to find it. The reason is that recup. is the difference in cumulated charge from the start of the trip till the end of the trip.

Thanks for verifying the numbers! I think we are getting closer to a version 1.0 and something we could add to the official OVMS repository

[^tom^]

Maybe you can insert total Kilometer in the command trip.

Last Trip:
xxxxxx

Total:
xx.xxkWh/100km
x.xxkm/kWh
ODO: xxxx km (this line to ad)

I know you have it in "stat", but.....

[goev_no05]

I was thinking the same thing

[^tom^]

From a trip today:
btmp:
Max27C Min26C

I even do not have 27C listed.

[goev_no05]

Interesting. We have now idea how these values are calculated. Was the module temperatures somewhere close to that?

[^tom^]

#1 to #8
28
26
26
26

26
26
26
23

inlet 26C (uff where is this sensor located)
Heat1=23C 2=23C
MotT=23C
McuT=11C
HST=49

[goev_no05]

Ok. Min should definitely have been 23, and max 28. Those values appears to be useless, so maybe I should just skip reading them from the can-bus and just pick the correct ones from the 8 module temperatures instead. That will actually free up two bytes of RAM which is sorely needed elsewhere.

I've past the RAM-limits of OVMS, so the next version is currently 4 bytes short on RAM. I have removed some values we don't need to show in SMS' anymore, compressed some fields into a common bit field and converted some values from UINT32 to 3 bytes as the most significant bytes weren't used, but still I'm a few bytes short. Min and Max-battery temperatures are good candidates for removal.

The inlet temperature sensor in installed on the 8th module, so it should be fairly equal to temperature on module 8. However they aren't always that. Inlet, max and min are fetched from package 21 05, while the module temperatures are fetched form 21 01. There could be some difference in time between the two readouts, which can explain the different values.

[^tom^]

It would be nice to have kW where the Volt and Amps are too.
So you do not have to calculate the kW.

About useless:
Does anyone need the results AC AD (Accumulative Charging and Discharging)?
There most the time at 90.00kW and for me useless (at the moment).

[HubertB]

I've past the RAM-limits of OVMS, so the next version is currently 4 bytes short on RAM. I have removed some values we don't need to show in SMS' anymore, compressed some fields into a common bit field and converted some values from UINT32 to 3 bytes as the most significant bytes weren't used, but still I'm a few bytes short. Min and Max-battery temperatures are good candidates for removal.

You guys are aware of the article in C´t No 25 of this year?
Its about reading OBD data with a Raspi.
Maybe worth a thought to overcome the Hardware limitations of the OVMS module.

Great work you are doing, by the way-