DiCE Unit "This device cannot start (Code 10)" Topic is solved

[prwood]

I was able to get it installed by setting the VM's system clock to a pre-12/31/2017 date.

It would not let you Install with a post 2017 date or you set the date back to run Vida?

I should clarify further: I did successfully install VIDA without adjusting the date, BUT the "admin" login did not work - it just returned me to the login screen. I then started the process over, and this time I manually set the date before installing VIDA. After doing that, I was able to log in to VIDA.

[VM] When I logged in to VIDA after connecting the device, there was just an "X" in the box for communication tools.

You can get that even when the driver is OK in Device Manager. It is that conflict between Dice, Internet explorer and .net Framework. My Chrome conversion gets around all that. viewtopic.php?f=40&t=83998

Ok. It wasn't a big deal to fix it, I just had to run an additional script that was included in the VIDA Utils folder from the DVD. That script essentially performed the same action as this procedure, which is to add the "EnableIEHosting" registry key: http://blog.cardiagtool.co.uk/how-to-fi ... tion-tool/

Seeing as the device isn't okay in device manager, I think trying to update the patch per your instructions will be my next step. Should be able to try that later tonight.

[RickHaleParker]

I should clarify further: I did successfully install VIDA without adjusting the date, BUT the "admin" login did not work - it just returned me to the login screen.

My 2099 patch fixes that. Afterwards you don't need to play with the clock.

Seeing as the device isn't okay in device manager

My patch won't do anything about that. Reinstall the Dice drivers.

[prwood]

My patch won't do anything about that. Reinstall the Dice drivers.

What process would you recommend to reinstall the DiCE drivers?

[RickHaleParker]

What process would you recommend to reinstall the DiCE drivers?

• Unplug the Dice from the USB.
  Go to Device Manager.
  Right-click the Dice entry.
  • Click uninstall.
    Click the Delete the driver software for this device option.
    Click OK
  When done reboot Windows.
  On the Vida install media, go to \3PP\Products\DiCE\
  Run the Dice installer.
  Plug the Dice hardware into the USB port.
  Wait for the Dice hardware to be added to Device Manager.
  Check in Device Manger to see if the Dice driver loaded or any other problems.

[prwood]

What process would you recommend to reinstall the DiCE drivers?

• Unplug the Dice from the USB.
  Go to Device Manager.
  Right-click the Dice entry.
  • Click uninstall.
    Click the Delete the driver software for this device option.
    Click OK
  When done reboot Windows.
  On the Vida install media, go to \3PP\Products\DiCE\
  Run the Dice installer.
  Plug the Dice hardware into the USB port.
  Wait for the Dice hardware to be added to Device Manager.
  Check in Device Manger to see if the Dice driver loaded or any other problems.

Thanks. I should be able to give it a try later this evening. I wasn't aware there was a separate folder with DiCE drivers. I assumed it was installed as part of the VIDA install process.

[prwood]

Update: Followed the above procedure, still no DiCE (sorry...sorry...). When I plug the DiCE back in after reinstalling the drivers, it spends about 30 seconds on the "Installing drivers" message, and then shows the "driver installation failed" message. I did notice that right at the point where it shows "driver installation failed," the yellow "USB com status" light flashes quite a bit before shutting off, so it seems that USB communication is happening at some level. Not sure it's useful, but I added Console logging messages from Mac OS X at the bottom to show what the Host OS is registering when the USB device is plugged in/unplugged.

Device Manager

Screen Shot 2018-01-09 at 9.55.06 PM.png (29.23 KiB) Viewed 4317 times

Device Properties

Screen Shot 2018-01-09 at 9.55.15 PM.png (28.75 KiB) Viewed 4317 times

Driver Details

Screen Shot 2018-01-09 at 9.55.29 PM.png (41.01 KiB) Viewed 4317 times

List of Installed Software

Screen Shot 2018-01-09 at 9.52.49 PM.png (64.56 KiB) Viewed 4317 times

Error in VIDA when trying to Read vehicle

Screen Shot 2018-01-09 at 10.46.38 PM.png (20.51 KiB) Viewed 4317 times

When plugging in:

default 23:03:48.065163 -0500 icdd #ICDebug - 23:{ICWiredBrowser.m} (USB Device first match)
default 23:03:48.066381 -0500 icdd #ICDebug - 388:{ICWiredBrowser.m} (7 USB Descriptions Managed)
default 23:03:48.068531 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfd120000 - ICDeviceDescriptionSUQuery)
default 23:03:48.128158 -0500 icdd #ICDebug - 213:{ICResourceManager.m} (44694345-2D32-3036-3735-314030303030|DiCE Automotive Adapter|MANUFACTURER:SETEK AB;MODEL:DiCE Automotive Adapter|SW=FALSE|)
default 23:03:48.128831 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfd120000 - ICDeviceDescriptionAdded)

When unplugging:

default 23:04:21.574287 -0500 icdd #ICDebug - 51:{ICWiredBrowser.m} (USB terminate)
default 23:04:21.574388 -0500 icdd #ICDebug - 344:{ICWiredBrowser.m} (--> USB Terminate)
default 23:04:21.574642 -0500 icdd #ICDebug - 363:{ICWiredBrowser.m} (Reclaiming Resource: DiCE Automotive Adapter)
default 23:04:21.574721 -0500 icdd #ICDebug - 371:{ICWiredBrowser.m} (6 USB Descriptions Managed)
default 23:04:21.574798 -0500 icdd #ICDebug - 373:{ICWiredBrowser.m} (<-- USB Terminate)
default 23:04:21.574994 -0500 icdd #ICDebug - 504:{ICDDMessageCenter.m} (-Rem DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfd120000 - ICDeviceDescriptionUndefined)

When selecting the DiCE USB device in the Virtualbox hypervisor:

default 23:11:18.114406 -0500 icdd #ICDebug - 51:{ICWiredBrowser.m} (USB terminate)
default 23:11:18.114507 -0500 icdd #ICDebug - 344:{ICWiredBrowser.m} (--> USB Terminate)
default 23:11:18.114759 -0500 icdd #ICDebug - 363:{ICWiredBrowser.m} (Reclaiming Resource: DiCE Automotive Adapter)
default 23:11:18.114821 -0500 icdd #ICDebug - 371:{ICWiredBrowser.m} (6 USB Descriptions Managed)
default 23:11:18.114877 -0500 icdd #ICDebug - 373:{ICWiredBrowser.m} (<-- USB Terminate)
default 23:11:18.115048 -0500 icdd #ICDebug - 504:{ICDDMessageCenter.m} (-Rem DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionUndefined)
default 23:11:18.116476 -0500 icdd #ICDebug - 23:{ICWiredBrowser.m} (USB Device first match)
default 23:11:18.117110 -0500 icdd #ICDebug - 388:{ICWiredBrowser.m} (7 USB Descriptions Managed)
default 23:11:18.118149 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionSUQuery)
default 23:11:18.324092 -0500 icdd #ICDebug - 213:{ICResourceManager.m} (44694345-2D32-3036-3735-314030303030|DiCE Automotive Adapter|MANUFACTURER:SETEK AB;MODEL:DiCE Automotive Adapter|SW=FALSE|)
default 23:11:18.324767 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionAdded)
default 23:11:19.498753 -0500 icdd #ICDebug - 37:{ICWiredBrowser.m} (USB Interface first match)
default 23:11:19.499758 -0500 icdd #ICDebug - 388:{ICWiredBrowser.m} (8 USB Descriptions Managed)
default 23:11:19.505512 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0xff/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionSUQuery)
default 23:11:19.505515 -0500 icdd #ICDebug - 213:{ICResourceManager.m} (00000000-0000-0000-0000-000017AAD1CE|DiCE Automotive Adapter|(null)|SW=FALSE|)
default 23:11:19.506969 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0xff/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionUndefined)

When deselecting the DiCE in the Virtualbox hypervisor:

default 23:12:43.889859 -0500 icdd #ICDebug - 51:{ICWiredBrowser.m} (USB terminate)
default 23:12:43.889953 -0500 icdd #ICDebug - 344:{ICWiredBrowser.m} (--> USB Terminate)
default 23:12:43.890297 -0500 icdd #ICDebug - 363:{ICWiredBrowser.m} (Reclaiming Resource: DiCE Automotive Adapter)
default 23:12:43.890375 -0500 icdd #ICDebug - 363:{ICWiredBrowser.m} (Reclaiming Resource: DiCE Automotive Adapter)
default 23:12:43.890487 -0500 icdd #ICDebug - 371:{ICWiredBrowser.m} (6 USB Descriptions Managed)
default 23:12:43.890557 -0500 icdd #ICDebug - 373:{ICWiredBrowser.m} (<-- USB Terminate)
default 23:12:43.890771 -0500 icdd #ICDebug - 504:{ICDDMessageCenter.m} (-Rem DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionUndefined)
default 23:12:43.891101 -0500 icdd #ICDebug - 504:{ICDDMessageCenter.m} (-Rem DiCE Automotive Adapter - 0xff/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionUndefined)
default 23:12:43.891377 -0500 icdd #ICDebug - 23:{ICWiredBrowser.m} (USB Device first match)
default 23:12:43.892147 -0500 icdd #ICDebug - 388:{ICWiredBrowser.m} (7 USB Descriptions Managed)
default 23:12:43.893511 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionSUQuery)
default 23:12:44.211093 -0500 icdd #ICDebug - 213:{ICResourceManager.m} (44694345-2D32-3036-3735-314030303030|DiCE Automotive Adapter|MANUFACTURER:SETEK AB;MODEL:DiCE Automotive Adapter|SW=FALSE|)
default 23:12:44.212788 -0500 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add DiCE Automotive Adapter - 0x0/0x0/0x0 - 0xfa130000 - ICDeviceDescriptionAdded)

I don't know if Windows has has any equivalent debug logging, but if there is further debugging info you would recommend, I can go get it.

[RickHaleParker]

Drivers, can log errors to the system event log. The errors are visible in the Event Viewer.
Click on the Windows Start icon and type "Event Viewer", launch Event Viewer.
Use the filter in Event Viewer to filter out everything but warnings and errors.
See if you can find some entries for the Dice driver.

There is a stand alone Dice diagnostic tool installed. Look for it in the Start menu under Dice.

Is there any way you can take the Dice installer from the Vida install media and test the Dice hardware on a Windows PC hardware. Install just the Dice Software not Vida. If your Dice works in a true Windows 7 hardware environment, we will know it not your Dice or the Dice software. Process of elimination. You got any buddies that do Windows?

If things start getting "WTF" keep in mind there is no Vida software per se. Vida is a Microsoft Access database with some helper programs. In turn, Microsoft Access is an assembly of stand alone programs. You got a lot of subsystems that got to play well together ....

At this point I suspect it a communication problem between the VM and the Mac USB port. You might want to look at the VM settings in the VM manager. You might need to stop the VM to make changes. DiCE supports USB 2.0, is the virtual USB port set for 2.0? Is it setup for passthrough or host managed?

[prwood]

At this point I suspect it a communication problem between the VM and the Mac USB port. You might want to look at the VM settings in the VM manager. You might need to stop the VM to make changes. DiCE supports USB 2.0, is the virtual USB port set for 2.0? Is it setup for passthrough or host managed?

Ding ding, we have a winner!

It turns out that Virtualbox, by default, only comes configured with USB 1.1. I had to download and install the Virtualbox Extension Pack in the Mac OS X host OS, which provides support for USB 2.0. Then I edited my VM's configuration in Virtualbox and switched USB from 1.1 to 2.0. After that, I booted up the VM, connected the DiCE unit to my Mac host, and it was properly recognized. I was able to start VIDA, read the vehicle, and operate everything in the diagnostics tab.

Thanks so much for all the help!

[RickHaleParker]

Good that you got it working.

[user12323]

DiCE supports USB 2.0, is the virtual USB port set for 2.0?

Beer for You. It was great help to find Your remarks.