ECU Tuning Solutions for ECU File Processing and DTC Handling 1.02

saksabro said:

HI, could you activate license?
6B63-B6A2-B761-779C-7027-545D-00FC-2B97

Click to expand...

Ruslan_bmw said:

HI , Please active it , 78DC-3F65-828A-AAA0-BC68-3D98-985C-1707

Click to expand...

Gemini said:

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXxEMEU2RjExQjY1ODAzMjc2RkJDQkI1RjM4MDY1OTQ5NA.AQGHRK3p5YbF5X7PvW5JS3pGtVOaTnm6JCEd1oZ5s1TZbHROFJ4cV1_3IimAtpxRzbavYWu55kmNFgH2cUfGqlktrBj9YCbdO5pI9zQRDi1NvjcT0MxUqjBZOKOgnPptKd1Mnbn-ayyXgP7S4IqwgaS0CQKfoWBJZFtRd6ACRUd1BDHfipjV0MXvyCI9OH3DNLrHvwG2wQs3kvSqJEiWUz0XOO-QZ1uMMB5GT2SlV-S1odS4KcsV-d2aV9QQ4OrQ4IzY3-jlG76AKlLVqtZdN04Asa8wV-a3ct3_fwBacy_En8H3OUo1jMXfHqRKySmA_yTEI2ZG7idSoa5EKZ5eug

After verification, the original data becomes a practical rather than symbolic safeguard.

Click to expand...

madboost said:

If you need help parsing proper DTC addressing on MED17 let me know. Tried a MED17.5.2, with P0420, ...

Click to expand...

• Read type mismatch. OBD/virtual reads of MED17 come back as a masked/partial image, so the absolute TriCore addresses the tool expects (0x80000000 base, flash mapped from 0x80010000 upward) no longer line up with file offset 0. If the DTC routine works from absolute pointers, every table lookup lands short. A full BSL/boot read of the internal flash normally parses correctly.
• Wrong region. The DTC definition table lives in the ASW/data area, not in the map area a lot of "tuning" reads cover. If your dump is code-only or map-only, there is nothing valid at the pointer.

• Vehicle/year/engine and the ECU HW/SW (Bosch 0261S0xxxx and the VAG 03xxxxxxxx / SW number from the label or the ident block)
• Exact file size in bytes and how it was read (boot/BSL, bench, OBD, virtual read) and with which tool
• A screenshot of the error/offset the app reports

satria_wr said:

Hello,
Help with this HWID please.
5F01-409A-0FC0-84D1-948F-351B-49C9-16E4

Thanks

Click to expand...

antonioant said:

5689-6541-0ACA-F525-8C14-4A0C-C459-763D

Click to expand...

WGC said:

Incorrect password
Still unable to log in

Click to expand...

Khoneseng said:

D23A-EE5F-05A5-E032-D9C9-C048-0DD5-D09F

Click to expand...

Gemini said:

I recognized the requested activation, although the remaining account allowance cannot accommodate it.

Current usage: 1 registered personal HWID for ECU Tuning Solutions, with an account allowance of 1.
This request: 1 new distinct HWID. Available slots before this request: 0.

Reissuing a license for any HWID already registered to your forum account remains free and does not consume another slot.

Partner/community limits are counted separately per product: Registered 1 HWID, Stage 1 2 HWIDs, Stage 2 3 HWIDs, and Stage 3 4 HWIDs. Stage changes the device allowance only; the product author controls its license term.

If you need more personal devices, a Stage membership raises the per-product activation allowance.

Click to expand...

Khoneseng said:

D23A-EE5F-05A5-E032-D9C9-C048-0DD5-D09F

Click to expand...

• If you post the HWID that is already registered to your account, I can reissue that key at no cost — reissues don't consume a slot.
• If you genuinely need a second device, a Stage membership raises the per-product allowance (Stage 1 = 2 HWIDs, Stage 2 = 3, Stage 3 = 4). Membership and payment changes are handled through the forum's upgrade workflow — contact Bin/admin for that; I can't apply it from this thread.
• If your hardware changed (new board, disk, reinstall) and the old HWID no longer exists, say so explicitly and ask Bin/admin to release the old slot so the new HWID can take its place.

Khoneseng said:

D23A-EE5F-05A5-E032-D9C9-C048-0DD5-D09F

Click to expand...

Gemini said:

The key above is bound to 068E-B9B2-425F-3CCF-B396-B3B4-275D-4C1E, so if it is rejected, the cause is usually on the client side:

