D
Deleted member 452
Guest
Good stuff Josh!
This is why I'lm a bit reluctant to PCV : if we increase fueling in closed loop area, it will work at first dyno test, but the ECU will learn it's richer than expected and will remove fuel everywhere (even full load)Closed loop is below 8000 RPM and below 65% TPS.
I sent him an email 6 months ago asking him to let me know when he figures out how to flash the ECU using the diagnostic port but haven't heard from him.
Hey guys, I wanted to start a thread about what I'm working on for tuning the RC390/Duke 390. I'll start with a little about me before I get into the details so you know my background.
I finished school in 2008 and was excited to start a career at a major tuning company. Since then I've worked for 3 different automotive/motorcycle tuning companies as an ECU Reverse Engineer and also own my own LLC where I do mostly e-tuning for German cars and Subarus. I love what I do, so the first thing I look at with a new vehicle is tuning options. I bought a Audi A4 about 2 years ago and immediately got to work on the ECU so I could tune it. As of now, it is running around double the stock horsepower with all upgrades, tuning, and ECU work done by myself. Fast forward to 3 weeks ago... I bought a 2016 RC390. I was excited to pull it apart and find a Bosch ME17 ECU, so I decided to start working on it as a side project.
First step was to get a read of the factory ECU image. Full disclosure, I actually bought a Duke 390 ECU on Ebay to try it on first:
View attachment 4138
Next, I started working on the assembly code and finding tables. I'm extremely familiar with Bosch ECUs, so I made pretty quick work of the main things I was looking for and started on defining some of the less obvious (but no less important) tables. So far I've done pretty well, but there are still quite a few things to test. As a side note, the Duke 390 ECU had exactly the same tuning and addressing as the RC390 (expected, but nice to verify). Here's a sample of what I've found so far:
View attachment 4139
View attachment 4140
Next, I wanted to verify as much as I could without having a real logging option for RAM values. I created a base flash, calculated the proper checksums, and wrote it to the ECU. The bike started and I was able to verify the rev limit and fan temp tables. Always satisfying when a vehicle fires up after an initial test flash, so I wanted more. In order to have some external control and logging, I decided to install a Power Commander 5, Auto-Tune with Wideband, and a POD device to log injector duty cycle, AFR, etc.
View attachment 4141
Watching the Wideband AFR at idle, I could see that everything was working, but the ECU was trying to fight a bit while in closed loop. I decided that I trust a wideband a lot more than an OEM narrowband O2, so I created a new ECU file which forced the ECU into open loop all the time. I also set the ECU AFR targets to what I thought would be as close as possible to perfect without dyno testing. I then set the PC5/Auto-tune AFR targets to the same and enabled auto-tune. This means that my bike is now running full-time open loop through the ECU, but the Auto-tune is providing full time closed loop fuel control with wideband O2 feedback. So far I'm very happy with the changes.
My plan is to throw the bike on the dyno Sunday and see where she sits as a baseline for further tuning/mods. I have an exhaust on the way thanks to Superpacman13 so I'll want to calibrate for that once installed. I also haven't played with ignition advance at all yet, so I'm sure that will net some gains once I'm on the dyno and can do some solid testing.
Anywho, just wanted to share my little project. Happy to answer questions if you have any. Also, I've only had the bike for a few weeks, so let me know of any quirks I should look out for that could be fixed via ECU tuning.