[Matthew53]

I'll describe my situation.

Yesterday I successfully flashed NBT via HTTP using ENET with esys version 3.30. Today I wanted to flash the same unit with the same files, the same PC, the same ENET cable and the same bench setup and it throws an error:

"[] Activate programming mode was not successful for: ECUId:HU_NBT_0x63 [WARN]
[] ECUId:HU_NBT_0x63 not accessible cause could not be switched to parallel programming mode [WARN]"

Of course I can't deactivate programming mode for switchable ECUs, because it automatically switch to UDS and it take 1% every 10minutes for only one SWFL (read - forever).

The same fault on 3.27 version and when using ICOM with DHCP-server.

So it looks a little like esys can throw a fault randomly, but it sound crazy I know. However I can't find other explanation for now.

If anyone has a clue about the fault I get, I would be grateful.

Post screenshots of your settings in ESYS options>settings>connections and also under TAL processing>parameters tab.

Here it is


EDIT: ok this is apparently NBT fault. I took another NBT and flash goes via HTTP with same settings with esys 3.30. But how is that possible that NBT could be flashed yesterday without any problems and today it throws a fault about activating programming mode.

Thats what my settings look like. ALL other mudules flashed over UDS even with my settings being like yours except NBT for some reason went through HTTP.

Could be bug in esys or faulty NBT as you say I dont know. Have you tried flashing with newer version of esys? Also I made sure AV was off and all firewalls off.

I tried several times with higher esys version like 3.34 and never succeed to flash NBT via HTTP. However it's the thing when you flash on bench. 

When I flashed EVO in car, it goes via HTTP with esys 3.34 (I guess that presence of other modules in car allowed for EVO to be flashed with esys 3.34 via HTTP, not sure about that)

On the bench it's best to use 3.30 or 3.27/28, however in my case it's apparently corrupted NBT.

I've got no AV and firewall is off all the time.

[BlueMeetsWhite]

So eSys and ISTA are both Java applications.  They undoubtedly use shared classes....

Is eSys open source?  I know some of the components it uses are.

ISTA is NOT Java application in itself. It's a .NET application. For flashing however, it starts psdzdatahost application which IS java.

Of course not.

Thanks for the info.

I notice there are two version of Java in the application directory:

D:\EC-APPS\ISTA\OpenJREx64
D:\EC-APPS\ISTA\OpenJREx86

From the log files, I can see that the 64-bit version is being used on my system.

Is there any way to force it to use the 32-bit version?

[Matthew53]

I solved the problem. It was ETH_A broken inside and I didn't notice it. When I checked cable for continuity I found that there is no connection. I replaced the wire and it's flashing via HTTP in 30 minutes. If anyone would like to check if there is ethernet connection from HU to ZGW, open _DEV_UDS.prg and check status "zgw_ethernet_status". If it's ok, then flashing with esys 3.30 will be done via HTTP.