CANVIEW

I will eventually re-post an up-to date detailed description to replace the lost CANVIEW posts, for all those who didn't like losing that information. For now, I am busy because FrankHudon brought his Prius round to do a test install of a CANVIEW monitor and I am having to make changes because he has the JBL amp (which is device 440 on the AVC) and I have the standard (device 190).
I have lost a few more grey hairs over this, but have now resolved it. For those of you interested, those nice beeps (that some of you astonishingly want removed) are created by the MFD sending this command string:
For the standard audio device 190:
wantSbeep:db 5,0,32h,29h,60h,1

For the JBL amp device 440:
wantJbeep:db 5,0,5eh,29h,60h,1

so you can see there is a circuit in the standard audio, address 32h and one in the JBL amp, address 5eh, which generates the beep. In both cases, the last '1' is the length of the beep
'0' is zero length (silence), '1' is standard, '2' is disturbing and '3' or more is get out of the car and run....
Technically, it is now possible to silence these beeps and still send the correct AVC response by monitoring the AVC and, on seeing the above messages, alter the final '1' to a '0' and change the parity (which is also a 1) accordingly. You can do this on the AVC because it allows '1's to be pulled down to '0's (but you cannot pull up a '0' to become a '1' without causing a bus contention problem) But it must be done in real time while the message is being sent which means flipping the bits in under 1uS after you detect the need to do so. It needs a dedicated processor which can't be used for anything else. Its possible but seems an expensive fix for the problem, the primary difficulty being the need to get at the AVC bus, for those without NAV. (That infamous connector) Those with NAV could more easily get at the +12, ground, TX+ and TX- needed. Are you beep-o-philes really that concerned?
eflier

 

Quick CANview update. Sorry about the lack of posts, I've been busy finishing the artwork for the printed circuit board for the larger CANVIEW version, incorporating some (but not all) of the suggestions that came in from those (now missing) posts. Also fixing some software bugs and adding a user selectable screen FrankHudon was really keen on. Mostly done, now waiting on boards arriving next week.
Basic idea is 2 versions, both initially for the 2004/5 Prius without factory NAV: The first is the original small die-cast box which fits up behind the glove compartment and is purely a monitor of some CAN bus messages, presented in text and bar graphs on the MFD display using the touch screen to select menu items. The second is twice as big and won't fit behind the glove box but is intended to go under whichever seat is currently empty. In response to the posts and e-mails, this version also has the basic CAN display, but also has as standard:
1) a SCART connector with RGB and sync inputs for those wanting to experiment.
2) same connector accepts a third-party NTSC composite video to RGB converter for camera video from 3W electronics in the UK. http://www.threedoubleyou.com/otherconverters.htm. About US$100
3) 2nd SCART connector configured to accept the modified cable from a Pioneer AVIC-88 NAV unit for those of us who want NAV but couldn't get it/afford it. The box handles the handshaking needed to convert Prius touch-screen data into the format the Pioneer needs to see. AVIC-88 units with latest North Americam data-base show my back-road in a small Canadian town so are not bad. Haven't got their steering wheel remote working yet, so its operation by touch screen and microphone. Also, who knows the most convenient place to pick up a speed sensor signal in the Prius?
4) a DB9 connector outputting touch screen data in 16 x 16 format at 57,600 baud for experimenters
5) same DB9 inputs data to an internal SIMM socket to accept a BOBIII data-to-video board from Decade Engineering http://www.decadenet.com/ also about US$100
Japanparts.com has now dinged my credit card for 100 of these infamous MFD Fujitsu connectors. (and I have now received 25, so maybe there is hope for the rest)
I know its taking time, this is a 1-man hobby interest, but its getting close now. On price, the first version will probably be US$225 and the second version US$275 (they both use the same 3 microprocessors) You would buy the the converter or the text-video or the Pioneer direct from whoever has the best deal. I'll post more details when I hear more back from Danny, who is understandably busy right now. Or maybe he did reply and I lost the PM?

 

C4: I can't find any reference to a speaker/sensor box at Pioneer, but that would make a lot more sense than me making my own IR sensor/speaker assembly. An IR detector module is cheap but the packaging/cabling costs for a small number make it uneconomic. Any further help identifying what this Pioneer part is and how to buy them would be much appreciated. As would where to get their CDE7024 cables for less than the ridiculous amounts they charge. (I cut one in half to add a SCART plug to both ends to make 2 useable cables, as the original Mitsumi 26 pin connector (G19-026-020-BFBAA-AA) is unique and unavailable.)
Thanks for the info on the speed sensor wire location
I believe you mentioned in a (now lost) post that you had a Classic Prius, which runs different AVC software than the 2004/5 which CANVIEW is aimed at. Have you switched cars or are you hoping to try to kluge this into a Classic? I think that would be a major project with much frustration.

 

Thanks, I didn't know about that purple wire. For convenience, I'm using a single connector in M14 which has the RGBs but also has (undocumented) 2 copies of the AVC on the upper left 4 pins. The speed sensor will hook up to the Pioneer harness, which also includes battery, acc, gnd, so it might be convenient when feeding wires to take the CANVIEW and the Pioneer along the same route. I'm not sure about tapping the M13 harness for the Pioneer power supply because it draws peak currents of a couple of amps, which might put noise on the video, but I'll try it up there instead and see. The CANVIEW only draws 50mA so hasn't been an issue.