<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Mark,<br>
<br>
Probably still a bit of a dangling topic. <br>
<br>
TL;DR: I don't think we should use an enumerated metric.<br>
<br>
For the Roadster, renaming Awake to Accessory I think would be
incorrect, or at least inadvisable. This is because of the
confusion over whether "accessory" refers to the 12v accessory
outlet or the Accessory position of the keyswitch. Unlike a
traditional ICE car, the Roadster can be Awake (in the common usage
of that term among Roadster owners) but not have the Key in the
first ("accessory") position. The 12v accessory jack power follows
Awake, not Accessory.<br>
<br>
If you recall, this matters (why the topic came up in the first
place) because of my desire to trigger OVMS events based on vehicle
state transitions, specifically the enabling of ext12v to power a
HUD when the key is turned, not when the car becomes Awake.<br>
<br>
Documenting for others, Roadster Awake is where the car's 12v system
is alive (coolant pump running is an indicator), and it is triggered
by anything that catches the car's attention. Opening a door, for
example, or turning on/off the headlights, or tapping the little
touch screen will wake the car up. (It's a pretty light
sleeper...) The V2 application can trigger the car into this
state. Awake will enable the dome light (if a door is open) and the
charge indicator (if the charge port door is open). The car will go
back asleep after 5 minutes. <br>
<br>
Accessory is like Awake, but with the dash lights and radio/nav unit
powered, and it requires the key in position 1. The car appears to
stay in this state (not go to sleep after an inactivity timeout) as
long as the key remains in that position. An OVMS "Vehicle Idling"
message appears after about 15 minutes.<br>
<br>
"On" is the keyswitch position 2, where the car can be driven
(contactor is in). Pushing the keyswitch to the momentary position
3 (ICE "Start") toggles the Performance driving mode setting. A
handy place to put that, I guess.<br>
<br>
Asleep is where there is minimal 12v presence (only the alarm, door
locks, and a few internals are powered), and the pump is off. The
car goes from Awake to Asleep after 5 minutes of inactivity, not
instantly when the key is turned to Off. There is no Off state,
without physically pulling internal interlocks or disabling the
power system via the "hidden" diagnostic menu. Key Off (and
physical removal) turns off the dash lights, and starts the 5 minute
timer that triggers Asleep.<br>
<br>
12v charging is not relevant, as the car always float-charges the
12v battery in the 2.x models, and there is no such battery present
in the 1.5's. <br>
<br>
So, bottom line, I don't think a single enumerated metric would
work. Too many car-specific exceptions if our objective is for OVMS
to follow the in-cabin interfaces and commonly used terminology.<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:95B61481-1AA3-43E8-9328-ADB6B3860E2A@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Looking back at the old thread "Vehicle is idling": A new
“Feature”, I don’t think we ever properly finished this. We did
add the aux12v standard metric, and we have the charging12v one.
But we never renames ‘awake’ to ‘accessory’ to avoid the
confusion.
<div class=""><br class="">
</div>
<div class="">The alternative suggested would be one single
enumerated metric to reflect all the possible states. Something
like:<br class="">
<br class="">
<ul class="MailOutline">
<li class="">off</li>
<li class="">deepsleep</li>
<li class="">lightsleep</li>
<li class="">awake</li>
<li class="">accessory</li>
<li class="">starting</li>
<li class="">on</li>
</ul>
<br class="">
I’m ok either way. But really depends on how the other vehicle
types fit into the model.<br class="">
<div><br class="">
</div>
<div>Regards, Mark.</div>
<br>
</div>
</blockquote>
</body>
</html>