If anyone is done with their logger, please pass it along to another that wants to test. Just let me know so I can keep track of them.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Chassis CAN Logging To ASCII Text Plus Graphing
- Thread starter lolachampcar
- Start date
-
- Tags
- Driving Dynamics Model S
MarcG
Active Member
I just received the one you sent me last night, thanks again!
Now, silly question but: what software can I use to start collecting data?
You will need to go back through the thread for specific instructions but, basically, the logger creates ASCii text files. You use a PC (not Mac) to copy the file from the logger just like you would copy a file from a memory stick. Several participants have put a lot of energy into Excel spread sheets to better visualize what is going on.
This is very propable
But I could not figure out how to make this "Interprete" tick box work. To my understanding I would need a .DBC-file with the all the parsing rules. This file I did not find. Anyways, I have made some parsing trials in Excel eek. I would like to have full parsed data set to compare against my trials.
breser
AutoPilot Nostradamus
Strange situation. I did some recording a while back and haven't had a chance to look at the logs or do anything with them. I'm at a conference helping man a booth and so I'm looking at them now. But it seems the entire log reports the throttle position and the rear torque is all over the place.
For example.
Any ideas on how to make sure this doesn't happen again or is this some sort of issue caused by a software update on Tesla's side.
For example.
Any ideas on how to make sure this doesn't happen again or is this some sort of issue caused by a software update on Tesla's side.
pupik
Member
because Tesla changed meaning for CAN messages 0x154 and 0x1D4 in firmware 2.16.17!
so I changed both torque messages to messages 0x145 and 0x116
new position pedal message I don't know right now
I just love it.....
Could it be that Tesla sees data on the forums then changes message structure? Why on earth would you do that?
Could it be that Tesla sees data on the forums then changes message structure? Why on earth would you do that?
pupik
Member
It is unlikely, if the wanted to, they would change everything what was monitored.
that's sad. Is that why I got no Drag data when I tried? I think it still pulls battery info.
it was neat while it worked, thanks!
MarcG
Active Member
Can you please provide the decodes you are using? Or are you saying the decode is the same, but the content is served as a different message id?
Anyone else know what the new TPS is?
Bill D
Member
Bill - I'll drop it into the UPS box tomorrow and you should get it in a day or two.
Sorry I was out-of-town and didn't have an opportunity to go to the Palm Beach drag strip and see how closely the excel virtual time slip compared to the real thing. Hopefully I'll get a chance to try that with the logger's next iteration. Perhaps a CAN-to-Bluetooth-to-iPhone-to-Cloud version.
Thanks again for building and loaning us these very cool loggers.
pupik
Member
I use this decode for both torque...
front - CAN3 - ID 0x0145
rear - CAN3 - ID 0x0116
torque = ((byte0 + ((byte1 & 0xF) << 8)) - (512 * (byte1 & 0x8))) / 2
Bill
Got it. Thank you!!!!
thank you pupik!
I'll likely revisit it in the future but and currently tied up with other projects.
I'll also go back and overlay the two reported torque values from files captured before the change to see how they compare.
Got it. Thank you!!!!
thank you pupik!
I'll likely revisit it in the future but and currently tied up with other projects.
I'll also go back and overlay the two reported torque values from files captured before the change to see how they compare.
