Recent Posts

Interesting project and given that its open source and on github I took a quick look at it.

So first of all, who are the developers?

Well it seems like they are called CT14 Garage and they are located in Thailand of all places, seems weird but they seem to be a genuine WinOls user, a porsche partner, and various flashing tools partner. Alright not bad.

Second:

The download links on the romhex website itself seem to be broken atleast for windows, it points to a different github location which is 404. Had to manually go to right adress and download the release from there.
No installer, just unzip and off you go.

The program is very flashy, very colourful like the trend it is these days, also its obviously heavily inspired by WinOls layout and design.

Importing .s19 or bin goes without any problem tried with MED9 file. Though processor identification is wrong , and some other data doesnt get parsed from the bin unlike WinOls.
A2L import seems to work aswell HOWEVER it does not import the groups/module folders which I hate, instead the maps get grouped based on name.
OLS project import seems to work aswell however in my case it didnt seem to import my maps in the project, just the version that is the original bin without maps it seems like, might be just me though.

Overall ofcourse there is integration of AI which requires an account, checksums I didnt see anything about in this quick test, also the program was obviously made using AI/with the help of AI coding, but so far it seems to work somewhat.
Competition is great, being open source is great.. what is the catch ? Apart from the "pro" version which requires an account.

you do have to download from the pro link tho, still free and I'm kool with that, paying just unlocks AI and I'm all set on that, and yes they are winols partners. i export rom so it saves as .bin and use me7checker and me7sum in cmd... could be used as training for someone looking to buy winols..

I like the dark red theme.. got me wanting to go mess with the theme in my winOLS lol

I have heat range on, that not a theme

Interesting project and given that its open source and on github I took a quick look at it.

So first of all, who are the developers?

Well it seems like they are called CT14 Garage and they are located in Thailand of all places, seems weird but they seem to be a genuine WinOls user, a porsche partner, and various flashing tools partner. Alright not bad.

Second:

The download links on the romhex website itself seem to be broken atleast for windows, it points to a different github location which is 404. Had to manually go to right adress and download the release from there.
No installer, just unzip and off you go.

The program is very flashy, very colourful like the trend it is these days, also its obviously heavily inspired by WinOls layout and design.

Importing .s19 or bin goes without any problem tried with MED9 file. Though processor identification is wrong , and some other data doesnt get parsed from the bin unlike WinOls.
A2L import seems to work aswell HOWEVER it does not import the groups/module folders which I hate, instead the maps get grouped based on name.
OLS project import seems to work aswell however in my case it didnt seem to import my maps in the project, just the version that is the original bin without maps it seems like, might be just me though.

Overall ofcourse there is integration of AI which requires an account, checksums I didnt see anything about in this quick test, also the program was obviously made using AI/with the help of AI coding, but so far it seems to work somewhat.
Competition is great, being open source is great.. what is the catch ? Apart from the "pro" version which requires an account.

How can I find the maps responsible for the hard rev limiter (that can shoot flames like in 1.8t) in MED9.5.10 06F906056xx?

I have found the KFTSRL and DNMAXH maps, but I am not completely sure if they are the correct ones

In ME7.5 it was necessary to modify:
FTOMN
KFSZT
KFTSRL
NMAXDVG
DNMAXH
NMAXDV
In MED9.5.10 I could not find any map called FTOMN. From what I found, there should be a map called FUBAOF instead (at least in MED9.1 TFSI), but I am not sure where to find it in this binary or if it is actually the equivalent map
Does anyone know the correct maps/offsets for a hardcut on MED9.5.10 06F906056xx?

The file attached is probably not 100% original because I removed the P&B from it using 56EK file. I am not sure if anything else was modified, because I have not been able to find a completely original binary for comparison

I have SGO converter tool I can share link again, in fact I think I made a thread about it already on here long ago I’ll see if the link is still good

I like the dark red theme.. got me wanting to go mess with the theme in my winOLS lol

here what i have its for MPH 8J0 920 930 F

Hi. PRJ, _nameless , Blazius, Nyet please some advice. ecu 022906032DP from audi tt mk1 3.2L can be made turbo with map replace maf? it has 2 processors ,one is c167 other st10? witch one is primary? and witch one use flash am29f800? thanks in advance

HI. Has it 2 processors? One is c167 other is st10? Witch one is primary? In ida pro the file can be open like a c167 from 1.8T ot not? Or it can be interchargeble with 022906032CB? Thanks

I had a customer who wanted a flash for 032TF as well as another with 032TL this was my first time working with those particular files initially I thought they might be rare but turns out they are just more common overseas outside the states. Anyways your trying to flash a file for an Audi A4 to an ECU for MK4 golf/jetta? This doesn’t usually go well

Regarding the 1.8T and the ECU types: from what I have personally seen, there are four variants of ME7.
First is the narrowband ME7.5 (examples would be the USA-market AWD and ATW). This ECU uses a 512 KB flash ROM, the AM29F400.
Next would be the ME7.1 version, I think. It was used in an APH Beetle, and if you look at the PCB layout, it looks more like a 12V VR6 ECU versus an actual ME7.5 1.8T ECU. These engines do not have VVT, but they do use an LSU 4.2 sensor.
Next up, we have the standard ME7.5 wideband variant that's used in all A-chassis cars regardless of factory HP rating. For example, I'll list off the USA variants: AWW, AWP, AWV. This ECU hardware version is compatible with early (pre-2003) B-chassis cars too. Possibly C-chassis too, but I cannot confirm, as here in the States we did not have four-cylinders in the C-chassis. For example: AWM, AUG, and early 2002 B6 A4 518F/M software version(s). In 2002, they still had the early wideband hardware and it is the only model year B6 that uses it.
The last hardware version is the late wideband ECUs that are used in the 2003+ B-chassis cars, for example AMB B6 and AWM B5.5 Passat. These ECUs are cross-flashable, but cannot be cross-flashed to the earlier wideband software versions, it will brick the ECU.