Diagnostic VDI, VNCI, MDI with MG4

[Deepbluexl]

@marekraska But thats Not an MG4... So not related to the topic..

 

[haloweenhamster]

After unpacking, I obtained:

• 11248183_02.sw (date 2021.09.27)
• AS23PEU_ClientTdbGdb.sw (date 2025.02.28)

I uploaded both to a USB flash drive and nothing happened.

I downloaded three “AS23PEU_ClientTdbGdb.sw” files and chose the most recent one.

Does the flash drive need to be specially prepared? Formatted FAT32.
View attachment 39726View attachment 39725

Unfortunately I have no experience with that model (only MG4)
With the MG4 some updates like TBOX you had to place the files in a folder with the correct name for the car to see it
It's even different for the SE & Trophy for the FICM
The software loading instructions might help if you have the document

 

[marekraska]

The manual does not contain such information.
I'll keep looking. Thank you for your help.

 

[rt45433]

I have now got my VDI3 hardware and went to get everything setup. I first installed everything on my surface pro and when opening VNCI Device Manager is would show the device and its correct serial number but it would just show the firmware as 0.0.0.0 which was odd. I then decided to install all the software and drivers onto my gaming pc and when opening VNCI Device Manager it showed the hardware with the correct SN and the firmware version now as 1.0.0.9 so i then put everything in the car and when I connect the VDI3 to the cars OBD port it will then not show up in either VNCI Device manager or VCI Manager. When i remove the VDI3 from the cars OBD port it then shows up both on VCI Manager and VNCI Device Manager. Am I doing something wrong? Any help would be super helpful. This is the hardware I bought.

VNCI VDI3 für Rongwei MG Wuling Baojun Datong Diagnoseschnittstelle unterstützt DoIP- und CANFD-Protokoll, passend für SAIC-Gruppensoftware - AliExpress 34

 

[hojnikb]

I have now got my VDI3 hardware and went to get everything setup. I first installed everything on my surface pro and when opening VNCI Device Manager is would show the device and its correct serial number but it would just show the firmware as 0.0.0.0 which was odd. I then decided to install all the software and drivers onto my gaming pc and when opening VNCI Device Manager it showed the hardware with the correct SN and the firmware version now as 1.0.0.9 so i then put everything in the car and when I connect the VDI3 to the cars OBD port it will then not show up in either VNCI Device manager or VCI Manager. When i remove the VDI3 from the cars OBD port it then shows up both on VCI Manager and VNCI Device Manager. Am I doing something wrong? Any help would be super helpful. This is the hardware I bought.

VNCI VDI3 für Rongwei MG Wuling Baojun Datong Diagnoseschnittstelle unterstützt DoIP- und CANFD-Protokoll, passend für SAIC-Gruppensoftware - AliExpress 34

did you try to run it in VDS or SIPS ?

 

[rt45433]

did you try to run it in VDS or SIPS ?

I tried both. Since the first try i have tried again and had some success.

1. When i have it just attached to the pc it shows as in usb connection but then when connected to the car aswell it disappears from VNCI device manager. (i read online that you can press the little black button for 3 seconds on the VDI3 device) but this just seems to restart the device and its then the same.

2. If i connect to just the car and then open my wifi on the pc I can see the VDI3 device and connect to it. This is the only way i can connect to it currently but i want to be able to just connect via USB. With this then connect to WIFI via my pc. I then added a usb wifi dongle to connect to my internet. This then let me use SIPS and connect to the car but every time I open VDS and login it then says network connection issue.

So to sum it up I can connect to car but only by wifi and I can not open VDS as its saying there is a network connection issue. Can anyone off some help with this?

 

[Geekice]

I tried both. Since the first try i have tried again and had some success.

1. When i have it just attached to the pc it shows as in usb connection but then when connected to the car aswell it disappears from VNCI device manager. (i read online that you can press the little black button for 3 seconds on the VDI3 device) but this just seems to restart the device and its then the same.

2. If i connect to just the car and then open my wifi on the pc I can see the VDI3 device and connect to it. This is the only way i can connect to it currently but i want to be able to just connect via USB. With this then connect to WIFI via my pc. I then added a usb wifi dongle to connect to my internet. This then let me use SIPS and connect to the car but every time I open VDS and login it then says network connection issue.

So to sum it up I can connect to car but only by wifi and I can not open VDS as its saying there is a network connection issue. Can anyone off some help with this?

I had a very similar issue. Try disabling Windows Firewall and any antivirus software. The VNCI communicates with the computer by creating a virtual network adapter, and sometimes Windows Firewall blocks it.

 

[rt45433]

I had a very similar issue. Try disabling Windows Firewall and any antivirus software. The VNCI communicates with the computer by creating a virtual network adapter, and sometimes Windows Firewall blocks it.

Thanks for the reply. I will give this a try. Can i ask which issue this will fix? Will it help with getting VDS to work or help getting the VDI3 connected via usb cable only?

 

[Geekice]

Thanks for the reply. I will give this a try. Can i ask which issue this will fix? Will it help with getting VDS to work or help getting the VDI3 connected via usb cable only?

Both, If VDS gives you a “network connection error”, it’s usually the firewall. Try turning off Windows Firewall and any antivirus, and also check if you have other network adapters enabled (like a VPN) and disable them. For the VNCI, the issue is also the firewall blocking it, since it talks to the PC as a network connection.

In my case, it was the network adapter created by NordVPN. Even if NordVPN was turned off via the app, VDS was still using that adapter. Once I disabled it from Windows settings and turned off the firewall, everything started working again.