Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]

Programming KOMBI and NBT fails on F series
01-12-2017, 06:56 AM,
Post: #151
RE: Programming KOMBI and NBT fails on F series
I found this in your log:

Subnet mask does not match with subnet mask of master gateway.

... and..

Subnetmask of ECU(HU_NBT2, 0x63) is 255.255.0.0 [ParallelTask-3]

Subnet Mask of Master-Gateway (read from ECU)= 255.255.255.0 [ParallelTask-3]

Subnet masks of FEM-GW and NBT EVO do not match.
Quote this message in a reply
[+] 2 users say Thank You to BimmerSLO for this post
04-12-2017, 23:37 PM,
Post: #152
XZBMW  RE: Programming KOMBI and NBT fails on F series
I use icom w router and use latest istap off line does not need wan connection but does not hurt if it does and loader 6.3 BB has fix for crash so use don't end up reinstalling istap
Quote this message in a reply
08-12-2017, 03:29 AM, (This post was last modified: 08-12-2017, 04:38 AM by abuqutaita.)
Post: #153
RE: Programming KOMBI and NBT fails on F series
Thanks for the tip of using a router instead of a direct connection. I was able to program NBT and KOMBI successfully using ISTA and an ICOM NEXT.

FWIW, I didn’t have to do any of the config steps mentioned in this thread on my laptop, router, or ICOM. By default, my ICOM is configured using a static IP address (169.254.11.92), and it wasn’t assigned one by the router’s DHCP server. And my laptop is configured to use DHCP by default as well.
Quote this message in a reply
09-12-2017, 23:38 PM,
Post: #154
RE: Programming KOMBI and NBT fails on F series
(01-12-2017, 06:56 AM)BimmerSLO Wrote:  I found this in your log:

Subnet mask does not match with subnet mask of master gateway.

... and..

Subnetmask of ECU(HU_NBT2, 0x63) is 255.255.0.0 [ParallelTask-3]

Subnet Mask of Master-Gateway (read from ECU)= 255.255.255.0 [ParallelTask-3]

Subnet masks of FEM-GW and NBT EVO do not match.

Thanks, It seems your router setup works perfectly. My problem was a loose wiregavel
Quote this message in a reply
27-09-2018, 21:36 PM,
Post: #155
RE: Programming KOMBI and NBT fails on F series
Do we still need DHCP server to program NBT and Kombi with Ista+ 4.3.14 when using ICOM A2?
Quote this message in a reply
27-09-2018, 23:40 PM,
Post: #156
RE: Programming KOMBI and NBT fails on F series
(27-09-2018, 21:36 PM)Spirit5676 Wrote:  Do we still need DHCP server to program NBT and Kombi with Ista+ 4.3.14 when using ICOM A2?

Yes
Quote this message in a reply
28-10-2018, 23:02 PM,
Post: #157
RE: Programming KOMBI and NBT fails on F series
(27-06-2016, 01:19 AM)jaramillo Wrote:  Hi everyone,

I want to share my configuration that worked flawless:

First of all the ICOM should be configured this way:

ICOM Config

ConnectionMode = STATIC_IP
Ip = 192.168.68.85
Netmask = 255.255.255.0
Gateway = 192.168.68.99

DHCPSRV.INI

[SETTINGS]
IPPOOL_1=192.168.68.1-254
IPBIND_1=192.168.68.99
AssociateBindsToPools=1
Trace=1
DeleteOnRelease=0
ExpiredLeaseTimeout=3600

[GENERAL]
LEASETIME=86400
NODETYPE=8
SUBNETMASK=255.255.255.0
NEXTSERVER=192.168.68.99
ROUTER_0=192.168.68.1

[DNS-SETTINGS]
EnableDNS=0

[TFTP-SETTINGS]
EnableTFTP=0
ROOT=C:\Users\Osx\Desktop\DHCP\wwwroot
WritePermission=0

[HTTP-SETTINGS]
EnableHTTP=0
ROOT=C:\Users\Osx\Desktop\DHCP\wwwroot
[00-01-A9-00-EE-E9]
IPADDR=192.168.68.1
AutoConfig=06/26/2016 12:41:32
Hostname=ICOM1120134
LeaseEnd=1467070189

