Register
Results 1 to 3 of 3
  1. #1
    DK Veteran

    Join Date
    Dec 2022
    Posts
    526
    Thanks Thanks Given 
    63
    Thanks Thanks Received 
    177
    Thanked in
    137 Posts

    Default Odis E with VAS5054 connection problem

    Hi just recently bought VAS5054 with cable, on driver mangement it's a scanmatic device.
    First install odis e for vas5054 no connection
    Then install odis e 7.2, 14, 9.2, 12.1 with passthrough choice, select SM2-USB(scanmatic) driver, but no communication with selected device appears
    But when i choose Moongoose the mini vci cheap cable, i have communication to do things but it is not stable that's why i buy vas5054, i also tried older odis e 3.0, 5.0 same result.
    Someone on other forums make chenge on D-PDU API and worked...

  2. #2
    DK Veteran
    ricked's Avatar
    Join Date
    Apr 2016
    Location
    Europe
    Posts
    2,382
    Thanks Thanks Given 
    241
    Thanks Thanks Received 
    1,688
    Thanked in
    940 Posts

    Default

    you need D-PDU and flash files for VAS5054to work with odis

    "Softing D-PDU API for Clones (Oficial Firmware/Drivers Setup)"

    steps by fantomel member:


    1. Connect VAS5054A to USB port and install Drivers
    2. Install D-PDU API
    3. Open Softing D-PDUAPI Test Application
    4. Select PDU-API Version - here choose your installed version
    5. Push Parse MDF File button
    6. On Select MVCI Module - now if all OK you should see your VAS
    7. Push PDUModuleConnect button
    8. Look at your VAS head and you should see it blinking.
    9. Wait for 30 sec or so and at the end if all OK you should have these lines:
    ----------------------------------------------------
    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

    10. Now look up on log and you should have:
    example for D-PDU API 1.20.23
    ----------------------------------------------------
    Module Short Name : VendorName='Softing AG' ModuleName='VAS5054' SerialNumber='082145725'
    Module Vendor Name : Softing Automotive Electronics GmbH
    Module HwName : VAS5054
    Module SerialNumber : 82145725
    Module FW Name : VeCom
    Module FW-Version : 2.20.23
    Module FW-Date : 8.9.2014 (Calendar week 36)
    Module PDU-API SW Name : Softing D-PDU API for VCIs
    Module PDU-API Version : 1.20.23
    Module PDU-API SW Date : 8.9.2014 (Calendar week 36)
    ----------------------------------------------------

  3. The Following User Says Thank You to ricked For This Useful Post:

    fuzz1 (16th September, 2024)

  4. #3
    DK Veteran

    Join Date
    Dec 2022
    Posts
    526
    Thanks Thanks Given 
    63
    Thanks Thanks Received 
    177
    Thanked in
    137 Posts

    Default

    Hi thank you this procedure work for tactrix open port with success
    But with scanmatic every time failed, i connect it then on obd maybe needs 12volt but same thing no ccommunication on dpdu api. On driver it see it driver succesfully installed as scanmatic. Something else i forget, may need something change on registry for scanmatic device?

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.