Complete car rewiring with module delete possible?

[gnalan]

I thought it was 4: 2 for CANH and 2 for CANL. Where'd the other 2 wires go?

[vtl]

The terminology might be confusing.

1. Volvo has 2 CAN-buses, one is "high-speed" and another one is "low-speed". You see them referenced as CAN-H and CAN-L sometime.
2. CAN uses a differential signalling, which consists of two signals known as "high" and "low", so you may them mentioned as CAN-H and CAN-L.
3. Sometimes they are named as CAN-H+/CAN-H- and CAN-L+/CAN-L-. Or CAN-HS+/CAN-HS-, ..., etc.

In OBD-II port there are 4 pins for 2 CAN-buses: high and low for high-speed CAN, high and low for low-speed CAN.

[gnalan]

So are there 4 wires from module to module, CANH+, CANH-, CANL+, and CAN-, or are those 4 wires only at the OBD-II plug?

I thought I had the workings of the CAN-bus figured out, but now I'm not so sure. Can both of the CAN+, high and low, be run on the same wire, and both of the CAN-, high and low, be run on another wire? Is that how there's only 2 wires from module to module?

Does a module ever send both a CANH and a CANL signal at the same time, and if so how does the priority get set for which one to send first? Wouldn't both signals be equally necessary, or am I just confusing myself more than what I already am? (This is assuming both CANH and CANL signals are sent over the same 2 wires.)

[vtl]

CAN-bus has 2 wires: high and low. Wikipedia has a pretty good article: https://en.wikipedia.org/wiki/CAN_bus CAN is a very smart solution invented for the automotive needs that solved way more existing problems than created new ones

In Volvo some modules are connected to one CAN-bus, while others - to another CAN-bus. Both can be accessed via OBD port, thus it has 4 pins for both CAN-buses.

[volvolugnut]

Like the horrible glue they used on the interior door panels? I still haven't found an adhesive that'll hold them together right yet. I don't know if the green stuff needs to be scraped off first, or if I need a stronger adhesive.

Tips for door panel attachment:
After trying several adhesives, I had good long term success with contact cement on the door panels. A tip I found was to spread the contact cement on both surfaces and then just before assembly, use acetone to activate the contact cement. Acid brushes work well for spreading. The contact cement may take quite a while to get spread on both surfaces, but the acetone will reactive the contact cement when you are ready to clamp. Have all the clamps planned out before applying the acetone.

Scrape down to the wood material to get good adhesive grip.

volvolugnut

[gnalan]

So it's the CAN-bus that allows VIDA to read/control/program everything in the car through DiCE? Is there a way to look at the raw data being transmitted to/from the car through either DiCE or VIDA? I'm assuming the data needs to be stored somewhere when connected to a laptop via DiCE in order for VIDA/VDASH to have access to it, right?

[gnalan]

Tips for door panel attachment:
After trying several adhesives, I had good long term success with contact cement on the door panels. A tip I found was to spread the contact cement on both surfaces and then just before assembly, use acetone to activate the contact cement. Acid brushes work well for spreading. The contact cement may take quite a while to get spread on both surfaces, but the acetone will reactive the contact cement when you are ready to clamp. Have all the clamps planned out before applying the acetone.

Scrape down to the wood material to get good adhesive grip.

volvolugnut

Is this what you're talking about?

[volvolugnut]

I actually used Pliobond brand contact cement. Any brand will likely work.

volvolugnut

[vtl]

So it's the CAN-bus that allows VIDA to read/control/program everything in the car through DiCE? Is there a way to look at the raw data being transmitted to/from the car through either DiCE or VIDA? I'm assuming the data needs to be stored somewhere when connected to a laptop via DiCE in order for VIDA/VDASH to have access to it, right?

Yes, you can watch the TSDice32-<date>-<time>.log somewhere down the VIDA install directory. Look for lines like

Code: Select all

02:42:50,578 0100 000004 PassThruWriteMsgs() msg[0].Data = [0x00, 0xf, 0xff, 0xfe, 0xcb, 0x50, 0xb9, 0xfb, 0x00, 0x00, 0x00, 0x00]
02:42:50,640 0100 000004 PassThruReadMsgs() msg[0].Data = [0x01, 0x20, 0x00, 0x03, 0x8f, 0x50, 0xf9, 0xfb, 0x57, 0x00, 0x30, 0x66]

VIDA has every aspect of all supported Volvos encoded in MSSQL database that is accessible to a curious user.

[gnalan]

Yes, you can watch the TSDice32-<date>-<time>.log somewhere down the VIDA install directory. Look for lines like

Code: Select all

02:42:50,578 0100 000004 PassThruWriteMsgs() msg[0].Data = [0x00, 0xf, 0xff, 0xfe, 0xcb, 0x50, 0xb9, 0xfb, 0x00, 0x00, 0x00, 0x00]
02:42:50,640 0100 000004 PassThruReadMsgs() msg[0].Data = [0x01, 0x20, 0x00, 0x03, 0x8f, 0x50, 0xf9, 0xfb, 0x57, 0x00, 0x30, 0x66]

VIDA has every aspect of all supported Volvos encoded in MSSQL database that is accessible to a curious user.

Looks like you missed a 4-bit value in your first row of code. 0xf means nothing.