[maxwarmer]

Originally Posted by ir655

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

I use a thunderbolt ethernet adapter because I concet from my mac with bootcamp, any sugestion?

I try and put ediabas.ini interface=enet, and Obd.ini try in com1, com2, com3, com4, com5, always the same error, net 0012, no connection.

Any comment?

[daviiiiid]

Hi guys im new to this forum, im looking for information on how to update the idrive on my 1 series and 4 series after carrying out oil and filter changes on both.

Any help would be much appreciated.

[JRF30]

Hi is there anyone in bristol or surrounding that could possibly update mine? Thanks

[Vodiebaz]

How do I change my ediabas ini

[Sasquartch]

Originally Posted by Vodiebaz

How do I change my ediabas ini

Just edit using Notepad or similar

[Tobi2211]

Originally Posted by Sasquartch

Unfortunately I couldn't get it to connect, just get

28: IFH-0018 INITIALIZATION ERROR

I'm thinking I have a problem with my C:\EDIABAS\BIN\EDIABAS.INI file, I suspect my connection type is wrong

Would you be able to share your settings please ?

The same laptop and cable connects to esys fine so the hardware side of things should be OK

Hey guys!
I have the same problem: I get the HU Service Manager running but I get the error message: Initialization Error.
When I change the ediabas.ini file from Stb: OBD to ENET -> IFH-00027: IFH not found.
Connection with Rh***go** works like a charm tho...
Can someone please help me? I’m also willing to reward you for that

[Superdaws]

Can anyone please provide me some advise on getting HU Service Manager to connect... x64 Win 10.

Connecting to 2016 F15 X5 with NBT HU.
ISTA+ and Esys connect and work fine.
in HU Service Manager i get the Net-0012 error NO CONNECTION, im guessing its a EDIABAS ini setting, but i just cant solve it.

Ive done a clean install of Standard Tools 2.12, and used Ediabas Konfigurator 2.0 with Ediabas 7.3.0.

I can see the connection ok both in the network connection (IP address assigns ok with car) and with ZGW Search i can see the Remotehost.

Ive disabled all other network connections + firewall + Antivirus.

Ive tried with XEthernet setting as autodetect and also entered the remotehost IP from ZGW search in ediabas.ini and it always result in NO CONNECTION. Interface is set as ENET. Heres the relevant section of my ediabas.ini:

;================================================= ============================
[TCP]
;================================================= ============================
RemoteHost = LMUC203404
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

[Superdaws]

Ok, solved my own problem, but for the benefit of anyone else with similar issues:

The problem revolved around the car IP address. I had tried manually entering the IP address from ZGW Search in the XEthernet variable of ediabas.ini after autodetect would not work.

When I played with it more and connected the dots as my ISTA+ and Esys was working, just not Ediabas connection; I found the cars IP address being used to connect in ISTA+ and manually entered that in XEthernet and then HU Service Manager would connect. I was then able to update service details on the car.

Seems ZGW Search was throwing a different car IP address...

[Sasquartch]

Originally Posted by Superdaws

Ok, solved my own problem, but for the benefit of anyone else with similar issues:

The problem revolved around the car IP address. I had tried manually entering the IP address from ZGW Search in the XEthernet variable of ediabas.ini after autodetect would not work.

When I played with it more and connected the dots as my ISTA+ and Esys was working, just not Ediabas connection; I found the cars IP address being used to connect in ISTA+ and manually entered that in XEthernet and then HU Service Manager would connect. I was then able to update service details on the car.

Seems ZGW Search was throwing a different car IP address...

I did not have to do this

The cable relies on auto-configuration working, ie if an address is not assigned by a DHCP/BOOTP server (which it wont if the cable is just connecting a laptop to the car) and an IP address starting 169. should get assigned

If you hard code a 169. address you may find that this address will change

It might be that you have a static address assigned to your ethernet port on the laptop

Usually you have to wait 30secs or more after connecting the laptop and turning on the car for auto configuration to do it's thing

Out of interest what was the IP address you put in ?

[Superdaws]

Originally Posted by Sasquartch

I did not have to do this

The cable relies on auto-configuration working, ie if an address is not assigned by a DHCP/BOOTP server (which it wont if the cable is just connecting a laptop to the car) and an IP address starting 169. should get assigned

