RomRaider

thats what i cant find. Sorry i suck. I attached it for reference. I use carberry 4.2 mapaxis

It looks like the LTV process is picking up on the stock version of that ECU ID. You can see that in the LTV output in the vehicle description and that's why the AF ranges are being interpreted as stock.
You could try changing the conversion in the ecu_defs.xml to that of the SD value.
Change this:
to this:

this will mess up any other ROM using this common table def.
Also, it will not change the A/F Learning units as this is hard coded in the table title.

Interesting. I didnt think i even had the ecu_def.xml in my manager. But i may have added it last year when i was looking at an 04xt rom

thank you

Hello,
I am sorry, I am sure I made a mistake somewhere, but I cannot get the learning tables for my D2WD701C.
I tried to apply all the instructions from the first page.
There is certainly something I missed, but I don't know what.
I can open the rom with romraider, I can log with the logger but the learning talbes give me the message:
ECU Definition not found or undefined. Learning Tables cannot be properly retrieved until an ECU definition is defined in the Editor's Definition Manager.
I downloaded the logger_METRIC_EN_v336 xml and added it to the Defnition file manager in the ECU editor.
Thanks
Guillaume

These two things do not match. Logger def is for the Logger, ECU def is for Editing.

http://www.romraider.com/Documentation/ ... rFAQ#toc17

Thanks for your support,
I checked everything.
Now I got one step further, I don't have this message, but an other one:
please check that the ignition is ON, that the cable is connected, that the USB is plugged...
Just before opening the learning table menu, I was datalogging the parameters, so the connection is OK.
I tried it with the engine running and the engine off, but always with ignition ON.
Datalogging has always been working well.

Thanks in advance

Can you provide the rr_system.log?
http://www.romraider.com/RomRaider/HowToDebug

Hi,
Here is the file,
I hope it will be helpfull

Guillaume

Your car is a 6-cyl. It has extra AF parameters and this is causing the query for AF info to be too large for the ECU to respond to.
This will be fixed in the next release.

In the meantime you could try commenting out a few of these parameter sections from your logger.xml file to make the query smaller until it works.
P2("P2"), // ECT
P11("P11"), // IAT
P17("P17"), // Battery Volts
P24("P24"), // ATM
Start by removing the ones you care lease about.

I get the results of the learning tables now.
Thanks.
but strange values:


So I imagine, like a few post above that the address is not the correct one and needs to be changed.

like this for example: Add these three line of code to the line below E173
Code:
<ecu id="3C4A384106">
<address length="4">0xFF2330</address>
</ecu>


The rr_system.log is attached too.

It's using FLKC parameter E41 as the reference to locate the table, that may not be correct for this ECU. We'll need to find the correct address and set it with E173.

For CAL ID D2WD701C ecu id="3C4A384106" use 0xFF2328 for parameter E173.

Sorry I could not answer earlier.
Thanks for your answer.
I tried to add the following lines to the logger XML:
<ecu id="3C4A384106">
<address length="4">0xFF2328</address>
</ecu>
under the parameter E173:
<ecuparam id="E173" name="FLKC Table Start (4-byte)*" desc="E173-The RAM address of the start of the FLKC table used by Learning Table Values tool" target="1">
<ecu id="2F1A357206">
<address length="4">0xFF2330</address>
</ecu>
<ecu id="3C4A384106">
<address length="4">0xFF2328</address>
</ecu>
<ecu id="2F12795606">
<address length="4">0xFF2690</address>
</ecu>
<ecu id="8B12784007">
<address length="4">0xFF3324</address>
</ecu>
<ecu id="3C0A387516">
<address length="4">0xFF831C</address>
</ecu>
<conversions>
<conversion units="°" storagetype="float" expr="x" format="0.00" gauge_min="-10" gauge_max="10" gauge_step="2" />
</conversions>
</ecuparam>

But with this addition, I get the same bug than previously, without removing the parameters as you said before.
Here is the rr systemlog.
Did I do something wrong? Do you have an idea?

Adding the E173 information doesn't correct for this problem, you still need to ensure the query size is not too big.

I have removed P2, P11, P17, P24, P66, P115, P118, P153.
I will remove some others and try again.

Thanks