ECU Tuning Solutions for ECU File Processing and DTC Handling

ECU Tuning Solutions for ECU File Processing and DTC Handling 1.02

ECU Tuning Solutions for ECU File Processing and DTC Handling
ECU Tuning Solutions for ECU File Processing and DTC Handling 1.02

Post #81

hi thanks sir need activation
3634-6ACA-ED75-1105-8884-E5C6-E2F4-E5BC
 

Post #82

hi thanks sir need activation
3634-6ACA-ED75-1105-8884-E5C6-E2F4-E5BC

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXwzNjM0NkFDQUVENzUxMTA1ODg4NEU1QzZFMkY0RTVCQw.j01Zee9jTsvFXn4XEnwECqbuiKLMdEJmm8pAd0f11o1MMG2BLWqgbCpQRyADUrnOKcjp7lID_3zmRS6Ygl0t_O7C_XvwGDZkFPxVa4OccLPC5fcU5ZUJePanLuGGld_LuuAU9Zu2fDIpiMdTVtyr3xtW5vIJ2UVvXfXqXT-SZi_6KEmoyxg90lntzkBlGAZdYIyEfkEUYjr783vShLdVGKEFLjc7fXzePOT3foSrNKlOqjp8lVqgY8X4Pg9WFUrq7K-Zrd1Sucuk4kmwwjAQAmpp4cMIDLasL9P8iqT5TIMRKPnnLX7guXdzd-gKGOxyQG6QnBWg6f2gviA7l-FdjQ

Put this activation through its paces and get a great result.
 

Post #83

Two things to isolate it:

  • Load a different ECU file — ideally another EDC17C46, but any supported type. If a second file loads to 100% and shows the toggles working, we know it's this particular CFGC dump (or how 1.02 parses it), not the app.
  • If every file stalls at ~20%, then it's the 1.02 build/environment on this machine, and the next step is to check whether it needs write access to its own folder (try running it from a normal writable path, not Program Files or a read-only location).

One more thing worth confirming: does this exact same 1037561802 bin still open fully in 1.0.1 right now on the same PC? If 1.0.1 finishes it and 1.02 stalls at the same point every time, that's a concrete parsing regression on this file to report on the resource thread, and it'd help to know the exact size/CRC of the bin.

When you get a chance to try the other bins (understood on the dual-boot), post back what happens — same ~20% stall or full load. That single test tells us which side the problem is on.
V1.0.1 loads all 3 files correctly.V1.0.2 exe launched now from own directory in D:/ with and without admin rights. All 3 loaded files show (independent of rights) the same behavior. EDC17C46 CFGC Tiguan & EDC17CP44 CRCA Touareg. Bin files by bench mode Scanmatik 3 with pcmflash. Tiguan & Touareg pictures are attached.
Maybe any body could double check opening any bin file on separate installation?
 

Attachments

  • EDC17C46 Tiguan bin not loaded completely ECU Tuning Solutions 1.02.webp
    EDC17C46 Tiguan bin not loaded completely ECU Tuning Solutions 1.02.webp
    73.1 KB · Views: 4
  • EDC17CP44 Touareg bin not loaded completely ECU Tuning Solutions 1.02.webp
    EDC17CP44 Touareg bin not loaded completely ECU Tuning Solutions 1.02.webp
    81.2 KB · Views: 4

Post #84

V1.0.1 loads all 3 files correctly.V1.0.2 exe launched now from own directory in D:/ with and withou...

Hi V.K.,

That Touareg screenshot is the key clue — 1.02 throws "Invalid Dump Size" on the EDC17CP44 file and then hangs on "Please wait ...". So this isn't your install or the license — it's a size/format check in the 1.02 build that 1.0.1 didn't enforce.

What's visible in your two shots:
  • Tiguan EDC17C46, 2048 KB, ID 1037561771 — DTC table fills, header stuck on "Please wait ...", toggles off.
  • Touareg EDC17CP44, 4096 KB, header reports "Invalid Dump Size" then "Please wait ...".

Both are Scanmatik 3 / pcmflash bench reads. The important detail: pcmflash bench reads on these EDC17 give you the full flash + internal/external EEPROM as separate regions, and depending on how you pulled/joined them the total can differ from the plain 2048/4096 KB that ETS expects. 1.0.1 was tolerant of that; 1.02's new size check is not. That's why 1.0.1 opens all three and 1.02 stalls at ~20% (it aborts right after the size/detection pass).

