ediabas.ini
;#################
;# EDIABAS 7.3.0 #
;#################
;=============================================================================
[Configuration]
;=============================================================================
Interface = REMOTE
Simulation = 0
EcuPath = C:\EDIABAS\ECU
SimulationPath = C:\EDIABAS\SIM
TracePath = C:\Windows\Temp
TraceSize = 1024
ApiTrace = 0
IfhTrace = 0
; IfhnTrace = 0
; SystemTraceSys = 0
; SystemTraceBip = 0
; SystemTraceIfh = 0
; SystemTraceNet = 0
; BipDebugLevel = 0
; BipErrorLevel = 0
UbattHandling = 0
IgnitionHandling = 0
ClampHandling = 0
RetryComm = 1
SystemResults = 1
TaskPriority = 0
; CodeMapping = C:\EDIABAS\BIN\ansi2oem.tab
; LoadWin32 = 0
NetworkProtocol = TCP
; --- neu ab EDIABAS 7.2.0 ---------------------------------------------------
ShowIcon = 0
LogLevel = 0
TraceBuffering = 0
TraceHistory = 999
TraceSync = 1
; TraceWriter = <FilePathName>
;=============================================================================
[TCP]
;=============================================================================
RemoteHost = LMUC203404
Port = 6801
TimeoutConnect = 2000
TimeoutReceive = 2000
TimeoutFunction = 10000
; TimeResponsePending = 5000
; DisconnectOnApiEnd = 1
; InitCmd0 = FE,04,00,03,01
; InitCmd1 = FD,05,00,03,01
;=============================================================================
[XEthernet]
;=============================================================================
RemoteHost = Autodetect
HeaderFormat = 0
TesterAddress = F4,F5
ControlPort = 6811
DiagnosticPort = 6801
TimeoutConnect = 20000
;=============================================================================
[IfhProxy]
;=============================================================================
Port = 6700
;=============================================================================
; End Of File EDIABAS.ini
;=============================================================================
Not joined yet? Register for free and enjoy features such as alerts, private messaging and viewing latest posts and topics.
DIS or INPA
-
- Member
- Posts: 670
- Joined: Sat Jul 06, 2013 11:18 am
DIS or INPA
Lost in space, found in a dustbin........
2005 Z4 2.2
2011 318 d Estate Recalled and repaired - Update: Turbo blown new one about to get fitted....
2008 2.0d Mondeo Estate Gone but not forgotten
2008 TDV6 Discovery 3 HSE
2005 Z4 2.2
2011 318 d Estate Recalled and repaired - Update: Turbo blown new one about to get fitted....
2008 2.0d Mondeo Estate Gone but not forgotten
2008 TDV6 Discovery 3 HSE
- GuidoK
- Lifer
- Posts: 3171
- Joined: Tue Aug 17, 2010 1:37 am
- Location: all over the place
DIS or INPA
Your ediabas.ini file is not good.
The interface parameter is wrong.
It should read:
Interface =STD:OBD
Now it reads
Interface =Remote
So you have to change that and save that.
Als my tracepath is set at:
TracePath =C:\EDIABAS\TRACE
I dont know if thats an issue but maybe change that too. (and make a C:\EDIABAS\TRACE folder if you dont have that yet)
Also check in the device manager that when you plug your cable in (in the usb port) that its assigned at COM3 (that is the com port designated in your obd.ini)
If your device manager decides to assign a different com port (could be any of them), change it in your OBD.ini
So thats this parameter:
Port=Com3
It can sometimes happen that if you use a different usb port, the cable gets a different com port assigned, so take that into account if you have connection problems.
Also I believe you have the cable with the switch. In one switched position it works, in the other one it doesnt (but thats usually clear to everyone)
What you also have to check are the system variables.
Go to the properties of my computer (of how its called on your pc); thats rightclick on my computer icon in windows explorer (file explorer), select properties.
Then you get a screen that gives you info on your computer, installed operating system version etc.
Go to change settings at the computer name/domain/workgroup section.
You get a new screen, select advanced.
Select environment variables (I think thats what its called, I'm doing this from a computer in a different language...)
Check at the window 'system variables' if you have a:
"ediabas_config_dir" set at "C:\ediabas\bin"
If not, add that parameter.
And check if at the variable "Path" it also says "c:\ediabas\bin"
At the path variable theres a whole bunch of things, you you have to click edit and scroll with the cursor from left to right to read all the path variables. If c:\ediabas\bin is not in that line, you have to add ;c:\ediabas\bin at the end (note the ; )
My guess is that those last 2 bits are all sorted, but check them anyway.
This should at least get INPA working, for Rheingold there could be other issues, but assuring that the ediabas software connection to the car works is the main thing.
of course also check if ediabas is loaded when inpa is started (you get an ediabas icon in the system tray)
The interface parameter is wrong.
It should read:
Interface =STD:OBD
Now it reads
Interface =Remote
So you have to change that and save that.
Als my tracepath is set at:
TracePath =C:\EDIABAS\TRACE
I dont know if thats an issue but maybe change that too. (and make a C:\EDIABAS\TRACE folder if you dont have that yet)
Also check in the device manager that when you plug your cable in (in the usb port) that its assigned at COM3 (that is the com port designated in your obd.ini)
If your device manager decides to assign a different com port (could be any of them), change it in your OBD.ini
So thats this parameter:
Port=Com3
It can sometimes happen that if you use a different usb port, the cable gets a different com port assigned, so take that into account if you have connection problems.
Also I believe you have the cable with the switch. In one switched position it works, in the other one it doesnt (but thats usually clear to everyone)
What you also have to check are the system variables.
Go to the properties of my computer (of how its called on your pc); thats rightclick on my computer icon in windows explorer (file explorer), select properties.
Then you get a screen that gives you info on your computer, installed operating system version etc.
Go to change settings at the computer name/domain/workgroup section.
You get a new screen, select advanced.
Select environment variables (I think thats what its called, I'm doing this from a computer in a different language...)
Check at the window 'system variables' if you have a:
"ediabas_config_dir" set at "C:\ediabas\bin"
If not, add that parameter.
And check if at the variable "Path" it also says "c:\ediabas\bin"
At the path variable theres a whole bunch of things, you you have to click edit and scroll with the cursor from left to right to read all the path variables. If c:\ediabas\bin is not in that line, you have to add ;c:\ediabas\bin at the end (note the ; )
My guess is that those last 2 bits are all sorted, but check them anyway.
This should at least get INPA working, for Rheingold there could be other issues, but assuring that the ediabas software connection to the car works is the main thing.
of course also check if ediabas is loaded when inpa is started (you get an ediabas icon in the system tray)
Z4 3.0i | ESS TS2+ | Quaife ATB LSD | Brembo/BMW performance BBK front/rear | Schrick FI cams | Schmiedmann headers+cats | fully polybushed | Vibra-technics engine mounts | H&R anti rollbars | KW V3 coilovers | Sachs Race Engineering clutch
-
- Member
- Posts: 670
- Joined: Sat Jul 06, 2013 11:18 am
DIS or INPA
Just gonna restore the laptop and try installation from scratch.
Had two versions of the .ini files and neither was correct so time to bin it all and start again..
Thanks will let you know if I succeed.
Had two versions of the .ini files and neither was correct so time to bin it all and start again..
Thanks will let you know if I succeed.
Lost in space, found in a dustbin........
2005 Z4 2.2
2011 318 d Estate Recalled and repaired - Update: Turbo blown new one about to get fitted....
2008 2.0d Mondeo Estate Gone but not forgotten
2008 TDV6 Discovery 3 HSE
2005 Z4 2.2
2011 318 d Estate Recalled and repaired - Update: Turbo blown new one about to get fitted....
2008 2.0d Mondeo Estate Gone but not forgotten
2008 TDV6 Discovery 3 HSE
- GuidoK
- Lifer
- Posts: 3171
- Joined: Tue Aug 17, 2010 1:37 am
- Location: all over the place
DIS or INPA
With some installations you have to run a file called obdsetup.exe to initiate the changes needed to use it with the K-line/D-can usb cable.
Z4 3.0i | ESS TS2+ | Quaife ATB LSD | Brembo/BMW performance BBK front/rear | Schrick FI cams | Schmiedmann headers+cats | fully polybushed | Vibra-technics engine mounts | H&R anti rollbars | KW V3 coilovers | Sachs Race Engineering clutch
-
- Member
- Posts: 670
- Joined: Sat Jul 06, 2013 11:18 am
DIS or INPA
Still no joy HELP
Lost in space, found in a dustbin........
2005 Z4 2.2
2011 318 d Estate Recalled and repaired - Update: Turbo blown new one about to get fitted....
2008 2.0d Mondeo Estate Gone but not forgotten
2008 TDV6 Discovery 3 HSE
2005 Z4 2.2
2011 318 d Estate Recalled and repaired - Update: Turbo blown new one about to get fitted....
2008 2.0d Mondeo Estate Gone but not forgotten
2008 TDV6 Discovery 3 HSE
-
- Senior Member
- Posts: 1178
- Joined: Tue Mar 21, 2017 11:11 pm
- Location: North West
DIS or INPA
Personally could never get DIS or SSS to work properly, ended up trying ISTA/D and ISTA/P and they work perfectly.
- thanatu55
- Senior Member
- Posts: 1452
- Joined: Mon Jul 25, 2016 4:50 pm
DIS or INPA
With some of the cheaper cables you need to link pins 7 and 8 together, that's what I had to do before the car would see any of the software or vice verser. Open up the plug and use a bit of solder between pin 7 and 8.
- ph001
- Lifer
- Posts: 3870
- Joined: Mon Oct 31, 2016 5:53 pm
- Location: N. Yorkshire.
DIS or INPA
Thats what the switch does on the bcables one.