DIS or INPA

Nelly Welly

Active member
Is there anyone local to Swindon who can get my Z out of transport mode, it’s showing energy efficiency mode active, after a battery failure.

I brought the cable and software but in three weekends I have still failed to get the communication with the car.
 
Don't think you can do it with INPA, but DIS can. Shame it's such a bitch to install. Is this any help.... https://www.motor-talk.de/forum/aktion/Attachment.html?attachmentId=722199

This Youtube video might help too... https://www.youtube.com/watch?v=MNgd4xY_Oic
 
Nelly Welly said:
Energy efficiency mode turns off non essentials like AC, blower above minimum and heated screen.

It's actually a vehicle settings mode specifically designed for when the car is being transported about, prior to delivery to a customer. It's designed to stop the battery getting flattened by repeated starting and moving of the car over short distances, by disabling non essential items that may be switched on by drivers during these movements.

During the PDI, dealers "should" delete transport mode, but as this can take 10 mins per car, they tend to just disable it which takes seconds. However, should the battery voltage subsequently drop below a predetermined level, even years later then it can reactivate transport mode. Best bet is to disable it - I can do it, but probably a little far for the OP.

Mike
 
No way you can limp it back to a dealer? Surely they should remove it FOC?
 
The car is still completely driveable in transport mode but good luck in getting a dealer to do it for free. If it was the dealer you bought it from you might have a better chance I suppose.
 
Ducklakeview said:
It's actually a vehicle settings mode specifically designed for when the car is being transported about, prior to delivery to a customer.

Of course, in the old days some manufacturers used to fit slave batteries on the production line that accompanied the vehicles to the dealers. Dealer would swap out battery for a new one and return slaves back to manufacturer for recharging and refitting to subsequent cars. Transport mode seams like a much cheaper solution.
 
Tried everything to get this damn software runn8ng, Rhiengold, Edbias and another but cannot get nowt to talk to the flipping car. Anyone near Warwick or Swindon or anywhere between that can help ?
 
I brought this when I brought the software.

https://www.ebay.co.uk/itm/BMW-OBD2-INPA-EDIABAS-Interface-NSC-DIS-SSS-USB-Cable/262977612059?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649
 
Nelly Welly said:
Tried everything to get this damn software runn8ng, Rhiengold, Edbias and another but cannot get nowt to talk to the flipping car.
Can you post your obd.ini and ediabas.ini?
 
OBD.ini

[OBD]
Port=Com3
Hardware=USB
RETRY=ON
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xF0000000
;Tracelevel=0x0000FFFF
; Bit 0 = Funktionsaufruf
; Bit 1 = io Ergebnis
; Bit 2 = nio Ergebnis
; Bit 3 = Detailinfos
; Nibble 0 = readchar_wait
; Nibble 1 = main
; Nibble 2 = cmd
; Nibble 3 = obd
; Nibble 4 = send_and_receive_...
; Nibble 5 = read_telegram_...
; Nibble 6 = send_telegram
; Nibble 7 = SendData


[UNIT_A]
Port=Com2
Hardware=OBD

[UNIT_B]
Port=Com3
Hardware=OBD

[UNIT_C]
Port=Com4
Hardware=OBD

[UNIT_D]
Port=Com5
Hardware=OBD

[UNIT_E]
Port=Com6
Hardware=OBD

[UNIT_F]
Port=Com7
Hardware=OBD

[UNIT_G]
Port=Com8
Hardware=OBD

[UNIT_H]
Port=Com9
Hardware=OBD

[UNIT_I]
Port=Com10
Hardware=OBD

[UNIT_J]
Port=Com11
Hardware=OBD

[UNIT_K]
Port=Com12
Hardware=OBD

[UNIT_L]
Port=Com13
Hardware=OBD

[UNIT_M]
Port=Com14
Hardware=OBD

[UNIT_N]
Port=Com15
Hardware=OBD

[UNIT_O]
Port=Com16
Hardware=OBD
 
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
;=============================================================================
 
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)
 
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. :headbang:
 
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.
 
Back
Top Bottom