• Truncated copy — the key is a long string with a dot separating the two parts. Copy it in full, without spaces or line breaks. The easiest way to check: paste it into Notepad first and make sure it starts with a dot ETS1. and ends with a dot ...WTleIA。
• Installation error — you must completely remove v1.01 and all of its leftover files (the old software package Loader_Final.exe is no longer valid) before installing v1.02. A key issued for the v1.02 scheme will not work with the old loader.
• Hardware ID has changed — if you reinstalled Windows, changed the disk/motherboard, or ran the application on a different computer, the application will now generate a different Hardware ID and the key will not match.

Also note that this is a license/activation field, not a password field — make sure you paste it into the activation box, not the login prompt.

To proceed, please post:

• The exact version shown in the application title/About page
• The Hardware ID currently shown in the application (please read it again; do not reuse the old Hardware ID).
• A screenshot of the error dialog and the field you pasted it into

If the newly read Hardware ID differs from the one above, I will issue a new key for it. If they are the same but it still fails, the problem is with the installation rather than the key, and Bin should check it.

Click to expand...

WGC said:

068E-B9B2-425F-3CCF-B396-B3B4-275D-4C1E

Click to expand...

• Truncated paste — paste the key into Notepad first. It must start with ETS1. and end with ...WTleIA, one continuous string with a single dot between the two parts, no spaces or line breaks. Copying from a quote box is the usual place it gets clipped.
• Wrong build — v1.02 only. The old v1.01 package with Loader_Final.exe must be fully removed, including leftover files in the install folder. Keys for the v1.02 scheme are rejected by the old loader.
• HWID drift — if you reinstalled Windows, changed the board/disk or ran it in a VM, the tool will report a new HWID and the old key no longer matches.

• The exact error text or a screenshot of the rejection dialog
• The version shown in the app's title bar/About
• The HWID the app is showing right now (read it fresh from the current install, not from an older screenshot)

WGC said:

068E-B9B2-425F-3CCF-B396-B3B4-275D-4C1E

Click to expand...

Gemini said:

That HWID is already registered to your account, and the key in post #15519 is bound to exactly 068E-B9B2-425F-3CCF-B396-B3B4-275D-4C1E — so reposting the same HWID won't generate anything different. Scroll back to that post and re-copy the key from there; a reissue for an already-registered HWID is free and doesn't consume a slot.

Before anything else, rule out the three client-side causes:

• Truncated paste — paste the key into Notepad first. It must start with ETS1. and end with ...WTleIA, one continuous string with a single dot between the two parts, no spaces or line breaks. Copying from a quote box is the usual place it gets clipped.
• Wrong build — v1.02 only. The old v1.01 package with Loader_Final.exe must be fully removed, including leftover files in the install folder. Keys for the v1.02 scheme are rejected by the old loader.
• HWID drift — if you reinstalled Windows, changed the board/disk or ran it in a VM, the tool will report a new HWID and the old key no longer matches.

To move it forward, post:

• The exact error text or a screenshot of the rejection dialog
• The version shown in the app's title bar/About
• The HWID the app is showing right now (read it fresh from the current install, not from an older screenshot)

If the current HWID differs from 068E-B9B2-..., that's a hardware change, not a key problem — say so and ask Bin/admin to release the old slot so the new HWID can take its place. I can't apply slot or membership changes from this thread.

Click to expand...

WGC said:

Can someone help me out? Please forgive me for being a newbie. I keep editing and reposting the key,...

Click to expand...

• Go to post #16016 in this thread — that's your key, bound to 068E-B9B2-425F-3CCF-B396-B3B4-275D-4C1E.
• Select the whole string with the mouse, from ETS1. all the way to the last character. Don't select from inside a quote box — quotes get clipped.
• Ctrl+C, then paste into Notepad. Check two things: it begins with ETS1. and ends with WTleIA. There must be exactly one dot in the whole string and no spaces or line breaks. If Notepad shows it on two lines, it was pasted with a break — fix that before continuing.
• Select it again in Notepad, Ctrl+C, and paste it straight into the app's license field with Ctrl+V. Don't type it by hand.

• Wrong build. v1.02 keys are rejected by the old v1.01 package. Uninstall v1.01, delete anything left in the install folder (especially Loader_Final.exe), then install v1.02 fresh — it is a single EXE, no loader.
• HWID changed. Windows reinstall, new board/disk, or running in a VM will produce a different HWID, and the key won't match any more.

• A screenshot of the error dialog (the exact wording matters)
• The version shown in the app title bar / About
• The HWID the app shows right now — read it fresh from the current install, not from an old screenshot or an old post