{"id":18875,"date":"2023-02-10T13:47:48","date_gmt":"2023-02-10T13:47:48","guid":{"rendered":"https:\/\/www.obd2tool.com\/blog\/?p=18875"},"modified":"2023-02-09T14:05:15","modified_gmt":"2023-02-09T14:05:15","slug":"vas-6154-possible-corrective-action-usb-connection","status":"publish","type":"post","link":"https:\/\/www.obd2tool.com\/blog\/vas-6154-possible-corrective-action-usb-connection\/","title":{"rendered":"VAS 6154 Possible corrective action – USB connection"},"content":{"rendered":"

Introduction<\/strong>
\nIn case you encounter errors or problems when using the new VAS 6154 VCI, here are some possible fixes that you can use or try out yourself before you need to contact support. This provision is intended to help you use the VAS 6154<\/a> quickly and efficiently.<\/p>\n

This document refers to one of the three available diagnostic modes that the VCI offers:
\n\u2022 USB<\/p>\n

Note: the following information refers to the standard VAS 6154 configuration:
\nRequirements:
\no Standard IP addresses for the VCI
\no Activated DHCP server in both USB and access-point mode<\/p>\n

1. USB connection<\/strong>
\n1.1 Requirements:
\n1. USB cap must be in place on the VCI
\n2. VCI must be connected to the tester via USB
\nFor further information please refer to the operating instructions of the VAS
\n6154.<\/p>\n

\"\"<\/p>\n

1.2 Locating faults:
\nIf you are losing connections with the VAS 6154 in USB mode please try the following suggestions, which may resolve the problem:
\n1. Visual check of the VCI\u2019s LED display
\n2. Does the tester have an existing network connection to the VCI?
\n3. Ping the VAS 6154 (ping must be permitted by the IT system)
\n4. Use the ACTIA PDU-API tester<\/p>\n

1. Visual check of the VCI\u2019s LED display<\/strong>
\nDesired state:
\nSuccessful connection status:
\nWhen you have successfully connected the VCI to the tester via USB, both the green and blue LEDs will be lit:
\n\u2022 green \u2013 VCI is active
\n\u2022 blue \u2013 connection to tester has been set up
\nNote: the blue LED will flicker while data is being transferred.<\/p>\n

\"\"<\/p>\n

Error situation:<\/strong>
\nBlue LED flashes (once per second):
\nIf the blue LED is flashing this indicates that it is waiting for a connection to the tester. If the flashing does not quite soon become a steady light, this indicates that it is not possible to establish a connection. In this case, check:<\/p>\n

\"\"<\/p>\n

\uff081\uff09 that the VAS 6154 is connected via the original USB cable
\n\uff082\uff09 whether the USB cap\u2019s serial number is listed as defective (see the document: VAS 6154-4 USB-module serialnumbers.xlsx)
\n\uff083\uff09 in Windows\u2019 Device Manager for a virtual network interface (to check the network, see item 2: \u201cDoes the tester have an existing network connection to the VCI?\u201d). If the network interface does not appear, check the driver installation and reinstall ODIS Service.<\/p>\n

Green LED is flashing:<\/strong><\/p>\n

\"\"<\/p>\n

If the green LED is flashing rather than steadily lit, then there is a system error.
\nUse Windows Explorer to navigate to the location XS_D_PDU_API -> manual,
\nopen the User Manual in your national language and check the reason for the
\nflashing green LED. Follow the recommended steps. If this does not help, or if the
\ndocument does not list your particular problem, please contact ACTIA Support.<\/p>\n

Only the green LED is lit:<\/strong><\/p>\n

\"\"<\/p>\n

The VCI is starting up. Please wait a few seconds<\/p>\n

All the LEDs on the VCI are off:<\/p>\n

\"\"<\/p>\n

The VCI has no power supply or is in power saving mode (for further information, see the Annex: \u201cPower Saving Mode\u201d). Power saving mode is standardly initiated after 15 minutes. You can reactivate the VCI by performing an ignition reset, or by restarting the device by unplugging it from the USB and then reconnecting it again. This setting can be disabled in the configuration.<\/p>\n

2. Does the tester have an existing network connection to the VCI?<\/strong>
\nTo check the network connection from the tester to the VCI, open the Device Manager on your tester and check whether the VCI is listed as a network adapter \u201cVAS6154 (USB)\u201d:<\/p>\n

\"\"<\/p>\n

If no network adapter is listed, check:
\n\uff081\uff09 whether the USB cap\u2019s serial number is listed as defective.
\n\uff082\uff09 check the driver installation and reinstall ODIS service.<\/p>\n

3. Ping the VAS 6154 (must be enabled by the IT system)<\/strong>
\nYou can test the connection between two network devices by issuing a ping.
\nTo issue a ping the tester sends a small network packet to the receiving station (in this case the VAS 6154). If the other party responds to the ping, this guarantees that the configuration is correct and that a connection is open.<\/p>\n

\"\"<\/p>\n

To issue a ping you will need the VCI\u2019s IP address. In the standard configuration, the VAS 6154 is assigned the IP address 192.168.13.69 for USB mode.<\/p>\n

Note: The VCI\u2019s configuration interface can be used to change this default configuration.
\nIf you do not know the IP address, go to the following locations on your tester: Control Panel -> Network and Internet -> Network Connection, then click on your specific VCI, and you will find its IP address under Details… .<\/p>\n

\"\"<\/p>\n

Then, go to your Windows Start menu, open the program cmd.exe and enter the following text \u201cping 192.168.13.69\u201d (if your VCI\u2019s IP address differs from this default value please modify the ping command accordingly).<\/p>\n

\"\"
\n\"\"<\/p>\n

The test is successful if the other party sends an appropriate response, as you will see below:<\/p>\n

\"\"<\/p>\n

If the test is not successful, ask your network administrator to check the network configurations (IP addresses+subnet masks) of the tester and the VCI.<\/p>\n

4. Use the ACTIA PDU -API tester<\/strong>
\nTo perform this test, open the ACTIA PDU-API tester. This is located on the following drive: C:\\ODIS-DIAG- MODULES\\PDUAPI\\ VEN-IME\\IME_D-PDU_API_ Tester.exe.
\nHere you can perform a test by clicking on \u201cStart\u201d . If you have a number of VAS 6154 devices connected to the tester, make sure you have selected the correct VCI.
\nIf, at the end of the test, each of the items is shown with a \u201ctick\u201d after it, then the test was successful:<\/p>\n

\"\"<\/p>\n

VCI was not found in the tester application:<\/strong>
\nStep 1: Restart the VAS 6154
\nIf the VCI is not found by the tester application, temporarily disconnect the VCI\u2019s power supply. To do this, unplug both the USB and the OBD connections. All the LEDs should go out. Then try again to set up a connection (if necessary, restart the tester).<\/p>\n

\"\"<\/p>\n

Step 2: Set up the file VAS6154-Static-Devices.ini
\nIf the VCI is still not found, this may be because a firewall is preventing you from searching for the VCI in the network. In this case you will need to configure the tester in such a way that the VAS 6154 can be reached via the network host name.
\nTo do this you will need to modify the configuration file \u201cVAS6154-Static-Devices.ini\u201d on the tester.<\/p>\n

When ODIS has been installed, you will find the configuration file at the following location:
\nC:\\ProgramData\\I+ME Actia GmbH\\VAS6154 Driver\\VAS6154-Static-Devices.ini<\/p>\n

\"\"<\/p>\n

Use a text editor to open this file and insert a new section:<\/p>\n

\"\"<\/p>\n

If the device\u2019s IP address is fixed, and known, then you have the option of entering it in the file. This enables the VAS 6154 to be located much more quickly.
\nNOTE: The extra lines you add to the file may not begin with a semicolon!<\/p>\n

Restart the tester and try to set up a connection again.<\/p>\n

If all the above tests were successful but you still cannot find the VAS 6154 in ODIS Service, or cannot link to it, use the LogHelper utility (see the document: Loghelper4.0.pdf) to gather together the extended logs and send in a support request.<\/p>\n

As one final check, restart the tester and see whether it is then possible to set up a connection to the
\nVAS 6154.<\/p>\n

Power save mode<\/strong><\/p>\n

\"\"<\/p>\n

Power Management:<\/strong>
\n\u2022 only visible in administration mode
\n\u2022 Power-saving settings<\/p>\n

The VAS 6154 has a two-stage shutoff:<\/strong>
\nShutoff stage 1: Power save mode
\nIf there is no communication with the diagnostic device or the vehicle for a (default) period of 15 minutes (diagnostic end), then the VAS 6154 will switch into its initial shutoff stage. When communication is reestablished, the VAS 6154 will switch back to normal operation.<\/p>\n

Shutoff stage 2: Automatic shutdown
\nIf there is no communication with the diagnostic device or the vehicle for a (default) period of 30 minutes (diagnostic end), then the device will switch right off. You can reactivate the VAS 6154 by switching the ignition off and back on (terminal 15). This will restart the VAS 6154. The
\nVAS 6154 will also be restarted if it is disconnected from the power supply and then reconnected. The process of starting up the VAS 6154 can then take up to one minute.<\/p>\n

Note: If the VAS 6154 is operated with the USB module, it does not switch right off.<\/p>\n

If you are logged on as an Administrator you can access information in the web interface or configure the timers governing the shutoff stage of the diagnostic interface:<\/p>\n

\"\"<\/p>\n

In the web interface you can change the settings governing the two shutoff stages and the buzzer.<\/p>\n

<\/div>\n","protected":false},"excerpt":{"rendered":"

Introduction In case you encounter errors or problems when using the new VAS 6154 VCI, here are some possible fixes<\/p>\n","protected":false},"author":1,"featured_media":18892,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[2238,2757,2171],"tags":[2080,751,1777,3148,752,2930,1778],"views":8628,"_links":{"self":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/18875"}],"collection":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/comments?post=18875"}],"version-history":[{"count":1,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/18875\/revisions"}],"predecessor-version":[{"id":18894,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/18875\/revisions\/18894"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/media\/18892"}],"wp:attachment":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/media?parent=18875"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/categories?post=18875"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/tags?post=18875"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}