Login Register

Help - VIDA (VM install) + VXDIAG tool

How to buy, install and use VIDA, VADIS, DiCE, VMWare and all the questions and answers that come with these tools.
Post Reply
juliow
Posts: 2
Joined: 30 November 2025
Year and Model: 2003 S40
Location: Mexico
Has thanked: 1 time

Re: Help - VIDA (VM install) + VXDIAG tool

Post by juliow »

lrock wrote: ↑24 Aug 2024, 18:59
Nikodog wrote: ↑13 May 2024, 20:24 Does anyone have an updated link to the instructions? They don't seem to be available anymore.

Thanks
Still need info? This is my daily diagnostic setup.
Hi Irock, can you tell us what version of software are you using?

I am trying to use a vxdiag with VIDA, i installed the latest version of VX Manager ans passthru, on vida vxdiag is detected, i select my car model (2003 Volvo S40), and says that the vin code cant be decoded, i think its okay because is says its a S40 or V40.
After that i put the VIN, select the transmision,etc and click ok, but when i enter the diagnostic tab, a brief window appears and dissapears instantly, after that i am in the diagnostic tab but with no access to the modules.

In the log i get this
17:42:11,622 [IdentifyVehicleW][016][Info] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Read VIN <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
17:42:11,622 [IdentifyVehicleW][016][Info]
17:42:12,786 [J2534ChannelMana][016][VehCom] PassThruOpen(, 4294967295)
17:42:12,787 [J2534ChannelMana][016][Error] J2534 function:PassThruOpen failed with return value:ERR_DEVICE_NOT_CONNECTED (J2534 DLL error description: "PassThruGetLastError returned ERR_DEVICE_NOT_CONNECTED")
17:42:12,787 [CommToolInformat][016][Warning] Error when writing commtool info
Vcc.Vida.DiagSwdl.VehCom2.CommToolException: Could not initialize communication device
en Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.OpenDevice()
en Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.GetCommToolProperties()
en Vcc.Vida.DiagSwdl.VehCom2.CommToolConnection.GetCommToolProperties(ICommToolSettingsResolver commToolSettingsResolver)
en Vcc.Vida.DiagSwdl.BizServices.VehicleCommProvider.VehicleConnectionProvider.GetCommToolProperties()
en Vcc.Vida.DiagSwdl.Workflow.CommToolInformation.CommToolInformationWriter.Write()
17:42:13,985 [J2534ChannelMana][016][VehCom] PassThruOpen(, 4294967295)
17:42:13,986 [J2534ChannelMana][016][Error] J2534 function:PassThruOpen failed with return value:ERR_DEVICE_NOT_CONNECTED (J2534 DLL error description: "PassThruGetLastError returned ERR_DEVICE_NOT_CONNECTED")
17:42:13,986 [IdentifyVehicleW][016][Error] No Vehicle response
Vcc.Vida.DiagSwdl.VehCom2.CommToolException: Could not initialize communication device
en Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.OpenDevice()
en Vcc.Vida.DiagSwdl.VehCom2.J2534.J2534ChannelManager.IsCanMsSupported()
en Vcc.Vida.DiagSwdl.VehCom2.J2534.DiagConnection.IsCanMsSupported()
en Vcc.Vida.DiagSwdl.VehCom2.Diagnostics.DiagnosticConnection.IsCanMsSupported()
en Vcc.Vida.DiagSwdl.AppServices.VehicleAccess.VehicleAccess.IsCanMsSupported()
en Vcc.Vida.DiagSwdl.Workflow.IdentifyVehicle.IdentifyVehicleWF.startIdentification()
Top
lrock
Posts: 122
Joined: 26 August 2022
Year and Model: 2001 v70 xc
Location: pennsylvania
Has thanked: 9 times
Been thanked: 37 times

Post by lrock »

juliow wrote: ↑30 Nov 2025, 17:01
lrock wrote: ↑24 Aug 2024, 18:59
Nikodog wrote: ↑13 May 2024, 20:24 Does anyone have an updated link to the instructions? They don't seem to be available anymore.

