thats why you get the can sniffer like he posts about and figure out what the data structure is.
The problem is still that I don't think anybody knows that CAN frame information for the Jeep.
It is easy to replicate CAN signals (like that CAN opener does) when you know what the frame/bit/byte information is. But near impossible if you dont, and that CAN opener wont do squat without it.
thats why you get the can sniffer like he posts about and figure out what the data structure is.
hmmm... good luck.
You see his abilities, and it's taken him how long to decode a couple of signals for the cluster.
Yeah, I guess it did take him a month from start to finish to get his car sorted.
I'm not saying it's impossible, but a month for someone with skills like that is an awful lot of effort compared to swapping a cluster and some harnesses.
I dont know the complexity of the car he is working on either, but I do know that todays cars that I deal with have over 2000 data signals in over 100 CAN frames.
If just one of them is not transmitted correctly, all sorts of failsafe action can happen.
Yea, I *could* do it, but I'd rather spend a weekend swapping looms than a month or more chasing data codes.....
Especially when the only difference between the canbus and non canbus models is the wiring loom and the boxes that plug into it, the mechanics has been the same since they introduced EFI in the 80's.
Bookmarks