F30POST
F30POST
2012-2015 BMW 3-Series and 4-Series Forum
BMW Garage BMW Meets Register Search Today's Posts Mark Forums Read
BMW 3-Series and 4-Series Forum (F30 / F32) | F30POST > Technical Forums > F30 DIYs and Coding Discussions > Updating idrive history with HU-ServiceManager
GetBMWParts
Post Reply
 
Thread Tools Search this Thread
      10-31-2018, 10:39 AM   #45
ir655
New Member
Sweden
0
Rep
9
Posts

Drives: F31 320d and F11 530d
Join Date: Sep 2018
Location: Sweden

iTrader: (0)

Quote:
Originally Posted by Sasquartch View Post
Is your ediabas.ini file definitely correct, ie set to ethernet (ENET) ?
I think it was set to OBD and I changed it to ENET.

When I changed it to ENET that the little icon on the right hand lower taskbar for Ediabas was Red. I tried connecting to HU and had a different error message.

I switched it back to OBD and the icon turned Green and I get the current fault message that i posted earlier.

Worth to mention is that I am using a USB to Ethernet adapter since my laptop does not have a real Ethernet port. Latency is set to 1 and COM1 is set for the adapter. Anyway, feels like if something was wrong with that I wouldnt have been able to do functions with ISTA-D and ESYS.

Anyway, I will update tomorrow night after trying different settings with the Ediabas.ini file.
Appreciate 0
      11-01-2018, 04:13 AM   #46
Sasquartch
Major
398
Rep
1,211
Posts

Drives: 520i G30
Join Date: Aug 2016
Location: Herts

iTrader: (0)

COM port settings are irrelevant

As long as the USB ethernet port functions correctly it should be OK but disable any firewalls in case these are preventing a connection

Make sure there are no other ethernet interfaces in use

When you connect the car it usually takes a few (20-ish) seconds for the PC to auto configure

Use the ipconfig command to check you have a 169. IP address.

Please post up any solution you find for the benefit of others.
Appreciate 0
      11-11-2018, 08:55 AM   #47
Cetar
New Member
3
Rep
18
Posts

Drives: BMW F20 116i 2014 AT
Join Date: Feb 2017
Location: Czech Republic

iTrader: (0)

Hi BMW fans,

some remarks i found out today:
The structure of the Service history record is as follows:
A;0xB;C;D;
Where A is type of the record (1= engine oil); B is if it was late; C = how late in KM; D how late in months.
So for example:
1;0x"not sure about the number";0;2; means Engine oil changed 2 months late.
You can found the exact number for "late" record when you change "Service carried out" to carried out late.

Cheers


Last edited by Cetar; 11-11-2018 at 08:57 AM.. Reason: added image
Appreciate 0
      11-12-2018, 04:03 AM   #48
cedchung
First Lieutenant
Mauritius
24
Rep
397
Posts

Drives: 2011 F25, 2014 F30
Join Date: May 2005
Location: Mauritius

iTrader: (1)

What is this error code?
92: SYS-0002: ECU OBJECT FILE NOT FOUND
Appreciate 0
      01-15-2019, 06:36 AM   #49
ir655
New Member
Sweden
0
Rep
9
Posts

Drives: F31 320d and F11 530d
Join Date: Sep 2018
Location: Sweden

iTrader: (0)

Quote:
Originally Posted by Sasquartch View Post
COM port settings are irrelevant

As long as the USB ethernet port functions correctly it should be OK but disable any firewalls in case these are preventing a connection

Make sure there are no other ethernet interfaces in use

When you connect the car it usually takes a few (20-ish) seconds for the PC to auto configure

Use the ipconfig command to check you have a 169. IP address.

Please post up any solution you find for the benefit of others.
Hi! Been a while I was at this, but now needing this to work to enter some service that I have done myself.

In Ediabas.ini I set the interface to OBD and even tried ENET still no Go.

Com port settings is COM3 with latency to 1 and 1.

OBD.ini file matched COM port setting of COM3.

in Ediabas.ini I read that I have to change the remote host section to: 192.168.68.1 from original 192.168.68.40

Port is 6801.

Today I got a different message when trying to connect to HU:

IFH-0018 INITIALIZATION ERROR

I have the required .prg files in Ediabas/ECU folder (Not all from Rheingold, just those relevant to the different HU's).

New tips and tricks pleeeease
Appreciate 0
      01-17-2019, 03:27 PM   #50
ir655
New Member
Sweden
0
Rep
9
Posts

Drives: F31 320d and F11 530d
Join Date: Sep 2018
Location: Sweden

iTrader: (0)

Just noticed I have 2 different EDIABAS folders...

One located in C:\Ediabas

And one in my Rheingold folder (Rheingold\Ediabas)

Should there be 2? The EDIABAS.ini file in the Rheingold\Ediabas\bin folder refers to C:\Ediabas for certain lines.

Is this supposed to be like this or?
Appreciate 0
      01-19-2019, 06:49 AM   #51
ir655
New Member
Sweden
0
Rep
9
Posts

Drives: F31 320d and F11 530d
Join Date: Sep 2018
Location: Sweden

iTrader: (0)

Just to update: Got it working now!

Reinstalled Ediabas etc using Standard BMW Tools pack and downloaded Ediabas configurator to config the ediabas.ini

HU Service manager connects to car and I am able to write service. I managed to delete all the service history already in there, but took pics before I did anything so I can enter those again 😊
Appreciate 0
      01-22-2019, 01:35 AM   #52
Chris_330
New Member
9
Rep
18
Posts

Drives: F31 330d Msport
Join Date: Jan 2017
Location: Yorkshire

iTrader: (0)

can anyone give me a link to download this please?
Appreciate 0
      01-22-2019, 03:36 AM   #53
Sasquartch
Major
398
Rep
1,211
Posts

Drives: 520i G30
Join Date: Aug 2016
Location: Herts

iTrader: (0)

Just google "hu service manager download"

Its all there if you look
Appreciate 0
      01-22-2019, 01:36 PM   #54
neo61uk
Second Lieutenant
neo61uk's Avatar
United Kingdom
76
Rep
247
Posts

Drives: F31 340i Performance Edition
Join Date: Feb 2014
Location: Bristol

iTrader: (0)

Quote:
Originally Posted by ir655 View Post
Just to update: Got it working now!

Reinstalled Ediabas etc using Standard BMW Tools pack and downloaded Ediabas configurator to config the ediabas.ini

HU Service manager connects to car and I am able to write service. I managed to delete all the service history already in there, but took pics before I did anything so I can enter those again 😊
Hi there

Reading your posts I'm trying to get mine to work.
I have esys and coded my cars many times no problem.

Installed HU-SERVICEMANAGER and had initialization error.
So edited ediabas.ini file from obd to esys and it went to different error saying Cannot Connect

I've checked my Ediabas/ecu files and there is no nbt.prg files or anything similar.

Could you tell me where to take all those ediabas/ecu files needed for nbt connection?
Also what else should be changed in ediabas.ini file to make sure its right?
Should I just edit it or use ini editor?

Can't find any instructions online at all.

Many thanks for all the help.
Appreciate 0
      02-13-2019, 12:22 PM   #55
coskunhc
New Member
0
Rep
11
Posts

Drives: BMW 118D
Join Date: Jun 2018
Location: Danmark

iTrader: (0)

Service menu disappeared

Hi all,

I hope there still are someone in this thread. I've done everything as written in the comments and got a connection to my NBT. I have a BMW F20 2014 with NBT Prof.

So normally my service history was visible in the idrive menu, and I wanted to add a manual listing as well, because I've just did a service on my car with oil change and so on. But after I did everything with HU ServiceManager, some how my service history disappeared from my iDrive menu.

And I noticed that you need to change the date format manually to MONTH;DAY;YEAR instead of MONTH-DAY-YEAR, but that didn't change anything either.

So guys/girls, what am I doing wrong?
Attached Images
  
Appreciate 0
      03-11-2019, 11:00 AM   #56
F30.FAN
New Member
0
Rep
26
Posts

Drives: F30
Join Date: Feb 2018
Location: Montenegro

iTrader: (0)

Same thing for my nbt?Did you solved the problem?
Appreciate 0
      05-05-2019, 10:46 AM   #57
alex-xs
New Member
3
Rep
14
Posts

Drives: BMW f31, BMW f25
Join Date: May 2019
Location: Amsterdam

iTrader: (0)

I have also a F31 NBT, and I am afraid to test the software, dont want to delete the service history.
The software is working and I got connection with the car...
did any of you solved the deleted service history issue.
Appreciate 0
      05-08-2019, 04:17 AM   #58
RoopD
Private
0
Rep
85
Posts

Drives: F30 Alpine Weiss
Join Date: Apr 2018
Location: Netherlands

iTrader: (0)

Will this put for my bmw f30 everything in KM?
and everything on 'OK' after I update HU?

Last edited by RoopD; 05-08-2019 at 04:22 AM..
Appreciate 0
      05-25-2019, 08:27 PM   #59
Bobbyjee
New Member
0
Rep
22
Posts

Drives: BMW F10
Join Date: Aug 2018
Location: London

iTrader: (0)

Thanks Sasquartch
Your instructions on enet worked a treat.

Managed to get the connection. Just need to input all the values
Appreciate 0
      06-04-2019, 04:05 AM   #60
ir655
New Member
Sweden
0
Rep
9
Posts

Drives: F31 320d and F11 530d
Join Date: Sep 2018
Location: Sweden

iTrader: (0)

Make sure you take pics of service history before beginning. Service history will disappear because you will make an error in the input format when entering the date of service.

Once you choose date the last thing you need to do is change the - between the date numbers to ; in the long string of mumbo-jumbo in the top left corner. Then press Write to HU. Make sure the date is in dd;mm;yyyy;
Appreciate 0
      06-04-2019, 04:10 AM   #61
ir655
New Member
Sweden
0
Rep
9
Posts

Drives: F31 320d and F11 530d
Join Date: Sep 2018
Location: Sweden

iTrader: (0)

Quote:
Originally Posted by neo61uk View Post
Hi there

Reading your posts I'm trying to get mine to work.
I have esys and coded my cars many times no problem.

Installed HU-SERVICEMANAGER and had initialization error.
So edited ediabas.ini file from obd to esys and it went to different error saying Cannot Connect

I've checked my Ediabas/ecu files and there is no nbt.prg files or anything similar.

Could you tell me where to take all those ediabas/ecu files needed for nbt connection?
Also what else should be changed in ediabas.ini file to make sure its right?
Should I just edit it or use ini editor?

Can't find any instructions online at all.

Many thanks for all the help.
prg files are found in Rheingold/ecu map. If you have ISTA-D installed you will find the required prg files in the folder i mentioned above.

Change the ediabas.ini and obd.ini files with wordpad.
Appreciate 0
      06-04-2019, 06:35 AM   #62
maxwarmer
New Member
0
Rep
24
Posts

Drives: M4 F82
Join Date: Apr 2018
Location: Barcelona

iTrader: (0)

Hello
I need help. I installed HU-ServiceManager when I try to connect to HU. The error appears: 28: IFH-0018: INITIALIZATION OF ERRORS
Can someone guide me?
I am using EDIABAS 7.3.0
I am using JAVA 1.8.0_144
I have ISTA + and it works
I have esys and it works
I use the ENET cable

I put the archibo ediabas.ini in:
Interface = ENET and I get error NET 0012 NO CONNECTION, I put it in Interface = STD: OBD and I get error IFH: 0018 INITIALIZATION ERROR.

I have all the PRG and DLL files in the ECU folder.

Any solution?
Appreciate 0
      06-04-2019, 06:37 AM   #63
maxwarmer
New Member
0
Rep
24
Posts

Drives: M4 F82
Join Date: Apr 2018
Location: Barcelona

iTrader: (0)

Quote:
Originally Posted by ir655 View Post
prg files are found in Rheingold/ecu map. If you have ISTA-D installed you will find the required prg files in the folder i mentioned above.

Change the ediabas.ini and obd.ini files with wordpad.
In OBD.ini file which line you suggest to change? please comment this, thanks a lot.
Appreciate 0
      06-04-2019, 06:51 AM   #64
maxwarmer
New Member
0
Rep
24
Posts

Drives: M4 F82
Join Date: Apr 2018
Location: Barcelona

iTrader: (0)

My EDIABAS.INI

;#################
;# EDIABAS 7.3.0 #
;#################

;================================================= ============================
[Configuration]
;================================================= ============================
Interface =STD:OBD
Simulation = 0

EcuPath = C:\EDIABAS\ECU
SimulationPath = C:\EDIABAS\SIM
TracePath = C:\EDIABAS\TRACE
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:\EC-Apps\EDIABAS\BIN\ansi2oem.tab
; LoadWin32 = 0

NetworkProtocol = TCP

; --- neu ab EDIABAS 7.2.0 ---------------------------------------------------
ShowIcon = 1
LogLevel = 0
TraceBuffering = 0
TraceHistory = 0
TraceSync = 1
; TraceWriter = <FilePathName>

;================================================= ============================
[TCP]
;================================================= ============================
RemoteHost = IP_VON_ENTFERNTEM_PC
Port = 3000
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


;################################################# ############################
;################################################# ############################
;## ausf¸hrliche Variante von EDIABAS.ini (mit Kurz-Info und Default) ##
;################################################# ############################
;################################################# ############################

;================================================= ============================
; EDIABAS Basic Configuration
; [Configuration]
;================================================= ============================

;### new Configuration elements since EDIABAS 7.2 ############################

;-----------------------------------------------------------------------------
; ShowIcon
; Description : Enable/Disable EDIABAS-Icon in System-Tray
; Value : 0 = EDIABAS-Icon disabled
; 1 = EDIABAS-Icon enabled
; Default = 1
; ShowIcon = 1

;-----------------------------------------------------------------------------
; LogLevel
; Description : Logging of fatal faults in EDIABAS.log
; Value : 0 = Logging disabled
; 1 = Logging enabled
; Default = 0
; LogLevel = 0

;-----------------------------------------------------------------------------
; TraceBuffering
; Description : Manner of Opening/Closing of Trace-Files
; Value : 0 = Opening/Closing after every dump
; 1 = Trace-Files stay open
; Default = 0
; TraceBuffering = 0

;-----------------------------------------------------------------------------
; TraceHistory
; Description : Number of History-Trace-Files
; Value : 0 .. 999
; Default = 0
; TraceHistory = 0

;-----------------------------------------------------------------------------
; TraceSync
; Description : Synchronisation of Trace files
; Value : 0 = Synchronisation disabled
; 1 = Synchronisation enabled
; Default = 1
; TraceSync = 1

;-----------------------------------------------------------------------------
; TraceWriter
; Description : FilePathName of a private TraceWriter
; Default = . (Default-TraceWriter "TWFile32.dll")
; TraceWriter = .


;### older Configuration elements till EDIABAS 7.1 ###########################

;-----------------------------------------------------------------------------
; Simulation
; Description : Enable/Disable ECU simulation
; Value : 0 = Simulation disabled
; 1 = Simulation enabled
; Default = 0
; Simulation = 0

;-----------------------------------------------------------------------------
; EcuPath
; Description : ECU file path
; Default = .
; EcuPath = C:\EC-Apps\EDIABAS\ECU

;-----------------------------------------------------------------------------
; SimulationPath
; Description : Simulation file path
; Default = .
; SimulationPath = C:\EC-Apps\EDIABAS\SIM

;-----------------------------------------------------------------------------
; TracePath
; Description : Trace file path
; Default = .
; TracePath = C:\EC-Apps\EDIABAS\TRACE

;-----------------------------------------------------------------------------
; TraceSize
; Description : Maximum size of each trace file [KB]
; Value : 0 .. 32767
; Default = 1024
; TraceSize = 1024

;-----------------------------------------------------------------------------
; ApiTrace
; Description : Enable/Disable API/User trace
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + time stamp
; 3 = User trace + time stamp + process id (Win32)
; 4 = Function trace
; 5 = Function trace + time stamp
; 6 = Function trace + time stamp + timing
; 7 = Function trace + time stamp + timing + process id (Win32)
; 8 = Debug trace
; Default = 0
; ApiTrace = 0

;-----------------------------------------------------------------------------
; IfhTrace
; Description : Enable/Disable IFH trace
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + interface
; 3 = User trace + interface + time stamp
; Default = 0
; IfhTrace = 0

;-----------------------------------------------------------------------------
; IfhnTrace
; Description : Enable/Disable IFH network trace (with XREMOTE)
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + interface
; 3 = User trace + interface + time stamp
; Default = 0
; IfhnTrace = 0

;-----------------------------------------------------------------------------
; SystemTraceSys
; Description : Enable/Disable system trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1 .. 7
; Default = 0
; SystemTraceSys = 0

;-----------------------------------------------------------------------------
; SystemTraceBip
; Description : Enable/Disable BIP trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1 .. 7
; Default = 0
; SystemTraceBip = 0

;-----------------------------------------------------------------------------
; SystemTraceIfh
; Description : Enable/Disable IFH system trace
; Value : 0 = Trace disabled
; Trace levels 1 .. 7
; Default = 0
; SystemTraceIfh = 0

;-----------------------------------------------------------------------------
; SystemTraceNet
; Description : Enable/Disable network trace
; Value : 0 = Trace disabled
; Trace levels 1 .. 7
; Default = 0
; SystemTraceNet = 0

;-----------------------------------------------------------------------------
; BipDebugLevel
; Description : BIP debug level of ECU files
; Value : 0 .. 32767
; Default = 0
; BipDebugLevel = 0

;-----------------------------------------------------------------------------
; BipErrorLevel
; Description : BIP error level of ECU files
; Value : 0 .. 32767
; Default = 0
; BipErrorLevel = 0

;-----------------------------------------------------------------------------
; UbattHandling
; Description : Ubatt ON/OFF handling
; Value : 0 = Ubatt ON/OFF: No EDIABAS error
; 1 = Ubatt ON/OFF: EDIABAS error
; Default = 1
; UbattHandling = 0

;-----------------------------------------------------------------------------
; IgnitionHandling
; Description : Ignition ON/OFF handling
; Value : 0 = Ignition ON/OFF: No EDIABAS error
; 1 = Ignition ON/OFF: EDIABAS error
; Default = 1
; IgnitionHandling = 0

;-----------------------------------------------------------------------------
; ClampHandling
; Description : automatic check of clamps for Ubatt and Ignition
; Value : 0 = no automatic clamp check with send_and_receive
; 1 = automatic clamp check with send_and_receive
; Default = 1
; ClampHandling = 1

;-----------------------------------------------------------------------------
; RetryComm
; Description : Repeat failed communication automatically (1x)
; Value : 0 = Retry disabled
; 1 = Retry enabled (1x)
; Default = 1
; RetryComm = 1

;-----------------------------------------------------------------------------
; SystemResults
; Description : Enable/Disable system results (ubatt/ignition/jobstatus)
; Value : 0 = Disable system results
; 1 = Enable system results
; Default = 1
; SystemResults = 1

;-----------------------------------------------------------------------------
; TaskPriority
; Description : EDIABAS process/thread priority (only Win32/16)
; Value : 0 = Optimal EDIABAS performance = 8
; 1 = Minimal EDIABAS performance
; ..
; 10 = Maximal EDIABAS performance
; Default = 0
; TaskPriority = 0

;-----------------------------------------------------------------------------
; CodeMapping
; Description : Character mapping file path
; Default = .
; CodeMapping = C:\EC-Apps\EDIABAS\BIN\ansi2oem.tab

;-----------------------------------------------------------------------------
; LoadWin32
; Description : Map EDIABAS Win16 calls to EDIABAS Win32
; Value : 0 = Win16/32 Mapping disabled (Win16-->Win16)
; 1 = Win16/32 Mapping enabled (Win16-->Win32)
; Default = 0 for Windows 9x/Me
; Default = 1 for Windows NT4/2000/XP
; LoadWin32 = 0

;-----------------------------------------------------------------------------
; NetworkProtocol
; Description : Network protocol
; Default =
; NetworkProtocol = TCP

;************************************************* ****************************
; Interface
; Description : Connected diagnosis interface
; Default = EDIC
; Interface = STD:FUNK

; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!

;................................................. ............................
; Interface = STD:FUNK
; Beschreibung : Funk-Diagnose Interface MDA von Fa. Siemens
; Installation : keine
; INI-Datei : FUNK.INI
; Ansprechpartner: Manuel.Rothenberger@bmw.de
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = STD:OMITEC
; Beschreibung : Nachfolger von OBD / enth‰lt CAN-Anbindung / Anschluss an OBD-Dose
; Installation : \EDIABAS\HARDWARE\OMITEC\AnleitungfuerOMITECInstal lation.pdf
; INI-Datei : siehe \EDIABAS\HARDWARE\OMITEC\Omitec_Doku.pdf
; Ansprechpartner: Reinhold.Drexel@bmw.de
; WINDOWS-Freig. : siehe \EDIABAS\HARDWARE\OMITEC\Omitec_Doku.pdf

;................................................. ............................
; Interface = STD:OBD
; Beschreibung : Serieller Pegelwandler (Nachfolger von ADS / Anschluss an OBD-Dose)
; Installation : \EDIABAS\HARDWARE\OBD\ODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
; INI-Datei : siehe \EDIABAS\HARDWARE\OBD\OBD_DOKU.pdf
; Ansprechpartner: Reinhold.Drexel@bmw.de
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = EDIC
; Beschreibung : Anbindung ¸ber K-Line
; HW-Derivate : PC-Card, PCMCIA , W-LAN (Interface von Fa. Softing)
; Installation : \EDIABAS\HARDWARE\EDIC\SETUP.EXE
; INI-Datei : EDICFW.INI, EDICHW.INI
; Ansprechpartner
; * EDIC-PC : Gerd.Huber@bmw.de
; * PCMCIA : Gerd.Huber@bmw.de
; * EDIC-NET : (Richard.Kolbeck@bmw.de)
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = EDICC
; Beschreibung : Anbindung ¸ber K-Line
; HW-Derivate : PC-Card, PCMCIA , W-LAN (Interface von Fa. Softing)
; Installation : \EDIABAS\HARDWARE\EDIC\SETUP.EXE
; INI-Datei : EDICFW.INI, EDICHW.INI, XEDICC.INI
; Ansprechpartner
; * EDIC-PC : Gerd.Huber@bmw.de
; * PCMCIA : Gerd.Huber@bmw.de
; * EDIC-NET : (Richard.Kolbeck@bmw.de)
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = STD:CAN
; Beschreibung : PCMCIA CAN-Interface CanCardX von Fa. Vector
; Installation : keine (ausser Installation der CAN-Karte)
; INI-Datei : CAN32.INI
; Ansprechpartner: FLASH.SERVICE@BMW.DE (Hotline)
; WINDOWS-Freig. : !nicht mehr im Paket enthalten!

;................................................. ............................
; Interface = REMOTE
; Beschreibung : Anbindung eines EDIABAS-Interfaces ¸ber TCP/IP (f¸r Normalbetrieb)
; Installation : Anpassung der Eintr‰ge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : keine
; Ansprechpartner
; * Remote-PC : Gerd.Huber@bmw.de => Referenz@bmw.de
; * OP(P)S : Michael.Rowedder@bmw.de
; * ICOM,Fertig. : ! keine Verwendung !
; * ICOM,Vertrieb: Robert.Schwinn@bmw.de
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = REMOTE:name
; Beschreibung : Anbindung eines EDIABAS-Interfaces ¸ber TCP/IP (f¸r Parallelbetrieb)
; Installation : Anpassung der Eintr‰ge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : REMOTE.INI (insbesondere f¸r Parallelbetrieb notwendig)
; In REMOTE.INI stehen unter [name] spezif. Einstellungen(z.B.: RemoteHost, Port).
; Ansprechpartner
; * Remote-PC : ! momentan keine Verwendung !
; * OP(P)S : Michael.Rowedder@bmw.de
; * ICOM,Fertig. : ! keine Verwendung !
; * ICOM,Vertrieb: Robert.Schwinn@bmw.de
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = RPLUS
; Beschreibung : Anbindung eines EDIABAS-Interfaces ¸ber TCP/IP (f¸r PROXY-Betrieb)
; Installation : Anpassung der Eintr‰ge in [TCP] auf beiden Seiten (insb.: RemoteHost, Port)
; INI-Datei : keine
; Ansprechpartner
; * Remote-PC : ! keine Verwendung !
; * OP(P)S : ! momentan keine Verwendung !
; * ICOM,Fertig. : Manuel.Rothenberger@bmw.de
; * ICOM,Vertrieb: ! momentan keine Verwendung !
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = RPLUS:name (z.B.:RPLUS:ICOM_P)
; Beschreibung : Anbindung des EDIABAS-Interfaces ICOM ¸ber TCP/IP
; Installation : Anpassung der Eintr‰ge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port) in den INI-Dateien
; INI-Datei : RPLUS.INI (Nutzung im Zusammenhang mit dem Interface ICOM)
; In RPLUS.INI stehen unter [name] spezif. Einstellungen(z.B.: RemoteHost, Port).
; Ansprechpartner
; * Remote-PC : ! keine Verwendung !
; * OP(P)S : ! momentan keine Verwendung !
; * ICOM,Fertig. : Manuel.Rothenberger@bmw.de
; * ICOM,Vertrieb: ! momentan keine Verwendung !
; WINDOWS-Freig. : WIN NT 4.0 : Ja
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;................................................. ............................
; Interface = ENET
; Beschreibung : Anbindung ¸ber Ethernet
; Installation : Anpassung der Eintr‰ge in [XEthernet] (insb.: RemoteHost)
; INI-Datei : ENET.INI (insbesondere f¸r Parallelbetrieb notwendig)
; Ansprechpartner: Gerd.Huber@bmw.de => Referenz@bmw.de
; WINDOWS-Freig. : WIN NT 4.0 : Nein
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja
; WIN 7 64-Bit : Ja