Thanks
Still need info? This is my daily diagnostic setup.
Hi Irock, can you tell us what version of software are you using?
lenovo t490 laptop running windows 10
which is running a virtual box image of windows10 vida install downloaded from https://volvodiag.com/virtualmachine-image/
it's $5, it's worth it. vxmanager already installed, i set up virtual box usb filter to grab the vxdiag anytime it plugs into my laptop, or you can switch it over manually. i updated the vxmanager to the latest inside the image, i log into vida using admin. i turn off virus protection and updates inside the image and only let it have network when i need to do a license update on the vxdiag.


if you want help to get your setup operational i need more info, system, type of install, vbox or vmware or not.

plug in your vxdiag open your vxmanager, and make sure you're able to communicate with the tool, and you have a good license, have you updated the firmware on your vxdiag? you have to make sure that's all sorted and the license is updated before using it in vida, if it says your license is expired do a firmware and license update through vxmanager.
once that's all good restart vida and try scanning again.
Top
juliow
Posts: 2
Joined: 30 November 2025
Year and Model: 2003 S40
Location: Mexico
Has thanked: 1 time

Post by juliow »

Hi irock,

I am following up with a description of my setup and the results of my testing. Your previous guidance allowed me to advance past the initial J2534 initialization errors, but communication with the vehicle still fails.

My setup is the following:

Laptop: Dell Latitude 5400
OS: Windows 10 (from the preconfigured VirtualBox image provided at volvodiag.com) on Windows 10 64bit
VIDA version: VIDA 2014D
Interface: VXDIAG VCX NANO for Volvo
Vehicle: Volvo S40 2003
VX Manager: Latest version available
Modules installed in VX Manager: VOLVO + PASSTHRU
Windows Defender and all antivirus modules fully disabled during testing

License was good, firmware the latest, i updated again just in case, i opened vida and select VXDIAG as diagnostic tool, selected read vin, and had a warning saying that a S40 or a V40 was connected, that i cant retrieve the VIN or something like that, i put the vin manually and select ok, but when i click the diagnostic tab, a brief pop up appears and disappear in a fraction of a second.

I reviewed the passthru J2534 DLL versions installed by different versions of VX Manager. The DLL provided by the current release was:

VCXPT32.dll
Size: 109,568 bytes
CRC32: 4E97926E

This version consistently resulted in immediate PassThruOpen failures in VIDA. I extracted older DLLs from archived installers, and only one of them allowed VIDA to progress further:

VCXPT32.dll
Size: 116,616 bytes
CRC32: 74E0D8D9

Once I replaced the VIDA J2534 DLL with this older 116,616-byte file, the behavior changed significantly. VIDA stopped returning ERR_DEVICE_NOT_CONNECTED and started partially initializing the diagnostic layer.

Here are some logs illustrating the previous failure mode with the 109,568-byte DLL:

PassThruOpen(, 4294967295)
J2534 function:PassThruOpen failed with return value:ERR_DEVICE_NOT_CONNECTED
PassThruGetLastError returned ERR_DEVICE_NOT_CONNECTED
CommToolException: Could not initialize communication device
No Vehicle response


And here is the behavior after replacing it with the 116,616-byte DLL:

IdentifyVehicleW Info >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Read VIN <<<<<<<<<<<<<<<<<<<<<<<<<<<<
PassThruOpen(, 4294967295)
DiagConnection.IsCanMsSupported()
Vehicle type recognized: S40 (-04)
VIN:
Error: Unable to read VIN from vehicle
When entering the Diagnostics tab, the VIDA popup responsible for initializing communication with the vehicle appears for less than a second and immediately closes. The corresponding log entries show that VIDA starts a diagnostic session but receives no ECU responses:

DiagSession started
DiagConnection: No response from ECU
Error: No Vehicle response

This suggests the J2534 interface is now being recognized correctly by VIDA, but the VCX hardware does not implement proper ISO9141/ISO14230 K-line support for Phase 1 Volvos. This aligns with several independent reports indicating that many VXDIAG units advertise J2534 compliance but lack functional K-line capability
. This according to ChatGPT

My question for you is whether you have ever successfully communicated with a Phase 1 Volvo (S/V40 up to 2004) using a VCX NANO or any VXDIAG device. Any details about firmware versions, VX Manager builds, or specific DLL revisions that worked for you would be extremely helpful.

Thanks again for the earlier insights — they helped narrow down the problem substantially.


