Hi guys, I'm John.
I'm new to all this so please be gentle.
I'm almost finished my Supra project and am just about to fit the Syvecs I've just purchased from Ryan. I've fitted a Dash2 display to the car which is to be linked to the Syvecs, but I'm struggling getting my head around a few things.
When I spoke to Ryan yesterday, if I understood him correctly, he explained that to link the Dash2 to the syvecs the plug on the can bus cable must be taken apart and 2 wires from there plug must be attached to the syvecs harness adaptor.
Am I correct in thinking that all the info required is transferred through these 2 wires.
Do I still need to connect the anolog inputs I wish to display on the dadh2 or will all the info go direct from the can bus.
My anolog 1 is for my fuel gauge, anolog 2 for boost and anolog 3 for AFR.
I have also been told on mkivsupra.net I do not need to connect the speed and rpm wires either as the can bus cable will transmit the relevant info from the syvecs.
I may sound like a complete fool here but here goes, what I cant understand is how does all that information transfer through 2 wires. I would have thought it would need 1 wire per signal input so to speak.
Or have I totally misunderstood what Ryan has told me here.
Would someone explain in simple terms how this all works please.
Thanks in advance for any help.
Thanks
John
S6 and Dash2, understanding can bus
-
pat
- Syvecs Staff - Cleaner
- Posts: 356
- Joined: Fri May 23, 2008 10:23 am
- Location: Out there... somewhere
- Contact:
Re: S6 and Dash2, understanding can bus
John,
the clue is in the name... CAN == Controller Area Network
It's a computer network that can connect two or more devices that may wish to share information. In the case of the implementation in our ECUs the bus runs at the maximum permissible 1Mbit/sec. Each data frame on the network uses either an 11 or 29 bit identifier and can have up to 8 bytes of data payload. We use CAN IDs 0x600 through 0x613 to transmit various ECU running parameters; each identifier carries up to four such parameters allowing up to 80 parameters to be sent. Each frame's repetition rate can be configured independently so things that are likely to change rapidly can be transmitted more frequently than things that change slowly (eg throttle position vs coolant temp).
Hope this helps,
Pat.
the clue is in the name... CAN == Controller Area Network
It's a computer network that can connect two or more devices that may wish to share information. In the case of the implementation in our ECUs the bus runs at the maximum permissible 1Mbit/sec. Each data frame on the network uses either an 11 or 29 bit identifier and can have up to 8 bytes of data payload. We use CAN IDs 0x600 through 0x613 to transmit various ECU running parameters; each identifier carries up to four such parameters allowing up to 80 parameters to be sent. Each frame's repetition rate can be configured independently so things that are likely to change rapidly can be transmitted more frequently than things that change slowly (eg throttle position vs coolant temp).
Hope this helps,
Pat.