The concept is proven. You can split the data from the CAN BUS! I have been thinking about the possibility of splitting the DLC3 plug and CAN BUS data to two different monitors so I can compair the data. I have finished a prototype splitter and it appears to work with the CAN View and the ScanGage together. I ordered two OBD2 extension cables : http://www.obd2cables.com/products/index.php. Then I cut them up and spliced them together. I have a few pictures. I now will be able to run the ScanGage and CAN View together. I hope that this may open other possibilities. So here are the pictures. Ok I am old and compulsive and my grandfather and father were compulsive so I soddered all the splices. There may be other simpler alteantives. Go for it. We can push back the darkness.
I have a scanguage as well as the canview and was wondering the same.. how can I use both.. the scanguage has much better MPG data.. How much to make me one of those cables? Scott
Careful here. The CANbus is a transmission line, with a terminator at each end -- in this case, one in the engine ECU and one in the battery ECU. See NCF "Multiplex Communication-CAN (Controller Area Network)", ileaf/toyncf2/toyncpdf/ncfsourc/2004ncf/04priusn/be/multi3.pdf. A high-speed bus like this is really supposed to pass very close to each device on it, with no branches, and the 120 ohm terminator at each end to prevent ringing. Toyota obviously takes a few liberties here, with short branches at each end of the car -- the whole bus is short enough over the length of car, I guess, that a few short branches don't cause problems... Or the harness is done in a way that minimizes branch length as much as possible -- haven't really looked. Anyway, adding more arbitrary branches off the DLC3 may affect communication quality. . The DLC3 carries the *direct* CANbus with no buffering, and most widgets that talk to it have the CAN transceiver right there in the DLC plug or a very short distance away. [Does CANview do that?] . _H*
my CAN-view module is approx. 9" from the DLC connector. Most OBD11 hand scanners have a 5-6' cable to connect to the DLC plug. At most, the CAN-view module locations are with in the 5' range.
"how can you tell that Henry is in the medical profession? hemostat as a soldering aid! " Or a 70s era stoner... ;-)
Thanks for the information. I would guess the cable for my CAN View a Nav model is about 4-5 feet long it runs from the connector, along the fire wall under the dash then under the front lower kick panel and the trim by the door to under the seat where the CAN view sits on top of the Nav ECU. It is just long enough for the job. The cable for the ScanGage is 5 1/2 feet. My splitter adds 22 inches. I have written Norm and it may be that the ScanGage is not reading the CAN Bus but acting as a OBD2 diagnostic device sending out a request for data and waiting to receive data back. This could explain the slow up date speed of the ScanGage as compared to the CAN View. Hobbit before I move on would that make a difference in using these devices together as apposed to 2 devices reading the CAN Bus? Maybe I should back off and stick to people?
Not sure. What might be needed is some sort of little repeater widget, that creates a new CAN bus and passes bytes between them. It might not even need to be a particularly smart device, just something to fix up impedances on either side of itself. But adding some smarts could also let it help filter messages. I haven't studied enough about CAN physical layer to be much more help here... . _H*
