[Ovmsdev] ODBII Error Code Resetting/Retrieval?

[Mark Webb-Johnson]

Nikki,

Some time ago, we added support to the virtual vehicle model to allow trouble codes to be sent back to the server+apps, and for the server to be able to reformat the trouble codes (per vehicle type) with a textual message (as there is not enough room for a textual mapping in the vehicle firmware, and doing it in the cloud allows us to add more mappings without having to update vehicle firmware).

The Tesla Roadster car module supports this, and can send alerts through to the cellphone.

It could be done in other vehicle modules, but is vehicle specific.

Regards, Mark.

On 21 Oct, 2013, at 4:08 pm, Nikki Gordon-Bloomfield <nikki at aminorjourney.com> wrote:

> Hi Folks, 
> 
> Just wondered if reading and resetting ODB codes have ever been thought about for OVMS? Our Volt threw a couple of error codes over the weekend, and it would have been great to receive them on the phone and remotely reset them. 
> 
> In this case, the two errors were common ones which reset themselves after a few hundred miles of driving, and relate to there being a problem with communications between the car and the charging station. Apparently, the error condition can be set if you don't plug the J1772 gun into the car just right…
> 
> Anyway. A though :) 
> 
> Nikki. 
> 
> P.S. While we're on the subject of the Volt, have we ever got a U.S. owner with OnStar to log the remote lock/unlock and pre-condition commands? I've got someone in mind I can ask to help log them if not… 
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev