DIY Rom tuning for exhaust pops and backfires W/ romraider

[steve99]

Originally Posted by lizbrayan

Yeah the icons are lit red and blue and the log is all exactly like that. Imma double check the logs after i charge my laptop. Imma also try pushing the pins in a little its just a little frustrating that it worked two days ago and now nothing.

ok if its reading the calid and vin CVN then its talking to tactrix, those parameters I believe are read using standard obd calls via a low speed protocol.


When it wants to read/write to ecu flash memory different higher speed protocol is used. so its possible its the connection.


are you using an obd extension cable, if so keep it short less than a metre, or try without extension cable.


while your having problems always do READ to check connection as you wont get issues if it fails. Wait till READs are good before you try writing.


you did buy a genuine tactrix ? not one of the dodgy chinese ones hopefully.

[lizbrayan]

Originally Posted by steve99

ok if its reading the calid and vin CVN then its talking to tactrix, those parameters I believe are read using standard obd calls via a low speed protocol.


When it wants to read/write to ecu flash memory different higher speed protocol is used. so its possible its the connection.


are you using an obd extension cable, if so keep it short less than a metre, or try without extension cable.

No extension cable just straight connection to the ecu to pc.

Sent from my SGH-T999N using Tapatalk

[steve99]

Originally Posted by lizbrayan

No extension cable just straight connection to the ecu to pc.

Sent from my SGH-T999N using Tapatalk

so tactrix plugged directly to obd port not via obd extension ?


as Reinfield said try bending both rows of pins on tactrix adapter inwards slightly about a 1mm or so, use something like an old full size SD card or similar piece of plastic to keep them in line

[lizbrayan]

[00:02:36.035] using metadata XML ID read_subarush72531brz from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_subarush72531brz.xml
[00:02:36.048] J2534 API Version: 04.04
[00:02:36.048] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[00:02:36.048] Device Firmware Version: 1.16.4769
[00:02:36.048] Device Serial Number: TAze0$hE
[00:02:38.574] reading vehicle info...
[00:02:38.582] CALID : ZA1JD00D
[00:02:38.584] CVN : F94B7935
[00:02:38.591] VIN : JF1ZNAA12F8711771
[00:02:38.710] starting programming session...
[00:02:38.715] turning off DTCs...
[00:02:38.731] turning off unnecessary communications...
[00:02:38.733] unlocking ECU...
[00:02:38.733] Requesting Seed...
[00:02:38.735] interface close
[00:02:38.736] interface close
[00:02:43.125] using metadata XML ID read_subarush72531brz from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_subarush72531brz.xml
[00:02:43.139] J2534 API Version: 04.04
[00:02:43.139] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[00:02:43.139] Device Firmware Version: 1.16.4769
[00:02:43.139] Device Serial Number: TAze0$hE
[00:02:45.014] reading vehicle info...
[00:02:45.021] CALID : ZA1JD00D
[00:02:45.024] CVN : F94B7935
[00:02:45.028] VIN : JF1ZNAA12F8711771
[00:02:45.148] starting programming session...
[00:02:45.150] interface close
[00:02:45.152] interface close

Thats what it gave me in ecuflash. I'm stumped. I going to try to uninstall everything and try again later.

[steve99]

Ok thats a comms issue with ecu

you are waiting about 20 sec ofter you turn on ignition before you hit ok to read\write ?.

either due to physical issue with obd port connevtions, or the ecu is in weird state.

when you originally flashed , did you get ant errors ? , at the end you should get message like flash completed oy ,finished with ecu, and the status bar at 100%.

try the tactrix pins but also try removing a battery terminal and then press brake, reconnect battery and try read of ecu at first turn on of ignition .

[lizbrayan]

Originally Posted by steve99

Ok thats a comms issue with ecu

you are waiting about 20 sec ofter you turn on ignition before you hit ok to read\write ?.

either due to physical issue with obd port connevtions, or the ecu is in weird state.

when you originally flashed , did you get ant errors ? , at the end you should get message like flash completed oy ,finished with ecu, and the status bar at 100%.

try the tactrix pins but also try removing a battery terminal and then press brake, reconnect battery and try read of ecu at first turn on of ignition .

So i tried again a few hours ago and i turnes the radio off and held the tactrix port to the od2 and it worked no problem i dont know if the radio being on had anything to do with it.

Sent from my SGH-T999N using Tapatalk

[steve99]

Originally Posted by lizbrayan

So i tried again a few hours ago and i turnes the radio off and held the tactrix port to the od2 and it worked no problem i dont know if the radio being on had anything to do with it.

Sent from my SGH-T999N using Tapatalk

unlikely it radio but possible, more likely your trying to read or flssh to soon after turning ignition on wait the 15 sec or so

[lizbrayan]

Got this map for a friend stage 1 manual and he wants the pops and backfire as well, trying to do this for him but the map numbers arent matching up to the screenshot. Any help ?

[FRSBRZGT86FAN]

Originally Posted by lizbrayan

Got this map for a friend stage 1 manual and he wants the pops and backfire as well, trying to do this for him but the map numbers arent matching up to the screenshot. Any help ?

Do you know how to use romraider? Make sure the definitions are correct.

[steve99]

Originally Posted by lizbrayan

Got this map for a friend stage 1 manual and he wants the pops and backfire as well, trying to do this for him but the map numbers arent matching up to the screenshot. Any help ?

That map you posted above is an OFT A01C map, but its actually a B01C internally.


If the guy has an oft your going to need to use the OFT romraider defs A01C as thay are actually hacked B01C defs to make it work with the hacked A01C OFT rom/tune that match the tune revision it will likely be a V2 map.


If you flashing with Tactrix use the B01C version of the map and standard romraider defs definitions.


seeing weird tables or axis values means the definition and rom are mismatched and editing will almost certainly end in tears.


If all that sounds like gibberish then I suggest you don't edit the guys map until you get your head around it, as he wont be impressed with a bricked ecu :-)

[lizbrayan]

So just edit the b01c map and flash it and he should be okay? Im using tactrix to flash.

[dhuang]

How on earth did I not discover this thread sooner?!

I'm in love with the popping...

...but it'll probably get old fast :P

I do feel like the engine lugs at low throttle input now. Does it need time to adapt? Or is it just how the modified ignition timing table acts?

[FLESH KILLA]

Originally Posted by dhuang

How on earth did I not discover this thread sooner?!

I'm in love with the popping...

...but it'll probably get old fast :P

I do feel like the engine lugs at low throttle input now. Does it need time to adapt? Or is it just how the modified ignition timing table acts?

I've had a more aggressive version of this flashed for about a month now. The throttle lag seems to have smoothened out some (not as harsh) but is still noticeable. It does makes the muffler drone a bit at times but nothing unbearable. All in all I'm pretty happy with the results. It's nice to be able to control the pops with the throttle. Keeps my car from making popcorn at every red light lol

Sent from my Nexus 6P using Tapatalk

[dhuang]

Already reverted after 3 days.

Will save the backfires for when I go turbo. :P