[xxiFear]

Thats why i dont want to use uds protocol.
I dont have any antyvirus installed and firewall was disabled. That pc are not connected to internet 
But i try diferent machine too...

How long flashing nbt goes throu uds protocol?

Last time I did over UDS it took me like 9-8 hours for NBT. You can Flash one by one and delete successful ones from TAL before continuing.

[tokarszczak]

NBT EVO flashes 3 Days with uds, nbt about 12 hours. Install esys 3.27 without launcher, use tal generated in newer esys, make path for newest psdzdata that you use with esys. In my case dhcp router with esys 3.33 wont work, it flashed succesfull with 3.27 and dhcp router and newest psdzdata. Did it 2 weekes ago but at this solution spent about 10 hours to Flash it correctly.

[lustek]

Hi,

Problem partially solved. swDeploy flash OK.
I don't know what actualy do the job but:

- last night delete all faults in ISTA ( after that I don't try flashing nbt)
- leve car without negativ battery terminal all night
- download one more time nevest sdp from different source
- use esys 3.27.1
- use nevest sdp
- use different pc
- use enet cable

Flash took aboute 25 minutes. NBT alive and working. Don't know why it do it so fast, esys show aboute 1 hour.

But now I can't do cdDeploy. I get error like when I set wrong shipment i-level:
SVK-ist does not match expected SGBMIDs....

[DayvG]

So CDDeploy is just loading CAFD. So rather than using TAL, just do it in coding. Select the ECU and detect CAFD, choose newest and VO code. If it doesn’t work play around with your FA until you have the right options. You can also use coding verification to effectively test your FA against the SVT tree. It’s a great tool, especially for EVO retrofits.

[danyro]

most probably your old sdp data was corrupted that's why i've advised you to change it.
if there was something with the esys, then bootloader would have failed too..

[lustek]

I forgot aboute injecting cafd. after that, even cdDeploy go OK.

I think problem is in ESYS 3.33.0 and 3.33.1.
I install 3.33.1 on PC in with I flash nbt and try to do ibaDeploy. Ended with HTTP error.
I revert to 3.27.1 and go OK.

Bootloader flashed OK in 3.33.0 becouse it use UDS protocol.
Software and iba goes throw HTTP.

Thank you everybody involved in this thread.
If you are in Poland, write PM...I buy drinks all the night

[danyro]

Bootloader flashed OK in 3.33.0 becouse it use UDS protocol.

You are wrong...i was like in the same situation like you and bootloader was done via UDS and it took ~2h to be completed.

UDS protocol is not capable of more than ~21 kB/s while your bootloader update  finished in few minutes. so esys used http protocol otherwise you have been wait a lot longer.

[lustek]

Bootloader flashed OK in 3.33.0 becouse it use UDS protocol.

You are wrong...i was like in the same situation like you and bootloader was done via UDS and it took ~2h to be completed.

UDS protocol is not capable of more than ~21 kB/s while your bootloader update  finished in few minutes. so esys used http protocol otherwise you have been wait a lot longer.

I dont save log but i think it goes throu uds....but i can see wrong

[tokarszczak]

Bootloader flashed OK in 3.33.0 becouse it use UDS protocol.

You are wrong...i was like in the same situation like you and bootloader was done via UDS and it took ~2h to be completed.

UDS protocol is not capable of more than ~21 kB/s while your bootloader update  finished in few minutes. so esys used http protocol otherwise you have been wait a lot longer.

Bootloader going thru UDS.

[danyro]

and is UDS capable of ~70Mbps without http?
maybe i am wrong but from my past experience, bootloader went to UDS and it took ~1,5-2h at ~21kB/s