Does someone have the connection diagrams for an Audi MIB2 main unit (quadlock) and control panel (2x10pin connector)?
I would like to make cables to do benchtesting on a spare A6 4G MIB2 unit..
Audi MIB2 Wiring diagrams
Hi Scrat,
no the MMI Displays are not compatible to the MIB series. I use for both (MIB1 & MIB2) the Audi A3 Display Unit PN: 8V0 857 273 J for the whole Mudule with cabinet motor frame.
The PN for the Display itself is 8V0 919 604 A.
The reason is, that the MIB units using local CAN commands between main unit and display module.
no the MMI Displays are not compatible to the MIB series. I use for both (MIB1 & MIB2) the Audi A3 Display Unit PN: 8V0 857 273 J for the whole Mudule with cabinet motor frame.
The PN for the Display itself is 8V0 919 604 A.
The reason is, that the MIB units using local CAN commands between main unit and display module.
I've connected a serial terminal, but i'm not sure what is wrong with my unit...
It looks like it is shutting down right after completing startup ?
complete log:
https://mega.nz/#!hQEn2a5L!CGeJPRtA76kx ... s0D7OGMzqw
It looks like it is shutting down right after completing startup ?
complete log:
https://mega.nz/#!hQEn2a5L!CGeJPRtA76kx ... s0D7OGMzqw
Код: Выделить всё
#2 HB: System is still alive.
00:00:18 HB: T=031C, CPU=66%, Free mem=1439MB
ESOComm::Accept: Socket accepted. Navi is alive errno 2
StartTransitiveModi : Started COMM: 300
StartTransitiveModi :About to start NAVI
Using resource path: /navigation/resources/app/au/eu/ (config version: 10.0.2283)[OOC.DelayManager] INFO: delaymanagerUpdateDelayBit: 5, 0
[OOC.DelayManager] INFO: eval_delay_request: phone: is 0, requests 0 uota: is 0, requests 0 online: is 0, requests 0 rtc: is 0, requests 0 phone_pdd: is 0, requests 0 nav_pdd: is 0, requests 0
00:00:19.008 traceserver Frontend Clients info 3003 [systemservices] connected
JOBMANAGER now at prio 10
JOBMANAGER RenderSystem OpenGL thread now at prio 10
ESOComm::StartupNaviSDK OK
[OOC.AsiTempMon] INFO: Try to connect proxy
[OOC.AsiTempMon] INFO: set DTC 0x604 to value 0
[OOC.AsiTempMon] INFO: sent diag temperature information: current 0x51, min 0x32, max 0x75
#3 HB: System is still alive.
00:00:23 HB: T=031C, CPU=56%, Free mem=1361MB
ESOComm::StartupNaviPresCon Finished successfully
StartTransitiveModi : Started NAV: 700
StartTransitiveModi : Started TTI: f00
Report f0c back to ESO
PMON now at prio 11
ESOComm::runApplication
created display with id:4 & render_target:0 returns 2ba9e8
#4 HB: System is still alive.
00:00:28 HB: T=032C, CPU=81%, Free mem=1222MB
00:00:28 HB: proc/boot/procnto-smp-instr (1) 9.37%: n/a, n/a, n/a, n/a
00:00:28 HB: sbin/devb-mmcsd-tegra3-devlite (20486) 13.42%: n/a, n/a, n/a, n/a
[OOC.IOC] INFO: MMI state: MMI_STATE_STANDBY_PWR_SAVE_2 -> MMI_STATE_IOC
[OOC.IOC] INFO: IOC shutdown request: SHUTDOWN_REQUEST_NONE -> SHUTDOWN_REQUEST_SHUTDOWN
[OOC.AsiServiceManager] INFO: Normal shutdown
S[OOC.AsiServiceManager] INFO: Shutdown processing
[OOC.IOC] INFO: Shutdown processing: true
YSSERVICES: power state POWERSTATE_OFF
SYSSERVICES: killing mnand tlog
SYSSERVICES: shutdown request ONOFF_SHUTDOWN_mNAND Usage Temperature Log Tool .. terminated
NORMAL
No need for gateway.
Check the can communication between the main unit and kbd/display.
If the can wires are reversed it will not work
My unit did the same shutdown when i didn't had kbd and display connected.
Worth checking the communication, plus the pin numbering in ELSA for the the back 12 pin connectors are wrong.
In elsa they are
1 2 3 4 5 6
12 11 10 9 8 7
But in reality they are
1 2 3 4 5 6
7 8 9 10 11 12
Display and KBD can are 1,7 (they are the inner most pins)
unit can is 6,12 (the outer most pins)
Regards.
Check the can communication between the main unit and kbd/display.
If the can wires are reversed it will not work
My unit did the same shutdown when i didn't had kbd and display connected.
Worth checking the communication, plus the pin numbering in ELSA for the the back 12 pin connectors are wrong.
In elsa they are
1 2 3 4 5 6
12 11 10 9 8 7
But in reality they are
1 2 3 4 5 6
7 8 9 10 11 12
Display and KBD can are 1,7 (they are the inner most pins)
unit can is 6,12 (the outer most pins)
Regards.
@congo: You were right.
I've reversed the wire order and now the lights come on and the display flips open!
The screen itself however still doesn't turn on.. I've tried switching display can high/low, but that doesn't help.
I then suspected that the hsd fakra cable was wired differently from the other hsd cables, and
I've made a new one based on the wiring diagrams, but that doesn't work either.
Time for the analyzer.
I've reversed the wire order and now the lights come on and the display flips open!
The screen itself however still doesn't turn on.. I've tried switching display can high/low, but that doesn't help.
I then suspected that the hsd fakra cable was wired differently from the other hsd cables, and
I've made a new one based on the wiring diagrams, but that doesn't work either.
Time for the analyzer.
Found the problem.
CAN analysis during startup showed that the display was not replying.
I've removed the display cover to take a look and discovered that the seller sold me the wrong display (4G1919605, 3GP display) instead of the advertised mib model (4G5919607).
Edit: For those who might find it useful, there IS a sticker with the model number, but it's on the inside.
CAN analysis during startup showed that the display was not replying.
I've removed the display cover to take a look and discovered that the seller sold me the wrong display (4G1919605, 3GP display) instead of the advertised mib model (4G5919607).
Edit: For those who might find it useful, there IS a sticker with the model number, but it's on the inside.
- Вложения
-
-
autoelettronica
- Новичок
- Сообщения: 3
- Зарегистрирован: Ср окт 11, 2017 10:39 am
- Откуда: IT