Greg,
That would be the system thinking the vehicle is
asleep, but speed > 0.
I did fix the roadster awake/sleep flag (which was
not being set correctly before), so most likely this is
something new.
The logic is in VehicleTicker1() in vehicle.cpp. It
is:
//
Idle alert:
if
(!StdMetrics.ms_v_env_awake->AsBool() ||
StdMetrics.ms_v_pos_speed->AsFloat() > 0)
{
m_idle_ticker = 15 * 60; // first alert after 15 minutes
}
else
if (m_idle_ticker > 0 && --m_idle_ticker ==
0)
{
NotifyVehicleIdling();
m_idle_ticker = 60 * 60; // successive alerts every 60
minutes
}
So, that resets the fifteen minute timer whenever the
vehicle is either asleep OR speed>0 (driving). Otherwise
the timer counts down, and after 15 minutes the alert is
raised (and every 60 minutes thereafter until either the
vehicle goes to sleep or speed>0).
For roadster, that work work. The car can ‘awake’ itself
for charging,etc.
I am not really sure why we are using ms_v_env_awake in the
first place here. Why do we care if the vehicle is awake or
not? Surely we should be looking at ms_v_env_on (ie; vehicle
switched on)? But for JDEMO users that would cause a problem
(as for they have to leave the vehicle ignition on while
charging).
Maybe simplest to disable this alert for Roadster, unless
someone else has any better ideas. In any case, we need to
think about using ms_v_env_awake vs ms_v_env_on.
Regards, Mark.
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev