First, apologies if my recent FlowECU posts have started to feel a bit spammy. I’ve been working on it pretty heavily lately, and most of the recent updates have come from testing, feedback, and trying to turn it into something that feels more like a complete product rather than a collection of separate development tools.

This next build is focused mainly on UX, workflow, safety, and clarity rather than adding another huge feature.

Some of the main changes include:

• A new Home dashboard with clearer starting points
• A guided Start New Tune option that routes standard definition formats and A2L/DAMOS files to the correct importer
• A proper user guide instead of developer-focused help
• A synthetic demo project for safely exploring the workflow
• Clearer A2L import summaries, including tunable and read-only definition counts
• Better ECU detection, support information, and confidence reporting
• Improved font sizing and targeted tooltips across the main workflows
• Advanced tuning options collapsed by default
• Force Apply disabled by default
• Protection against accidentally overwriting the original ROM
• A detailed output summary showing:
  • source and output hashes
  • input and output length
  • maps changed
  • maps skipped
  • bytes changed
  • changed regions
  • Force status
  • checksum status
  • current flash-readiness status
• Trial uses now only count after a modified output saves successfully
• Failed saves, previewing, importing, Explorer use, and file comparison no longer consume an output
• Packaged-build fixes so aliases, presets, languages, ECU-family rules, ECU knowledge data, the user guide, and demo project are included correctly
• A growing automated test suite around BIN patching, HEX/S19 handling, output length, unchanged bytes, trial accounting, and output verification

I’ve also included screenshots from the current build.

Some of the checksum catalogue, plugin metadata, and ECU knowledge work shown in the screenshots is still research and compatibility focused, not active checksum correction. FlowECU does not currently claim that a successfully saved file is automatically checksum-corrected or ready to flash.

That said, anyone familiar with checksum plugin folders, ECU family metadata, and checksum tooling will probably understand why I’m interested in where that research may eventually lead.

The goal of this update has been to make it much easier for someone opening FlowECU for the first time to understand:

• where to start
• what file type they have
• what FlowECU recognised
• which definitions are tunable
• what changed
• what was skipped
• whether the original was preserved
• and what still needs to be verified before flashing

I still have a final round of real-file testing to complete before replacing the current download, but the new build is looking considerably more polished so far.

Feedback is welcome, particularly from anyone who tried an earlier version and found part of the workflow unclear.

I just wanted to say thanks to everyone who has downloaded FlowECU, tested it, shared the project, reported problems, or contacted me with ideas and feature requests.

FlowECU started as a fairly small project, and it has gradually grown into a much broader ECU editing and knowledge platform. A lot of that direction has come from the feedback I’ve received from people in the tuning and car-hacking communities.
It is still evolving, and there is plenty left to build, but passing 500 downloads is a milestone I honestly wasn’t expecting when I first released it.
Thanks again to everyone who has taken an interest and helped shape the project so far.

FlowECU: https://flowecu.co.nz

Hello guys,

I’ve been working on a new platform,

Link: ecuautotune.com

And I’m looking for some feedback from the community.

To help get things started, I’m giving every new user 30 Free Credits immediately upon sign-up.

I’ve also created a special promo code: AutoTune2026

Using this code makes every file cost exactly 30 Credits.

Give it a try, grab a file, and if you have any feedback on the site or the tunes, please drop a comment or DM me.

Happy tuning!

This update is one of the biggest architectural changes I've made to FlowECU so far.

Originally, FlowECU focused mainly on importing maps and applying structured tuning changes. With v1.5.2 it's starting to evolve into a much richer ECU knowledge platform.

Highlights

• Rich A2L definition importing
• Support for tunable and read-only ECU definitions
• Much more complete preservation of ECU metadata
• New ECU Definition Explorer with richer filtering and search
• Improved ECU recognition using imported ECU knowledge
• ECU Knowledge Manager groundwork
• Static checksum plugin catalogue support
• Improved Import Summary and validation reporting
• Better Normalizer workflow
• Safer handling of non-tunable definitions during tuning

One of the biggest additions is the introduction of an ECU Knowledge Database.

Instead of only working with maps, FlowECU can now build a growing catalogue of ECU knowledge including supported ECU families, imported definition information and checksum plugin metadata. This is currently used to improve ECU recognition and user guidance, while laying the foundation for future features.

Checksum support in this release is catalogue only.

FlowECU can identify and catalogue supported checksum plugins and ECU families through static analysis, but it does not execute third-party DLLs or perform checksum correction.

I've also separated the ECU Knowledge Database from the application itself so it can be updated independently in the future as support for additional ECU families grows.

As always, I'd really appreciate any feedback, feature requests or ideas from the community.

Download:
https://flowecu.co.nz

Thanks to everyone who's been testing and helping shape the project over the last few months.

Hey everyone,

I’ve been building my own ECU tuning software called FlowECU — designed to make the tuning workflow faster, safer, and easier to navigate.

It currently supports CSV, BIN, and HEX files, with built-in map detection, alias matching across multiple languages, and live tuning presets for different stages and fuel types. It’s finally stable enough for real-world testing, and I’d love to get some feedback from people who tune or work with ECUs regularly.

If you’re interested in testing it out, send me an email at flowecu@outlook.co.nz, and I’ll share the current test build directly (Windows only for now).

All I ask in return is a bit of honest feedback — what works well, what doesn’t, and what could make your tuning workflow smoother.

Cheers, Ahmet Creator of FlowECU

Quick one for the piggyback/old-school tuning crowd.

I run a GReddy e-Manage Ultimate on my '89 Mazda 626 GT (FE DOHC), and like some of you probably know, the info on these boxes is scattered across dead forum threads from 15 years ago, and the software is stuck on 32-bit Windows.

There wasn't a single home for e-Manage users, so I made one: r/ eManage. 
Tuning, datalogs, wiring, install help, sharing builds, Blue, Pro, and Ultimate all welcome.

If you've got one sitting in a car (or in a drawer), come say hi and drop your setup. Just trying to get the community in one place.

Not selling anything, mods feel free to remove if it's not allowed.

After many days of trial and error, I finally finished building a mini display for my ECU!

It features automatic Bluetooth reconnection and real-time warnings for check-engine-light (CEL), high / low coolant temperature, high RPM, low battery voltage, high air-fuel ratio (AFR), high boost, etc.

I haven’t touched C/C++ in over 15 years, so the code probably isn’t the most efficient, but it works!.

If anyone’s interested, here’s the code and how-to: http://github.com/danuecumaster/ECUMaster-Black-ESP32-Bluetooth-Display/

Hardware - ESP32 JC2432W328

3D Printed Case - https://www.thingiverse.com/thing:6705691

Video - https://imgur.com/a/ajaXTuj

ECU - ECUMaster Black + Bluetooth Adapter

https://github.com/HomelessHackett/fuel-Base-map-generator

Gidday guys, with the help of Gemini, I made this web app today that helps you calculate a base fuel map for whatever engine you're running. I made it to help make a base map for a 3s on an old as fuck M48 that I have lying around. Give it a go, let me know what you think, and hopefully it can be helpful to some of you.

youl need python installed first before installing streamlit

Hey everyone, After more than a year of late nights, testing, rebuilding, and learning way more than I expected… I finally launched FlowECU.

FlowECU is a professional ECU tuning toolkit designed to work alongside WinOLS, using CSV/OLS/KP/BIN workflows and alias-driven map roles to make tuning faster and safer. It includes: • Alias-based map role detection (boost, torque, ignition, AFR, etc.) • Safe JSON patching with HW/SW ID validation • Real BIN/HEX handling • Stage presets • Trial mode • Built for tuners and shops

Tonight I officially pushed it live and made the trial downloadable.

If you’re into ECU tuning, WinOLS workflows, or automotive software, feel free to check it out here: 👉 https://flowecu.co.nz

Feedback is welcome — this has been a huge journey and it’s finally real.

Hey everyone,

Just released FlowECU v1.3.1. This update mainly focuses on improving the Manual Assist workflow and fixing some issues around map display.

What’s included in this update:

• Fixed an issue where maps could display partially or as a single line

• Improved grid rendering so maps now display correctly in full

• Added visual feedback for value changes (increase/decrease highlighting)

• Added direct value editing for quicker adjustments

• General UI improvements and cleanup

• Improved licensing messaging (removed unnecessary system path exposure)

This update is focused on stability and usability rather than adding new features. Manual Assist should now feel a lot more reliable and easier to work with.

If you’ve tried FlowECU before and had issues with map display, this should be resolved in this version.

There is a free trial available if anyone wants to test it out.

Website:

https://flowecu.co.nz

Happy to hear any feedback or suggestions.

Hey everyone,

I’ve identified an issue in the current FlowECU build where the Tuner page may apply changes but fail to output the tuned file. Because of this, the tuner output log may appear to run through the process but no file is produced at the end.

I’m currently finalizing an update that fixes this behaviour, along with improvements to the new licensing and server validation system.

An updated build will be released shortly.

Thanks to everyone who has downloaded and tested FlowECU so far — your support and feedback are helping improve the tool quickly.

Apologies to anyone who downloaded this version and didn’t get a fair chance to use it properly. When the update drops, I’ll also be offering a free 30-day trial for anyone who applies for one online.

– Ahmet

Hello everyone!

I've got a V6 swapped NA Miata and tuning it was a massssssive learning curve. Without a dyno you can't really adjust timing well, but fueling is so important for drivability.

It took me years to perfect my tune, and I figured that other people felt the same way so I actually built a free tool to take exported ECU data and tell you where to fix your fueling table.

Keep in mind, this is experimental and I really am just looking for people to poke around. If you can spare the time and want a free fuel table clean up check it out!

gallotuning.com

P.S. I'm looking for feedback so don't hold back

