Can Bus Settings / Speeds / Commands

[jmccorm]

https://github.com/beaups/giulia_ESCape

That's your project? I'll take a look!

Sponsored

 

[jmccorm]

I've finally gotten the driver working. I was using the latest build of raspbian (5.10.63) so the CAN driver was already built into the kernel. By using Waveshare's driver install instructions, I prevented the native driver from working properly.

And... wow. The CAN driver takes advantage of kernel's built-in FIFO stack (and kernel memory buffer) just like it uses for TCP/IP networking. Event filtering is possible as well as multithreading. Dropped packets shouldn't be an issue, at least, not at the kernel level. NICE!

At this point, I'm moving my project's discussion over to it's own thread. Thanks for all the help, redracer. Hopefully we'll both still continue to have things to learn from one another!

 

[jmccorm]

--vehicle settings from radio screens:
314#01.01 02 auto door locks off - on
314#02.01 02 auto unlock on exit off - on
314#07.01 02 flash lights with lock off - on
[ ... ]
314#21.01 02 Hill start assist off - on

I've uploaded all of your contributions to the CAN ID tracking spreadsheet along with the findings of others and myself. I have to say, I think it's coming along quite nicely! If you haven't taken a look recently, I hope to inspire you.

While I was plugging in all of your uConnect vehicle configuration settings, I saw that it used a completely different format for storing those than is used anywhere else I've come across so far. You start with a CAN address of 314, then the first byte (or the first byte followed by 03) is used to identify the setting being modified, followed by the changed value that you want to store. So writing $05.03 to CAN ID $314 selects the "Sound horn when locking" feature and adding a final $00 to the message is what tells it to disable that feature.

The problem I wondered is how you or I might go about determining what these and other variables have already been set to? Were you able to find a way?

I was thinking that it might not be possible at all (because the method of storing them is not reverseable), but then I remembered something. What the uConnect radio forgets it's settings, if you wait 24 hours, it finds a way to read them back in. And you there's an obscure procedure which can make that happen even faster.

Someone would have to simultaneously press the button that is in the center of the left volume knob, and press the button that is in the center of the right tuner knob, and hold those buttons down for a full 60 seconds. Then, when both the buttons are released, the uConnect radio radio reboots and recovers all of it's previous settings. I'm thinking that these settings (like the radio's configuration) are stored in another module, like the body control module, and they are retrieved from scratch whenever a reset method like that is used?

What are your thoughts?

 

[huntb]

I've uploaded all of your contributions to the CAN ID tracking spreadsheet along with the findings of others and myself. I have to say, I think it's coming along quite nicely! If you haven't taken a look recently, I hope to inspire you.

While I was plugging in all of your uConnect vehicle configuration settings, I saw that it used a completely different format for storing those than is used anywhere else I've come across so far. You start with a CAN address of 314, then the first byte (or the first byte followed by 03) is used to identify the setting being modified, followed by the changed value that you want to store. So writing $05.03 to CAN ID $314 selects the "Sound horn when locking" feature and adding a final $00 to the message is what tells it to disable that feature.

The problem I wondered is how you or I might go about determining what these and other variables have already been set to? Were you able to find a way?

I was thinking that it might not be possible at all (because the method of storing them is not reverseable), but then I remembered something. What the uConnect radio forgets it's settings, if you wait 24 hours, it finds a way to read them back in. And you there's an obscure procedure which can make that happen even faster.

Someone would have to simultaneously press the button that is in the center of the left volume knob, and press the button that is in the center of the right tuner knob, and hold those buttons down for a full 60 seconds. Then, when both the buttons are released, the uConnect radio radio reboots and recovers all of it's previous settings. I'm thinking that these settings (like the radio's configuration) are stored in another module, like the body control module, and they are retrieved from scratch whenever a reset method like that is used?

What are your thoughts?

I doubt the default settings are stored in the BCM. What is most likely occurring is that there is a copy of the default software stored in flash on the head unit itself and when the reset procedure is applied, it runs a bootloader application that reflashes the head unit with the default software

 

[Nicor]

I am about to join this project, the only question I have now is what are the best connectors to use?

Do you guys have both part numbers for the CAN-C and CAN-IHS if I want to get these from Mopar?

Thank you

Nico

 

[covidcommander]

What happens if you wire something to the can bus backwards?

 

[Bob Burd]

What happens if you wire something to the can bus backwards?

If it's just a listener, that thing won't work. If it's a transmitter, you will likely brick the canbus and your vehicle until corrected.

 

[covidcommander]

I keep seeing can hi and can low. My wiring diagram books shows can + and can -

Are these the same thing?

 

[Bob Burd]

Yes

 

[covidcommander]

I have the white and the green star connectors. According to my research the can "c" network (500 kbps) is the big green star connector with the small white plugs and the can ihs (125 kbps) is the big white star connector with small green plugs?

 

[Bob Burd]

This is correct

Sponsored