I am using patched Tech2Win, as provided on CDROM purchased with device and VXDIAG VCX Nano GM off ebay and have not been able to communicate with any modules in a 2001 Holden Vectra JS, same as Opel/Vauxhall Vectra B, with a C22SEL engine. The ECU is identified as a Simtec 56.5.
I know that the ECU and Central Door Lock Modules and Immobiliser in the vehicle are not faulty because I can successfully communicate with them using Op Com v1.45 China Clone. I can read DTCs from the ECU module and I can perform Central Door Lock function tests and read the PIDs for the Central Door Lock Module and I have successfully programmed key to immobiliser.
I also have done a successful scan of ECU and Central Door Lock and immobiliser Modules using Autel MaxiDAS DS708.
I have installed the patched Tech2Win as provided on the installation disc with the VCX Nano GM device and it shows 42 days unlocked. It is installed on a Dell Inspiron 8600 Laptop, Intel Pentium M processor 2.00GHz, 2Gig of RAM, runninng Windows XP version 2002 Service Pack 3.
I am using Holden v157 and Opel v180 bins gratefully obtained from this forum with Tech2Win to communicate with the vehicle. The Tech2Win software appears to be communicating with the VCX Nano device, indicated by the green bidirectional arrows in the lower left corner of the Tech2Win app window.
When scanning the ECU Tech2Win indicates Identification Running … with green arrows in lower left of app window, then it would change to Loss of Communications with Vehicle… Then it will change to Unkown ECU. Then it would show the Abort and ID Data select keys at lower part of App Window. If I select the ID Data button, Tech2Win App will display the 5 ID Paramaters, usually with an asterix for all ids, only one time I was able to see the correct ID parameters, even though it said Unknown ECU. If I select MDI Bosch API at the interface select window instead of MDI2 Bosch API, No Communication Message is displayed on the Tech2Win app window.
I also tried to scan the Body Module – Central Door Lock, it would show waiting for data and never establish comms with module. With green bidirectional arrows displayed on the Tech2Win app in lower left corner.
I was using firmware version 184.108.40.206 and I updated the firmware to the latest version 220.127.116.11 from the VX Manager update window, did not help. I noticed in the firmware updates descriptions in some previous firmware updates are related to Opel KW82 protocol. Opel uses KW82 protocol on pin 3 for Body System Modules such as Central Door Locking and Immobiliser and uses KW2000 protocol on pin 7 for the ECU. I know this because Op Com Device shows this when it successfully connects to those modules.
I have not tried scanning any vehicles using GDS2 also provided on the CDROM with VCX Nano GM as I have not had access to any vehicles later than 2006.
Update: I saw this: http://blog.obd2diy.fr/2017/08/09/vxdiag-vcx-nano-gm-good-or-not/
decided to have another new one from obd2diy.fr
Update: Test on a 2009 GMC Savannah full size van:
So I just tested the VXDIAG VCX NANO GM interface and Tech2win on a 2009 GMC Savannah full size van. I was able to connect, read engine data, read other modules data ( BCM ETC) with no issues. Not sure if this vehicle uses the same low speed CAN in any way. But at least I know the interface and tech2win are working together.
I have screenshots if anybody is interested.
Test on 2008 Vauxhall Vivaro 2.0:
Have Vcx Nano GM with Tech2Win for speed limiter removal on a 2008 Vauxhall Vivaro 2.0 (90bhp m9r 782): success!
Test on a Buick 2008 GL8 Firstland:
Buick 2008 GL8 Firstland engine: (C) 3.0L V6 LZC
Worked perfect. Both OK in ECM & TCM programming! Online!
So far, satisfied with the second one from obd2diy.fr.