I bought a cheap 5054a scanner for $79, not Bluetooth pairing. Then, i took a tour in my home town and buy 3 different Bluetooth modules, to do some interesting thing with Bluetooth not connecting problem…
3 different Bluetooth modules i got:
All installs on my Win 7 SP1 as Bluetooth Radio on Device Manager.
But only 1 recognize my VAS5054A head and working flawlessly with VAS-PC, ODIS-S and ODIS-E !
Two of them had CSR chip inside:
And The Winner Is :
I hook up an Airbag control unit to a female OBD2 connector on my worktable and this are the results:
Obviously in ODIS-E you can check only the connection…
I hope this info help a lot of people who is struggling with BT connection.
But now, new vas 5054a units come with Bluetooth, like this
http://www.worldobd2.com/wholesale/vas-5054a-odis.html
Attachment: logfiles:
VAS-PC
************ Getting MVCI Module paths ************* Root description file contains 5 MVCI modules.—————————————————-Selected MVCI module: EDIC_D_PDU_API_1_10_048—————————————————-PDU-API dll:C:PDU-APISofting1.10.048vecomPDUAPI_SoftingAG_1.10.048.dllPDU-API ModuleDescriptionFile:C:PDU-APISofting1.10.048vecomMDF_SoftingAG_EDIC-PDU-API_1.10.048.xmlPDU-API CableDescriptionFile:C:PDU-APISofting1.10.048vecomCDF_SoftingAG_EDIC-PDU-API_1.10.048.xmlLoading PDU-API library file…Loading successful!—————————————————-Return of PDUConstruct:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Parsing MDF file…MDF parser initialisation successful, MDF file loaded!MDF file parsing completed!Fixing references completed!MDF information successfully extracted!—————————————————-Return of PDUGetModuleIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of modules found: 1—————————————————-Return of PDUGetResourceIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of matching resource IDs: 1—————————————————-Selected resource ID: 81—————————————————-Return of PDUModuleConnect:PDU_STATUS_NOERROR: PDU function call successful ************* Get module version Info ************** —————————————————-Module Short Name : VendorName=’Softing AG’ ModuleName=’VAS5054′ SerialNumber=’082145725’Module Vendor Name : Softing Automotive Electronics GmbHModule HwName : VAS5054Module SerialNumber : 82145725Module FW Name : VeComModule FW-Version : 2.10.48Module FW-Date : 7.11.2011 (Calendar week 45)Module PDU-API SW Name : Softing D-PDU API for VCIsModule PDU-API Version : 1.10.48Module PDU-API SW Date : 7.11.2011 (Calendar week 45)—————————————————-Return of PDUGetResourceIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of matching resource IDs: 1—————————————————-Selected resource ID: 81
ODIS-S
************ Getting MVCI Module paths
************* Root description file contains 5 MVCI modules.
*********** Changing the PDU-API module
************ —————————————————-Selected MVCI module: EDIC_D_PDU_API_OS—————————————————-PDU-API dll:C:Program FilesSoftingD-PDU API1.20.037vecomPDUAPI_SoftingAG_1.20.037.dllPDU-API ModuleDescriptionFile:C:Program FilesSoftingD-PDU API1.20.037vecomMDF_SoftingAG_EDIC-PDU-API_1.20.037.xmlPDU-API CableDescriptionFile:C:Program FilesSoftingD-PDU API1.20.037vecomCDF_SoftingAG_EDIC-PDU-API_1.20.037.xmlLoading PDU-API library file… PduApiLibPath:”C:Program FilesSoftingD-PDU API1.20.037vecomPDUAPI_SoftingAG_1.20.037.dll”Loading successful!—————————————————-Parsing MDF file…MDF parser initialisation successful, MDF file loaded!MDF parsing completed!Fixing references completed!Warning: ComParam ID=4, value Overflow (Max or Min value is set) !Warning: ComParam ID=5, value Overflow (Max or Min value is set) !Warning: ComParam ID=6, value Overflow (Max or Min value is set) !Warning: ComParam ID=7, value Overflow (Max or Min value is set) !Warning: ComParam ID=38, value Overflow (Max or Min value is set) !Warning: ComParam ID=39, value Overflow (Max or Min value is set) !Warning: ComParam ID=40, value Overflow (Max or Min value is set) !Warning: ComParam ID=132, value Overflow (Max or Min value is set) !Warning: ComParam ID=134, value Overflow (Max or Min value is set) !—————————————————-Parsing CDF file…CDF parser initialisation successful, CDF file loaded!CDF parsing completed!—————————————————-Return of PDUConstruct:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Return of PDUGetModuleIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of modules found: 1hMod: 1, ModuleStatus: PDU_MODST_AVAIL, Module Type ID: 531, Vendor Module Name: VendorName=’Softing AG’ ModuleName=’VAS5054′ SerialNumber=’082145725′, Vendor Additional Info: ConnectionType=’Bluetooth’—————————————————-Return of PDUModuleConnect:PDU_STATUS_NOERROR: PDU function call successful ************* Get module version Info ************** —————————————————-Module Short Name : VendorName=’Softing AG’ ModuleName=’VAS5054′ SerialNumber=’082145725’Module Vendor Name : Softing Automotive Electronics GmbHModule HwName : VAS5054Module SerialNumber : 82145725Module FW Name : VeComModule FW-Version : 2.20.37Module FW-Date : 15.1.2016 (Calendar week 2)Module PDU-API SW Name : Softing D-PDU API for VCIsModule PDU-API Version : 1.20.37Module PDU-API SW Date : 15.1.2016 (Calendar week 2)—————————————————-Return of PDUGetResourceIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of matching resource IDs: 1—————————————————-Selected resource ID: 81—————————————————-Return of PDUGetResourceIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of matching resource IDs: 1—————————————————-Selected resource ID: 81
ODIS-E
************ Getting MVCI Module paths ************* Root description file contains 5 MVCI modules. *********** Changing the PDU-API module ************ —————————————————-Selected MVCI module: EDIC_D_PDU_API_OE—————————————————-PDU-API dll:C:Program FilesSoftingD-PDU API1.20.023vecomPDUAPI_SoftingAG_1.20.023.dllPDU-API ModuleDescriptionFile:C:Program FilesSoftingD-PDU API1.20.023vecomMDF_SoftingAG_EDIC-PDU-API_1.20.023.xmlPDU-API CableDescriptionFile:C:Program FilesSoftingD-PDU API1.20.023vecomCDF_SoftingAG_EDIC-PDU-API_1.20.023.xmlLoading PDU-API library file… PduApiLibPath:”C:Program FilesSoftingD-PDU API1.20.023vecomPDUAPI_SoftingAG_1.20.023.dll”Loading successful!—————————————————-Parsing MDF file…MDF parser initialisation successful, MDF file loaded!MDF parsing completed!Fixing references completed!Warning: ComParam ID=4, value Overflow (Max or Min value is set) !Warning: ComParam ID=5, value Overflow (Max or Min value is set) !Warning: ComParam ID=6, value Overflow (Max or Min value is set) !Warning: ComParam ID=7, value Overflow (Max or Min value is set) !Warning: ComParam ID=38, value Overflow (Max or Min value is set) !Warning: ComParam ID=39, value Overflow (Max or Min value is set) !Warning: ComParam ID=40, value Overflow (Max or Min value is set) !Warning: ComParam ID=132, value Overflow (Max or Min value is set) !Warning: ComParam ID=134, value Overflow (Max or Min value is set) !—————————————————-Parsing CDF file…CDF parser initialisation successful, CDF file loaded!CDF parsing completed!—————————————————-Return of PDUConstruct:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Return of PDUGetModuleIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of modules found: 1hMod: 1, ModuleStatus: PDU_MODST_AVAIL, Module Type ID: 531, Vendor Module Name: VendorName=’Softing AG’ ModuleName=’VAS5054′ SerialNumber=’082145725′, Vendor Additional Info: ConnectionType=’Bluetooth’—————————————————-Return of PDUModuleConnect:PDU_STATUS_NOERROR: PDU function call successful ************* Get module version Info ************** —————————————————-Module Short Name : VendorName=’Softing AG’ ModuleName=’VAS5054′ SerialNumber=’082145725’Module Vendor Name : Softing Automotive Electronics GmbHModule HwName : VAS5054Module SerialNumber : 82145725Module FW Name : VeComModule FW-Version : 2.20.23Module FW-Date : 8.9.2014 (Calendar week 36)Module PDU-API SW Name : Softing D-PDU API for VCIsModule PDU-API Version : 1.20.23Module PDU-API SW Date : 8.9.2014 (Calendar week 36)—————————————————-Return of PDUGetResourceIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of matching resource IDs: 1—————————————————-Selected resource ID: 81—————————————————-Return of PDUGetResourceIds:PDU_STATUS_NOERROR: PDU function call successful—————————————————-Number of matching resource IDs: 1—————————————————-Selected resource ID: 81