P.D. I had the car key on acc only, i did not start the car, because i just notice that my timing belt is loose, i have the parts, but i am waiting for a few days off, i don't know if this makes a difference (having the key in acc vs having the car with the motor on)


Here is the log

Code: Select all

---------------------------------------------------------------------
Starting new logsession: 2025-12-03 22:42:57
---------------------------------------------------------------------

VIDA release: VIDA2014D

22:42:57,849 [CarStatus       ][008][Info]    Init CarStatus
22:43:11,396 [CarComRepository][001][Event]   Database: CarCom, SP: vadis_GetEcuTypeDescriptions
22:43:12,413 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: '' ScriptId: 'ecuspec_Unknown' Language: 'en-US' EcuType: '-1' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:43:12,413 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: 'VehCommSpecification' ScriptId: '' Language: 'en-US' EcuType: '0' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:43:12,443 [RunScriptService][001][Error]   GetVehCommSpecification threw an exception.
Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptMissingException: Script missing: Scripttype: 'VehCommSpecification' ScriptId: '' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
   at Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptProvider.GetFromDb(String scriptType, String scriptId, VehicleProfile vehicleProfile, String languageCode, Int32 ecuType, Boolean returnMultipleScripts)
   at Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptProvider.GetOneScriptFromDb(String scriptType, String scriptId, VehicleProfile vehicleProfile, String languageCode, Int32 ecuType)
   at Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptProvider.GetScript(ScriptType scriptType, String scriptId, VehicleProfile vehicleProfile, String languageCode, Int32 ecuType)
   at Vcc.Vida.DiagSwdl.AppServices.Scripting.RunScriptService.GetVehCommSpecification(VehicleProfile vehicleProfileIds, Int32 ecuType)
22:45:56,193 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: '' ScriptId: 'ecuspec_CEM' Language: 'en-US' EcuType: '-1' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:45:56,193 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: 'VehCommSpecification' ScriptId: '' Language: 'en-US' EcuType: '372302' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:45:56,256 [ScriptProvider  ][001][Info]    Fetched script: 'VCC-237363-1 1.3' title: 'ecuspec_cem'
22:45:56,271 [Script          ][001][Info]    Running script: 'VCC-237363-1 1.3' title: 'ecuspec_cem'
22:47:20,990 [CarStatus       ][008][Info]    Init CarStatus
22:48:25,709 [CarStatus       ][011][Info]    Init CarStatus
22:48:33,974 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: '' ScriptId: 'ecuspec_Unknown' Language: 'en-US' EcuType: '-1' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:48:33,974 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: 'VehCommSpecification' ScriptId: '' Language: 'en-US' EcuType: '0' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:48:33,990 [RunScriptService][001][Error]   GetVehCommSpecification threw an exception.
Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptMissingException: Script missing: Scripttype: 'VehCommSpecification' ScriptId: '' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
   at Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptProvider.GetFromDb(String scriptType, String scriptId, VehicleProfile vehicleProfile, String languageCode, Int32 ecuType, Boolean returnMultipleScripts)
   at Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptProvider.GetOneScriptFromDb(String scriptType, String scriptId, VehicleProfile vehicleProfile, String languageCode, Int32 ecuType)
   at Vcc.Vida.DiagSwdl.BizServices.ScriptRepository.ScriptProvider.GetScript(ScriptType scriptType, String scriptId, VehicleProfile vehicleProfile, String languageCode, Int32 ecuType)
   at Vcc.Vida.DiagSwdl.AppServices.Scripting.RunScriptService.GetVehCommSpecification(VehicleProfile vehicleProfileIds, Int32 ecuType)