Windows Ethernet config:

"Use the following IP Address"
IP 192.168.68.99
Subnet mask 255.255.255.0


Hope this help

I don't understand why you got ICOM with static IP 192.168.68.85 and with DHCP 192.168.68.1 IP? So ICOM with static IP or DHCP? Can't be both. The static IP will take presidence. Since the ICOM address is 192.168.68.85 why is the ROUTER_0=192.168.68.1 (that would be IP for ICOM from DHCP, but since the ICOM got static IP it won't use DHCP IP)?
Quote this message in a reply
29-10-2018, 03:07 AM,
Post: #158
RE: Programming KOMBI and NBT fails on F series
(28-10-2018, 23:02 PM)Spirit5676 Wrote:  
(27-06-2016, 01:19 AM)jaramillo Wrote:  Hi everyone,

I want to share my configuration that worked flawless:

First of all the ICOM should be configured this way:

ICOM Config

ConnectionMode = STATIC_IP
Ip = 192.168.68.85
Netmask = 255.255.255.0
Gateway = 192.168.68.99

DHCPSRV.INI

[SETTINGS]
IPPOOL_1=192.168.68.1-254
IPBIND_1=192.168.68.99
AssociateBindsToPools=1
Trace=1
DeleteOnRelease=0
ExpiredLeaseTimeout=3600

[GENERAL]
LEASETIME=86400
NODETYPE=8
SUBNETMASK=255.255.255.0
NEXTSERVER=192.168.68.99
ROUTER_0=192.168.68.1

[DNS-SETTINGS]
EnableDNS=0

[TFTP-SETTINGS]
EnableTFTP=0
ROOT=C:\Users\Osx\Desktop\DHCP\wwwroot
WritePermission=0

[HTTP-SETTINGS]
EnableHTTP=0
ROOT=C:\Users\Osx\Desktop\DHCP\wwwroot
[00-01-A9-00-EE-E9]
IPADDR=192.168.68.1
AutoConfig=06/26/2016 12:41:32
Hostname=ICOM1120134
LeaseEnd=1467070189

Windows Ethernet config:

"Use the following IP Address"
IP 192.168.68.99
Subnet mask 255.255.255.0


Hope this help

I don't understand why you got ICOM with static IP 192.168.68.85 and with DHCP 192.168.68.1 IP? So ICOM with static IP or DHCP? Can't be both. The static IP will take presidence. Since the ICOM address is 192.168.68.85 why is the ROUTER_0=192.168.68.1 (that would be IP for ICOM from DHCP, but since the ICOM got static IP it won't use DHCP IP)?

Hello,

Im not a tech expert, but the config has worked for a while without issues
Have you tried to work with the config?
Quote this message in a reply
29-10-2018, 09:41 AM,
Post: #159
RE: Programming KOMBI and NBT fails on F series
(29-10-2018, 03:07 AM)jaramillo Wrote:  
(28-10-2018, 23:02 PM)Spirit5676 Wrote:  
(27-06-2016, 01:19 AM)jaramillo Wrote:  Hi everyone,

I want to share my configuration that worked flawless:

First of all the ICOM should be configured this way:

ICOM Config

ConnectionMode = STATIC_IP
Ip = 192.168.68.85
Netmask = 255.255.255.0
Gateway = 192.168.68.99

DHCPSRV.INI

[SETTINGS]
IPPOOL_1=192.168.68.1-254
IPBIND_1=192.168.68.99
AssociateBindsToPools=1
Trace=1
DeleteOnRelease=0
ExpiredLeaseTimeout=3600

[GENERAL]
LEASETIME=86400
NODETYPE=8
SUBNETMASK=255.255.255.0
NEXTSERVER=192.168.68.99
ROUTER_0=192.168.68.1

[DNS-SETTINGS]
EnableDNS=0

[TFTP-SETTINGS]
EnableTFTP=0
ROOT=C:\Users\Osx\Desktop\DHCP\wwwroot
WritePermission=0

[HTTP-SETTINGS]
EnableHTTP=0
ROOT=C:\Users\Osx\Desktop\DHCP\wwwroot
[00-01-A9-00-EE-E9]
IPADDR=192.168.68.1
AutoConfig=06/26/2016 12:41:32
Hostname=ICOM1120134
LeaseEnd=1467070189

Windows Ethernet config:

"Use the following IP Address"
IP 192.168.68.99
Subnet mask 255.255.255.0


Hope this help

I don't understand why you got ICOM with static IP 192.168.68.85 and with DHCP 192.168.68.1 IP? So ICOM with static IP or DHCP? Can't be both. The static IP will take presidence. Since the ICOM address is 192.168.68.85 why is the ROUTER_0=192.168.68.1 (that would be IP for ICOM from DHCP, but since the ICOM got static IP it won't use DHCP IP)?

Hello,

Im not a tech expert, but the config has worked for a while without issues
Have you tried to work with the config?

Well I'm an IT tech, so those thing didn't look right to me. I assume we need the DHCP for control modules in the car not the laptop/ICOM itself. Laptop/ICOM won't be restarting during the update, so there is no need for them to get new IP's. Modules of the car will be restarting so I assume they need to get new IP's during update.

Would be nice to get a technical document that got some real information on what actually happens during update, so it would be easier to understand the best way to config system. I haven't tried that config, because I don't like to use something that doesn't seem right. I'm not trying to be a smart ass here, I just want to understand what is the best practice to avoid any issues with update.
Quote this message in a reply
30-10-2018, 17:25 PM,
Post: #160
RE: Programming KOMBI and NBT fails on F series
(29-10-2018, 09:41 AM)Spirit5676 Wrote:  Well I'm an IT tech, so those thing didn't look right to me. I assume we need the DHCP for control modules in the car not the laptop/ICOM itself. Laptop/ICOM won't be restarting during the update, so there is no need for them to get new IP's. Modules of the car will be restarting so I assume they need to get new IP's during update.

Would be nice to get a technical document that got some real information on what actually happens during update, so it would be easier to understand the best way to config system. I haven't tried that config, because I don't like to use something that doesn't seem right. I'm not trying to be a smart ass here, I just want to understand what is the best practice to avoid any issues with update.

Actually the gateway setting on ICOM is not required, as the traffic won't leave from the subnet.
All we need are, static IP on ICOM, static IP on computer, a hard or soft dhcpd in the subnet.
When the NBT boot up / restart, it will obtain IP for itself for communication; and the KOMBI with MOST fibre connection to NBT, will treat NBT as their gateway. So if NBT cannot get IP, KOMBI will be update fail too.
Quote this message in a reply
[+] 1 user says Thank You to simonchs for this post


Possibly Related Threads…
Thread Author Replies Views Last Post
  How to code hands free driver assistant (G-series) btvaleks 21 5,645 14-05-2024, 07:27 AM
Last Post: btvaleks
XZBMW using Inpa for f series hero3838 1 157 07-05-2024, 04:26 AM
Last Post: Stratofortress
  F25 5AS,8th and 5AC coding with 6wb kombi simplextibi 1 92 04-05-2024, 06:37 AM
Last Post: Stratofortress
  dissable RDC on G series ? xMoses 6 261 02-05-2024, 08:48 AM
Last Post: Node
  BMW F40 (1 series) no FZD module Ibrahim24 5 200 01-05-2024, 19:27 PM
Last Post: Siki78
XZBMW G12 used Kombi 35128WT palapas1974 14 597 29-04-2024, 17:54 PM
Last Post: johann74270
XZBMW E60 M5 KOMBI cruise control bmwfnatic 4 201 29-04-2024, 09:51 AM
Last Post: bmwfnatic
XZBMW Difference 677 vs. 688 F series ? AlpinWeiss2k18 8 478 16-04-2024, 19:55 PM
Last Post: sebastianfernandes
  Making F-series combox work in e-series Ryn079 5 654 11-04-2024, 15:03 PM
Last Post: wrp_199
XZBMW Lost Navigation - aircon wont turn off 2016 BMW 2 series DannyDans435 6 300 08-04-2024, 08:45 AM
Last Post: painsage

Forum Jump:


Users browsing this thread:
3 Guest(s)

Return to TopReturn to Content