[biela]

Hello

Can anybody help with a definition file for 2GGA ECU?
Car is an european Ford Sierra.

Thanks

EEC-IV 2GGA small.jpg

[jsa]

What are your goals?
What software package do you have or wish to use?
Do you have any J3 hardware?

This link might be of help.
http://tunerpro.net/forum/viewtopic.php?t=3325

[biela]

Hello

I want to make a Stage 1 tune. I was looking for fuel maps, ignition maps and rpm limiter.
I was thinking in Tunerpro software.
I have found J3 hardware at moates.

Thanks for the link, but some files are not avalilable yet.

[jsa]

Can you post a bin file out if it?

[biela]

Hello

I am attaching the bin file and a .xdf file created from SAD806x disassembler.

I have named some tables and some functions.

Car is Ford Sierra 2.0 DOCH 125 hp, N9A engine and 1991 year.

[biela]

Hello

Can anybody help to find rpm limiter?
May be at 4D6 or at 552?

Thanks

[jsa]

It will be a value in ROM ABOVE 0x2000.

Have you identified the RPM pid?

[biela]

Do you mean NLM_CL or NLM_SH?

From GUFB.xls
12.1 NLM_CL RPM - Rev Limit - Fuel Cut Off (Fuel Returns)
12.1 NLM_SH RPM - Rev Limit - Fuel Cut On (Fuel Cut)

I see

Code: Select all

Table lookup 
2400	2944	2C7E	3016	3298	36B6	3954	3AF0

but in this bin, the data start at the beginning.

[jsa]

Do you mean NLM_CL or NLM_SH?

Not all strategies are the same as GUFB, so there could be rev limits for different gears and loads for example.
What other strategy documents do you have?

I see

Code: Select all

Table lookup 
2400	2944	2C7E	3016	3298	36B6	3954	3AF0

but in this bin, the data start at the beginning.

Typically rev limits will be a number of word size scalars, not a table.
It does not matter if the calibration data is at the beginning, so long as it is somewhere in the ROM range above 0x2000.

May be at 4D6 or at 552?

Have you found these addresses to contain RPM values by logging?

Your RAR attachment above contains no files, but a quick disassembly of the bin does not show up 4D6 or 552?

If you know the exact rpm value of the rev limit you can work back to looking at scalars with that hex value.
Say 7000rpm limit for example. RPM's are often scaled by 4.
7000*4=28000 decimal or 6D60 hex or 60,6D for endieness.
A quick search turns up that value at line 0x242A.
Line 0x2426 is also close in value.

Another approach is to log registers and RAM to see which addresses respond to engine RPM changes, Then look at what those addresses are being compared to in ROM.

[biela]

Hello

Rename 2GGA.xdf.txt to 2GGA.xdf, please.

2GGA_lst.txt it is a quick disassembly. May be Sub25, Sub65 or Sub95 are RPM limiters subroutines?

Rpm limiter is around 6500 rpm. I made calculations, and found near values in 24D6 and 24d8.

jsa, thanks for your patience.

[jsa]

The xdf and listing appear to have different names for functions?
At 0x282C Function 022 vs Func17
At 0x27F0 Function 020 vs Func52

May be Sub25, Sub65 or Sub95 are RPM limiters subroutines?

Sub25 Comparing bytes not words
Sub65 Maybe not
Sub95 Maybe not

Rpm limiter is around 6500 rpm. I made calculations, and found near values in 24D6 and 24d8

Now find the code where they are compared to a register word value.
Then find where that register word gets used against your RPM tagged functions at 0x282c & 0x27f0.

Alternatively, write lower values to 0x282c & 0x27f0 and see if your rev limit changes. Accept responsibility for whatever happens and proceed with caution of course.