[gvitkis]

I have a question not realted to your problem. I have f10 with EVO retrfoitted and I don't know how should I connect it with ZGW? My car is 2015 and I want to wire OABR to ZGW but I have no idea where they should go, do you have some wiring diagram? Thanks.

Page 9 my friend
http://carsystems.com.ua/uploads/pdf/CAN..._Rev_6.pdf

---

Hi guys,
I'm trying to update my EVO B210 HW 3.1 with esys 3.31 and the last PSZ with test bench with ZGW 02_8SK
For flash I used ENET and ICOM with DHCP and without, I can not understand why esys starts the flash only in UDS mode.
EVO is connected correctly with ETH from the small ZGW connector, towards OABR.
I have also tested the PC network card and it seems that it works, no problem for the coding and for the internet connection via LAN.
I hope the experts can help me
Thanks so much

Can you ping NBT?
If so then wiring is good, if not, then wiring is not good that's why it goes over UDS cause it can't use ethernet

If you can ping NBT but still going through UDS, then edit your TAL file, search for PROTOCOL (Prefered_Protocol) and change all values to HTTP.

If you have flashed Bootloader already using UDS, then leave it alone, don't flash it again. Only do SWFLASH and IBA, just those 2.
CDDeploy (Encoding) can be done after flash manually by doing CODE, make sure you use correct FA with matching VIN.

bmwcoder75 thank you very much for your help.
From tool32, I read IP of EVO which is 169.254.199.99 and subnet 255.255.0.0
I run PING from cmd and this is the answer:
C: \ Users \ SERVICE_BMW> ping 169.254.199.99

Running Ping 169.254.199.99 with 32 bytes of data:
Reply from 169.254.199.99: byte = 32 duration = 1ms TTL = 255
Reply from 169.254.199.99: byte = 32 duration <1ms TTL = 255
Reply from 169.254.199.99: byte = 32 duration <1ms TTL = 255
Reply from 169.254.199.99: byte = 32 duration <1ms TTL = 255

Ping Statistics for 169.254.199.99:
     Packages: Transmitted = 4, Received = 4,
     Lost = 0 (0% lost),
Approximate time round trip routes in millisecond
     Minimum = 0ms, Maximum = 1ms, Middle = 0ms

also imposed preferred protocol in HTTP, but esys keeps flashing via UDS.
I can not figure out how to solve