<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p id="reply-intro">On 2025-02-24 01:46, Michael Geddes wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="replybody1">
<div dir="ltr">The one that matters most is OvmsPoller::m_poll_state - as that is the one used in processing. It is possible to set this separately per bus.</div>
</div>
</blockquote>
<div id="replybody1">
<div dir="ltr">
<div> </div>
<div>That makes sense.</div>
<div><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div>The one at OvmsPollers level is there if you choose to keep one 'poll-state' and so set the values on all busses together... which is normally the case. It's mostly there so multiple calls to setting poll-state without actually changing the poll-state will not actually have to queue calls.</div>
</blockquote>
<div> </div>
<div>And that also makes sense, as a common performance optimisation.</div>
<div> </div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div>The one at OvmsVehicle is there because that used to be where it sat. It's still there for reading convenience and for non-blocking access to the value.. but it really should always just be a reference copy of the m_poll_state on OvmsPollers.</div>
</blockquote>
<div> </div>
<div>I see. Yes, I agree it would be better to remove it as a separate variable. I don't plan to work on that myself, but I'll use your description in helping to understand the Leaf's state management. Thank you.</div>
<div> </div>
<div>Chris</div>
<div> </div>
</div>
</div>
</div>
</body></html>