[Ovmsdev] Fwd: [openvehicles/Open-Vehicle-Monitoring-System-3] 9a68e2: Tesla Model S basic vehicle support

phil hochstetler phil.hochstetler at gmail.com
Thu Mar 8 02:15:55 HKT 2018


I am technically capable and my "configure your Tesla Model3" email came on
2/28 but i am waiting on the Dual Motor option to be available (now Mid
2018).

So, give me a few months and I will be actively contributing to the Tesla
Model3 code.

I own a V2 OVMS module that I used with  my Think City (now drive a 2016
Leaf).

Phil H.

On Tue, Mar 6, 2018 at 5:05 PM, Mark Webb-Johnson <mark at webb-johnson.net>
wrote:

> It would be cool. First to have a HUD in the Model 3.
>
> We just need someone technically capable who owns a Model 3.
>
> Regards, Mark.
>
>
> On 7 Mar 2018, at 8:19 AM, Greg D. <gregd2350 at gmail.com> wrote:
>
> Given the spartan interior and endless chatter about getting a HUD,
> perhaps our next real target should be the Tesla Model 3?  Use the Model S
> as a learning platform, presuming there will be some continuity between
> vehicles...  Just a thought.
>
> Greg
>
>
> Mark Webb-Johnson wrote:
>
>
> No, I don’t consider Tesla Model S to be a high priority car to support
> OVMS.
>
> However:
>
>
>    - It is the car I currently drive
>    - I am interested in seeing how usable OVMS v3 is as a CAN bus reverse
>    engineering tool
>    - The Model S can bus is relatively high volume, so will stress the
>    system
>    - I can put OVMS v3 into it, and monitor it on a daily basis to get
>    the bugs out (particular modem stability, and modem/wifi switch)
>    - https://github.com/openvehicles/CAN-RE-Tool/blob/
>    master/rules/teslamodels
>
>
> I’ve committed a stub at the moment. Just need to put it into my car, make
> sure the CAN bus parameters are fine, then I’ll flesh it out. Looks like
> the Tesla Roadster cable should work fine for this (I’ve got a ‘classic’
> 2014 Model S).
>
> Regards, Mark.
>
>  Branch: refs/heads/master
>  Home:   https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3
>  Commit: 9a68e225969e45bafa0accc604305c6b17de4971
>      https://github.com/openvehicles/Open-Vehicle-
> Monitoring-System-3/commit/9a68e225969e45bafa0accc604305c6b17de4971
>  Author: Mark Webb-Johnson <mark at webb-johnson.net>
>  Date:   2018-03-06 (Tue, 06 Mar 2018)
>
>  Changed paths:
>    M vehicle/OVMS.V3/changes.txt
>    A vehicle/OVMS.V3/components/vehicle_teslamodels/component.mk
>    A vehicle/OVMS.V3/components/vehicle_teslamodels/src/
> vehicle_teslamodels.cpp
>    A vehicle/OVMS.V3/components/vehicle_teslamodels/src/
> vehicle_teslamodels.h
>    M vehicle/OVMS.V3/main/Kconfig
>
>  Log Message:
>  -----------
>  Tesla Model S basic vehicle support
>
>
>
>
> _______________________________________________
> OvmsDev mailing listOvmsDev at lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>
> _______________________________________________
> OvmsDev mailing list
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20180307/3784f548/attachment-0001.html>


More information about the OvmsDev mailing list