;................................................. ............................
; Interface = PROXY:<Interface>
; z.B. Interface = PROXY:STD:FUNK
; z.B. Interface = PROXY:ENET
;
; Beschreibung : EDIABAS wird im PROXY-Modus betrieben
; Installation : h‰ngt vom benutzten Interface ab
; INI-Datei : h‰ngt vom benutzten Interface ab
; Ansprechparter : Gerd.Huber@bmw.de => Referenz@bmw.de
; WINDOWS-Freig. : WIN NT 4.0 : Nein
; WIN XP 32-Bit : Ja
; WIN 7 32-Bit : Ja

;************************************************* ****************************
; Konfigurationslemente, die existieren,
; aber nicht in EDIABAS.ini ge‰ndert werden kˆnnen

;-----------------------------------------------------------------------------
; BipEcuFile
; Description : Dateititel der aktuell geladenen SGBD
; (nur g¸ltig w‰hrend einer Job-Verarbeitung)
; Value : String
; Default = -

;-----------------------------------------------------------------------------
; EdiabasIniPath
; Description : Pfad der verwendeten EDIABAS.ini
; Value : String
; Default = -

;-----------------------------------------------------------------------------
; EdiabasVersion
; Description : verwendete EDIABAS-Version
; Value : String
; Default = -