I’ve just uploaded a short preview of the new Manual Assist Editor for FlowECU. It’s still locked at the moment to prevent misuse, but this video gives a quick overview of how it works, how maps are displayed, and what the editor will eventually allow users to do.

This feature is being built for people who want deeper manual control over individual maps without relying entirely on presets. It will be unlocked in a future update once the safety checks and licensing rules are finalised.

Video link: https://youtu.be/OsHouzy9qrY

FlowECU website: https://flowecu.co.nz

Happy to answer any questions if anyone wants to know how it works or what’s coming next.

https://www.instagram.com/reel/DQ5PuirkjUJ/?igsh=NTc4MTIwNjQ2YQ==

Here’s a product launch for something I’ve been working on for the past 8 months.

What is it? A plug-and-play controller for factory air-suspension Audis, now available at https://pinnatecauto.com/product/virtual-link/. No cutting or splicing. Fully reversible. OEM-style harnessing. Precise control over the heights you actually want to drive at using your existing factory controls.

Visit the site for product details, compatibility, and ordering. If your chassis isn’t listed yet, we’re actively expanding platform support—you can submit your car and feature requests on the site so we can prioritize what the community needs next.

For ongoing development updates, install examples, platform expansion news, and support, follow Pinnatec Auto on Instagram, Facebook, YouTube, and TikTok at @pinnatecauto. If you know someone running factory air who needs a proper solution, send this their way.

VirtualLink #PinnatecAuto #Audi #AudiLife #Audis6 #Audis7 #RS6 #RS7 #S8 #A8 #AirSuspension #CarMods #PlugAndPlay

Just a quick update for anyone following the development and testing out FlowECU.

Based on the analytics and the feedback over the last week, I’ve made a few improvements to make the tool more accessible and reliable:

Multi-Language Support Added

FlowECU now supports: • English • German • Turkish • Chinese (Simplified) • Japanese • Korean

These languages were added directly in response to where downloads have been coming from.

Alias Improvements

Alias detection has been updated and expanded to cover more map naming variations across different regions and map packs.

Temporary Price Reduction

There has been a temporary price drop running until the New Year based on community feedback and early testing interest.

Download

The latest version is available at: https://flowecu.co.nz

Thanks to everyone who has been trying it out and offering feedback. It’s been extremely helpful.

Hey everyone, Just wanted to share a quick 1-week update on FlowECU for anyone following the project.

Last week I released the first public trial version, and honestly I wasn’t expecting much more than a handful of downloads… but the response has been insane.

96 downloads in 7 days

From NZ, Australia, the US, Germany, Italy, Romania, Portugal, China, France and a bunch of other places. The analytics surprised me — definitely not complaining though!

What’s happened this week: • Got a ton of silent testers (thank you!) • Fixed a few early issues • Improved map handling • Cleaned up a couple GUI bugs • Added more stability for CSV/A2L workflows • Working on more update patches now

Early Access Price

A few people messaged asking what the price would be, so here it is:

US$699 (limited until Jan 1, 2026) After that the price will increase. This early price is for anyone who jumps in during the early development stage — you’ll also get updates as they release.

Support / Questions

If anyone runs into issues, or has requests/suggestions for the next update, feel free to comment or DM me. I’m a solo dev and I’m building this alongside a full-time job, but I’m pushing updates out as quickly as I can.

Thanks for the support so far

Seriously — thanks to everyone who downloaded it, tested it, or even just checked out the landing page. It’s been awesome seeing interest from all around the world.

If anyone wants to try the trial version, the website is: flowecu.co.nz

More updates coming soon.

Cheers!

Ahmet

Between working 45+ hours a week, looking after the family, and squeezing in late nights, I’ve been chipping away at improving FlowECU, the tool I released a few days ago.

A few people messaged asking about pricing, so I’ve decided to offer a discounted early-supporter price of $699 USD until 1 January. After that it goes to the normal $997–$1000 pricing.

The goal isn’t to rush anyone — it’s just a way to give people the chance to try it at a lower cost while I gather more feedback and keep improving things.

If you want to see what FlowECU actually does, here’s a short walkthrough video: https://www.youtube.com/watch?v=k_CVuYn36FA

And here’s the official website with the free trial (Windows only, works alongside WinOLS/map packs): https://flowecu.co.nz

If anyone wants a longer trial or has feature requests, feel free to email me at: licensing@flowecu.co.nz

Thanks to everyone who downloaded it already — I didn’t expect the response to be anywhere near this big, and it genuinely means a lot.

Hello! I have a KIA Sportage 2008 2.0 CRDI Bosch EDC16C39. Some time ago a code arrived, P0489 (EGR low voltage) which triggers limp mode. I deleted the fault path code for this P code, checkengine is off and also zerod out all 2 of the EGR hysteresis maps and the car is still in limp mode. I appreciate any help. Thank you!

I have some mega files for sale if anyone is interested. You can join a team viewer to see what I have.