[user0086]

I have a setup with E-Sys and ISTA+, where I (normally) use an Enet cable for E-sys and an ICOM-1 for ISTA, but sometimes I use the ICOM-1 with E-Sys.


Everything works fine, however when I use ISTA+ on a car (Mini F56) to read and clear the fault memory, I cannot use E-Sys anymore. If I try to connect E-Sys with my Enet cable, it just does not find a ZGW and if I try to connect E-Sys via my ICOM it fails to connect. I tried both ICOM/Ethernet and ICOM/DCAN. I only work on Mini F56, but it happens on multiple cars.

When I wait 15 minutes or so I can connect again, but it is a pain if I try to code out bulb faults and need to check if I was successful.
Am I the only one with this issue, or is this a known issue? Is there a workaround, other than disconnecting the battery?

[Node]

Reason is simple. ZGW needs and IP address. And if you have DHCP (or router) when you connect ICOM the address assigned is from your local subnet, when you connect cable directly (nothing to do with E-Sys, just with how you connect cable!!!) ZGW does not find DHCP so defaults to automatic private address. After deciding on IP address ZGW does not look for another address for some time (hence after 15 minutes it works again). Same effect is possible on a computer side as well.

So you either need to connect E-Sys via router too or connect ICOM directly AND use DHCP server on your computer. Or some other combination which will ensure same subnet in both cases.

[user0086]

It sounds plausible that it has something to do with the IP address of the ZGW. However, my PC has a static IP in the APIPA range (169.254.1.2) and I am not running any DHCP server. I don't have WiFi on my ICOM, I just connect it to the same Ethernet port as I would connect the Enet cable. So normally, when I connect with E-Sys I already connect to the APIPA address of the ZGW and my ICOM always has an APIPA address as well.

So apparently either ICOM is running DHCP or ISTA is setting the IP address of the ZGW. Do you have any idea in what range this IP-address lies, so that I can add it to my interface as work-around?

[Node]

I do not use such crappy setup with static address in APIPA range so I don't know. You can't properly flash F+ series in that case anyway. If I remember correctly from the old times - when ICOM is set to static IP it uses internal DHCP server to assign address to ZGW. If its set to DHCP then it passes through DHCP requests to external DHCP server. So I suggest you clean your own mess with config

[Matthew53]

Use this ICOM configuration for dhcp server software (www.dhcpserver.de/cms) or router (May not work with I series Intel processors – require external DHCP server e.g. hardware router)


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