ECUTEK RACEROM 13

[B T]

Received a new tune for the updated RACEROM13 version at the end of last week. The new version requires use of both O2 sensors( so have fun plugging those back in), cannot scale for ethanol outside of CANBUS protocol (requires new CANBUS ethanol content analyzer), cannot remove emissions related codes (Hello CEL) and also is currently not playing nice with the old hardwired ECUTEK data cable.

I can read live and log while the the car is in the accessory key position, but once started, ECUTEK loses the ability to connect to the ECU. Error reads "Map Access Error: No Response from ECU" when reconnecting while live. Also, any default parameter lists you have previously setup are no longer valid as the parameter names have changed. Use of an invalid parameter will yield "Map Access Error: Array index 3 is out of bounds on string 05 7D"

Has anyone been able to get around the live connect issue? I have a ticket open with ECUTEK awaiting response.

[tomm.brz]

just wait ecutek

i have been using racerom 13 on euro roms for weeks, no big problems
there are bugs but not in main tables

old cable works good to me
of course check if connection is good, eventually use an adapter
can also disable everything emission related and not using the rear 02 as i dont even have it installed in the car

if you need help for a unrestricted US base i can help you

[B T]

This is for a US ZA1JD00C. My rom is locked by password per the tuner who cannot legally remove those codes any longer in the US. Connection seems to be fine as it will download the entire tune without issue. It's not the first issue I've had with an ECUTEK update beign compatible with my cable unfortunately.

[tomm.brz]

cable needs to be updated sometimes
as i told you i write rr13 without problems
send me a message anyway regarding locked tune can help you maybe

[B T]

ended up having two issues, one on my OBD2 port pins and another error within the ECUTEK software itself still in process of being fixed by the company.

[tomm.brz]

closed loop in rr13 is bugged and hard capped at 12.49 afr
burble is just shitty useless
can t set blinking CEL to monitor knocks
i give up and go back to rr12.3

[B T]

Zach has been working through the bugs. ECUTEK seems to have fixed the issues we were having and now it pulls like a beast even though we still have a ways to go on tuning.

[mikalem]

Anyone with RR13 doing self tuning? Was on 12.3 flashed to a non-US ROM because of a legacy Flex Fuel solution, but like an idiot decided that I should "do the right thing" and get the CANBUS interface and replace the legacy O2 solution. Tried getting RR13.3 up with the ROM I was using (Japanese 2019 Manual) and had issues with the ignition timing once warm going to 60 degrees of timing and just staying there. Asked ECUTek support about it and they wanted to first get my car back to a "supported" state and get it reflashed to the US based ROMs, which are locked down for no *real* good reason other than.... lawyers.

Worked with ECUTek to get the ability to force reflash back to my original ROM (2020 BRZ Manual) and asked for which ROM they have tested the best with that was compatable. They replied the K10C ROM was the right route to go.

Got all of that figured out, looked at RR13.3, which they completely changed a bunch of tables and structures on, thought I got it figured out and working - CANBUS sensor was wired up and working correctly, car started and warmed up fine...... until I go to press the go pedal, then ignition timing jumps to 60 degrees and just stays there until I let off and it goes back to idle timing. So either, it's way bugged or I have just completely misunderstood their new table structures when I was moving things over for FF. Needs more documentation at the very least. So now, I'm stuck with tuning on a US based ROM, so in order to not through a bunch of codes with 12.3 I have unplug the flex sensor, and put the secondary O2 sensor on the car..... into a UEL catless header which will still throw codes. Big PITA to be "compliant" with the EPA. B_T, do you know which version of RR13 Zach is using? I'm wondering if this is just something they shouldn't have let the Retail RaceROM crowd into yet because of the massive change and complete lack of documentation.

[tomm.brz]

i can give you a us rom base with the things you need set already set
i mean i do not have the restriction

If you want to use racerom13 go back to US roms as ecutek is focusing more on american roms
i d like to use rr13 on my car but it's been a waste of time
You ll encounter less bugs

[mikalem]

Originally Posted by tomm.brz

i can give you a us rom base with the things you need set already set
i mean i do not have the restriction

If you want to use racerom13 go back to US roms as ecutek is focusing more on american roms
i d like to use rr13 on my car but it's been a waste of time
You ll encounter less bugs

Figured out how I could get around this in RR12, so all good there. They've done something to the RR update procedure for 13 though, so the same trick to disable the codes before opening in EcuTEK doesn't work - means I get to try out O2 sims, or get a different header before I try to hop to RR13. I love my government <eyeroll>.