Well, in preparation for going down to ChargePoint
I thought I'd verify the 36% point at which the 'timeout' occurs.
I drove my car down to two bars and plugged into my old 240vac JuiceBox (rare for me at home as I use 120vac nowadays), set up my Android with CaniOn to run off a separate USB power source, and went away and then came back to monitor things as the SoC approached 33%...
Sat there watching it go all the way to 42% with no 'timeout', so I went back into the house to see what my house power and JuiceBox monitors were saying and they both showed that the 'timeout' had already occurred much earlier! My uncalibrated guess is that the 'timeout' took place at about 25% SoC.
So, perhaps 36% is not the magic number which instigates the 'timeout'? Never could figure out what triggers it.
Anyone have any suggestions for setting up some sort of automated elapsed-time snapshots or screenshots of CaniOn to capture both the instant that the 'timeout' kicks in as well as its duration?
What I want to do is be able to drive down to ChargePoint
and deplete my pack getting there (sufficient to guarantee a 'timeout' will occur) but also not wanting to sit there more than necessary waiting for it once I'm there.
As an aside, I have such a 'timeout' feature on one of my West Marine lead-acid chargers
(after about two minutes into a charging session it stops charging and checks for excessive voltage sag before continuing with the charging cycle) , but have not heard of it on any other BEV.