VXDIAG Tech2win Opel 2009 No Cummunication Solution

Problem:

I have bought a vxdiag Vcx nano for Gm, i cannot set the communication to car with them. It says no communication with all modules. Car is a Opel Corsa D 1.3 diesel 2009. I'm running in windows 7 64bit Os if it's matters. All drivers and firmware are up to date.

Answer:

vcx nano gm tech2win won't do Open or Saab. Missing proper bin files.

GDS2 will do newer Opel.

Free download Tech2win Bin File for GM Saab Holden Isuzu Opel

Free download other Tech2win Opel bin files here and find a proper version to test on your car.

*You are at your risk.

VXDIAG Ford VCM2 No License Solution

Problem:

I got the Ford VCM2 clone (using vxdiag vcx manager). I got the software installed but when run VX Manager, it detects the device, but no license.

When try to update the license, it says license is invalid, contact the dealer to confirm this is a valid device.

Solution:

00001 is the serial number of clone VCM2 using vxdiag solution.

You need to contact your seller to send back the unit to modify the device serial number to renew license.

How to Solve VXDIAG Benz Driver File Check Failed Error?

Problem:

I noticed there was a new Benz C6 driver for the vxdiag vcx se benz scanner. I got the xentry 06/2022. I installed the C6 driver today but it failed me.

Error: File check failed.

Solution:

The new version Benz C6 driver is updated to support the 09/2022 version Xentry.

If you xentry 06/2022 and previous versions, run XDVCI UPDATE program on the desktop

If still get the same error, close vx manager, and try again.

VXDIAG Subaru SSM4 Time for Updating Software Expired Solution

Problem:

I got the vxdiag vcx se Subaru SSM3/SSM4 scanner today but failed to install the SSM4 software on Windows 11.

Error" You cannot intall the software. Time limit for updating the software has expired.

Perform the license authentication.

Any solution?

Solution:

Change your computer date/time.

For example: The SSM4.exe last date modified is 1/1/2022, you can change the time to any day in July 2022.

Computer date should not exceed six (6) months from the date (i.e date can not be set newer than 1/7/2022).

Don't need to restart computer. Direct install SSM4 after change time.

VXDIAG and Forscan 2.4.6 Update Ford Escape 2012 PCM

Just a quick note to advise that I was able to update the PCM calibration on MY2012 Ford Escape under Forscan 2.4.6 Beta using a recently purchased VXDIAG VCX Nano Ford configured as a J2534 pass thru device. While the ECU calibration update process was relatively smooth within Forscan, the more challenging process was to configure the VCX Nano to act as a J2534 pass-thru device.

The key, as noted elsewhere on the net, is to ONLY use the VXManager package to configure the VCX Nano as a J2534 pass-through device; and not use the AllScanner version of IDS at all. VX Manager can also be used to update the firmware on the VCX Nano in case a newer version is available. Once I had configured the VCX Nano as a J2534 pass-thru device within VXManager, it was straight-forward within Forscan to select the VCX Nano as the adapter/device to be used while updating the PCM calibration. Of note is that I connected my 2amp battery maintainer to the MY12 Ford Escape to ensure consistent voltage throughout my use of Forscan 2.4.6 Beta to perform the PCM update.

You can also use the vcx nano without having to run VX Manager (i.e. Use VCX Nano straight out of the box with Forscan). Can even leave adaptor choice on auto and it finds it.

I further updated the PCM from BRG to BRJ today using Ford FJDS with VCX Nano connected to MY12 Escape. I am assuming that the absence of similar option within Forscan to update the PCM from BRG to BRJ is simply the result of the development cycle for Forscan Beta. Below is configuration of the PCM on my MY12 Escape as things stand today:

PCM – Powertrain Control Module

Part number: AL8A-12A650-BRE

Calibration level: AL8A-12A650-BRE

Strategy : AL8A-14C204-BRJ

Hardware type: BL8A-12B684-BB