thomas.bergo at gmail.com
Wed Jan 22 05:00:40 HKT 2014
Was testing the new 2.6.2 code on i-Miev today.
- Lots of restarts and "Vehicle authentication failed" messages in the iOS
- No CAN bus messages form PID in poll0, while messages in poll1 is working
Programmed the OVMS module with a version, and verified that the module was
2013/10/30 Thomas Bergo <thomas.bergo at gmail.com>
> Please report back when you have done some testing on the QC.
> If the car report 0A while QC, the current code will not detect that we
> are charging. So then we need to rely on the estimated range reported as
> 255 to detecting that the car is QC.
> Regards, Thomas
> 2013/10/30 Matt Beard OVMS <smvo at mxf.org.uk>
>> Hi Thomas,
>> During QC you don't get valid values reported in 0x389 - it seems to be
>> constant 255V, 0A during QC.
>> My code is relying on the fact that the estimated range only ever seems
>> to be reported as 255 during QC (except for the first few messages at
>> startup, but those are easy to filter out). In my testing so far this seems
>> to work for detecting the start and end of QC. I am going to be doing 3
>> more tests today with my latest code and will report back later.
>> On 27 October 2013 20:13, Thomas Bergo <thomas.bergo at gmail.com> wrote:
>>> Hi Matt
>>> I have started to look into the QC code. And i have one concern.
>>> Have you seen if the voltage and charging current (PID 0x389) is
>>> reported during QC?
>>> If not, we are not able to detect that the car is charging during QC
>>> with current code.
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev