Address 01: Engine (J623-DKFA) Labels:. 06K-907-425-V1.clb
Part No SW: 5G0 906 259 Q HW: 06K 907 425 J
Component: R4 2.0l TFS H13 0007
Revision: --H13--- CVN: 1BCB9B8F
Coding: 092500124424012F1000
Shop #: WSC 00066 790 00382
ASAM Dataset: EV_ECM20TFS0205G0906259Q 001008
ROD: EV_ECM20TFS0205G0906259Q.rod
VCID: 3C213BECD6EE17ABD37-8068
VINID: 0E69C690746501B740043144202D170A5E
The more and more I read about problems with X tuner or Y tuner's files, the more it seems it may fit my needs. I track my car and really don't want to get stupid with power or anything... and writing a custom DSG tune to force shifting ONLY based on RPM (to always maintain the lowest gear on track) would be pretty damn nice.
I'm going to have to read all 16 pages to catch up and try to understand everything... but I take it regardless of whatever your original file/box code is, you can back up the OEM tune 100%? (Not like how the Cobb OTS "stock" tune is a non-PP tune which would actually detune any PP equipped cars... as I understand it anyway).
edit: Just went through it all. The Macchina A0 is out of stock everywhere... however due to my day job (ADAS calibrations and software flashing - usually SRS modules and stuff - for basically all makes and models... I have a Drewtech Cardaq +3... which I would imagine should be capable?
http://drewtech.com/products/cardaqplus3.html
As a side note: I also have access to ODIS (intermittently, it's on a laptop that floats around between a few techs in the area)... would there be anything worthwhile that can be done with that to help you guys?
I have nowhere near the technical/bit-level knowledge you guys have... I'm like a few weeks into a CS50 online class though Slowly trying to absorb information.
double edit: Here is the info from my 2019 GTI for reference. Not sure if anyone has messed with the newer box codes yet or not? Or if it's even compatible?
Code:Address 01: Engine (J623-DKFA) Labels:. 06K-907-425-V1.clb Part No SW: 5G0 906 259 Q HW: 06K 907 425 J Component: R4 2.0l TFS H13 0007 Revision: --H13--- CVN: 1BCB9B8F Coding: 092500124424012F1000 Shop #: WSC 00066 790 00382 ASAM Dataset: EV_ECM20TFS0205G0906259Q 001008 ROD: EV_ECM20TFS0205G0906259Q.rod VCID: 3C213BECD6EE17ABD37-8068 VINID: 0E69C690746501B740043144202D170A5E
Returning to stock: 5G0906259Q 0007 or whatever version is readily available, no issues flashing back to stock. the PP and non-PP cars run the same box code and tune file. The difference is there is something internal to the ECU that will identify the 2 trims as different "power classes". In this case non PP is powerclass 1 and PP is powerclass 2. There's separate torque request tables (among a few others) per power class for this sorta thing. This sorta thing is actually way more common with the ROW box codes.
For fun, here's PC1 vs PC2 torque request in a 2018 GTI file...... very very small difference.
View attachment 252312
That drewtech device appears to be J2534 compliant, so it MAY work with VW_Flash, but if you want phone app logging, flashing and all the latest cool stuff, you need the macchina a0 or esp32 based clone. There's a few guys who are making them now in their spare time and I would recommend going that route for sure.
Just added 'beta' support for DQ381 as well--still in testing.
Have a DIY tuning group if you're interested in joining and learning more, that's probably the best place to get started and in touch with the folks to get your dongle made, etc. Shoot me a PM if you're interested.
Thanks for the explanation!
Will send a PM shortly once my minion is in bed.
I would imagine the Cardaq would work for flashing... I mean it's what I use with ODIS to flash new modules and remove CP. They're actually THE company that worked with OEM to write the J2534-1/-2 standards.
I'd like to but I don't have Macchina-A0, I own scanmatik 2 proWhy not use SimosTools?
Yeah, I thought it also, but I coulnd find them at all, even on creator's github, VW_Flash_GUI is directly downloaded from githublooks like you're missing the logging config, or something's wrong with the file.
The example one would be S50, and @razor1199 that will only work provided you've patched your software with a compatible logging patch.https://github.com/joeFischetti/SimosHighSpeedLogger
should be there. you may need to adjust the memory locations used, can't say which ecu file structure is being used in his example parameters.yaml.