22:48:36,240 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: '' ScriptId: 'ecuspec_CEM' Language: 'en-US' EcuType: '-1' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:48:36,240 [ScriptProvider  ][001][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: 'VehCommSpecification' ScriptId: '' Language: 'en-US' EcuType: '372302' Profile: '0b00c8af804cb2c7,0b00c8af80206631,0b00c8af80206735,0b00c8af8020959c,'
22:48:36,256 [ScriptProvider  ][001][Info]    Fetched script: 'VCC-237363-1 1.3' title: 'ecuspec_cem'
22:48:36,256 [Script          ][001][Info]    Running script: 'VCC-237363-1 1.3' title: 'ecuspec_cem'
And here is another log

Code: Select all

---------------------------------------------------------------------
Starting new logsession: 2025-12-04 23:02:17
---------------------------------------------------------------------

VIDA release: VIDA2014D

23:02:17,982 [SoftwareProductI][001][Event]   Database: DiagSwdlRepository, SP: GetSWDLSupportedVehicleModels
23:02:18,610 [DotNetPreLoader ][001][Info]    PreLoad time: 00:00:04.6738329
23:02:47,278 [IdentifyVehicleW][00E][Info]    
23:02:47,278 [IdentifyVehicleW][00E][Info]    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Read VIN <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
23:02:47,278 [IdentifyVehicleW][00E][Info]    
23:02:47,387 [J2534ChannelMana][00E][VehCom]  Loading J2534 driver: C:\ProgramData\VCX\Apps\PASSTHRU\VCXPT32.dll
23:02:49,700 [J2534ChannelMana][00E][VehCom]  PassThruOpen(, 1)
23:02:49,700 [J2534ChannelMana][00E][VehCom]  J2534-2: Checking pin switching for protocol CAN_PS
23:02:50,513 [J2534ChannelMana][00E][VehCom]  PassThruConnect(1, 0x8004, 0x100, 125000, 1)
23:02:50,560 [J2534ChannelMana][00E][VehCom]  J2534Channel::Close()
23:02:50,591 [J2534ChannelMana][00E][VehCom]  PassThruDisconnect(1)
23:02:50,591 [J2534ChannelMana][00E][VehCom]  J2534-2: Checking pin switching for protocol ISO15765_PS
23:02:50,654 [J2534ChannelMana][00E][VehCom]  PassThruConnect(1, 0x8005, 0x00, 125000, 1)
23:02:50,701 [J2534ChannelMana][00E][VehCom]  J2534Channel::Close()
23:02:50,732 [J2534ChannelMana][00E][VehCom]  PassThruDisconnect(1)
23:02:50,732 [J2534ChannelMana][00E][VehCom]  Device supports J2534-2
23:02:50,732 [J2534ChannelMana][00E][VehCom]  Driver information: FirmwareVersion: 1.9.4.2 VCX-NANO NEAVV08198, DLLVersion: 04.04.240321, APIVersion: 04.04
23:02:50,887 [ScriptProvider  ][00E][Event]   Database: DiagSwdlRepository, SP: GetScript,  Type: 'ReadVin' ScriptId: '' Language: 'en-US' EcuType: '-1' Profile: 'EMPTYPROFILE,'
23:02:51,278 [ScriptProvider  ][00E][Info]    Fetched script: 'VCC-225200-1 1.8' title: 'Read VIN first readout (Odometer Value) (No immo check)'
23:02:51,372 [Script          ][00E][Info]    Running script: 'VCC-225200-1 1.8' title: 'Read VIN first readout (Odometer Value) (No immo check)'
23:02:51,419 [CarComRepository][00F][Event]   Database: CarCom, SP: general_GetEcuId, EcuId: 30728270 AA, Result: 821
23:02:51,419 [DiagnosticVehCom][00F][Info]    Using diagnostic part number '30728270 AA' for system type: '0'
23:02:51,419 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuVariantData, EcuVariant: 821
23:02:51,512 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetAllEcuDataForProfile, VehicleProfiles: EMPTYPROFILE
23:02:51,637 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuInitFromConfigId, ConfigId: 611
23:02:51,669 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagInit, ConfigId: 611, EcuConfig: 82
23:02:51,684 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:51,700 [CarComRepository][00F][Event]   Database: CarCom, SP: service_GetInitTimingValueAll, EcuVariantId: 821
23:02:51,826 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:51,934 [RequestTimingBui][00F][Info]    GGD timing for service 0x22, P2CanClient: 1000+25 ms, P2*CanClient: 5000+25 ms, P4Can: 120000+25 ms
23:02:51,934 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '726', Message '22F114' 
23:02:52,076 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x06, 0x00, 500000, 1)
23:02:52,107 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 1
23:02:52,107 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(1, PASSTHRU_MSG, 1, 5000) - ReadVinScriptThread ->VXDIAG<-
23:02:52,138 [J2534ChannelMana][00F][VehCom]  --->	(0) 00,00,07,26,22,F1,14,
23:02:52,138 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(1, PASSTHRU_MSG, 1, 1024 ) - ReadVinScriptThread ->VXDIAG<-
23:02:52,138 [J2534ChannelMana][00F][VehCom]  <---	(0) 00,00,07,26,
23:02:52,138 [J2534ChannelMana][00F][VehCom]  TRANSMITTED FRAME indication
23:02:52,138 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(1, PASSTHRU_MSG, 1, 1020 ) - ReadVinScriptThread ->VXDIAG<-
23:02:53,169 [J2534ChannelMana][00F][Error]   J2534 function:PassThruReadMsgs failed with return value:ERR_BUFFER_EMPTY (J2534 DLL error description: "PassThruGetLastError returned ERR_BUFFER_EMPTY")
23:02:53,169 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error
23:02:53,169 [CarComRepository][00F][Event]   Database: CarCom, SP: general_GetEcuId, EcuId: 09469693  A, Result: 230
23:02:53,169 [DiagnosticVehCom][00F][Info]    Using diagnostic part number '09469693  A' for system type: '0'
23:02:53,169 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuVariantData, EcuVariant: 230
23:02:53,200 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 1
23:02:53,200 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:02:53,263 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(1)
23:02:53,263 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuInitFromConfigId, ConfigId: 240
23:02:53,263 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagInit, ConfigId: 240, EcuConfig: 64
23:02:53,263 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:53,263 [CarComRepository][00F][Event]   Database: CarCom, SP: service_GetInitTimingValueAll, EcuVariantId: 230
23:02:53,278 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:53,294 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '40', Message 'B9FB' 
23:02:53,388 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x8004, 0x100, 125000, 1)
23:02:53,512 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 1
23:02:53,512 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:53,559 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:1
23:02:54,060 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(1, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:02:54,076 [J2534ChannelMana][00F][VehCom]  --->	(0) 00,0F,FF,FE,CB,40,B9,FB,00,00,00,00,
23:02:54,076 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(1, PASSTHRU_MSG, 1, 60 ) - ReadVinScriptThread ->VXDIAG<-
23:02:54,138 [J2534ChannelMana][00F][Error]   J2534 function:PassThruReadMsgs failed with return value:ERR_BUFFER_EMPTY (J2534 DLL error description: "PassThruGetLastError returned ERR_BUFFER_EMPTY")
23:02:54,138 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error
23:02:54,138 [DiagnosticVehCom][00F][Info]    Trying next ecuconfig in list
23:02:54,138 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuInitFromConfigId, ConfigId: 241
23:02:54,138 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagInit, ConfigId: 241, EcuConfig: 80
23:02:54,138 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:54,138 [CarComRepository][00F][Event]   Database: CarCom, SP: service_GetInitTimingValueAll, EcuVariantId: 230
23:02:54,138 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:54,138 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '50', Message 'B9FB' 
23:02:54,279 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x05, 0x100, 250000, 2)
23:02:54,310 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 2
23:02:54,310 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:54,388 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 2 pMsgId:1
23:02:54,903 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(2, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:02:54,919 [J2534ChannelMana][00F][VehCom]  --->	(0) 00,0F,FF,FE,CB,50,B9,FB,00,00,00,00,
23:02:54,919 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(2, PASSTHRU_MSG, 1, 50 ) - ReadVinScriptThread ->VXDIAG<-
23:02:54,981 [J2534ChannelMana][00F][Error]   J2534 function:PassThruReadMsgs failed with return value:ERR_BUFFER_EMPTY (J2534 DLL error description: "PassThruGetLastError returned ERR_BUFFER_EMPTY")
23:02:54,981 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error
23:02:54,981 [CarComRepository][00F][Event]   Database: CarCom, SP: general_GetEcuId, EcuId: 08666792  F, Result: 70
23:02:54,981 [DiagnosticVehCom][00F][Info]    Using diagnostic part number '08666792  F' for system type: '0'
23:02:54,981 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuVariantData, EcuVariant: 70
23:02:55,013 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 2
23:02:55,044 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:2 MsgId:1
23:02:55,044 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:02:55,106 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(2)
23:02:55,137 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 1
23:02:55,170 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:1
23:02:55,170 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:02:55,262 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(1)
23:02:55,262 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuInitFromConfigId, ConfigId: 74
23:02:55,262 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagInit, ConfigId: 74, EcuConfig: 80
23:02:55,262 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:55,262 [CarComRepository][00F][Event]   Database: CarCom, SP: service_GetInitTimingValueAll, EcuVariantId: 70
23:02:55,262 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:55,278 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '50', Message 'B9FB' 
23:02:55,435 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x05, 0x100, 500000, 1)
23:02:55,481 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 1
23:02:55,481 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:55,545 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:1
23:02:56,060 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(1, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:02:56,075 [J2534ChannelMana][00F][VehCom]  --->	(0) 00,0F,FF,FE,CB,50,B9,FB,00,00,00,00,
23:02:56,075 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(1, PASSTHRU_MSG, 1, 100 ) - ReadVinScriptThread ->VXDIAG<-
23:02:56,185 [J2534ChannelMana][00F][Error]   J2534 function:PassThruReadMsgs failed with return value:ERR_BUFFER_EMPTY (J2534 DLL error description: "PassThruGetLastError returned ERR_BUFFER_EMPTY")
23:02:56,185 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error
23:02:56,216 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 1
23:02:56,247 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:1
23:02:56,247 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:02:56,310 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(1)
23:02:56,310 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '50', Message 'B9FB' 
23:02:56,310 [J2534ChannelMana][00F][VehCom]  Driver information: FirmwareVersion: 1.9.4.2 VCX-NANO NEAVV08198, DLLVersion: 04.04.240321, APIVersion: 04.04
23:02:56,498 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x03, 0x1000, 10400, 1)
23:02:56,622 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 1
23:02:56,622 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:56,669 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:1
23:02:56,747 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x05, 0x100, 250000, 2)
23:02:56,779 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 2 on channel 1
23:02:56,779 [J2534ChannelMana][00F][VehCom]  Starting periodic relay opener
23:02:56,779 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:56,841 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:2
23:02:57,387 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 2
23:02:57,387 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:57,420 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 2 pMsgId:1
23:02:57,935 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(2, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:02:57,951 [J2534ChannelMana][00F][VehCom]  --->	(0) 00,0F,FF,FE,CB,50,B9,FB,00,00,00,00,
23:02:57,951 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(2, PASSTHRU_MSG, 1, 50 ) - ReadVinScriptThread ->VXDIAG<-
23:02:58,013 [J2534ChannelMana][00F][Error]   J2534 function:PassThruReadMsgs failed with return value:ERR_BUFFER_EMPTY (J2534 DLL error description: "PassThruGetLastError returned ERR_BUFFER_EMPTY")
23:02:58,013 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error
23:02:58,013 [DiagnosticVehCom][00F][Info]    Trying next ecuconfig in list
23:02:58,013 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '40', Message 'B9FB' 
23:02:58,060 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x8004, 0x100, 125000, 3)
23:02:58,122 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 3 on channel 1
23:02:58,122 [J2534ChannelMana][00F][VehCom]  Starting periodic relay opener
23:02:58,122 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:58,169 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:3
23:02:58,700 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 3
23:02:58,700 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:02:58,747 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 3 pMsgId:1
23:02:59,262 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(3, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:02:59,278 [J2534ChannelMana][00F][VehCom]  --->	(0) 00,0F,FF,FE,CB,40,B9,FB,00,00,00,00,
23:02:59,278 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(3, PASSTHRU_MSG, 1, 60 ) - ReadVinScriptThread ->VXDIAG<-
23:02:59,341 [J2534ChannelMana][00F][Error]   J2534 function:PassThruReadMsgs failed with return value:ERR_BUFFER_EMPTY (J2534 DLL error description: "PassThruGetLastError returned ERR_BUFFER_EMPTY")
23:02:59,341 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error
23:02:59,341 [CarComRepository][00F][Event]   Database: CarCom, SP: general_GetEcuId, EcuId: 9451570, Result: 714
23:02:59,341 [DiagnosticVehCom][00F][Info]    Using diagnostic part number '9451570' for system type: '0'
23:02:59,341 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuVariantData, EcuVariant: 714
23:02:59,341 [J2534ChannelMana][00F][VehCom]  Stopping periodic relay opener
23:02:59,373 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:2
23:02:59,373 [J2534ChannelMana][00F][VehCom]  Closing diagnostic relay
23:02:59,373 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(1, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:02:59,388 [J2534ChannelMana][00F][VehCom]  --->	(0) 84,40,13,B2,F0,00,
23:02:59,419 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 2 on channel 1
23:02:59,451 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 2
23:02:59,482 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:2 MsgId:1
23:02:59,482 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:02:59,544 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(2)
23:02:59,544 [J2534ChannelMana][00F][VehCom]  Stopping periodic relay opener
23:02:59,576 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:3
23:02:59,576 [J2534ChannelMana][00F][VehCom]  Closing diagnostic relay
23:02:59,576 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(1, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:02:59,591 [J2534ChannelMana][00F][VehCom]  --->	(0) 84,40,13,B2,F0,00,
23:02:59,622 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 3 on channel 1
23:02:59,654 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 3
23:02:59,685 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:3 MsgId:1
23:02:59,685 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:02:59,747 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(3)
23:02:59,794 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:1
23:02:59,825 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 1
23:02:59,825 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:02:59,888 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(1)
23:02:59,888 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuInitFromConfigId, ConfigId: 726
23:02:59,888 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagInit, ConfigId: 726, EcuConfig: 80
23:02:59,888 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:59,888 [CarComRepository][00F][Event]   Database: CarCom, SP: service_GetInitTimingValueAll, EcuVariantId: 714
23:02:59,888 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:02:59,888 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '50', Message 'B9FB' 
23:02:59,903 [J2534ChannelMana][00F][VehCom]  Driver information: FirmwareVersion: 1.9.4.2 VCX-NANO NEAVV08198, DLLVersion: 04.04.240321, APIVersion: 04.04
23:03:00,044 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x03, 0x1000, 10400, 1)
23:03:00,185 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 1
23:03:00,185 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:03:00,247 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:1
23:03:00,372 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x05, 0x100, 250000, 2)
23:03:00,404 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 2 on channel 1
23:03:00,404 [J2534ChannelMana][00F][VehCom]  Starting periodic relay opener
23:03:00,404 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:03:00,482 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:2
23:03:01,029 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 2
23:03:01,029 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:03:01,091 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 2 pMsgId:1
23:03:01,607 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(2, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:03:01,622 [J2534ChannelMana][00F][VehCom]  --->	(0) 00,0F,FF,FE,CB,50,B9,FB,00,00,00,00,
23:03:01,622 [J2534ChannelMana][00F][VehCom]  PassThruReadMsgs(2, PASSTHRU_MSG, 1, 50 ) - ReadVinScriptThread ->VXDIAG<-
23:03:01,701 [J2534ChannelMana][00F][Error]   J2534 function:PassThruReadMsgs failed with return value:ERR_BUFFER_EMPTY (J2534 DLL error description: "PassThruGetLastError returned ERR_BUFFER_EMPTY")
23:03:01,701 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error
23:03:01,701 [CarComRepository][00F][Event]   Database: CarCom, SP: general_GetEcuId, EcuId: 30887708  A, Result: 693
23:03:01,701 [DiagnosticVehCom][00F][Info]    Using diagnostic part number '30887708  A' for system type: '0'
23:03:01,701 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuVariantData, EcuVariant: 693
23:03:01,701 [J2534ChannelMana][00F][VehCom]  Stopping periodic relay opener
23:03:01,748 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:2
23:03:01,748 [J2534ChannelMana][00F][VehCom]  Closing diagnostic relay
23:03:01,748 [J2534ChannelMana][00F][VehCom]  PassThruWriteMsgs(1, PASSTHRU_MSG, 1, 2000) - ReadVinScriptThread ->VXDIAG<-
23:03:01,778 [J2534ChannelMana][00F][VehCom]  --->	(0) 84,40,13,B2,F0,00,
23:03:01,809 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 2 on channel 1
23:03:01,857 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 2
23:03:01,903 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:2 MsgId:1
23:03:01,903 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:03:01,966 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(2)
23:03:01,998 [J2534ChannelMana][00F][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:1
23:03:02,029 [J2534ChannelMana][00F][VehCom]  Stop J2534 message filter ID 1 on channel 1
23:03:02,029 [J2534ChannelMana][00F][VehCom]  J2534Channel::Close()
23:03:02,091 [J2534ChannelMana][00F][VehCom]  PassThruDisconnect(1)
23:03:02,091 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetEcuInitFromConfigId, ConfigId: 705
23:03:02,091 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagInit, ConfigId: 705, EcuConfig: 81
23:03:02,091 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:03:02,091 [CarComRepository][00F][Event]   Database: CarCom, SP: service_GetInitTimingValueAll, EcuVariantId: 693
23:03:02,106 [CarComRepository][00F][Event]   Database: CarCom, SP: vadis_GetDiagTimings
23:03:02,106 [DiagConnection  ][00F][VehCom]  VehComm request: Ecu '51', Message 'B9F0' 
23:03:02,106 [J2534ChannelMana][00F][VehCom]  Driver information: FirmwareVersion: 1.9.4.2 VCX-NANO NEAVV08198, DLLVersion: 04.04.240321, APIVersion: 04.04
23:03:02,232 [J2534ChannelMana][00F][VehCom]  PassThruConnect(1, 0x03, 0x1000, 10400, 1)
23:03:02,357 [J2534ChannelMana][00F][VehCom]  Start J2534 message filter ID 1 on channel 1
23:03:02,357 [J2534ChannelMana][00F][VehCom]  J2534Channel::PeriodicSend()
23:03:02,419 [J2534ChannelMana][00F][VehCom]  Start J2534 periodic message channelId: 1 pMsgId:1
23:03:02,419 [J2534ChannelMana][00F][VehCom]  Calling FiveBaudInit on address 0x51
23:03:05,934 [DiagnosticVehCom][00F][Warning] J2534 diagnostic error (five_baud_init)
23:03:05,934 [VehicleAccess   ][00E][Error]   Could not retrieve VIN from vehicle
23:03:05,966 [J2534ChannelMana][00E][VehCom]  Stop J2534 periodic message ChannelId:1 MsgId:1
23:03:05,997 [J2534ChannelMana][00E][VehCom]  Stop J2534 message filter ID 1 on channel 1
23:03:05,997 [J2534ChannelMana][00E][VehCom]  J2534Channel::Close()
23:03:06,075 [J2534ChannelMana][00E][VehCom]  PassThruDisconnect(1)
23:03:06,075 [IdentifyVehicleW][00E][Error]   Identification error
Vcc.Vida.DiagSwdl.AppServices.VehicleAccess.VinException: Exception of type 'Vcc.Vida.DiagSwdl.AppServices.VehicleAccess.VinException' was thrown.
   at Vcc.Vida.DiagSwdl.AppServices.VehicleAccess.VehicleAccess.IdentifyVehicle()
   at Vcc.Vida.DiagSwdl.Workflow.IdentifyVehicle.IdentifyVehicleWF.startIdentification()
23:03:11,904 [J2534ChannelMana][001][VehCom]  PassThruClose(1)
23:03:11,904 [J2534ChannelMana][001][VehCom]  Unloading J2534 driver: C:\ProgramData\VCX\Apps\PASSTHRU\VCXPT32.dll
And here is the dll that i used
https://drive.google.com/file/d/1YlHexw ... drive_link

Saludos!
— Julio
Top
lrock
Posts: 122
Joined: 26 August 2022
Year and Model: 2001 v70 xc
Location: pennsylvania
Has thanked: 9 times
Been thanked: 37 times

Post by lrock »

juliow wrote: ↑07 Dec 2025, 23:14
Saludos!
— Julio
the only vehicle i've used with the vcxnano is a 2001 v70 xc.

just to double check, you've captured the usb device that is the vcxnano in the virtual machine?

if yes, when you're plugged into the vehicle what are you getting for the voltage of the device in vcxmanager?

then after closing vcxmanager and opening vida, what does vida say the connection voltage is for your diagnostic device?
Top
Post Reply
  • Similar Topics
    Replies
    Views
    Last post

Return to “VIDA, VADIS, DiCE”