[Ovmsdev] i-Miev/C-Zero/iOn

Michael Balzer dexter at expeedo.de
Thu Jan 23 16:29:47 HKT 2014


Mark,

if the Mitsubishi code does not use the new polling hooks, poll0() will 
not be called if the polling code is compiled in.

I had the same problem for the Twizy, that's why I introduced the 
OVMS_POLLER compiler switch.

Regards,
Michael


Am 22.01.2014 02:18, schrieb Mark Webb-Johnson:
> Thomas,
>
> Strange. So far, I see 4 cars using 2.6.2, but only one (presumably 
> yours) is showing authentication errors.
>
> I also can't see any changes to the vehicle_mitsubishi.c code that 
> would cause poll0 to stop working. It is certainly working in other 
> vehicle modules.
>
> I'll keep looking, but would be grateful if you could try to narrow 
> down the poll0 problem.
>
> Regards, Mark.
>
> On 22 Jan, 2014, at 5:00 am, Thomas Bergo <thomas.bergo at gmail.com 
> <mailto:thomas.bergo at gmail.com>> wrote:
>
>> Mark,
>>
>> Was testing the new 2.6.2 code on i-Miev today.
>>
>> Two observations:
>> - Lots of restarts and "Vehicle authentication failed" messages in 
>> the iOS app
>> - No CAN bus messages form PID in poll0, while messages in poll1 is 
>> working OK.
>>
>> Programmed the OVMS module with a version, and verified that the 
>> module was OK.
>>
>> Regards, Thomas
>>
>>
>> 2013/10/30 Thomas Bergo <thomas.bergo at gmail.com 
>> <mailto:thomas.bergo at gmail.com>>
>>
>>     Matt,
>>
>>     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 <mailto: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.
>>
>>         Matt
>>
>>
>>
>>         On 27 October 2013 20:13, Thomas Bergo
>>         <thomas.bergo at gmail.com <mailto: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.
>>
>>             Thomas
>>
>>
>>
>>             _______________________________________________
>>             OvmsDev mailing list
>>             OvmsDev at lists.teslaclub.hk
>>             <mailto:OvmsDev at lists.teslaclub.hk>
>>             http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>>
>>
>>         _______________________________________________
>>         OvmsDev mailing list
>>         OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>         http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20140123/7e6e41e5/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dexter.vcf
Type: text/x-vcard
Size: 206 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20140123/7e6e41e5/attachment-0002.vcf>


More information about the OvmsDev mailing list