Regardless of the limit of 4, the poller can handle any number of states.  Each block can only have 4 states.   Ioniq 5 has an example.


//.ichael

On Sat, 13 June 2026, 18:49 Solterra via OvmsDev, <ovmsdev@lists.openvehicles.com> wrote:
Hi all,

While working on the Toyota e-TNGA platform module (Toyota bZ4X / Subaru
Solterra), I ran into the VEHICLE_POLL_NSTATES limit in
components/poller/src/vehicle_poller.h.

I wanted to produce richer charging tracking / reporting than a single
"charging" state, so I came up with a cable-negotiation/handshake
window, a plugged-but-idle wait, and separate AC and DC phases each
needing their own poll cadences (like PISW at 1 s during handshake but
30 s while waiting and station-telemetry PIDs only in DC). I ended up
with 7 poll states total (SLEEP, AWAKE, DRIVING, plus four charge
phases) versus the 4 the framework currently allows.

My questions:
1. Is there a reason VEHICLE_POLL_NSTATES was fixed at 4?
2. Would the project accept widening it, and if so, in what form would
you prefer?

Thanks
_______________________________________________
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com
To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com