Hi MsEnj ! Good to see you around
Hope everything is going well for you and your partner !
....
In terms of the VIM function, think of it as a means to an end.
The function itself is completely useless unless you intend to use it for something.
Now here is where people can try and contribute....
Its great that people want to use the composite input for In car PCs !
This is something that definitely should be encouraged. (Just like the iPad mini install on BigBoss's VE)...
Now if you really wanted to get some benefit out of connecting an in car PC to the composite input, you REALLY need to sort out a number of things,
in tandem with the VIM function.
1) System Input. You have Windows/WindowsCE/Linux/MacOS/iOS/Andriod running, and displaying on the stock headunit !
Great, Fantastic, Brilliant !
Now how are you going to control the interface ?
Touch screen, steering wheel buttons, the lower screen buttons, the existing radio buttons and knobs ?????
Trust me, at this point this problem will make or break your system, far before VIM becomes an issue !
I can currently count only 12 or so people that have contributed anything to Single Wire Can Bus Sniffing.
(Which you are going to NEED to figure out to get the button stuff working).
If people contributed some good quality information here, then I am sure the person that paid $$$$ and contributed many hours to work out the VIM, will quite happily give the information out. (As is the case with the 4 members that have this information already).
2) Say now you have the above nutted out ? Next you will want to probably display something like the HSV EDI system.
(If you just wanted an in car pc for NAV, then you are better off either using an Omega pod with a handheld nav unit fitted, or fitting a Series I nav unit)...
Standard OBDC Can bus data will give you engine parameters, and that's about it. (Revs, Intake temps, throttle position, etc etc).
You REALLY want to pull information such as ESP Pitch and Yaw rates, Brake application, individual wheel traction information under acceleration and braking, transmission gear position, trans temps.
All this requires investigating Proper Hgh Speed J1850 VPW Can data, which cannot be done nicely using a standard ELM Based OBDC Dongle.
3) Now, assuming you know all about the above packets, and you have the hardware to sniff them out, you are going to need software to display this information.
You can try and buy something thats already out there (Either some generic OBDC software that will display engine params), or try and get some specific GM High speed Can software and see how much of it works with the VE....
Maybe even if you have a bit of programming nouse, start an open source project, and try to get some enthusiasts on board to get something really good going ?
.......
So as you can see, there is a LOT of information that needs to be nutted out, and if people are genuinely interested in doing things themselves,
then they will get involved, experiment, and share their findings.
Without people getting involved in the above, the good stuff will never happen (Or will, but the people that worked this stuff out with be very loathe to share the information).
Most of the time however, people want the end solution, and aren't really prepared to put in any hard work (or at least share the information as to how they got to where they are).
If this is the case, then there are places that are more than willing to help out, for a fee of course.
(Nothing in life that is of any value is easily obtained) !