Hi All,
I tried to tune SIMOS18 ECU with upgrade turbo to is20, no matter what i did the boost is not liner, i tried to play with the wastegate maps but i can't to understand the axis.
Some can give more information about an axis in wastegate maps? also, i read about the option to change the axis to boost / rpm.

Thanks

hi, i tried to find it in FR but it's too far doc, i will try more if you have a reference for a page that will help a lot.
also, i copy the wastegate maps from mk7 gti and still have the issue, about VehiCAL i thought about that but looks like needs a boot with autotuner.
the best idea is to replace the axes with a simple patch but i don't have the skills for that, if you can give me someone who can do that it will be great.

thanks

If you are willing to maybe adopt a new workflow you can now use my open source tools also and ditch AT:

https://github.com/bri3d/VW_Flash/blob/master/docs/windows.md

These tools plus VehiCAL and an editor represent a pretty good end to end tuning solution without the locked down garbage commercial vendors seem to love on Simos18.

- Purchase Tactrix openport 2.0
- Purchase vehical-- the program will take your bin file and patch it
- Use Vehical / openport to datalog
- Use VW_Flash / openport to flash

You'll likely want to start over with VW_Flash to unlock the ecu etc.  He recently updated and released a GUI/EXE version with lots of pictures/screenshots to walk thru the entire process of initial flashing on github.  Docs -> windows I believe.

Prj also has wastegate patch now which would solve your logging issue...but I would still get Vehical IMO, good logging is critical.  Then from there you can decide whether to tune OEM logic or use his wastegate patch which replaces the wastegate feedfwd axis with put_sp and engine rpm

First part, yes. The full BINs output by my FRF to BIN process and flashed using "Full Flash Unlocked" are in a format vehical understands (I guess you could call it "standard" if such a thing were to exist).

As for checksums: the open source tool automatically corrects all checksums, all the time - which is debatable on technical merit but you don't have to worry about them!

And as for AT compatibility: Not sure. Everyone unlocks differently, the "way in" is just arbitrary code execution so to go from there to "flash whatever you want," there are many, many mechanisms. If AT just turns RSA off (for example using the production/sample mode check function like I do), then you're good to go. If it does something else requiring custom flashing logic, it won't work. I don't own any commercial tools so I can only know what other people tell me in terms of what's compatible and what's not.

ok so after a lot of reading, I understand the ip_fac_bpa is just pre-control, it can help to improve boost but this is not open close loop, so i think my main problem is the torque model and how boost controller works on that ecu, so i think the issue is with ip_tqi_ref_n_m_air_vvl_cam_h and ip_maf_stk_sp_vvl_cam_h, i still don't activate RAM logger but from VCDS it looks like "Driver torque request" is always very high from engine torque even boost is high and I think that influence the something in the logics.

Someone can help with some information about "boost / torque model"? or a reference to the page in FR will help too.

Thanks

I don’t think so, i did the boost patch from prj, so no intake air/exhaust gas flows.

The whole magic is behind combustion chamber pressure and gas flows - patch not patch it does not matter if there no horsepower spinning turbo. Where common failures? improper MPI usage during spool, vvti/vvl not optimized, wrong ignition strategy for spool phase.