[Ovmsdev] OVMS Logging and HTTP API

Tom Saxton tom at idleloop.com
Mon Sep 16 06:00:54 HKT 2013


The new logging stuff plug the HTTP API is pretty cool. I've got a 2.5.2
build running on our v1.5 Roadster, so I'm now getting logging information
recorded on the server. With HTTP API, I can now easily download both
current and historical information.

Here's what my Perl script is currently dumping out:

Charge Status:

Charge State: done
Charge Mode: standard
Ambient Temperature: 21C, 70F
Battery Temperature: 22C, 72F
PEM Temperature: 31C, 88F
Motor Temperature: 26C, 79F
Line Voltage: -1V
Charge Current: 0 of 32A
SOC: 97%, 183 IM

Vehicle History:

C 09/11/2013-03:00:12 (0:06:42): 242V/27A, 96% -> 97%, 182 -> 183 ideal
miles
D 09/11/2013-16:49:23 (0:11:20): 3.2 mi, 97% -> 95%, 183 -> 179 ideal miles
D 09/11/2013-17:56:53 (0:07:52): 1.3 mi, 95% -> 94%, 177 -> 177 ideal miles
D 09/11/2013-18:22:28 (0:14:43): 3.2 mi, 94% -> 93%, 177 -> 175 ideal miles
C 09/12/2013-03:00:11 (0:27:24): 241V/34A, 92% -> 97%, 174 -> 183 ideal
miles
C 09/13/2013-03:00:16 (0:07:42): 241V/29A, 96% -> 97%, 182 -> 184 ideal
miles
C 09/14/2013-03:00:11 (0:08:01): 243V/27A, 96% -> 97%, 182 -> 184 ideal
miles
C 09/15/2013-03:00:09 (0:06:21): 244V/26A, 96% -> 97%, 182 -> 183 ideal
miles

The historical records don't seem to have a "units" field, so I just have
to assume miles. It would be great to add that, especially for those of us
who live near the US/Canada border and switch back and forth.


I'd also like to see CAC added to the current charge status.

It would be cool to have CAC in the historical records, too, but I'm
guessing that would take more EEPROM storage. Maybe only send that field
for the current record and drop it from records that have to be stashed
for transmission later?

    Tom






More information about the OvmsDev mailing list