Quote:
|
Originally Posted by terahertz
I used Windows 10 in VMware on Windows 10. No issues.
|
That's more radical than my setup! So you had to purchase two Win10 licenses
why not run Esys on your native Win10 host? I am at this stage a bit hesitant to proceed with more flashing without discovering the root cause of the issue, I just did another test now. I've connected Esys, and during reading coding data I switched off the ignition and presto the same "Timeout P2/T2" error... as during my Phase 2 Flash session.
So now its confirmed even further that either the ignition went Off or loss of connectivity during the TAL execution cdDeploy phase!
Code:
NCD read from ECU "ECUId:KOMBI_0x60" for CAF "cafd_000009c8-006_003_053" failed! [C069]
negative response error:
code: TIMEOUT P2/T2 occurred
description: P2 timeout on Service RDBI_PLAIN has error in result: [Severity=2051][ErrorCode=58640][ErrorCodeDescription=resource not available][VendorCode=2142][VendorCodeDescription=P2 timeout occured]; ECU: KOMBI_60_ETHERNET
severity: ERROR