merlin.oz

The posted xml for 401702 has now been updated to fix the missing scalings that Raptord noted.

In addition, the AYC section has been revised and some tables added. Table M has been renamed Table X ATM with some new M Tables added (as they follow the N-tables in the ROM). These should all be treated as speculative at the moment. The three AYC final current drive tables are solid though. Note that these three tables do get tuned in the Ralliart roms.

Raptord

iTrader: (10)

Thank you sir!

Floppyz

Headake!

merlin.oz

General AYC table info update:

Have identified most of the tables involved with AYC, its a bit complex.

There are two groups of matching tables, presumably one for accel and the other for decel.
Each group has 15 tables and Ralliart tuned ten tables in each group.

There is the Drive-Sum group of three tables, which seem to set the peak current.

There are another 28 tables, which include three sets of Tarmac/gravel/snow tables, the remainder are function unknown ATM, though I have worked out what the axis are for some of them. There are only eight tables in this group that Ralliart tune.

In summary, Ralliart have been tuning 28 AYC tables in their ROMs, I can only hope we do get to understand this area better as there is a lot going on in there.

joseph143

iTrader: (8)

I wish i could be helpful in disassembly... I thought what we had was it when this started... Granted none of my cars have ayc... Have you tried to figure out where acdtuning gets there 6map tuning from? It would be really interesting if we could allow for more then the 3... Not that its truly necessary

merlin.oz

A colleague of mine on this ACD stuff has developed a six-map version, still in the developmental stage though.

turboand

Just for fun, here's a 401000 rom pulled from an E7 RS2 JDM (non AYC)
...I think it may be tuned

burgers22

Just a little Corky.......

burgers22

Great work Merlin and all the devs- I'm just updating the 400021 xml to match your format and in doing so found the time constant scalling may be off as it reads 0.40 where the text says 4.00?

changing to the following allows the map to match the text

<scaling name="TimeConstant" units="Sec" toexpr="1/x*13177" frexpr="1/x*13177" format="%.2f" min="0" max="20" inc="0.01" storagetype="uint16"/>

merlin.oz

The text is probably wrong, as at one time I was using 1/x*13177.

When we started logging we realized i was out by a factor of ten. So, probably not all the text was correctly edited.

We knew there were some lengthy delays in there (somewhere) on some conditions.
Later on learned that most if not all the multipliers/adders were filtered, but with quite short delays, typically 0.1-0.2 seconds. But only a few at the end of the calc have the longer delays.

Logging the current showed the error.

Has anyone been using the EvoScan logging xml I included in the definitions?

burgers22

Ah - cool. Thanks for the feedback

joseph143

iTrader: (8)

For the people that have ran a wire from the acd ecu pin to the obd2 connector... Have you tried reading, writing, and logging with the 1.3u cables? Or does it have to be 2.0? It would be nice if 1.3 would work for the cheaper of us to still be able to flash...

TougeGod7

iTrader: (2)

can someone do a write-up, preferably with pictures, of how to connect the wire from the acd ecu pin to the obd2 connector? i know its super simple, i've just have always been scared of electrical

Raptord

iTrader: (10)

It's very simple Touge. You just need to connect a wire to pin 25 on one of the connectors going into the ACD ECU (hopefully you have small hands). The other end of that wire will go to the single pin in the reflash connector of your OBD2 cable. Then you just plug the OBD part of your tactrix cable to the OBD port under the steering wheel like you normally would for using evoscan/ecuflash.

See this post for pics: https://www.evolutionm.net/forums/ec...789-acd-2.html

TougeGod7

iTrader: (2)

ok that is easy. does this effect flashing/reading the engines ecu?