Diagnostic VDI, VNCI, MDI with MG4

Deepbluexl · Sep 10, 2025

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

haloweenhamster · Sep 10, 2025

marekraska said:
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 39726 View 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 · Sep 11, 2025

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

rt45433 · Sep 13, 2025

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 · Sep 13, 2025

rt45433 said:
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 · Monday at 10:33 AM

hojnikb said:
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 · Monday at 10:44 AM

rt45433 said:
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 · Monday at 10:52 AM

Geekice said:
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 · Monday at 12:06 PM

rt45433 said:
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.

EVfanatic · Tuesday at 12:31 PM

rt45433 said:
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?

Open windows firewall and set up an output rule, select output rule, then go to program files/Saic and select the exe file for SIPS. Then reboot the laptop and the software will connect ok.

Onehebergeur · Wednesday at 10:15 AM

rt45433 said:
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

Hello, IP address of the adapter to put in DHCP...

EVfanatic · Wednesday at 8:57 PM

dphanix said:
Hey anyone know if you can program rear light bar to stay on during the day with the front DRL? MG4

haloweenhamster said:
Alternative way, using USB & SIPS

Are the T Box files for all car types? I have a 2023 SE, fully updated everything except I have a tick against T box, so trying to update that but unsure which version I need? My unit currently says SNAKP18E32. It's not allowing me to update via SIPS, keeps saying update with u disk.

Mouss · Wednesday at 10:11 PM

Yes because you need to update TBOX MPU first.
Use 23E32 file to get the last software

EVfanatic · Wednesday at 10:15 PM

Mouss said:
Yes because you need to update TBOX MPU first.
Use 23E32 file to get the last software

Thanks, I couldn't find anywhere that lists the compatible versions. So what's the 43 version for?

Mouss · Wednesday at 11:55 PM

I just told you 23E32 for SNAKP23E32.
If you try to install the wrong TBOX software, you can brick your unit...

EVfanatic · Wednesday at 11:58 PM

Mouss said:
I jus told you 23E32 for SNAKP23E32.
If you try to install the wrong TBOX software, you can brick your unit...

Yeah I get that, I'm just curious what the other versions are for. If there was a list somewhere so others searching the threads know which are which.

Deepbluexl · Thursday at 4:21 AM

These are the TBOX Sw Versions.. the 23 is the newest.. 04 seems to be the oldest Version.. important is the SNAKP Naming for the Hardware Version or Platform. the newer MGs or for different regions have a different name.

haloweenhamster · Thursday at 6:15 AM

If you have a sips login the best way is to go to large file downloader, enter vin,, it'll download files only for your car, open the .51 files with a zip program

Or go to the zz sso mg motor website use Sips login and you can see the current version of any module on the car in mg style eg 11734123.51

EVentropy · Thursday at 8:36 AM

I went for my first service (2yr, 40K km) Learnt very little, except for a software status "report".

They said they upgrade foc, and as I don't have time at the moment I think I will hold off getting a SIPs a/c and get them to do it. But it would be good to know what they are updating.
Attached below is report (i guess thru sips) but I can't understand what the crosses, ticks and ? mean. And "configuration file vs calibration file".
Can someone some in the know throw light on the context?
Sorry for crap definition.
Thanks!

haloweenhamster · Thursday at 8:44 AM

up to date

Not latest version
? Not something that can be read so unknown status

Diagnostic VDI, VNCI, MDI with MG4

Established Member

Established Member

Novice Member

Novice Member

Attachments

Established Member

Novice Member

Established Member

Novice Member

Established Member

Standard Member

Established Member

Standard Member

Attachments

Established Member

Standard Member

Established Member

Standard Member

Established Member

Established Member

Established Member

Established Member

Similar threads

Yes

I'm in the middle

No

Latest MG EVs video