If you hard code a 169. address you may find that this address will change

It might be that you have a static address assigned to your ethernet port on the laptop

Usually you have to wait 30secs or more after connecting the laptop and turning on the car for auto configuration to do it's thing

Out of interest what was the IP address you put in ?

Yes i agree that is the way it should happen. The notebook is definitely set to automatic IP assignment by DHCP, and it correctly assigns the IP address to the PC of 169.254.xx.xxx can’t remember exactly. I think it may be a network specific problem as it is a new notebook with Killer networking Ethernet. Everything I’ve read says the cars IP address will remain the same when autonegatiating with and individual PC (not router). The manual entry I used for the car IP in XEthernet is 169.254.44.xx

I think my problem arises by not running a DHCP server on the notebook, I was just using a direct connection, but it worked that way. What program are you using to create a DHCP server on Win10?

[Sasquartch]

I don't use a DHCP server

I'm relying on auto configuration working (which is where the 169. address comes from) which seems to work fine for me.

Maybe it's some sort of power saving feature or something like that on your new laptop (my laptop is about 8 years old)

[2020shaun]

hi
fingers crossed some one can help , ive just downloaded hu service manager and unzipped it but i have no idea how to install it
i have ista+ installed already
any advice please

thanks in advance

[Sasquartch]

There is no installer so some IT knowledge is required

Here are the notes I made for someone :

To Install

Simply copy the EDIABAS and BMW-HU-ServiceManager folders to the root of C:\
Create a shortcut to HU-ServiceManager.bat on the desktop and (optionally) rename
as desired, also the icon can be used for the shortcut

The EDIABAS.INI file must have the correct interface specified. To use the E-Sys
cable (Ethernet) this should be set to ENET

As long as EDIABAS is under D:\ then run ediabas konfigurator2.0.0.exe to change, use the second
ENET entry in the pulldown, otherwise just use notepad to edit the ediabas.ini

If using another drive, eg D:\ edit ediabas.ini to update the first three references to C:\ to D:\ and update
the .bat file to set the correct path

If you search my threads you will find all you need

[BO££RZA]

Hi guys,

Could someone please help me out with this.

I have everything working and I was able to connect HU Service Manger to my F20 with Entry-HU through ENET cable, but when I write to HU, the iDrive is not updating even after resetting it few times.

I look forward to any advice.

Thank you!

[thaking]

Is there any new solution that new entry is on the top od service history log and not at the bottom?

[Sasquartch]

Originally Posted by thaking

Is there any new solution that new entry is on the top od service history log and not at the bottom?

Not that I am aware of

The way it works means that the existing idrive entries are deleted, then the data from BMW's server is then uploaded in one go - this is what happens at a dealer once the new service details are uploaded to the central server

The HU ServiceManager just works around this. It's not the way HU works but the way the idrive works.

[thaking]

Hmm, then this make no sense to use it...

[gIzzE]

Originally Posted by thaking

Hmm, then this make no sense to use it...

You enter them all again.

[gIzzE]

I think it better to enter them all again so newest is on the bottom, then when you add anything it is in order still.

[mcraeCCS]

Hi guys,
F31 LCI 2016, ENET interface. INPA working good, of course EDIABAS.ini configured properly with ENET interface set. On HU Service Manager I still get the "92: SYS-0002: ECU OBJECT FILE NOT FOUND" error. Seems that some file required to connect to the HU unit misses, or it cannot be found.
IP get settled automatically, 169 apipa range.. and communication doesn't seem to be the issue, as other prg as INPA work fine, launching the EDIABAS with green light, etc.
ECU file path also configured correctly, i found the nbt.prg file inside. (also must mention that ecu path is configured to point to this folder inside ediabas.ini.)
So, does anybody have a clue, or managed to get over this?

Appreciate your help.
Cheers.

[cossie1]

Ok guys could do with some help to get this working.

I have INPA working for E46 / E92 series.

I have ISTA working for my F82

E-sys is also working fine for my F82.

But HU manager never connects.

I have all the files in the correct places.

I have tried editing the EDIABAS.INI to show Interface =ENET

I have tried using the car's IP instead of Autodetect.

But nothing seems to work, HU-Manager never connects.

[cossie1]

Anyone ?