[Spirit5676]

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.

That clears it up quite a bit. I was wondering why there was gateway set since the traffic won't leave the subnet as you said. I was also wondering why people were saying to set the DHCP on ICOM and laptop. I prefer static IP's on use like this. So the ROUTER_0 in DHCPSRV.INI isn't needed either. That makes sense to me. Thank you.

[mislavto]

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 have one, maybe stupid question
Once we set up connection with router like you described, which connection type should we use in esys (e.g., Connection via gateway, via ICOM, via VIN, etc.). Should it be via ICOM with IP: 192.168.68.85:50160?

[wademan]

I had the same issue. You need to connect your Icom Next through a router and your laptop. In your router type your laptop IP address and save it. Without a router you cannot update Kombi or HU-H with Icom next connect direct. I can walk you through it if you are having problems.


Does anyone else have issues when updating an I level on a F (F22 specifically) ?
NBT and KOMBI always fail. I'm using an ICOM to connect to the car.
I can flash them fine with E-Sys.
If I'm doing something wrong I would love to know

[Fatalix]

Have got issues updating on MOST after latest firmware update.

Router dhcp is set to 192.168.0.1 sub 255.255.0.0 with pool from 1-199, icom to dhcp will set to 192.168.0.150.
Used to work fine for programming on most, but now doesnt work any longer. Anyone knows what the issue might be?