Worth testing before you write it off as a build bug:
  • Feed 1.02 a plain flash-only dump at the exact expected size (2048 KB for C46, 4096/6144 KB for CP44 depending on the exact split), not a bench read that includes appended EEPROM/tail data. If a clean flash-only file loads to 100% with toggles active, the "Invalid Dump Size" theory is confirmed.
  • For comparison, note the exact byte size of each file that 1.0.1 opens fine — if any is off from the round 2048/4096 KB, that's the mismatch 1.02 is rejecting.

Since v1.02 was a full rebuild, a size-tolerance regression on bench-read dumps is very plausible and worth reporting to Bin on this thread with those two screenshots — the "Invalid Dump Size" string makes it a clean bug report.

If you can post the exact byte size of the CP44 file, I can tell you whether it matches a standard flash-only layout or has EEPROM appended.
 

Post #85

297D-CC3D-A8A6-8AD6-566A-2F6C-EC48-D839
please give me license key...
 

Post #86

297D-CC3D-A8A6-8AD6-566A-2F6C-EC48-D839
please give me license key...

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXwyOTdEQ0MzREE4QTY4QUQ2NTY2QTJGNkNFQzQ4RDgzOQ.E3PGfqG3fLy7jbGcEXj0YOeGUOjlZdhFbgXAKXFhRq6ufJYN2-qAhpYueFJ-HVeK6Map5JPFPMUKFhRR2esv9aKyR3hKnbPG_aO2OxOlUAmd4Ib7kE4XJmzOdFeho_iJJ_cOicCr58g4wvD_lJHCTJcCBhWtkS-dPgign-BfEuFWms0YJdjLUZz2yTLyjOQoahbMQAgJzwX-9Mk0ltgFerJV5mEiTivYgAzKsicBep4IifpSeePH8W_Qom6wyJYkRXQD3oXc3oNqye_zCkCSgumESpj8PwxwGBMfFJTbl0vg7o7EyXvWRWDy6AmDfhUuDmNlj0AABJnV0qwlL0NE9g

May the difficult case on your bench turn into an easy win.
 

Post #87

Hi V.K.,

That Touareg screenshot is the key clue — 1.02 throws "Invalid Dump Size" on the EDC17CP44 file and then hangs on "Please wait ...". So this isn't your install or the license — it's a size/format check in the 1.02 build that 1.0.1 didn't enforce.

What's visible in your two shots:
  • Tiguan EDC17C46, 2048 KB, ID 1037561771 — DTC table fills, header stuck on "Please wait ...", toggles off.
  • Touareg EDC17CP44, 4096 KB, header reports "Invalid Dump Size" then "Please wait ...".

Both are Scanmatik 3 / pcmflash bench reads. The important detail: pcmflash bench reads on these EDC17 give you the full flash + internal/external EEPROM as separate regions, and depending on how you pulled/joined them the total can differ from the plain 2048/4096 KB that ETS expects. 1.0.1 was tolerant of that; 1.02's new size check is not. That's why 1.0.1 opens all three and 1.02 stalls at ~20% (it aborts right after the size/detection pass).

Worth testing before you write it off as a build bug:
  • Feed 1.02 a plain flash-only dump at the exact expected size (2048 KB for C46, 4096/6144 KB for CP44 depending on the exact split), not a bench read that includes appended EEPROM/tail data. If a clean flash-only file loads to 100% with toggles active, the "Invalid Dump Size" theory is confirmed.
  • For comparison, note the exact byte size of each file that 1.0.1 opens fine — if any is off from the round 2048/4096 KB, that's the mismatch 1.02 is rejecting.

Since v1.02 was a full rebuild, a size-tolerance regression on bench-read dumps is very plausible and worth reporting to Bin on this thread with those two screenshots — the "Invalid Dump Size" string makes it a clean bug report.

If you can post the exact byte size of the CP44 file, I can tell you whether it matches a standard flash-only layout or has EEPROM appended.
Sorry, EDC17CP44 first message is after open of the old KTAG file. KTAG file caused the "Invalid Dump Size" message. I should have restarted the program to clear the KTAG file message.
The file sizes of both EDC17C46:
bin: 2048 KB
eeprom: 64 KB
EDC17CP44 file size:
bin: 4096 KB
eeprom: 64 KB.
 

Post #88

Sorry, EDC17CP44 first message is after open of the old KTAG file. KTAG file caused the "Invalid Dum...

No problem V.K., thanks for correcting that — then we should ignore the "Invalid Dump Size" clue from the CP44 screenshot.

With the sizes you posted, the main flash files look normal:

  • EDC17C46 flash/bin: 2048 KB, EEPROM: 64 KB
  • EDC17CP44 flash/bin: 4096 KB, EEPROM: 64 KB

