Datalogging EV-CAN Bus Information through OBDII

[pcspilot]

Anyone made any progress on Data porting. I’ve got a bad tire pressure sensor somewhere and the dealer doesn’t know how to find it without plugging their computer in. AND of course they don’t have the right computer here in Milwaukee.

 

[alflash]

under construction

 

[TonyWilliams]

... I’ve got a bad tire pressure sensor somewhere and the dealer doesn’t know how to find it without plugging their computer in. AND of course they don’t have the right computer here in Milwaukee.

1. The technicians of an authorized serviceshop must have and must be able to use at least scan tool Techstream Lite: https://techinfo.toyota.com/techInfoPortal/appmanager/t3/ti?_pageLabel=ti_ts_lite with this interface: http://drewtech.com/mongoose/toyota2.html

2. These supposeds (ostensibly) experts should know, that the TPWS any trouble codes (aka flash-codes from the tire pressure warning light in the combination meter) can be read also without a scan tools by connecting (shorting) of terminals 13 (TC) and 4 (CG) of the DLC3.

Such ignorance is a Shame for "Toyota Motor Sales, USA"

Can you take a picture and clarify this “shorting” method?

 

[alflash]

... I’ve got a bad tire pressure sensor somewhere and the dealer doesn’t know how to find it without plugging their computer in. AND of course they don’t have the right computer here in Milwaukee.

1. The technicians of an authorized serviceshop must have and must be able to use at least scan tool Techstream Lite: https://techinfo.toyota.com/techInfoPortal/appmanager/t3/ti?_pageLabel=ti_ts_lite with this interface: http://drewtech.com/mongoose/toyota2.html
2. These supposeds (ostensibly) experts should know, that the TPWS any trouble codes (aka flash-codes from the tire pressure warning light in the combination meter) can be read also without a scan tools by connecting (shorting) of terminals 13 (TC) and 4 (CG) of the DLC3.
Such ignorance is a Shame for "Toyota Motor Sales, USA"

Can you take a picture and clarify this “shorting” method?

Let me know , how I can send to You this Description (for TPWS) from original RM for RAV4EV 2013 MY?

 

[pcspilot]

Is there a way to get a copy of the repair manuals for these vehicles?

 

[alflash]

under construction

 

[alflash]

under construction

 

[asavage]

Interesting. Thank you for the link.

 

[asavage]

We opened up the communications "Gateway computer" module at the left rear of the Rav4, and logged data for a future "energy level" instrument.

Hey! You've got my Tek 'scope!

Seems like you've paid Photobucket the requisite pizzo, and I can finally see the images in this post, so I'm just now seeing my 'scope in your RAV. Too bad Photobucket doesn't (seem to) provide any way to see a higher-res version, but I'm pretty sure my two Flukes are older than yours I have a 79 for bench work and an antique 23 for field work.

 

[ogmm]

I saw the pinout for the back DLC3 port and seems to be a RJ-45 ethernet connector on the other side, but the voltage levels seems to be different.


Should it work on any ethernet port and what program are beeing using for datalogging?

 

[asavage]

While Tesla/Toyota may be using an RJ45 connector, I doubt that it should be treated as an ethernet port.

For example, I have at least four different pieces of equipment in this building that use RJ11/12/45 connections, and none of them are POTS/POTS multiline/ethernet respectively, though you might guess otherwise.

 

[ogmm]

although on several sites seems to be a simple cisco ethernet usb adapter.

http://alflash.com.ua/phpBB2/download/file.php?id=2963&sid=245c80eccc8c3b512c331c5ddd3e239e&mode=view

see page 12:
https://static.nhtsa.gov/odi/tsbs/2013/SB-10060730-2280.pdf

on this video from Alltech, pins used are 1,2,3,6 same used on an ethernet cable:

https://www.youtube.com/watch?v=H-9nJeN80oA

the adapter seems to be this one:

https://www.walmart.com/ip/linksys-usb-ethernet-adapter/12321722

 

[hokiematt]

The rear data link connector is indeed Ethernet (pins 1/3/9/11) as well as 500kbps CAN (pins 6, 14).

If you're looking to log data, the CAN feed is your best choice as there's a live stream of over 100 ID's being broadcast.

 

[asavage]

Good information, Thanks!

 

[alflash]

under construction

 

[hokiematt]

With this use of CAN, Tesla's "live stream of over 100 ID's" can be considered?

Yes. For instance, as Tony noted in the first post, data in message ID 0x102 increased while charging. A search of the web will show that for the Model S, ID 0x102 is from the BMS, with the lowest 16 bits representing battery voltage (0.01 V/bit scaling).

 

[ogmm]

Its been a long time.

Working hardware:
1)arduino nano and two MCP2515 modules(some PIDs seems to be missing due Nano performance. Can't be used with Savvycan tool)
2)arduino due and two sn65HVD230 modules(better performance than nano and can be use Savvycan directly to inyect your own PIDs and other features)https://aws1.discourse-cdn.com/arduino/original/4X/d/7/e/d7e0b38189b57523c43726dea2ea85e3e724502d.jpeg

Progress so far:
Tested and working. Send the all the IDs ending with HEX value C from a previous capture( with the charger module connected to the CAN BUS and READY ON). I was able to fool the other ECUs and turn on(READY ON) without the charger module connected to the CAN BUS and the EVSE connected to the charging port.

Decoded IDs:
63A Firmware version THC-R8.. Thermal ECU
5F2 Firmware version BMS-R20. BMS
5EC Firmware version CHG-R9.. Charger
5F4 Firmware version PMR09-08 Pedal
5F6 Firmware version DIR09-08 Drive Unit

Also the ending HEX value on other IDs is the originating device, for example the "C" in the ID "5EC" indicates that the Charger made that CAN message and all other messages ending with xC.




My Goal is not achieved yet, i want to be able to charge while driving (where I'am located there isn't charging infrastructure) so I'm planing to charge with a generator(only for long distance travel). I had tried to send a capture (captured when vehicle was connected to the EVSE and not charging and then push "charge intermediately" on the central console), but the contractor won't close and the charger doesn't start to charge with the capture. My question is Am I missing something?(probably a lot hahaha) Could someone help me to decode some other IDs? any help will be appreciated.

Captured data and other information:
https://drive.google.com/drive/folders/1gGruQLR76xKQYuuA2xGA-ZdYn6lncv5d?usp=sharing

 

[miimura]

I have a OVMS port in progress on GitHub but I haven't had time to work on it for about 6 months. Starting with a DBC file from a 2012 Model S was very useful for decoding the Tesla CAN bus. The Toyota CAN bus is another story.

The goal is to have something working before SafetyConnect is shut down. The OVMS LTE modem has been released to production, but I don't think it's available at the US distributor yet. I have one with a 3G modem, but that's not useful going forward. You could always use it with a WiFi Hotspot device.

https://www.openvehicles.com/
https://medlockandsons.com/product/ovms-v3/

 

[ogmm]

Thank you miimura maybe you can share your DBC file or GitHub, it will very helpful.

Also if someone knows which is the ID for enable the battery internal contactor and/or Switch the BMS to charging mode, it will highly appreciated.