Vida 2014D Times out 12/31/2017 23:59 Topic is solved

Post by **xHeart** » 04 Feb 2019, 12:40

DiCE connection over USB Port is now erratic "USB Driver Unsuccessful".

An attempt to restore and run x/DiCE/setup returns:

: MVS_DiCE_2947.jpg (156.32 KiB) Viewed 2195 times

Reading this:
https://technet.microsoft.com/en-us/ff544842(v=vs.96)

Post by **RickHaleParker** » 04 Feb 2019, 17:00

Some people have gotten around that error with other install programs by running the installer in compatibility mode.

Post by **xHeart** » 07 Feb 2019, 15:00

RickHaleParker wrote: 04 Feb 2019, 17:00 Some people have gotten around that error with other install programs by running the installer in compatibility mode.

When DiCE worked, the act of plugging and unplugging DiCE would toggle DiCE Driver (COM4) at Device Manager. Yesterday's effort, it show USB to UART Bridge Controller error -- it is responsive yet fuzzy.

Docking space shuttle to ISS may be easier, Lol!

Post by **xHeart** » 09 Feb 2019, 11:35

Following two comments added a boost to find a fix. cn90 says winners don't quit and quitters don't win. So there I go again.

DiCE Diagnostic and VIDA 2014D are working independent of each other.

: MVS_DeviceManager_Ports_COM4.jpg (101.68 KiB) Viewed 2152 times

: MVS_DiCEusbDriverFile.jpg (43.52 KiB) Viewed 2152 times

: MVS_DiCEDiag_PassThru.jpg (83.09 KiB) Viewed 2152 times

For VIDA to read vehicle, it needs to pass communication test with DICE, log says, PassThruSupport function failed.

: MVS_DiCE_CommTest.jpg (30.1 KiB) Viewed 2152 times

Looking through the Registry, following feels out of order.

HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04 - w/o SETEK AB driver for DiCE 209510

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PassThruSupport.04.04 - with SETEK AB driver for DiCE 209510

Post by **xHeart** » 09 Feb 2019, 17:55

Error recorded in C:\VIDA\System\Diagnostic\Log\TSDice32_xxx_xx file. Would you check yours and share for isolating breaking point. Ty!

Running: HP Centrino Wintel7 x62 IE11 VIDA2014D (for life).

********************************************************************************
Executable application: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Log generated by: C:\Program Files (x86)\DiCE\Tools\TSDiCE32.dll
DLL version: 6, 1, 0, 0
Operating system version: 6.1 buildno: 7601 Service Pack 1
Date: 2019-02-09
LogValue: 4
********************************************************************************

18:03:52,003 0103 000000 PassThruOpen() enter
18:03:52,081 0100 000000 PassThruOpen() In parameter pName = DiCE-209501
18:03:52,097 0300 000000 UsbHardware::Open() failed, could not open read end point.
18:03:52,097 0300 000000 UsbHardware::Open() GetLastError() returned: 3 The system cannot find the path specified.
18:03:52,097 0200 000000 HardwareHelper::CreateHardwareConnection() Could not connect to USB device.
18:03:52,128 0300 000000 HardwareHelper::IsValidBluetoothAdapter() No valid Bluetooth adapter found.
18:03:52,128 0300 000000 HardwareHelper::CreateBluetoothConnection() Bluetooth device not supported. Make sure that the Volvo/Ezurio/Laird USB Bluetooth adapter is connected.
18:03:52,128 0300 000000 HardwareHelper::CreateHardwareConnection() Failed to find any Bluetooth device.
18:03:52,128 0300 000000 PassThruOpen() Could not create hardware connection
18:03:52,128 0104 000000 PassThruOpen() exit result: ERR_DEVICE_NOT_CONNECTED
18:03:52,128 0103 000000 PassThruGetLastError() enter
18:03:52,128 0100 000000 PassThruGetLastError() Out parameter pErrorDescription = Unable to communication with device.
18:03:52,128 0104 000000 PassThruGetLastError() exit
********************************************************************************

Post by **RickHaleParker** » 09 Feb 2019, 22:02

XHeart: Do you have one of them DiCE "Mini" that was floating around a few years back?

JoseBQ · Post by **JoseBQ** » 10 Feb 2019, 05:41

Hello!

I followed the instructions (or so I thought), and got the following message in DICE Diagnosis when running interface test:
"Self diagnostic connector is not attached".

Does anyone know what's the matter?

Post by **xHeart** » 10 Feb 2019, 09:19

JoseBQ wrote: 10 Feb 2019, 05:41 Hello!

I followed the instructions (or so I thought), and got the following message in DICE Diagnosis when running interface test:
"Self diagnostic connector is not attached".

Does anyone know what's the matter?

Unless otherwise said this appears to be x64 Diagnostic, please confirm?
I believe, Self diagnostic is small device that comes with Volvo DiCE original, not clone. If your VIDA<->DiCE communication passes "OK" than you are good to go JoseBQ.

Post by **xHeart** » 10 Feb 2019, 09:55

RickHaleParker wrote: 09 Feb 2019, 22:02 XHeart: Do you have one of them DiCE "Mini" that was floating around a few years back?

No. But happy to try.

Rick, the clone was a 2014A purchase -- DVD with VIDA file dated Feb 2012 and patch dated Jan 2014 (aka 2014A). DiCE unit lights with blue/green LEDs and are labeled like this:

.

Now that I've read through EACH post in this thread and over at other forums for clarity. I feel, my DiCE related posts may have spilled over into the working of Windows, sorry!

JoseBQ · Post by **JoseBQ** » 10 Feb 2019, 11:30

xHeart wrote: 10 Feb 2019, 09:19
JoseBQ wrote: 10 Feb 2019, 05:41 Hello!

I followed the instructions (or so I thought), and got the following message in DICE Diagnosis when running interface test:
"Self diagnostic connector is not attached".

Does anyone know what's the matter?
Unless otherwise said this appears to be x64 Diagnostic, please confirm?
I believe, Self diagnostic is small device that comes with Volvo DiCE original, not clone. If your VIDA<->DiCE communication passes "OK" than you are good to go JoseBQ.

Do you mean that dice works perfectly even if it doesn't pass the interface test?

If that's the case, VIDA doesn't show any communication tool... It shows an "X" where there was supposed to be the dice unit to select.

I changed the register in Windows as supposed but it continues not working... I'm getting desperate...