Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Very slow EVO flashing
13-03-2018, 21:18 PM,
Post: #11
|
|||
|
|||
RE: Very slow EVO flashing
I can not understand why ESYS starts Flash always on UDS protocol.
The TAL is calculated with FA of X3 07/06, because I remember that it should be native ZGW_02, so as not to cause problems, with my test bench which is installed ZGW_02_8sk I tried the FLASH 2 times, changing the preferred protocol to TAL_EDITOR, with KWP2000 and HTTP but not working. I hope you help me solve this mystery. Thanks so much. |
|||
13-03-2018, 21:24 PM,
Post: #12
|
|||
|
|||
RE: Very slow EVO flashing
How do you connect on bench? I would use enet without DHCP. Most times BTLD is flashed over UDS. And try pinging your zgw to see if you have stable connection. You did the nbt ping? Also had one unit with same issue no way to flash over HTTP, never found the issue but unit still works. You experience same issues with other NBT? Faulty network adapter can also be an issue what I have faced once.
|
|||
13-03-2018, 22:28 PM,
Post: #13
|
|||
|
|||
RE: Very slow EVO flashing
(13-03-2018, 21:24 PM)larshutten Wrote: How do you connect on bench? I would use enet without DHCP. Most times BTLD is flashed over UDS. And try pinging your zgw to see if you have stable connection. You did the nbt ping? Also had one unit with same issue no way to flash over HTTP, never found the issue but unit still works. You experience same issues with other NBT? Faulty network adapter can also be an issue what I have faced once. larshuttenin hank you very much for your support, I try to answer your questions. I connect to my bench via OBD, in fact this thing has already happened to me with other EVO HW3.1 without GPS connector, For the flash I used ENET and ICOM with DHCP and without BTLD is definitely FLASH on UDS because up to 15% takes more than 20 minutes (but I interrupt) PC network card, it seems that it works, no problem for encryption and for internet connection via LAN. now the unit is in FLASH mode with the fan at maximum, because I have interrupted the FLASH twice. I also pinged EVO with this CMD response 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 |
|||
14-03-2018, 06:48 AM,
Post: #14
|
|||
|
|||
RE: Very slow EVO flashing
I have flashed on table 10+ times EVO with different HW version and allways BTL go thru UDS but rest go thru http....
|
|||
14-03-2018, 07:38 AM,
Post: #15
|
|||
|
|||
RE: Very slow EVO flashing
You interrupted BTLD flash at 15%??
You do realise that by doing so you may have bricked your unit? You may not be able to flash that unit again. BTLD is the most crucial part of the flash. Usually when it fails on NBT you can kiss it goodbye Yes BTLD sometimes takes over 1h even though TAL is set to use HTTP, it will use UDS regardless. But Swl and Iba will go through HTTP. |
|||
14-03-2018, 07:43 AM,
Post: #16
|
|||
|
|||
RE: Very slow EVO flashing
You should check this option ENABLED for your EVO:
BMW tuning & retrofitting, https://www.instagram.com/cebepspb/
* lifetime EVO, ROUTE codes, Carplay, ECU Remap and other crap |
|||
21-01-2019, 19:01 PM,
Post: #17
|
|||
|
|||
RE: Very slow EVO flashing
anyone found a solution to this problem
I tired everything and still, e-sys is forcing the SWFL flashing via UDS protocol which is damn slow |
|||
18-02-2019, 12:08 PM,
(This post was last modified: 18-02-2019, 12:12 PM by rickynguyen.)
Post: #18
|
|||
|
|||
RE: Very slow EVO flashing
Evo flash with enet 50-60 mins to completed
|
|||
20-03-2019, 18:55 PM,
Post: #19
|
|||
|
|||
RE: Very slow EVO flashing
(12-03-2018, 12:26 PM)bmwcoder75 Wrote: 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. Hi, I am in the same situation. Can you clarify where in the TAL file is the protocol part? I don't see it in the TAL xml file. My NBT Evo HU (retrofit) is wired to my donor ATM through the OABR and using the same quadlock as the NBT. Everything is behind a can filter. |
|||
« Next Oldest | Next Newest »
|
Users browsing this thread:
2 Guest(s)
2 Guest(s)
Return to TopReturn to Content