ALLScanner vcx-plus

  • Thread starter Thread starter ziemelis
  • Start date Start date
  • Tagged users Tagged users None

ziemelis

Bolt-On Member
Thread Owner
Joined
03.02.2026
Messages
29
Reaction score
11
Location
Latvia
ALLScanner sn:V94XD5310 Diagnostics with Toyota techstream, but it was time to update online - it happened that it no longer works. The question is, can anything be done there?
 
ALLScanner sn:V94XD5310 Diagnostics with Toyota techstream, but it was time to update online - it ha...

It sounds like the liсеnsе might have been wiped during the update or the firmware version is now mismatched with your driver.

Please connect the VCX-PLUS to your computer and open VX Manager.

  • Check the Device tab: Is the device detected? What is the Firmware version?
  • Check the liсеnsе tab: Do you see PASSTHRU and TOYOTA listed with valid dates?

If the licenses are missing, the device won't communicate with Techstream. You may need to reload the liсеnsе file or contact the seller if it was a subscription-based unit.

Also, verify that the Toyota driver is still installed:
Code:
Open VX Manager -> Diagnostic Tab -> Toyota -> Click "Install/Update"

If the device is detected but shows a firmware error, try to force a firmware update again via the manager. If it is not detected at all, check your USB cable and drivers in Device Manager.
 
[07:51:16.571] LOG DATE = 2026-02-10
[07:51:16.571] LOG PATH = C:\ProgramData\VCX\Logs\VCX\VCX.log
[07:51:16.571] LOG LEVEL = 0xff
[07:51:16.571] LOG FLAG = 0x00
[07:51:16.571] APP Name: C:\Program Files (x86)\VCX\Manager\Tools\LogManager\LogManager.exe
[07:51:16.571] DLL Name: C:\Windows\VCX.dll
[07:51:16.581] VCX_Open:
[07:51:16.581] VCX_OpenEx:
[07:51:16.581] VCX_API_VERSION = 1.8.9.0
[07:51:16.581] VCXCommOpen: ulCommType = 255, pParam = 6d5427c0, bUnlock = 0
[07:51:16.581] VCXCommAutoDiscover
[07:51:16.581] VCXNetDiscoverDevice...
[07:51:16.681] VCXNetDiscoverDevice...
[07:51:17.381] TestDiscoverDevice: PingDiscoverDevcie error!
[07:51:17.985] SocketDiscover: device not found
[07:51:17.985] VCXNetDiscoverDevice...
[07:51:18.085] DoNetDiscover: device not found
[07:51:18.085] SerialUsbDiscover...
[07:51:18.085] FT_ListDevices: FT_LIST_ALL, DevCount = 0.
[07:51:18.085] SerialPortList: pPrefixName = VCP.
[07:51:18.095] SerialPortList VCP: PortSize = 0
[07:51:18.095] SerialPortList: pPrefixName = sеriаl.
[07:51:18.095] SerialPortList CH: PortSize = 0
[07:51:18.095] VCXCommOpen error!
[07:51:18.095] Error: VCXCommOpen!

Maybe the log files can help determine the cause.
 
LOG DATE = 2026-02-10
LOG PATH = C:\ProgramData\VCX\Logs\VCX\VCX.log
LOG LEVEL = 0xff
LOG FL...

The log clearly shows that the software cannot detect the hardware physically connected to the computer. The critical line is here:

Code:
FT_ListDevices: FT_LIST_ALL, DevCount = 0.

This means the driver sees 0 devices connected. This is a hardware detection issue, not a liсеnsе issue (yet).

Please check the following:

  • Open Windows Device Manager (devmgmt.msc).
  • Look under Universal sеriаl Bus controllers or Ports (COM & LPT).
  • Do you see an entry like "USB sеriаl Converter", "VXDIAG", or "ALLScanner"?
  • If you see an "Unknown Device" or a device with a yellow exclamation mark, try to manually update the driver pointing to the VX Manager installation folder (usually C:\Program Files (x86)\VCX\Driver).

If the device does not appear in Device Manager at all and no LEDs light up when plugged in, the firmware update likely failed and the unit may be "bricked" (stuck in bootloader mode or dead). Try a different USB cable and port just to be sure.
 
Back