alexander

The K+DCAN interface is currently not supported by CarPort.

Can post a picture of the cable ?

Please manually delete the folder, where CarPort.exe is installed. Then reinstall the latest version of CarPort, which is currently 1.4.2.

You have to enter the access code via "Coding 2". This is a feature of the upcoming Pro-Modules. There is a time limited preview (30.11.2012) available, where you can test the features of the Pro-Modules. CarPort_2.0.0_beta2_Setup.exe

Thanks for the ideas ! We have planned to optimize the measurement block scan and adaptation channel scan, so that the channels are not scanned again for the same ECU. An "offline mode" where you can look at previous results is also interesting. For the time being i suggest you create a diagnostic report via the autoscan feature. This report contains all vital information of the ECUs.

Activation codes are generated manually at the moment. I have sent the code to you just now, please check your mail.

When you connect to an ECU, just go to the "Adaptation"-tab and either choose the adaptation channel from the combo-box or enter the channel number manually (after entering the number press the enter key). Then enter the new value and press the "Test"-button. If the ECU accepts the new value, you can press the "Write test value" button, to permanently store the value in the ECU.

You can perform a service interval reset via adaptation. Although adaptation is not officially supported in the basic modules KKL and CAN, it should work for VAG cars (Volkswagen, Audi, Seat, Skoda) with KWP1281 and KWP2000 over K-Line and CAN-Bus. UDS is currently not supported.

If you buy the Basic-Module OBD2, we will email you a new activation code that includes both Basic-Modules (KKL and OBD2).

When you connect to the motor control unit (address 01), you can see the part number in the info-tab.

What is the partnumber of the motor control unit ?

Unfortunately no. The Ross-Tech cable uses a proprietary and undocumented protocol. It is not compatible with CarPort.

~60 euro in total is correct. You can upgrade later for the price difference between pro and basic.

Priced versions are not offered yet. We plan to release the basic-modules very soon. the pro-modules will be available early 2012. An upgrade from the basic-modules to the pro-modules will be offered. The pro-modules include the complete functionality of the basic-modules. Prices: basic-module OBD2 : 9,95€ basic-module VW K-Line: 29,95€ basic-module VW CAN : 29,95€ pro-module OBD2 : 49,95€ pro-module VW K-Line : 79,95€ pro-module VW CAN : 79,95€ functions of the basic-modules VW K-Line and CAN: - all measurement-blocks - data recording of measurements - freeze-frame information - printable diagnostic report - clear errors functions of the pro-modules VW K-Line and CAN: - all functions of the basic-module - adaptation - coding - login - output tests - basic settings If there is anything unclear, please ask us. Regards, Alexander

Version 1.0.8 includes following bugfixes and new features: [ul][li]closing of the application was revised[/li][li]fix of communication problems with some bluetooth chipsets[/li][li]fix of login problems with some KWP2000 ECUs[/li][li]minor fixes in the KWP2000 implementation[/li][li]reliable detection of the mOByDic 3200 interface[/li][li]support of the automatic mode change feature of the AGV4000B[/li][li]support of OBD2 over PWM, VPW, CAN 11-bit and CAN 29-bit[/li][li]display of the OBD2 system status[/li][li]current drivers of the supported interfaces are now included in the installer[/li][/ul]

We recommend using a USB KKL-interface based on the USB-serial converter chip from FTDI with CarPort car diagnostics software. Most of the available USB KKL-interfaces use this kind of converter chip (if in doubt, ask the dealer). The FTDI-chip allows a more stable connection to ECUs that communicate at custom baudrates. Additionally the latencies are lower with the FTDI-chip. Even though, when using a RS232 KKL-interface, the converted signal is immediately available at the RS232 connector, the time it takes till this information is available in windows is typically around 5ms. When using the FTDI-chip the time is around 2ms. Although this difference might seem small, it can have some impact to the very timing sensitive KWP1281 protocol.