Ginkgo USB-CAN Part 3
Posted 02-24-2019 at 09:03 PM by Indymaynard
So, this project seems like the slowest project in the world...
That's probably because it is. I'll get it figured out one day. At least there is some progress today.
My biggest goal was to get the CAN code that would turn on the stereo and amplifier. Luckily, someone had actually figured this part out already! In this video, the guy demonstrates that you can just send data with an ID of 0. Simple! So I tried to send a 1, using boolean or bit style logic to attempt to turn on the stereo. Spoiler alert: it didn't work that simply. I even tried looking at the code the guy put up. Since I don't speak C, this was as fruitful as teaching my military students electronics theory...
Sometimes, I feel as though it just takes some time for things to sink in. In my case, it's nearly year-long gaps. No worries. Success is success.
As it turns out, the ID of the message has to be 0 (or 0x000). "But the guy said that in the video!" you might say. Yeah, got it. What I didn't have is the data to send in the message. What I also didn't know when I first started working on this project was that the Ginkgo CAN-extend software that you can get from the ViewTool website can give you a ton of info. Like the Linux can-utils, it can update each ID with more recent data. Very cool! What I could then do was to observe the data change listed with the ID I was looking for. This left me with a ton of good info.
I assume this is pretty standard across the 2006-2010 Chrysler family. Your mileage may vary. Here is what I found:
I am going to wind up searching some more, but this is quite a decent breakthrough. Also, I am okay with having been slightly ignorant about the capabilities of the already written software. This is new ground for me.
Jacob
That's probably because it is. I'll get it figured out one day. At least there is some progress today.
My biggest goal was to get the CAN code that would turn on the stereo and amplifier. Luckily, someone had actually figured this part out already! In this video, the guy demonstrates that you can just send data with an ID of 0. Simple! So I tried to send a 1, using boolean or bit style logic to attempt to turn on the stereo. Spoiler alert: it didn't work that simply. I even tried looking at the code the guy put up. Since I don't speak C, this was as fruitful as teaching my military students electronics theory...
Sometimes, I feel as though it just takes some time for things to sink in. In my case, it's nearly year-long gaps. No worries. Success is success.
As it turns out, the ID of the message has to be 0 (or 0x000). "But the guy said that in the video!" you might say. Yeah, got it. What I didn't have is the data to send in the message. What I also didn't know when I first started working on this project was that the Ginkgo CAN-extend software that you can get from the ViewTool website can give you a ton of info. Like the Linux can-utils, it can update each ID with more recent data. Very cool! What I could then do was to observe the data change listed with the ID I was looking for. This left me with a ton of good info.
I assume this is pretty standard across the 2006-2010 Chrysler family. Your mileage may vary. Here is what I found:
Code:
10 00 00 00 or 11 00 00 00 seemed to be what was sent when the engine was off and the key was not in accessory mode. 73 00 00 00 seems to be when the key is turned to accessory mode. 85 00 00 00 appears to be when the key is in the "On" mode, regardless as to whether or not the engine is running. B9 00 00 00 showed as I turned the key.
Jacob
Total Comments 0
