![]() |
Quote:
Sent from my Pixel XL using Tapatalk |
Quote:
|
Quote:
|
Quote:
Are you driving when reading this? The sensors go to sleep and only start sending values after a minute or so of > some minimum speed. One of the bytes in the 385 signal tells you which sensors are sending valid data. |
Thanks for that. I'll pull a CAN log while driving later today and report back.
|
I made a run and pulled some CAN data for 10 minutes while driving, and sure enough I get the tire pressures on 0x385. Thanks for the tip!
|
Great work and information here everyone!
I see that you were able to read when a commands like ‘unlock doors’ ‘open trunk’ were issued but has anyone determined how to send the commands over the obd2? Also, i am aware of how to request pid information to the obd2 (in theory but not in practice yet) but how do you listen to the can bus data? Sent from my iPhone using Tapatalk |
I personally have access to some decent CAN tools through work (write software for braking control ECUs), so I borrowed them one night to pull data. I didn't send any messages, but it's simple with decent tools. What are you working with?
|
I have to check when i get home, but i believe it is an obd to usb based off the stn1110 chip through a raspberry pi using python
Sent from my iPhone using Tapatalk |
I'm not familiar with the CAN solutions on the Pi. Does that just give you raw data? Can you load database files
|
Im sure there may be a way to work with database files through python but i am not sure how. I can get raw data from the obd2 by sending requests over a serial port. From my understanding of this thread, it seems that it is possible to intercept the CAN data and record what the control systems are sending back and forth. This would allow me to get some of the more interesting data like tire pressures and yaw rate etc.
Sent from my iPhone using Tapatalk |
I just dont know how to intercept that CAN data
Sent from my iPhone using Tapatalk |
1 Attachment(s)
I could be misunderstanding the tools that you're using, but I would assume that the raw data that you're reading over the serial->OBD connection you have is the raw CAN data.
I'm personally using a program called CANalyzer by Vector. It interfaces to a hardware module that plugs into my laptop's USB port and then into the OBD port. I added a screenshot that shows some of the CAN traffic, including the line for the tire pressure from address 0x385. I asked about CAN database files because we could more easily give meaning to the data (Instead of showing 0x385, maybe it would say something like "tpm_ecu") and it can give interpretations of all the bytes of the response message, along with any conversion or scaling |
I should probably add that my data doesn't line up completely with the spreadsheet. I have ids that he doesn't list, which I wouldn't think too much about. But he also has ids that I don't see over the course of a ten minute log
|
I just want to add a little info to this. Nothing truly helpful; just something I noticed. I have a manual base model (no rev matching) and I REALLY want to plot my current gear against other data.
I noticed that in all of my logs that I never receive any messages with id 0x421 (what's supposed to contain this data). Looking at the spreadsheet, I see that this message also transmits the S-Mode status. I remember a post I read a while back about adding rev matching to a base model, and two of the things needed are a gear position sensor and a new ECU. Given that I don't have the proper ECU (or even the actual sensor!), this has to be the reason that this message isn't on the bus. Just a heads-up to anyone with a base model trying to sniff out the CAN bus. |
All times are GMT -5. The time now is 06:02 AM. |
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 PL2