So if you are loading only the bin/flash file into 1.02, and not the 64 KB EEPROM, then this is no longer a wrong-size case. The more likely conclusion is a v1.02 parsing / solution-detection regression, because:

  • same files load correctly in v1.0.1
  • activation is successful
  • DTC/P-code table appears
  • progress stops around ~20%
  • solution buttons stay inactive / not detected
  • admin rights and clean folder make no difference
  • happens on both VAG EDC17C46 and EDC17CP44

For reporting to Bin/developer, I would summarize it exactly like this:

Code:
ECU Tuning Solutions 1.02
Windows 10 x64
Clean 1.02 package, single EXE, run from D:\ own folder
Run with and without admin = same result

Files:
VAG EDC17C46 CFGC Tiguan - flash 2048 KB + EEPROM 64 KB
VAG EDC17C46 CFGC/Passat/Tiguan - flash 2048 KB + EEPROM 64 KB
VAG EDC17CP44 CRCA Touareg - flash 4096 KB + EEPROM 64 KB

Read tool:
Scanmatik 3 + pcmflash bench

Result:
v1.0.1 loads all files correctly
v1.0.2 loads DTC/P-code list, progress stops around 20%, header remains "Please wait ...", solution switches inactive

Only thing I would still double-check: after fresh program start, load only the 2048/4096 KB flash .bin, not EEPROM and not a KTAG combined/export file. If that is already what you are doing, then yes, this looks like a real 1.02 build issue and not your installation.
 

Post #90

2A13-2836-D74B-7310-9FF8-ED37-B367-9A2B

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXwyQTEzMjgzNkQ3NEI3MzEwOUZGOEVEMzdCMzY3OUEyQg.NXmC_CuenfapD7UGAdILjHdbfs1k7J-HLz7cIAFg0gyzp9qH03NvTc9EdaldURJWWPH0E1jaNxkwLSqht-oeyGIuvX3hy26Tt-XuEwaoTf2tRXt6OFWxbvg9-MGwYg1DTEwjo7tKlK-2seDWcx_V6keCCt3pbCAbRm2YzyVll4OVb0TayctM2kyzzroi-jaP-sH94MaEw6wzZnqnDAAnGBVzhLtjUu-AL1XMXMGick9g3_VM5PJMlbBeGJS2bieuO-rhMmLkqepN-Y_VhveiKsDc-wnFOaLioi2s3CqGUEI_9fdaFPwYQYzBrXqtKwWK-Ik1DllZLlKFZVg6q8oEHA

The road from fault to solution just got a little shorter.
 

Post #91


Windows 10 x64
Clean 1.02 package, single EXE, run from D:\ own folder
Run with and without admin = same result

Files:
VAG EDC17C46 CFGC Tiguan - flash 2048 KB + EEPROM 64 KB
VAG EDC17C46 CFGC/Passat/Tiguan - flash 2048 KB + EEPROM 64 KB
VAG EDC17CP44 CRCA Touareg - flash 4096 KB + EEPROM 64 KB

Read tool:
Scanmatik 3 + pcmflash bench

Result:
v1.0.1 loads all files correctly
v1.0.2 loads DTC/P-code list, progress stops around 20%, header remains "Please wait ...", solution switches inactive
[/CODE]

Only thing I would still double-check: after fresh program start, load only the 2048/4096 KB flash .bin, not EEPROM and not a KTAG combined/export file. If that is already what you are doing, then yes, this looks like a real 1.02 build issue and not your installation.
Only bin files opened, never eeprom file. But so many downloads now with license keys. Maybe wait for reply of others, if they have same problem or not. Hope all others are not only file collectors to have it, but never use it ;-)
 

Post #92

Windows 10 x64
Clean 1.02 package, single EXE, run from D:\ own folder
Run with and without admin = ...

Yes, exactly — with only flash .bin loaded and the correct 2048/4096 KB sizes, your test is already clean enough. At this point I would also wait for 1-2 other users to confirm with a real file, because this separates a local PC issue from a general 1.02 parser/solution detection bug.

If anyone else tests, the useful check is simple:

  • open any known working flash file in v1.02
  • see if progress finishes past ~20%
  • check if header leaves “Please wait ...”
  • check if solution buttons become usable

Best would be another VAG EDC17C46 / EDC17CP44 flash-only file, because your cases are already clear. And yes, I agree — many people download and activate, but never actually process a file, so real feedback is the important part here. 😉
 

Post #93

726E-AEC6-A193-7CE0-2583-E3BE-7C35-8BA0
thank you
 

Post #94

726E-AEC6-A193-7CE0-2583-E3BE-7C35-8BA0
thank you

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXw3MjZFQUVDNkExOTM3Q0UwMjU4M0UzQkU3QzM1OEJBMA.WiI5-Pf7O6r3e1AgoY0cfvd7fm1cobpoFGQaIouVrWJACigClqxhNiTKb0PXfmt6E3lefwdKImf42V00Z74O2udNsXaHAUOF6tX5Fi5FzJbOlPkZBViE2W3EeArSZaFBvcI2gZqGl08tmDD5ueIGRjVqk3lreFB4f1C8QW5fpqms-RBCJ3PAKpGqvhhnkY-DZV1s-YRktqP913NMdmA4KBicpqKE569_bsb6oThjVXsnwTd1J_BQ4tsFU8V5MBqwNyrIoQQq_Dt3YItu0fspqmDl5R8867eXFioZXZ8Ewf8T4YdSnvq6YuUK3v5sANRCzuAxnyugQE2cs4CUc9c9Eg

No repeated attempts, no unexplained errors — that's my wish for this session.
 

Post #95

D81D-E72D-5653-33B0-6EE9-E467-5083-09DC
gracias
 

Post #96

D81D-E72D-5653-33B0-6EE9-E467-5083-09DC
gracias

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXxEODFERTcyRDU2NTMzM0IwNkVFOUU0Njc1MDgzMDlEQw.ElDwYyk5NseevazTGfysR_tshw3dDx4BvUDidZO-Pu01KyuwCDuc0Mygr49gykqwTvMtZaKr5rrq2T0yxovh5wV17Xh97LZMwLNfCU42P-hCAhfPv-_voBjwPI-QsFDsvXvQqfptNKZK045dUdgWno4k1-5GoWrZ7xgFeO1WIwrHk-IfpL4ZYuoNhqTVoUvNWUJnHA7BS68bdbTZAPWyUQqSDjqnM5tQ-mdfQuNpjJ6uyKXXxnuVrmNnnNPJZjuZLaCEpyZuPNr2qmPnnqB1c57bJioEPUcpStYfp7pb_8e1m9DTbDT8Z5Hyc4LCuQYmJwrDUiShv17Z32iQjIdvgA

Smooth communication with every ECU — that's the plan for today.
 

Post #97

DDFD-33FF-749C-BC7E-6A27-3E8B-0D6D-A163
muchas gracias
 

Post #98

DDFD-33FF-749C-BC7E-6A27-3E8B-0D6D-A163
muchas gracias

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXxEREZEMzNGRjc0OUNCQzdFNkEyNzNFOEIwRDZEQTE2Mw.lyOjxdb_lzVQtRkAgAthw7L81PYOCPOm4vQwyvAyoCDFOuMCKQxGi_cnzu2AMPWPFx4rHYtQy-aJgUU-o8qwY9FBpbgYLAUaK4rRDd3OLhEfpNupplGejA9Dt3QEM7as1vTXhCglyII4v0M8k9gh2BGBGUpcVyu-EkXj_8vCJ6cpHKpOuMvJV67g-aw4IvDCJ_Rf-Wb08C4eWZSh72rtxqgQ9wF-AruJl6oQwRtev1bDXADiSC9URntyM4kAon5uB71WjKTb-_HRgjtQW9GinQOGpe_h_Kl8DY0d-AM8GXjf_LurH63fUN8XGcmdUKKyG7K7mE0Ek8bfFxzEXIDcQw

Ready for action — I hope every module answers on the first try.
 

Post #99

thank you sir
my hwid : 68A3-4922-3F0C-D28D-F357-B7D4-4512-6D47
 

Post #100

thank you sir
my hwid : 68A3-4922-3F0C-D28D-F357-B7D4-4512-6D47

License key: ETS1.RUNVX1RVTklOR19TT0xVVElPTlN8MXw2OEEzNDkyMjNGMENEMjhERjM1N0I3RDQ0NTEyNkQ0Nw.nG4OcBZIQNZoszoNqBSjtT0Awx-9JH-Vnu72mAhNzcBze8jiF_TVyrVHRgFEH3o7oglTFY2Ga2U7im05G62AOjixAuIQ-3msDmxYFgZ33wMa-lvq_3Ed6q7KDnqB_ozD_Z-P15RokO4zpMuuZsc2O_ILftfuMHkYWW22QPfI-6ilcG-9MKv3phRBAxPLkJg35dsTcM8g-fLEej-k6NtMakpzTvMty4d717jQ2enBPMw0Qae7ElB70lcdC9tePvrV-tsyzmkIWwnb0G8DZIl5Pl3I3lw9tQSS2-3fFOnyn0UpsYwSm97hCIt1KidwP8Tf-vbcbOB8IV2i-oF5vHOoPg

A dependable read and a confident write — that's all I ask for your next job.
 
Activity
So far there's no one here