Interestingly, Tesla just announced their EDR (aka black box data retrieval) program. http://www.crashdatagroup.com/tesla-edr-kit/ <http://www.crashdatagroup.com/tesla-edr-kit/> That lists: The EDR Retrieval Hardare Kit for Tesla Includes TIV-144: In-vehicle cable for Tesla Model S and Model X TIV-145: In-vehicle cable for Tesla Model S (legacy) TIV-996: In-vehicle cable for Tesla Model 3 TD2M-601: Direct-to-module cable for Tesla Model X and 3 TD2M-602: Direct-to-module cable for Tesla Model S Power: AC Power supply unit (110v-240v, USA style, 2-prong plug) TPCAN: PCAN-USB adapter CASE: Hard-shell protective carrying case We already know about those TIV-145 and TIV-144 diagnostics connectors (for Tesla Model S and X). This implies that TIV-996 is a different connector/wiring for Tesla Model 3. Given that it is a different platform, there would probably be major differences amongst the messaging. Regards, Mark.
On 7 Mar 2018, at 9:05 AM, Mark Webb-Johnson <mark@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@gmail.com <mailto:gregd2350@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 <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 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3> Commit: 9a68e225969e45bafa0accc604305c6b17de4971 https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/9a68... <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/9a68e225969e45bafa0accc604305c6b17de4971> Author: Mark Webb-Johnson <mark@webb-johnson.net <mailto:mark@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 list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev