SwedeSpeed - Volvo Performance Forum banner
Cancel
Create thread New Garage Forums

Dice Unit Won't Connect/Communicate

Jump to Latest
28K views 10 replies 9 participants last post by  pczeilon  
D
#1 ·
Hi guys,

Just got Vida/Dice and installed 2012a fine on my Win 7 Pro laptop. Everything looks good, except when I open the dice diagnostics tool included, it doesn't see any unit connected. When I plug the unit into my car or laptop, the firmware status and vehicle interface status both light up solid. When I try to read info from the car or do the dice test in vida, it fails saying it could not connect. Device manager says the unit is working correctly and the drivers all installed fine.

I looked through the log and all I could find was this, where it repeatedly mentions "Invalid Device ID."

VIDA release: VIDA2012A

17:45:22,183 [SoftwareProductI][001][Event] Database: DiagSwdlRepository, SP: GetSWDLSupportedVehicleModels
17:45:24,090 [DotNetPreLoader ][001][Info] PreLoad time: 00:00:08.2504719
17:45:56,258 [J2534ChannelMana][00D][VehCom] Loading J2534 driver: C:\Program Files (x86)\DiCE\Tools\TSDiCE32.dll
17:45:56,442 [J2534ChannelMana][00D][VehCom] PassThruOpen(DiCE-207188, 4294967295)
17:45:56,444 [J2534ChannelMana][00D][VehCom] Get last J2534 error:
17:45:56,446 [J2534ChannelMana][00D][Error] J2534 function:passThruOpen failed with return value:ERR_INVALID_DEVICE_ID
17:45:56,446 [J2534ChannelMana][00D][Error] J2534 DLL error description:
17:45:56,461 [J2534ChannelMana][00D][VehCom] PassThruOpen(DiCE-207188, 4294967295)
17:45:56,462 [J2534ChannelMana][00D][VehCom] Get last J2534 error:
17:45:56,462 [J2534ChannelMana][00D][Error] J2534 function:passThruOpen failed with return value:ERR_INVALID_DEVICE_ID
17:45:56,462 [J2534ChannelMana][00D][Error] J2534 DLL error description:
17:45:56,536 [DiceFirmwareChec][00D][Warning] Vcc.Vida.DiagSwdl.VehCom2.CommToolException: Could not initialize communication device
at Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.OpenDevice()
at Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.GetCommToolProperties()
at Vcc.Vida.DiagSwdl.VehCom2.CommToolConnection.GetCommToolProperties(ICommToolSettingsResolver commToolSettingsResolver)
at Vcc.Vida.DiagSwdl.BizServices.VehicleCommProvider.VehicleConnectionProvider.GetCommToolProperties()
at Vcc.Vida.DiagSwdl.UI.CommToolActions.CommTool.GetFirmwareVersion()
at Vcc.Vida.DiagSwdl.UI.CommToolActions.DiceFirmwareCheckingAction.Start(CommTool ct)
17:48:43,800 [IdentifyVehicleW][009][Info]
17:48:43,800 [IdentifyVehicleW][009][Info] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Read VIN <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
17:48:43,800 [IdentifyVehicleW][009][Info]
17:48:43,811 [J2534ChannelMana][009][VehCom] PassThruOpen(DiCE-207188, 4294967295)
17:48:43,812 [J2534ChannelMana][009][VehCom] Get last J2534 error:
17:48:43,812 [J2534ChannelMana][009][Error] J2534 function:passThruOpen failed with return value:ERR_INVALID_DEVICE_ID
17:48:43,812 [J2534ChannelMana][009][Error] J2534 DLL error description:
17:48:43,813 [CommToolInformat][009][Warning] Error when writing commtool info
Vcc.Vida.DiagSwdl.VehCom2.CommToolException: Could not initialize communication device
at Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.OpenDevice()
at Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.GetCommToolProperties()
at Vcc.Vida.DiagSwdl.VehCom2.CommToolConnection.GetCommToolProperties(ICommToolSettingsResolver commToolSettingsResolver)
at Vcc.Vida.DiagSwdl.BizServices.VehicleCommProvider.VehicleConnectionProvider.GetCommToolProperties()
at Vcc.Vida.DiagSwdl.Workflow.CommToolInformation.CommToolInformationWriter.Write()

Is this a faulty dice unit or is something else wrong?
 
Save
Reply Quote Like Like
D
#2 ·
Solved this finally, after about 10-15 hours of frustration. Turns out the DICE unit I purchased is a cheaper version that uses some non-standard driver (CP2102 USB to UART Bridge Controller available here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx) that I had to find and install myself. It also would not work on Windows 7 Pro, I had to install to XP mode which was an ever bigger pain due to incredible instability. I think the fact that I have an AMD processor and needed a hotfix to even get XP mode to work contributed to it, but if I changed the RAM for XP mode to anything other than 512MB, the virtual PC would reboot constantly. So I had to copy the entire VIDA 2012A DVD to my desktop (about 2 hours) and then modify the installation file to eliminate the 2GB RAM requirement check, and then install VIDA (about 3 hours). VIDA 2012A runs fine with only 512MB RAM, just a lot slower.

If your DICE unit is cheap and has only blue LEDs and when plugged in the Firmware Status LED is solid, you probably are going to need to download that driver to get it to work.

Hope this helps someone in the future.
 
Save
Reply Quote Like Like
I
#6 ·
wow...this junk keeps getting worse and worse lol. Prety soon I'm sure they will just arrive as a box of parts and Chinese instructions to put them together. Someone is going to brick their car with this **** one of these days.
 
Save
Reply Quote Like Like
SwedeSpeed - Volvo Performance Forum
posts
4.1M
members
192K
Since
2000
A forum community dedicated to Volvo owners and enthusiasts. Come join the discussion about performance, builds, modifications, classifieds, troubleshooting, maintenance, new releases, and more!
Full Forum Listing
Explore Our Forums
R Forum (2004-2007) S40 & V50 (2005-2012) XC90 (SPA: 2016 - ) S60, S60CC & V60, V60CC (2011-2018) XC90 (2003 - 2014)