;-----------------------------------------------------------------------------
; IfhVersion
; Description : verwendete IFH-Version
; Value : String
; Default = -

;-----------------------------------------------------------------------------
; Session
; Description : Name der EDIABAS-Session
; Value : String
; Default = -


;================================================= ============================
; TCP/IP Configuration
; [TCP]
;================================================= ============================

;-----------------------------------------------------------------------------
; RemoteHost
; Description : server address/name
; Default = -
; RemoteHost = LMUC203404

;-----------------------------------------------------------------------------
; Port
; Description : IP communication port
; Value : 1000 < port < 30000
;
; Spezialfall OP(P)S / ICOM:
; Value : 6801 ;OBD-Treiber (CAN)
; Value : 6802 ;Most-Treiber
;
; Default = -
; Port = 3000
;
; weitere Details siehe Dokumentationen

;-----------------------------------------------------------------------------
; TimeoutConnect
; Description : Timeout for establishing the connection
; Value : 1000 ... 59000
; Default = 5000
; TimeoutConnect = 2000

;-----------------------------------------------------------------------------
; TimeoutReceive
; Description : Timeout for receiving a message
; Value : 1000 ... 59000
; Default = 5000
; TimeoutReceive = 2000

;-----------------------------------------------------------------------------
; TimeoutFunction
; Description : Timeout for a long function
; Value : 5000 ... 59000
; Default = 59000
; TimeoutFunction = 10000

