Good to hear.

One other thing to bear in mind is that my RAX Patch "baro" variable loses resolution compared to the normal Baro that you're logging. It will therefore be a bit more coarse in its values. If you log the two together on a drive to the coast, the RAX version "baro" will have a more stepped graph.

That's all fine - it's just because it is rescaled to align with the Boost Target table scale.

Rich

 

Big new patch added. See here for details:

https://www.evolutionm.net/forums/ec...t-logging.html

Rich

 

^^^just downloaded. will try it tonight!

 

Any chance you could post up a zip file of all the patches so those of us that see a lot of different roms could just download the whole pack at once?

 

That's how it works now. There are only 2 download files -v1 and v2. I just reference them per ROM ID so people can choose their ROM from the list.

Rich

 

Could anyone help me with a stock rom from Rich's list ?

I want to compare the sub-routines with my Triton rom to see if I can get the RAX fast logging working.

My ECU is almost identical to EvoX...

 

Check these out...

http://norcalmotorsports.org/users/b...ch/ROMs/Evo10/

Rich

 

Awesome, Thank you

 

IMPORTANT

Please be aware that a number of people are experiencing ECU-flashing problems. References...

http://www.evoxforums.com/forums/showthread.php?t=71479

http://www.evoxforums.com/forums/showthread.php?t=71268

We don't currently know what is going on, or why. But given that RAX Fast Logging requires updating to EvoScan 2.9.0023, I'm concerned that a lot is changing at once with [a] ECU processing, [b] Reading/Clearing DTCs, and [c] Logging. Multiple things are changing at the same time, which is bad news from a diagnosis point of view.

If you are planning on applying RAX Patch, hold off for now... until we have a handle on this thing.

It may be nothing to do with any of the above - pure conjecture at present. I'll post an update when we're on top of it.

Rich



My list of peoples' usage... will update as I see 'em. Perhaps some pattern will emerge.

(ROM / EcuFlash / EvoScan / RAX?)

"NO ISSUE" PEOPLE
53610013 / 1.43.3150 / 2.9.0023 / RAX / ES+EF never open together - richardjh
58010005 / 1.43.3252 / 2.9.0023 / RAX / ES+EF never open together - momostallion
58020005 / 1.43.3252 / 2.9.0023 / RAX / ES+EF never open together - Section212(EvoXForums)
53050109 / 1.43.3252 / 2.9.0023 / RAX - RS200Z(EvoXForums)
56890013 / 1.43.3252 / 2.9.0023 / RAX / ES+EF never open together - Drkramm

"WEIRD ISSUE" PEOPLE
5690000? / ? / ? / ? - weebles(EvoXForums) [See NOTE 1]
55580005 / 1.42.???? / 2.8.???? / No RAX / ES+EF open together - Vutall(EvoXForums) [See NOTE 2]
58020005 / 1.43.3252 / 2.9.0023 / RAX / ES+EF open together - khaydin(EvoXForums) [See NOTE 3]
55590107 / 1.42.2595 / 2.9.0023 / RAX / ES+EF sometimes open together, but not often - sstevojr [See NOTE 4]
52690122 / 1.43.3252 / 2.9.0023 / RAX / ES+EF open together - black_e(EvoXForums)

NOTE 1: weebles had EcuFlash report a crc error 60% through the flash.
NOTE 2: Vutall's tuner said the OEM ROM was corrupt.
NOTE 3: SST was acting up. Fixed by dealer without reflashing ECU.
NOTE 4: Excessive SST CPRU tuning settings caused ETACS warning on startup, battery died, ECU fried during bench process, slipped on banana peel, got foot stuck in bucket, attacked by bees.

 

it might be worth noting which rom ids people are having issues with.

i can say i just flashed this patch last week. i've flashed 4x since the patch with out issues.

my rom is 58010005 (gsr)
i use ecuflash to flash only. version 1.43.3252
i use evoscan to log. version 2.9.0023

i make sure nothing else is running when i flash and my laptop battery is in no danger of dying. i also make sure the openport connected successfully before flashing.

mo

 

I got in a good half dozen flashes before the whole issue started.
I thought it was a voltage issue originally, and replaced the battery. But then it happened 2 more times since the new battery (a total of 5 times in 3 days). It doesn't go into "fan cycling/bricked mode" but gets stuck at the ACC "clicking" stage and won't come out (with a xmas dash and not able to hold an idle, sounding like only 2 or 3 cylinders). I can revert it back to the last "safe flash" but any others (including making a single change to the safe flash) casuses complete havoc.
Friday I'll be taking the car down to RRE to see if we can dig into it a bit more. I'm apprehensive about flashing at home any more, as I don't have a benched-ecu station set-up.

 

I'm using 1.43.3252 and Evoscan 2.9.0023

 

I'm also using 1.43.3252 and Evoscan 2.9.0023. Pretty sure I had Evoscan open in the background while flashing as I use that to clear the SST codes after the flash before turning ignition off. That's been my routine since I got my car and I've done more than 30 flashes without serious issue till now. I've done 2 previous flashes using the new RAX Fast logging patch.

For me my issue is that ever since my last flash the gear lights blink every 10 seconds or so and if I try to drive around it feels like everytime the gear lights blink the clutches open up and re-engage the same gear. When driving in manual mode the car will sometimes upshift and downshift on its own.

One weird thing that happened before the flash that broke my car was that I plugged in my tactrix cable and windows re-installed the driver for it. Not sure why it did that as I haven't updated Ecuflash or Evoscan in several weeks.

I haven't really had a chance to do anything with the car since this happened due to the holidays, it's just sitting in my garage for now. I've tried flashing back to stock and other previous maps. My ECU isn't really bricked as I can freely flash it and start the car/drive around. I'm hoping that it isn't the TCU, really don't want to have to get it towed to a dealership. I'm going to try to bench the ECU tonight.

 

Details updated above. Thanks.

Rich

 

both evoscan and ecuflash only open the ftdi usb port when you click "start datalogger(evoscan)" or "write rom(ecufash)". and then they both close the ftdi usb port when you press stop datalogger, and when completed writing the rom. so that rules out the cable in use at the same time, the only other possible thing in use at the same time is the binary rom file. both map tracer and ecuflash can open the rom at the same time. evoscan is only programmed to lock and edit the rom when you press ctrl+ or ctrl- to move the timing or afr values up and down on the map tracer. hope that helps.