- #Ediabas k dcan usb interface install#
- #Ediabas k dcan usb interface serial#
- #Ediabas k dcan usb interface archive#
- #Ediabas k dcan usb interface software#
#Ediabas k dcan usb interface software#
It’s used when ISTA (or any BMW diag software needing Ediabas to connect to car), is run from another PC than the one where Ediabas itself is installed, and “discusses” remotely with it over a network. You also don’t have to care about ifhsrv32, which is a network proxy for Ediabas. You don’t care about anything TCP or Ethernet here as you’ll be using an USB K+DCAN cable if I’m correct (=> nothing to do with a network connection).
– modify EcuPath parameter inside C:\Rheingold\Ediabas\BIN\EDIABAS.INI to C:\Rheingold\Ecu – the rest of Ediabas package (docs, helper files, sim files, etc ….) will be installed in C:\EDIABAS as usual – this will create a new C:\Rheingold\Ediabas\BIN directory containing all Ediabas binaries + DLLs + INI files
#Ediabas k dcan usb interface install#
– reinstall Ediabas MSI package, changing its install path to C:\Rheingold\Ediabas\ during installation – in your main ISTA/D deployment directory, rename C:\Rheingold\Ediabas\BIN to C:\Rheingold\Ediabas\OLD_BIN – uninstall supplemental Ediabas altogether (right click/uninstall on Ediabas MSI file if it’s the one that’s currently installed) The problem is then to know which of both version is actually used by ISTA/D when it starts.
#Ediabas k dcan usb interface archive#
The main ISTA/D archive deploys a Rheingold directory which already contains a minimal Ediabas install (C:\Rheingold\Ediabas), and it’s that install that ISTA/D is configured to use, so the supplemental Ediabas install (from the Ediabas 7.3.0 MSI file) comes as a duplicate in my understanding, but adds some features as it’s a complete Ediabas version. I think you’ve installed the same kind of ISTA/D standalone package, so here’s what I’ve learnt wandering through the various directories. Please check the access to the vehicle and check whether the testing-analysis-diagnosis has been activated. Selected operations and then read out vehicle data and selected complete identification VCI Config tab and selected Ediabas standard settings (ediabas.ini) Enter the number 1 in the ISIS, ignore the error. If it asks for a license, copy from the file License.txt which is in the Rheingold directory. Run C: \ Rheingold \ TesterGUI \ bin \ Release \ ISTAGUI.exe. Unpacked to C: \ Rheingold, unzip and copy SQLiteDBs to Rheingold \ SQLiteDBs \ Opened C:\EDIABAS\BIN\OBD.INI with notepad and checked for “Port=com9”
Opened C:\EDIABAS\BIN\EDIABAS.INI with notepad and checked for “Interface = STD:OBD” and in TCP settings set “Port=6801”
#Ediabas k dcan usb interface serial#
Plugged K+DCAN Cable into laptop and let it install the latest drivers on its ownĭevice Manager -> USB serial port properties -> port settings -> advanced -> change port number to com9 and latency timer to 1 This is the solution of error on K+DCAN INPA cable “vehicle could not be identified”
0 kommentar(er)
