WinOLS Tuning/Support for the United States

Hey there, was curious if anyone knew who may be within the US or supporting the United States with WinOLS tuning? I'm on the West Coast, enrolled here and working on my own training soon for both WinOLS and Motec among the plethora of courses available under the VIP package. For now I need professional tuning on the platform to get things going tuning wise for track days and time attack/HPDE, and just overall adjustments for something not set up for this tuning wise (could help the community of us at large). There just aren't really good options for us Mazda folk anymore who aren't in Miatas/MX-5s, especially on the modern platforms. We are pigeonholed into MazdaEdit at the moment.

Platform is a 2021 Mazda 3 Turbo and it's not terribly loved by the tuning world but it's turning out to be fairly spicy as chassis and responding well to parts and some tuning on MazdaEdit (little lackluster software suite, not very powerful, better than nothing). Been working on this car for awhile with my sponsors Corksport and Antigravity Batteries, but impacted by covid and following logistics chain issues; Corksport is putting in some work to make things happen. Antigravity Gravity Batteries bringing down the weight and helping keep things powered. I'm also working with MeLe Design Firm to help out Mazda folk on their kits as well (stock stuff just isn't up to par to take a beating), since they're local to me and it's easy that way (trying to support people best I can)

Gotta catch up with Mad Mike's rotary madness and beat Mazda to the punch a bit US based time attacks outside of the spec Miata and MX-5s.

Thanks ahead of time, I appreciate the help and insights always! :)

can you upload the binary file, ecu type, and processor, and some data logs? highly doubt I will be able too help you, but I will look at it.

Do I need to get these through WinOLS? I have held off getting it for now until I know I can begin to give it a proper effort/get help. However I may just go for it anyways, haha.

It's a Mitsubishi ECU, unsure on processor. I've got an ECU dumpfile via Mazdaedit, lots of logs as well from the tuning development with that software.

I would think ECUtek would be your best bet for the Mazda 3.

https://www.ecutek.com/proecu-mazda-tuning-suites/

The MX-5 has an open-source things going - sometimes referred to as "speepsware" after the fellow that is doing the development. You can learn more about that here:

https://forum.miata.net/vb/showthread.php?t=630805

ECUtek has denied supporting the current gens, much like Cobb has. I'll check out the other thread there you linked.

With just ECM tuning via Mazdaedit we're getting to about 400wtq on the AWD 2.5t Mazda 3s (just a few bolt ons and additional ethanol content) but we're neutered heavily by the lack of PCM/TCM controls in these torque logic ECMs.

Biggest hurdles are reverse engineering the systems. Perhaps we can use the Miata work as a launch pad for some core functions, so I'll check that out.

Before deciding to use winols you need to have a flashing solution. I'd check if PCMFlash can handle the job, its the most cost effective pro tool. This may be the module needed:

https://ecutools.eu/chip-tuning/pcmflash/module-72/

Once you have a tool to read / write, that should provide the .bin file. Alternatively, you can download the .bin from a place like Dyno-ChiptuningFiles.com.

The EVC.DE (winols) project db has a bunch of tuning files, though I'm not seeing a map pack.

Tactrix Openport 2.0 does work, that's what Mazdaedit uses and we've been using for a couple years now. I have a dump file (which I'm guessing is just a bin file needing converted to .bin format)

I have looked for a map pack/damos file but haven't found any yet, I figure I'm probably at a point I'd have to pay a company who can build them to do it or take the time to just learn it myself and pull the trigger on the software necessary (which would just take a little longer as I'm still new to this). The turbocharged 2.5s (186kW/433Nm) have such a different ECU (well...3 of them) and torque logic from all other Mazdas, haha. Figured this was a good spot to chase down leads/learn and reduce time in dev/risks :)

Perhaps I misread your OP, but if Mazdaedit can read / write the ecu, then that should also be used to edit the binary. No need for winols unless there's a shortcoming in defined maps.

Yup, there are issues with the definitions, haha. I haven't tried messing with the binary in it yet (as the program also isn't very powerful, regarded, or well documented, nor supported very well by Epifan)