Product dynamics


Current position:index>FAQ>Product dynamics
All 11 Company Dynamic 1 Product dynamics 10

Resolve PIWIS3 software cannot connect to VNCI PT3G issue

Date:2024-03-18   Page view:1301

When your PIWIS3 software cannot connect to the original PT3G/PT4G device or cannot connect to the VNCI PT3G device, your PIWIS3 software driver is tampered with or replaced. At this time, we need to restore the original PIWIS3 driver to normally connect the original PT3G/PT4Gs and VNCI PT3G devices.

The steps to restore the original PIWIS3 driver are as follows:

1. Download the original driver (the current driver version is v3.5.6)

2. Open the PIWIS3 driver location, delete all files below the location, and copy the original driver file to the location.

PIWIS3 driver location path:  D:/PiwisApps/VCI/Actia_64/XS_D_PDU_API_64/


3. Copy the following registry contents to a text file with a.reg suffix, and double-click the file to run it.

Windows Registry Editor Version 5.00
"Image Version"="3.5r06-13787-108"
"Image File"="D:/PiwisApps/VCI/Actia_64/XS_D_PDU_API_64/PT3G-VCI-3.5r06-13787-108-20220801"
"Module Version"="3.5.6"
"Module File"="D:/PiwisApps/VCI/Actia_64/XS_D_PDU_API_64/PT3G-VCI-D-PDU-API-Fw.tgz"
"Image Boot Timeout"=dword:0001d4c0
"Update Timeout Default"=dword:00003a98
"Update Timeout Image"=dword:00030d40
"Update Timeout Module"=dword:0000afc8
"Module Name"="D-PDU-API"

4. Finally, connect the VNCI PT3G or the original PT3G/PT4G device, run the ACTIA_D-PDU_API_Tester.exe program, click Start to run, all communication protocols are completely passed, indicating that the original device driver is fully restored to normal, as shown below:


Previous post:Solved SDD software does not recognize VNCI JLR DoIP device problem

Next chapter:VNCI-Bosch diagnostic interface sync operate with bosch vci device manger

Email me

Scan with whatsapp