[dracon]

BMW has officially released 4.01.22 today which is the official release for programming via ISTA.

[Qwerti]

Hi!

I tested yesterday, and is work fine. Why there are modules, after test on the control unit tree, that they are not built into the car. E.g EGS, DSP, NAV etc.

Sorry my bad english.

ISTA/D has been like this on a few models now, even though it has identified the car as a manual, it will still show unfitted ECUs like EGS in grey.

Green=good
Orange=fault
Red = Should be fitted but no communication
Grey = Possible ECU location in the diagnostic tree
Blue = ECU stuck in programming mode.

Can i switch off this function, like old version (3.47.10)?

[PhilipM]

I'm not sure, maybe one of these keys-

Code:

<add key="TesterGUI.EcuTree.ExpertMode" value="false" />
    <add key="TesterGUI.EcuTree.ECUTreeDrawBusLines" value="true" />
    <add key="TesterGUI.EcuTree.ECUTreeShowGridLines" value="false" />
    <add key="TesterGUI.EcuTree.ECUTreeShowCoordEditor" value="false" />
    <add key="TesterGUI.EcuTree.ECUTreeShowDuplicates" value="true" />
    <add key="TesterGUI.EcuTree.ECUShowVirtualBusECU" value="false" />
    <add key="TesterGUI.EcuTree.ECUShowNoneBusECU" value="false" />

[aboulfad]

Tested it again,ETH still don t work for programming and measurement plan .
...

I was wondering if you can share existing logs in order to help solve this aging issue of ISTA-D programming over ENET. I am doing this as a challenge and want to contribute to the CTUK community if I can.

I have been looking into traces and debugging in real time ISTA and it's getting darn too complex. Having other set of logs would greatly help especially that you have both devices (ENET cable and ICOM).

All that is required is just to connect using each method to the car, run the vehicle test and that's it. No need for a programming session as the error occurs after the vehicle test, during the "read current vehicle context". You can obsfucate any private details like VIN, ... and share the logs. It would be greatly appreciated. Cheers and TIA!

PS: your PM inbox is FULL!

[botho]

I was wondering if you can share existing logs in order to help solve this aging issue of ISTA-D programming over ENET. I am doing this as a challenge and want to contribute to the CTUK community if I can.

I have been looking into traces and debugging in real time ISTA and it's getting darn too complex. Having other set of logs would greatly help especially that you have both devices (ENET cable and ICOM).

All that is required is just to connect using each method to the car, run the vehicle test and that's it. No need for a programming session as the error occurs after the vehicle test, during the "read current vehicle context". You can obsfucate any private details like VIN, ... and share the logs. It would be greatly appreciated. Cheers and TIA!

PS: your PM inbox is FULL!

Would be great for those as you and me that only have ENET capabilities...
Perhaps, BB88 could you give some tips because i'm sure he already have this working

[aboulfad]

...
Would be great for those as you and me that only have ENET capabilities...
Perhaps, BB88 could you give some tips because i'm sure he already have this working

Actually, I mostly use Esys for my flashing needs. I have tough taken this as a challenge and I know some people would like to use ISTA-D for programming instead of Esys.

Bb88 said he didn't look into it in detail, but just in case he's reading, I made it to Tresult CallFunction(), and the socket error is thrown by the silly java psdz-api.j4n.jar , as to why, it is still a mystery. (I can't stand java...)

Code:

16-09-16 10:33:22,308 [Thread-16] [WARN] [] com.bmw.psdz.vehicle.base.topology.access.EthernetAccessLinkImpl: connection test failed. Attempt 1 of 3
java.net.ConnectException: Connection refused: connect�

[Loliceman]

Link seems to be broken. Here is a reupload if anyone is interested.