Reputation:
893
Thanks Given: 580
Thanks Received: 1617 (203 Posts)
Posts:
1,107
Threads:
253
Joined: Nov 2011
1
12-21-2016, 05:17 PM
Without any error codes at all at the top...
Initialization of diagnosis multiplexer failed
Possible causes:
The link between the diagnosis multiplexer an the
diagnostic socket is interrupted
The link between the diagnosis multiplrxer an the
diagnostic unit is interrupted.
The voltage supply at the diagnostic socket (circuit30
and(or) circuit31)is fault.
Note:
When using SDconnect, check the connection status
using the Toolkit.
"
Thanks given by:
Reputation:
309
Thanks Given: 60
Thanks Received: 546 (86 Posts)
Posts:
247
Threads:
40
Joined: Sep 2015
Yes this always happens. its probably that short cable that connects your multiplexer to your PC Com port cable.
Dont forget to Thanks + Rep If I helped you
Thanks given by:
Reputation:
1,545
Thanks Given: 834
Thanks Received: 3312 (599 Posts)
Posts:
1,500
Threads:
108
Joined: Feb 2016
4
12-21-2016, 06:21 PM
(This post was last modified: 12-21-2016, 06:21 PM by EASatlanta.)
(12-21-2016, 05:31 PM)crazy40 Wrote: Reset C4 mux. Take out battery if necessary. Reboot PC. Open SD Selection make sure it is accessible. Open toolkit admin, self test and look at the stat.
(12-21-2016, 05:17 PM)j4g3d Wrote: Without any error codes at all at the top...
Initialization of diagnosis multiplexer failed
Possible causes:
The link between the diagnosis multiplexer an the
diagnostic socket is interrupted
The link between the diagnosis multiplrxer an the
diagnostic unit is interrupted.
The voltage supply at the diagnostic socket (circuit30
and(or) circuit31)is fault.
Note:
When using SDconnect, check the connection status
using the Toolkit.
"
That is a common message... post the error ID from the top-left corner of the error message window. Attached picture for reference.
Is there a ( ! ) symbol on your multiplexer screen?
Just a squirrel trying to get a nut.
Thanks given by:
Reputation:
893
Thanks Given: 580
Thanks Received: 1617 (203 Posts)
Posts:
1,107
Threads:
253
Joined: Nov 2011
Guys, i know this common message. I have seen it many times before.
But my point is, there is no error number on the top left of this message. Like the pic EASatlanta posts. There is NO error numbers. Instead of the error numbers it just says 'WARNING'. I have never seen this before.
This is C4 mux using WIFI.
It is not bin folder problem or anything like the common simple fixes.
Reputation:
1,545
Thanks Given: 834
Thanks Received: 3312 (599 Posts)
Posts:
1,500
Threads:
108
Joined: Feb 2016
(12-21-2016, 07:07 PM)j4g3d Wrote: Guys, i know this common message. I have seen it many times before.
But my point is, there is no error number on the top left of this message. Like the pic EASatlanta posts. There is NO error numbers. Instead of the error numbers it just says 'WARNING'. I have never seen this before.
This is C4 mux using WIFI.
It is not bin folder problem or anything like the common simple fixes.
Tried on another xentry install?
Tried LAN cable only?
Tried different OBD cable? I recently had an OBD cable go bad for the first time... Yudi figured that out for me. but not that error, it had a code at the top.
I learned the hard way on this stuff, so I have decent troubleshooting knowledge for the hardware and lots of spare parts. If you need help or need me to send a cable or something PM me.
Just a squirrel trying to get a nut.
Thanks given by:
Reputation:
1,545
Thanks Given: 834
Thanks Received: 3312 (599 Posts)
Posts:
1,500
Threads:
108
Joined: Feb 2016
(12-21-2016, 07:28 PM)j4g3d Wrote: (12-21-2016, 07:15 PM)EASatlanta Wrote: (12-21-2016, 07:07 PM)j4g3d Wrote: Guys, i know this common message. I have seen it many times before.
But my point is, there is no error number on the top left of this message. Like the pic EASatlanta posts. There is NO error numbers. Instead of the error numbers it just says 'WARNING'. I have never seen this before.
This is C4 mux using WIFI.
It is not bin folder problem or anything like the common simple fixes.
Tried on another xentry install?
Tried LAN cable only?
Tried different OBD cable? I recently had an OBD cable go bad for the first time... Yudi figured that out for me. but not that error, it had a code at the top.
I learned the hard way on this stuff, so I have decent troubleshooting knowledge for the hardware and lots of spare parts. If you need help or need me to send a cable or something PM me.
I know these systems since 2011. So like to think i have the knowledge, but in this case i can't pin point the problem.
The error appears randomly. Not all the time. It doesn't matter if its DAS or XENTRY. It can work fine on 4 cars, then it wont work and get this message.
-The OBD cable was replaced.
-The software has been refreshed completely
-Only got this error using WIFI after refreshing the software. So i will try using Lan cable to see if the same error still comes up. But i suspect it will.
Bit confused what it can be. When i refreshed the software (03.2016) again, i also installed all addons. I was advised its OK to do this. But like i say, problem still randomly comes.
I was also advised addons are okay to install. This also blocked both of my muxes. Only in DAS.
What car are you trying?
Try a xentry vehicle...
Again, what is your mux screen showing?? If you have the ( ! ) icon to the right as shown in my attachment. Mux is blocked in DAS.
Just a squirrel trying to get a nut.
Thanks given by: