2006 Prius MFD GVIF Video Input

<div class='quotetop'>QUOTE(theforce @ Dec 18 2006, 10:10 PM) [snapback]364043[/snapback]</div>

Here are some DIY instructions I found. Looks like a relatively simple circuit to merge the h/v sync together.

<div class='quotetop'>QUOTE(theforce @ Dec 18 2006, 12:36 PM) [snapback]363879[/snapback]</div>

If you do wind up giving up your NAV for this, can I buy it from you?

 

I just realized my last post was exactly backwards. That if you're outputting 800 pixels wide and the MFD is doubling up the right side like that, and the tearing is caused by a resolution mismatch, then it means it's native resolution would be greater than 800, not less than 800. I also have this odd, nagging recollection that someone did find out the native res of the MFD several months ago, and it was some odd number like 864 by something. Perhaps in one of the really long CanView threads? Or - I could have imagined the entire thing.

What you've accomplished so far is damn impressive. I'm just tossing out my stray thoughts in case one might actually lead somewhere.

-Ken

 

Ahhh. I found the comments I was thinking of, it was in the other GVIF thread. The MFD was suggested as being either 848x480, or 840x480.

So get out your magnifying glass, and see if you can count the duplicate pixels.

I'm kidding.. I'm kidding... ... ... mostly

-Ken

 

<div class='quotetop'>QUOTE(theforce @ Dec 19 2006, 12:54 AM) [snapback]364075[/snapback]</div>

Don't forget that it is possible the pixels are not square... Thus the ratio on your PC may be different.

 

<div class='quotetop'>QUOTE(kdmorse @ Dec 18 2006, 11:48 PM) [snapback]364064[/snapback]</div>

Actually, I took you literally... ... ... mostly. What I did was calculate that the mouse cursor in that closeup screen shot is 27 pixels across and that the distance between the duplicated cursors is 71 pixels. Knowing that a standard Windows mouse cursor is 16x16 pixels, we can divide (71 / 27) * 16 to find out how big that glitch is. Using this inaccurate method, I come up with a distance of 42 *actual* pixels. Which is, probably not coincidentally, right in the range of the 840 - 848 you were quoting. It does make sense that the component video conversion would be using a fixed resolution. And since theforce's research indicates the land rovers use 800x480 screens, that is also consistent with the doubling of the last 40-something pixels. All of which is my long winded way of saying I think you're right.

I wonder if using a RGBS is passed through unmolested, allowing us (you) to test this theory...

 

Hi All,

This is awesome. I'm really looking forward to seeing this work.

I had a similar problem years ago with an old computer connected to a new LCD panel. I think (it was a really long time ago) I fixed it by changing the refresh rate to the monitor and working with powerstrip to fine tune the settings. Try downloading powerstrip and give it a go. What I don't know is how the settings in powerstrip effect the composite output on computers.

I have two request of those of you who are actively working on trying to make this work for us.

Can someone take a good look at the GVIF connector on the MFD and tell us if there are any markings on it? I'd like to locate the proper connector at some point.

Those of you who have NAV systems and are testing out this solution, can you run a simple test for us. Completely disconnect the NAV system from the Prius and let us know if the GVIF video input still works. I'm trying to figure out how to make this input work for those of us who do not have NAV systems. With that said, has anyone without a NAV unit tried this adapter yet?

-momanz

 

<div class='quotetop'>QUOTE(momanz @ Dec 19 2006, 08:52 AM) [snapback]364126[/snapback]</div>

I've been working on that too. I know someone makes the connector. I plan to do some really extensive testing right after Christmas and I'll look really closely at the connector for all of us. I know we all want a plug and play system with touch screen cords. I may be wrong but I think the touch screen cords are end voltages and not digital cords, if this helps anyone.

 

That is good enough for me.

 

wow if CANVIEW will work on this mod for an 06, im in. keep us posted

 

<div class='quotetop'>QUOTE(DaveinOlyWA @ Dec 19 2006, 02:22 PM) [snapback]364279[/snapback]</div>

That is the first thing I thought, but now I think I would like the two screens of the V4 CAN-View because I can keep the MFD doing what it is doing such as Nav stuff and the other screen can give me data at the same time.

 

i still have CANVIEW V3 from my 04. i really dont want an extra screen unless someone can make it easy to hide. plus i dont have nav anyway...at least not built in

 

I took a week off to Orlando, FL. I had fun at Disney and Seaworld. I found this great work and progress by theforce. I have been searching as well for a simple cable to connect directly into MFD through GVIF interface. Since I do not have Nav, I will not need to worry about switching between this Video In and Navigation System.

I found a cable on clublexus site specifically using a connector from Mark Levison DVD system. The cable is cheap, about $25.





More information can be found here. Maybe Ken can help us translate exactly how it works.
http://www.rakuten.co.jp/t-plaza/710010/713290/

This gave me idea of connecting straight (Blue connector) into non-Nav MFD. Here is how non-Nav MFD looks like (thanks Darell).



I looked up in the repair manual and created this diagram that I hope would work. See below:



From the back of MFD, M16 is the video connector for Navigation System. This connector only uses pin1 to transfer Video (pin2 and pin3 are not documented).

Now, look at M13-18 and M13-19. I drew two lines where Toyota have wires connected already. They give AVC-LAN communication signals between MFD and the Radio Reciever.

Now, look at M15-3 and M15-6. I envision using these two wires to "tell" MFD" to switch to Navigation video screen. Since I am not an EE graduate, maybe someone can help out here (ScottY? Darell?). Would it work by simply gounding M15-3 or M15-6? For example, I want to simulate the action of pressing the Power button. Hmm I am not sure if turning on Radio would switch MFD into "Audio" screen. I know the "Audio" button on MFD do this but my MFD does not have Navigation button on it.

So two questions are:
1) Will modifying and connecting this cable into M16 work?
2) Even if 1) works, how do we switch to it? Can we do it by using M15-3 and M15-6?

Dennis

 

From what I am starting to understand you have to tell the system a new part or signal is there like adding new hardware to your computer. You have to tell it that it is there and then you can start using it. Sort of like adding the Satlite radio. You have to tell the system it is there and then the three sat screens start to work. How do you tell the system or fake the system into thinking a nav unit is there? I don't know yet, but I think that is how costal is adding an additional channel for the lock pick units. The extra channel is already there we just have to figure out what part of network to tell.

Force, did you notice that is a 6 pin wire and the plug to the right of the GVIF port on the back of the MDF is also a 6 pin plug? Any ideas? I wish we had a full pin out map for the MFD.

 

Hi Theforce
Hope all is well.
On the MB cars that have No nav you can do the following trick. If you hook up a nav unit and then unplug it the network thinks the nav unit is still there and you can open the video port. If you can please try this on the Prius. If you can I can program a micro controller to send out the same data that the nav unit sends to the car so that the car thinks that there is nav in the car even when there isn't.
Thanks Dominic www.TVandNav2Go.com


<div class='quotetop'>QUOTE(theforce @ Dec 20 2006, 07:06 PM) [snapback]364849[/snapback]</div>