@that_kid Let the party begin
Meanwhile, I've spent 3 hours trying to get my system to remember switching to MFD2 if by chance previously booted without it connected.
My system is somehow weird so this might not apply to most of you. I am using an Asus EEEPC 900HA with a broken (and removed) lcd screen.
But anyway, the problem is that it still thinks it has its internal monitor attached so whenever it boots without a monitor attached it defaults to full screen internal lcd with no output to VGA and it STAYS that way even if you reboot it with the MFD2 attached.
I've managed to get a solution by using the intel included with the drivers utility igfxcfg.exe together with a 3rd party tool called qres.
So what I did is save the Scheme when everything is in good working order with a proper name from Scheme Manager in Intel Settings and then created a batch file in startup folder with this:
qres c=32 x=800 y=480
The stupid igfxcfg utility would not save the actual resolution but the closest it can validate (800x600) so I had to use the qres util to switch back to 800x480.
This way if I somehow boot without MFD2 plugged in, i just restart the PC and everything should go back to normal. It's ugly but it works.
If it were on linux, this would had been a non issue, everything being neatly configurable from xorg.conf.
Unfortunately on linux there's no iGO navigation software.
@dlbogdan I see that you are using the MFD2 out of the car to do testing work. How are you powering the device?
12V on SAFE pin and UB+ pin. Used chassis for 0V
For my mfd2 I needed the safe pin code as well.
Yes, a minor nuisance if you have your MFD2 powered outside the vehicle (no CAN Gateway) is that every time you lose power you have to input the code at start-up. The bright side is that you'll soon burn that code deep into your brain so you'll never need to scavenge for it through the car dusty manuals ever again :)
Also, it's interesting to know that all of VAG navigation units share (pretty much) the same AUX video input specs (with some US units that don't have one at all). Like RNS 510, even RNS 3xx, Audi Navigation Plus, etc..
So most of this investigation should apply to all of them.
Things might be different on the data side of the story (i.e. Video in Motion and CAN-Bus telegrams) but we haven't yet touched the subject.
I'm still thinking of a way to listen for can data on bench. It's way too cold out there for can bus sniffing. Still waiting for @that_kid with his results on that.
(I might need some help from someone in US to buy that touch panel. I think I've found a fujitsu touch panel compatible to the MFD2 unit but there's a very high price tag on package handling for europe. If someone's willing to help, PM me)
I think that sygic drive exist in linux !
This morning I wrote up a nice ling post with the steering wheel id's and such and then i went to attach a picture of my steering wheel buttons and the site crapped out. so I'll have to do it again.
For the steering wheel controls here's what I have
ID D0 Function
0x5C3 0x6 Volume up
0x5C3 0x7 Volume down
0x5C3 0x8 Ok button
0x5C3 0xA menu up
0x5C3 0x9 menu down
0x5C3 0x1 scroll wheel up
0x5C3 0x81 scroll wheel down
those id's will keep getting transmitted as long as the button is held down. Once you release the button the a message of
is sent and I've found that you can use this as a debounce trigger.
I have a bunch of captures of all sorts of things including registering the mfd2 on the canbus although I don't know all the id's needed but i did capture from the moment the mfd2 was plugged into the bus until all the msgs stopped. I can post those files too.
Brilliant @that_kid. Keep it up. Definitely useful information. 1st post updated with this.\
@pierrotm777 I'll definitely try Linux now when nothing is really pinned. I'll have to get a hold of a good IVI software (centrafuse for linux?!) and see if there's a trial for sygic linux version to see where that takes me. Thanks for the tip.
What I'll miss the most on my old tablet setup is Waze. That thing has traffic info very well done.
Very sad news as I've read. It seems Centrafuse dropped linux support before it left beta. So I'm left with Windows for now. I've sent an email to them in the last hope that there might be a stable built forgotten in a drawer somewhere at Centrafuse HQ...
As I've looked over other choices, it seems that nothing comes close to the polish and maturity Centrafuse has. As I'll be getting closer to finishing this project I'll most likely buy the Centrafuse. I hope the trial version is enough for all the tests I need to do first.
A key point in this project will be controlling some functions of Centrafuse (like volume and next/prev, scrolling through a list, etc) with the MFD2 buttons and knobs. I'll tackle this when I have the adapter and touch screen. Have to finish all the hardware first.
The fact that I know C programming (even though I haven't programmed for windows in a while) will help making a man-in-the-middle app if it comes to it. I'm sure Centrafuse has some mechanism of communicating (as in taking commands) with 3rd party apps.