;-----------------------------------------------------------------------------
; TimeResponsePending
; Description : Time between alive-messages
; Value : 500 ... 59000
; Default = 2000
; TimeResponsePending = 5000

;-----------------------------------------------------------------------------
; DisconnectOnApiEnd
; Description : Enable/Disable Disconnection with function call ApiEnd
; Value : 0 = Disconnection disabled
; 1 = Disconnection enabled
; Default = 0
; DisconnectOnApiEnd = 1

;-----------------------------------------------------------------------------
; InitCmd<n>
; Description : Initialization command <n> (normally for OPPS)
; Default =
; InitCmd0 = FE,04,00,03,01
; InitCmd1 = FD,05,00,03,01


;================================================= ============================
; XETHERNET Configuration
; [XEthernet]
;================================================= ============================

;-----------------------------------------------------------------------------
; RemoteHost
; Description : server address/name
; Value : Autodetect
; 169.254.1.1 ; Beispiel
; 192.168.100.1 ; Beispiel
; Default =
; RemoteHost = Autodetect

;-----------------------------------------------------------------------------
; IfhRemoteHost
; Description : server address/name
; Value : Autodetect
; 169.254.1.1 ; Beispiel
; 192.168.100.1 ; Beispiel
; Default =
; IfhRemoteHost = Autodetect

