ANyone with a quickshifter, what are you using for your kill time? Currently I'm running a single time, but plan to add a gear/speed input so I can set times per gear. Just wondering what kind of times you guys have found to work well.
PM'd ya. That looks like something similar to the O2 simulator that Dynojet includes with their PCV. Looks like you need to leave the O2 installed, so not really an "eliminator"
Kinda... Every dyno plot I've seen, including my own where I had richer targets than stock, the actual AFR was quite a bit leaner. So I don't think the VE table is set up properly to actually hit the target AFR. Once I do more testing, I'll post more dyno sheets with actual AFR included.
Not...
There's a table for "max TPS for closed loop trims" which from the factory is set to 65% TPS. So anything under 65% TPS and when the ECU is requesting stoich, it will be in closed loop. Target AFR is just a target though... so if VE is not properly set up, then these values will not be achieved...
Actually, that matches up pretty close. They don't have 65% TPS row in that map, so the cells with a value of 8 in the 80% TPS column are likely interpolating the 65% value. Closed loop does vary a bit in the 5-20% TPS columns as they show.
Sorry, should have mentioned fan temps are already tested. I'll add that to the list. Bluetooth would be on the tun device side and would be reasonably easy if it was a phone app instead of a proprietary device, I'll add that to the 'wants'.
I'd have to look into how the ECU does that code. ABS is a separate unit, so I'm not sure I could do that... worth looking into though!
@CDN Duke , go help me get some posts on the Duke forum thread I made so I can upload photos over there and gain ideas and interest.
To add to this, here's what I have so far and what I'm thinking of adding:
Tested:
- Ignition Timing
- Rev limits
- Idle targets
- Forced full-time open loop
- Target AFR
- Sensor scaling
- Injector scaling
To find:
- rollover sensor
- DTC disabling
- logging via diag port
- flashing via...
Thanks dude. If I think it's feasible and there is interest, I'll definitely see what I can do. I have enough defined to do tuning for a pretty serious build already... in fact it should be totally possible to tune for a turbo kit at this point other than it really needs to be capable of logging...
Sure, we make custom tuning software, so I expose as many tables as possible for end-user software. That includes pretty much anything needed to calibrate for parts that have been changed. If you check out the list of tables in the first post, you'll see there are 6 tables for just the injector...
Checksum calculations and signing are done using proprietary tools either written by myself or a co-worker. I do this for a living (for different ECUs), so I have some experience dealing with these sorts of things. For determining ECU logic, data scaling, and how tables interact, I use IDA Pro...
1. First, these are not single values, they are large 3d tables. At WOT, I was targeting a 13.2 with a 13.0 above 7500 RPM. So the ECU is close, but with some adjustments to the VE table, I would expect to be able to keep the bike within a tenth of a point of the target.
2. All of the target AFR...
Right now it's just a personal project since I can't leave an ECU alone lol. But if there was enough interest, i would love to support all the 390s. We'll see...
Great questions. I'll go through them one by one.
1. I am currently using the RC390 ECU with my changes applied. I will test with the Duke ECU, but I expect it to work just fine since I don't think there is an immobilizer feature on our bikes. If there is an immobilizer, I would need to...