Rodn
New Member
Hi thereI went through CAN-C message $023 again. It's steering wheel position (2 bytes), steering wheel force applied by driver (2 bytes), apparently unused data of $0000 (2 bytes), and then a checksum plus counter (2 bytes). It's not going to be there.
One of the best ways is going to be to record a CAN dump while a vehicle is misbehaving. But we're a little ways away from that in terms of hardware and setting something up that we could distribute to willing volunteers.
On the other hand, someone privately suggested a procedure to better identify what car module is responsible for which messages. You create a list of all the message IDs and then you unplug on of the CAN-C or CAN-IHS connectors from the bus (behind the glovebox). You note which feature(s) have been disabled on your vehicle. You massage the CAN bus traffic to determine which message IDs have disappeared. You can then associate what messages are transmitted by what device.
I know that the Power Steering Module is on the CAN bus, and that second procedure will work well for that. Now that I'm on vacation, I think I finally need to disconnect CAN bus connectors one-by-one and see what associations I'm able to make.
PS: As I go over more strange numbers, I'll keep an eye out for a floating value that might be connected to wide steering events.
I have been working on the dodge / jeep electric power steering pump for a electric car conversion project. I figured out the can packet to enable the pump (believe it's to default 80% output) would like to be able to control the speed as well. I tried a few of the packets you posted (vehicle speed, steering wheel position, torque etc) and no luck in changing the speed. Any ideas.
Thanks a lot and keep up the great work!!
Sponsored