;-----------------------------------------------------------------------------
; HeaderFormat
; Description : type of header
; Value : 0 ; 6Byte Header (B-Muster)
; 1 ; 3Byte Header (A-Muster)
; Default = 0
; HeaderFormat = 0

;-----------------------------------------------------------------------------
; TesterAddress
; Description : list of permitted tester adresses
; Value : F4 ; F1 durch F4 ersetzen
; F5 ; F1 durch F5 ersetzen
; F4,F5 ; F1 zuerst durch F4 ersetzen, dann F1 durch F5 ersetzen
; F5,F4 ; F1 zuerst durch F5 ersetzen, dann F1 durch F4 ersetzen
; Default = -
; TesterAddress = F4,F5

;-----------------------------------------------------------------------------
; ControlPort
; Description : port of control channel of TCP connection to ZGW
; Value : 1000 < port < 59000
; Default = 6811
; ControlPort = 6811

;-----------------------------------------------------------------------------
; DiagnosticPort
; Description : port of diagnostic channel of TCP connection to ZGW
; Value : 1000 < port < 59000
; Default = 6801
; DiagnosticPort = 6801

;-----------------------------------------------------------------------------
; TimeoutConnect
; Description : timeout in ms for connection to ZGW
; Value : 1000 ... 59000
; Default = 20000
; TimeoutConnect = 20000


;================================================= ============================
; XPROXY Configuration
; [IfhProxy]
;================================================= ============================

;-----------------------------------------------------------------------------
; Port
; Description : IP base proxy port
; Value : 1000 < port < 30000
; Ports : +0 = unknown interface
; +1 = EDIC
; +2 = EDICC
; +3 = ENET
; +4 = STD
; +5 = REMOT
; Default = 6700
; Port = 6700


;================================================= ============================
; End Of File EDIABAS.ini
;================================================= ============================


Chequed and no work.
Appreciate 0
      06-04-2019, 06:52 AM   #65
maxwarmer
New Member
0
Rep
24
Posts

Drives: M4 F82
Join Date: Apr 2018
Location: Barcelona

iTrader: (0)

OBD.INI, use this configuration and no work.

[OBD]
Port=Com1
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
Appreciate 0
      06-04-2019, 01:49 PM   #66
ir655
New Member
Sweden
0
Rep
9
Posts

Drives: F31 320d and F11 530d
Join Date: Sep 2018
Location: Sweden

iTrader: (0)

Quote:
Originally Posted by maxwarmer View Post
In OBD.ini file which line you suggest to change? please comment this, thanks a lot.

If you are using ENET cable then in Ediabas.ini you need to change "Interface=ENET"

In Obd.ini the "port=comx" should correspond with the same com port that you have selected as default under Device Manager "Ports and LPT" tab. Mine is set as Com3 so my obd.ini file says "port=com3"

Not sure if "Hardware=USB" or if it should say "Hardware=OBD". Mine is set to the latter in Obd.ini
Appreciate 0
Post Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -5. The time now is 03:47 AM.




f30post
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.
1Addicts.com, BIMMERPOST.com, E90Post.com, F30Post.com, M3Post.com, ZPost.com, 5Post.com, 6Post.com, 7Post.com, XBimmers.com logo and trademark are properties of BIMMERPOST