Ford EU EEC IV&V specificities

Tuning specific forum for all of Ford European and Australian specific tuning

Ford EU EEC IV&V specificities

Unread postby Pym » Sat Mar 04, 2017 5:04 am

Hi all,
I have just joined this really interesting forum to continue my work, started since several weeks on some EEC IV&V European, not previously studied ecus.
I am based in France, and after some searches, I have understood that for cars I am working on, people in western Europe are progressively replacing the standard management for other things, often Megasquirt based.
It is not my wish, even if no one, around me is really able to tune something like an EEC IV management.

I think many things can be done on this hardware and I want to do it.
For now, I am essentially working on a specific EEC IV 0FAB program, because I have 3 different versions, well tuned or not and because the related car can really be tuned, compared to my EEC V cars.
So my first job it to create the best strategy/definition for this program and I have well progressed.
But I have to admit that we are really far from Ford A9L standard, because it is an European car coded by Europeans, or a strange car, I do not know.

So if you have any advice, information on how EEC IV European programs were written, you are welcome.
Thanks
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby decipha » Sat Mar 04, 2017 9:36 am

sailorbob is out in the UK, if anyone has done anything with those ecus it would most likely be him, maybe he will reply here

what are the 3 catch codes and hardware codes of your eec-4s ? what about the codes for your eec5?

what vehicle, engine, and trans are they for specifically?

can u post the bin files?
User avatar
decipha
Tooner
 
Posts: 14285
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Sat Mar 04, 2017 10:49 am

Yes I know that more people in the UK have tried/worked on this subject, but as I was saying,
result is often the use of magneti marelli, megasquirt management or more expansive solution, so...
In France, I only know 2 persons having read the code without a great success. Others are still talking about EEC (without OBD) as a black box without interest.
I am currently working on catch code 0FAB, with 3 versions standard, stage 1 & stage 2. Hardware code should be EFI-VM120.
I have also at disposal following ECU in cars : EEC IV (91 Fiesta 1AFA / EFI-SD111), EEC V (97 Mondeo TICK / ?, 98 Cougar USES / MLF-4G7, 97 Puma DUDE / LP2-110).
I only have with me the 0FAB binaries, still not read others. I wanted to begin with the 'simplest' one.
0FAB is for a 90-91 Fiesta RS Turbo, 4 cylinders, 1600cc, Manual.
This is I think one of the first EFI EEC IV cars in Europe (like the 1AFA one).
What is interesting is this strategy, is that it is essentially based on a MAP sensor (+TPS +ACT +ECT +...), but no MAF sensor or Lambda sensor at all.
This is the main difference with an Escort Cosworth EEC IV, in addition with the fact that it was not written by the same persons.
But it should be the same thing than for the 1AFA one, even if 1AFA is using a digital MAP sensor compare the the analog one on 0FAB.

Is this legal to post Ford or other binaries ?
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Sat Mar 04, 2017 3:07 pm

Sailorbob did the escos def. PM him to see if he has done any of yours.

A single hardware code can run multiple strategies. The catchcode like 0FAB and others in that series are tied to a single strategy requiring a single definition.

Leagal, you would have to ask a few lawyers, never seen a copyright claim by ford on the eec-iv code. Besides it is for your education.

What information and dissassembler are you working with?
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Sat Mar 04, 2017 5:24 pm

Thank you John,
I was thinking about the same thing some time ago, the ability to run a single strategy and a single definition on ECU codes related with similar engines and periods.
It is clearly the case for early EEC IV on American market and probably later on EEC V on European one. But it is only, when an engine has been declined in mass, on multiple vehicles, with small differences in setup and time.
I have looked at the strategy, with def made by Sailorbob, the one your are using and it is limited to a specific vehicle/engine, even if ford was able to use it for following zetec engines.
And nothing common with my strategy, even if the main part of sensors are common, even if period is the same, ... I think people from Cosworth wrote it, even for the EEC IV version.
The most approaching catch code for the same car, should be the 0FAC one (using a digital MAP sensor and different connections to the ECU), but I am pretty sure that it will not use the same strategy (I have none under my hand to compare).
I have just compared with 1AFA & 1ADA binaries, still for CVH 1600 EFI engines of same period and result is the same, nothing common (nothing in the same place).
I was just expecting to find the same logic, the same table construction, between this similar engines, but no way.

Do you have any idea about the software used by Ford to create these strategies ?

I am working with SAD and all the information that I can collect.
But the major advantage that I have, is to know global differences between the binaries that I am studying. I will provide them, no one will complain about it, you are right.
0fab has a security cut over 8psi.
Stage 1 remove this security cut and changes ignition advance (tables at 2fd0, 30d0 and 31d0).
Stage 2 adds to Stage 1 reduced fuel map (for bigger injectors) (table at 2ba6), different injection timings (table at 2e34) and another version of ignition advance.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Sun Mar 05, 2017 3:52 am

Ford used some inhouse software.

Run the Bill Lawrence dissassembler on them as well, it sometimes works in areas where SAD does not initially work.

Ironmanisaneamic has a collection of info.

viewtopic.php?f=30&t=1414&p=15817#p15817

https://drive.google.com/folderview?id= ... sp=sharing
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Sun Mar 05, 2017 5:50 am

Thank you for information. Plenty of additional documents for me.
I have also tried Bill Lawrence disassembler, which gives me as result a more complicated information to decode.
Hopefully SAD seems to work well on my binaries and when I have doubt, I force it to decode everything and I check op codes.

You make me reflect on this link between strategies & hardware. I was only comparing binaries from same period and using a similar EFI type.
I will try to extend this to hardware codes with existing 88 VM120 (0FAB, 0FAC, 8GEA, 8GDA, ...), previous generation 85-87 VM11X (G2A, 8GCA, AA, BA, 5GAD, 6GBB, ...)
and the next ones 89-91 SD11X (1AFA, 9AAA, ...), 88-92 SD13X-SD23X (8BAB, 8BAC, 8GAB, 2BAA, 2GEA, 2BGA, 2BHA, 2BJA, ...). Just the time to get samples.
Result should be logically better than comparing with a SMD-490 or a totally different code.

Any idea about the meaning of hardware codes, characters for pure hardware, numbers for pin-out, for example ? VM110 code applied to a SD130 ecu will not work at all ?
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Sun Mar 05, 2017 2:18 pm

Found SD230 2GEA, many things similar to VM120 0FAB, but a different strategy (seems more evolved for me, more tables, more functions).
SD230 2GEA is based on the same car / same engine than VM120 8GEA, but as you know Ford, certainly differences on sensors.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Sun Mar 05, 2017 3:00 pm

I suspect there is some meaning to the hardware codes but I've got no info on that. Compilling info about a lot of hardware codes might allow a pattern to be recognised.

GHAJ0 run on SMD-190 and SMD-490, with wiring pinouts changed to suit the hardware internal layout. The 4 catchcodes under GHAJ0 are all the same software layout with some different values for certain parameters.

The code in close hardware cousins is very different in the layout of instructions and parameters. The wiring pinouts are very similar though. Essentially Ford tweaked existing hardware to run GHAJ0. There is an above average chance they did similar for other RS or low production number performance cars. Dictated by economies of scale.

So yes it could be possible to run your code on other hardware or vice versa. I think it less likely that code from other strategies will be similar to your code. Start with other speed density applications as anything with a maf will be very different. Have you compared C1A1 from a 2.3 mustang?

If you do collect bins from all those, pop the lids a take photo's of the hardware. It would be interesting to look at.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Mon Mar 06, 2017 11:09 am

I just looked quickly at C1A1 binary and its strategy is really different from mine (and SAD has suffered).
You will find picture of EEC I had outside cars, a little bit burned EECIV VM120 and an EECV LEE101 (JOKE for 96 mondeo 1800cc).
On EEC IV, I first think white cards are analog converters, but I will check on EEC IV reference. But no chance, their codes seem not corresponding with binary registers.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Tue Mar 07, 2017 3:36 am

Here's some pics and bins I have laying around.
You do not have the required permissions to view the files attached to this post.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Tue Mar 07, 2017 3:41 am

Are you aware of this list of addresses where scalars, functions and tables start?

Code: Select all
2022: 00,24             word  2400
2024: 30,26             word  2630
2026: 82,29             word  2982
2028: 02,2e             word  2e02
202a: 34,2f             word  2f34
202c: a4,37             word  37a4
202e: 56,3a             word  3a56
2030: 86,3e             word  3e86
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Tue Mar 07, 2017 4:59 am

For now I have understood this list of addresses as relative pointers (essentially for scalars), creating a kind of groups of predefined values.
Documentation indicates them as Hi Byte vectors, meaning they could be updated directly. It has to be checked.

Have you looked at VM120 simplicity ? Nothing common with smd490. No EEC IV document can a such thing. I will look at files you have provided.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Tue Mar 07, 2017 6:01 am

They do not change, they are in ROM.

Yes, nothing much in the box. Most eec-iv seem to be fairly basic from what I've seen. SMD 490 is an outlier to some extent.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Tue Mar 07, 2017 7:52 am

You have forgotten
Code: Select all
2020: 08                byte  8
2021: 01                byte  1

which is in fact
Code: Select all
2020: 08,01             word  108

not in rom.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Tue Mar 07, 2017 1:32 pm

Not fogotten, just didn't mention.

How many addresses in the list in my previous post?

Is there an opcode with 0x2020 as an argument?
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Tue Mar 07, 2017 2:27 pm

You have described 8 "pointers" or "vectors" and this is always present as far as I can see.
I was trying to match them with EEC IV pocket reference, providing fixed addresses for this group from 0x2020 to to 0x202E, but inappropriate for 0x2030.
0x2020 is always used one time, as byte, but yes, I see no real interest on it. Pocket reference is not really useful in this case.
To finish on these addresses, they are useful for SAD & for us to identify and to group some scalars, knowing the value of the first pointer, is always a pointer to the second and so on.

Anyway, actually my current issue is differentiate the Load information from the MAP/BAP information.
14/21 identified tables in these binaries that I link directly to "MAP/BAP", but only one that I link to "Load". Really strange compared with other strategies, I should be wrong somewhere.
Same thing for ACT vs ECT. These registers [10X] => [43X] are really difficult to identify at 100%.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Tue Mar 07, 2017 3:03 pm

I don't think the pocket reference is relevant as the list is in different locations in different strategies.

Air density calc needs MAP and temp. Load calc needs air density and rpm. Hence speed density. Beyond that Ford are cross checking, correcting or adjusting for transient.

8061 general registers start at 0x12. Many of R12 to R43 are likely scratch or temporary, so they are only valid for the life of a single subroutine or part thereof.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Tue Mar 07, 2017 5:47 pm

Yes, I still have some work to do and with many comparisons. I should receive more EEC in the next weeks.
Do you have more details on these registers, not named by sad, but with an output like [104], [3ff] ? They are those that I can see starting from [102] to end around [434].
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Wed Mar 08, 2017 3:46 am

For 8061 R0 to R11 have a fixed purpose as per the pocket reference, beyond that they are strategy specific except for a couple blocks as outlined in the pocket reference.

I would need to do the complete disassembly for you to tell you what a specific register does.

It just happens that a small number of registers from R12 up are usually scratch registers in strategies I've seen detail on.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Wed Mar 08, 2017 6:17 am

In parallel, I am looking at the ANTI binary, which as real clean definition. It helps.
Some remarks :
- Compiler/Assembler has clearly changed since VM120 (probably still Vax Cross Assembler, but in a different version at least for this hardware output).
- As result, tables, functions and scalars are put (groupped) at the end of binary. That is really clean.
- Much more pointers are used for addresses for tables, functions and scalars, instead of directly using addresses in routines. Same thing cleaner, but more complicated to follow.
I add some information on Vax Cross Assembler & tools used 25 years ago.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Wed Mar 08, 2017 3:09 pm

Sailorbob has already done all the hard work on CARD, QUIK, COSY and ANTI, and provides a definition for them. I will leave it to him to decide what specific detail he is prepared to divulge publicly or privately.

Looks like 3 versions for VAX input files. I can't imagine a version specific to every hardware code.

Seems like good money for that era, EEC developer is somewhat of a charity job these days ;).
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Wed Mar 08, 2017 5:18 pm

Thing that is interesting is this Vax Cross Assembler flowchart, is to understand it was working like current compilers.
The 3 (or more input files) were probably
- a core code / framework (common to all EEC programs or dedicated to a specific hardware)
- a specific strategy / vehicle code (with a bit coder liberty)
- a constant file for tables, functions & scalars
The 3 (important) output file were
- the complete binary
- the vector file (for coherence I suppose)
- the addressed constant file (to be used in simulator and to permit updates inside the same strategy)

It is a bit more complex when we have only 1 file !

Just a question John, I am using a 2.5bar MAP sensor (0 - 5v) from a T25 Escort. For me all Sierra & Escort Cosworth have always used 3bar (2.5 for last Escort T25) analog MAP sensor.
Do you confirm that they have never used digital ones ?
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Wed Mar 08, 2017 6:41 pm

The T25 MAP is 5V 50% PWM varying frequency up to 255Hz.

It is not varying voltage. I think the read only GHAJ0.CRY on eecanylizer.net shows the transfer function. If not, I can paste up the transfer function.

All Weber controlled Cosworths got varying voltage MAP sensors.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Thu Mar 09, 2017 1:13 am

Please find attached the technical description of this 2.5bar MAP sensor. Should be a T35 P8 reference with the Bosch EV-1 connector.
What is strange, is when you apply a 12800 divider to the MAP transfer function in GHAJ0 strategy, you match properly a voltage.
I have also forgotten early Sierra Cosworth, using a 2bar MAP sensor, same than the Fiesta RS one.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Thu Mar 09, 2017 3:47 am

Is the Marelli sensor 10bit?
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Fri Mar 10, 2017 11:53 am

10bit? what do you mean ?

I add another photo for EECIV VM120, from a Sierra 2L OHC 8GEA. Hardware is exactly the same, even if some chips have changed (just the maker).
But nothing similar between 0FAB & 8GEA for the strategy. I was not expecting it.
I add 2 binaries (EECIV 8GEA & EECV JOKE). It was a good idea for me to start working on EEC IV, EEC V is another world (for now).
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Fri Mar 10, 2017 12:56 pm

10bit resolution sensor output.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Sat Mar 11, 2017 11:26 am

In ANTI binary, sensor conversion function works on 2 bytes, 16 bits, I can not say more on it.

I add another photo for EECIV SD130, from a Sierra 2L DOHC 8GAB (real EFI this time). Hardware is different, it could do the job, but Pin-out that I can see is not the same.
Strategy is not the same than for 0FAB, but it's close to it, really. Tables, functions & scalars are not in the same place, not with the same size, but everything is organized in the same way.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Sat Mar 11, 2017 1:37 pm

You said OFAB used a Marelli MAP sensor, which would have to be Hooked up to an analog in. EEC analog ins are 10 bit ADC giving 1024 possible values. For best results the Marelli needs to be pure analog or at least 10 bit DAC on tbe output.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Mon Mar 13, 2017 5:25 am

Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Mon Mar 13, 2017 10:32 am

The MAP transfer function I have identified for 0FAB, seems to match this range 0 to 1023, but it could be also the TPS. I have to validate it.
Thank you John, for the eBay link. I had already thought it was a good idea to compare with 0FAC, just to differentiate the MAP transfer function.
But I prefer read one that is at 30km from me, instead of buying one. Just the time to do it.
0FAC mngt uses a digital MAP sensor (2bars), the same hardware than 0FAB and globally the same Loom Pin-out except for interesting elements :
- MAP signal is on Pin 27 (behind a suppressor) on 0FAB, on Pin 45 on 0FAC.
- CO adjust is on Pin 8 on 0FAB, on Pin 27 on 0FAC.

For now, with the elements I have, I am comparing with 1ADA (CVH 1600 EFI) binary, which has few differences with 0FAB one.
1ADA uses SD102 hardware, with a Pin-Out with few differences (but more in binary, because of hardware) and like 0FAC, a digital MAP sensor.

And your were right John, like GHAJ0 strategy, the 0FAB one (probably 0SLTXA) are part of really specific strategies, for a small number of vehicles.
But they are still adapted from classical strategies. For example, external EDIS ignition (4 cylinders) is classically managed by 3 main tables, often 13x13.
For 0FAB, these tables are 16x16, what really was the interest ? A standard strategy will give the same result, in my idea.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Tue Mar 14, 2017 1:46 am

Yeah TPS would also be 10 bit.

Yeah, why buy when you can try for free.

What is pin8 on OFAC?

I wonder if interpolation and transient calcs got better later on allowing a table size reduction.
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Tue Mar 14, 2017 12:21 pm

Sorry, it was a mistake, 0FAC uses a 2b5 digital MAP sensor (not a 2bar one).
I am always thinking about 2bar MAP, because no one I know, is able to use more than 0.9b boost on 0FAC mngt, with a chip.
And for Pin 8 on 0FAC, there is nothing, same thing for Pin 45 on 0FAB.
For table size, it should be a choice (strange) fro this strategy. XR2i and 1.6i with the same production dates are using smaller tables.
0FAB is clearly based on 1AFA (SD111) / 1ADA (SD102). 1AFA and 1ADA are using the same strategy. I will provide them quickly.

Now lets talk about disassembly code. I think that I have understood, why I was not able to simply find the source of the analog information.
Registers are filled with analog information, by a loop, through a single method and based on a table like thing with channel numbers and register addresses.
Have you ever seen such things before ?

Code: Select all
  Sub16:
                                  R20 = 40fe;
625c: ad,02,24          ldzbw R24,2          R24 = (uns)2;
625f: 20,23             sjmp  6284           goto 6284;

  Sub28:
6261: a1,3c,04,24       ldw   R24,43c        R24 = 43c;
6265: a1,64,40,20       ldw   R20,4064       R20 = 4064;
6269: ef,04,00          call  6270           Sub76();
626c: 91,20,f5          orb   Rf5,20         Rf5 |= 20;
626f: f0                ret                  return;

  Sub76:
6270: 65,0e,00,20       ad2w  R20,e          R20 += e;
6274: 89,0c,41,20       cmpw  R20,410c       
6278: db,f5             jc    626f           if ((uns) R20 >= 410c) return;
627a: 4a,25,a2,22       sb3w  R22,Ra2,[R24++] R22 = Ra2 - [R24++];
627e: 35,f5,03          jnb   B5,Rf5,6284    if (!B5_Rf5) goto 6284;
6281: 3f,23,ec          jb    B7,R23,6270    if (B7_R23) goto Sub76;
6284: a2,20,36          ldw   R36,[R20]      R36 = [R20];
6287: af,20,06,22       ldzbw R22,[R20+6]    R22 = (uns)[R20+6];
628b: 66,22,36          ad2w  R36,[R22]      R36 += [R22];
628e: 56,36,00,36       ad3b  R36,0,[R36]    R36 = [R36];
6292: de,44             jlt   62d8           if (0 < [R36]) goto 62d8;
6294: fa                di                   disable ints;
6295: ff                nop                 
6296: b0,36,04          ldb   R4,R36         AD_CMD = R36;
6299: a3,20,02,36       ldw   R36,[R20+2]    R36 = [R20+2];
629d: af,20,07,22       ldzbw R22,[R20+7]    R22 = (uns)[R20+7];
62a1: 66,22,36          ad2w  R36,[R22]      R36 += [R22];
62a4: 46,36,a2,22       ad3w  R22,Ra2,[R36]  R22 = Ra2 + [R36];
62a8: c3,24,fe,22       stw   R22,[R24+fe]   [R24+fe] = R22;
62ac: a3,20,04,36       ldw   R36,[R20+4]    R36 = [R20+4];
62b0: 47,20,08,00,22    ad3w  R22,0,[R20+8]  R22 = [R20+8];
62b5: df,02             je    62b9           if (0 != [R20+8])  {
62b7: c8,22             push  R22            push(R22); }
62b9: 31,98,06          jnb   B1,R98,62c2    if (B1_R98)  {
62bc: a2,36,22          ldw   R22,[R36]      R22 = [R36];
62bf: fb                ei                   enable ints;
62c0: 27,ae             sjmp  6270           goto Sub76; }

62c2: 33,0a,fd          jnb   B3,Ra,62c2     if (!AD_RDY) goto 62c2;
62c5: b0,04,22          ldb   R22,R4         R22 = AD_LO;
62c8: b0,05,23          ldb   R23,R5         R23 = AD_HI;
62cb: fb                ei                   enable ints;
62cc: 61,c0,ff,22       an2w  R22,ffc0       R22 &= ffc0;
62d0: 08,01,22          shrw  R22,1          R22 = R22 / 2;
62d3: c2,36,22          stw   R22,[R36]      [R36] = R22;
62d6: 27,98             sjmp  6270           goto Sub76;

62d8: fb                ei                   enable ints;
62d9: 45,ff,7f,a2,36    ad3w  R36,Ra2,7fff   R36 = Ra2 + 7fff;
62de: c3,24,fe,36       stw   R36,[R24+fe]   [R24+fe] = R36;
62e2: 27,8c             sjmp  6270           goto Sub76;


and the table (logically not recognized by SAD)

Code: Select all
4064: 83,74             word  7483

4066: 03,40,f2,80,2f,04,83,78 ??   3, 64,242,128, 47,  4,131,120  16387,-32526,  1071, 30851,
406e: 03,02,f1,00       ??      3,  2,241,  0    515,   241,

4072: 32,00             word  32

4074: 3c,00,6a,01,7c,7c,00,00 ??  60,  0,106,  1,124,124,  0,  0     60,   362, 31868,     0,
407c: 39,80,f0,85,0b,00,00,00 ??  57,128,240,133, 11,  0,  0,  0 -32711,-31248,    11,     0,
4084: 66,01,8a,00,00,00,00,00 ?? 102,  1,138,  0,  0,  0,  0,  0    358,   138,     0,     0,
408c: 00,00,33,00,00,00,6c,01 ??   0,  0, 51,  0,  0,  0,108,  1      0,    51,     0,   364,
4094: 7c,00,00,00,4a,80,f7,85 ?? 124,  0,  0,  0, 74,128,247,133    124,     0,-32694,-31241,
409c: 36,00,00,00,6e,01,7c,00 ??  54,  0,  0,  0,110,  1,124,  0     54,     0,   366,   124,
40a4: 00,00,00,00,e1,85,38,00 ??   0,  0,  0,  0,225,133, 56,  0      0,     0,-31263,    56,
40ac: 00,00,70,01,7c,00,00,00 ??   0,  0,112,  1,124,  0,  0,  0      0,   368,   124,     0,
40b4: 00,00,00,00,39,00,00,00 ??   0,  0,  0,  0, 57,  0,  0,  0      0,     0,    57,     0,
40bc: 72,01,7c,00,00,00,00,00 ?? 114,  1,124,  0,  0,  0,  0,  0    370,   124,     0,     0,
40c4: 00,00,3b,00,00,00,f0,02 ??   0,  0, 59,  0,  0,  0,240,  2      0,    59,     0,   752,
40cc: 7c,00,00,00,00,00,00,00 ?? 124,  0,  0,  0,  0,  0,  0,  0    124,     0,     0,     0,
40d4: 3a,00,00,00,ee,02,7c,00 ??  58,  0,  0,  0,238,  2,124,  0     58,     0,   750,   124,
40dc: 00,00,1d,80,00,00,35,00 ??   0,  0, 29,128,  0,  0, 53,  0      0,-32739,     0,    53,
40e4: 00,00,74,01,7c,00,00,00 ??   0,  0,116,  1,124,  0,  0,  0      0,   372,   124,     0,
40ec: 00,00,00,00,0c,00,00,00 ??   0,  0,  0,  0, 12,  0,  0,  0      0,     0,    12,     0,
40f4: bc,02,8a,00,00,00,00,00 ?? 188,  2,138,  0,  0,  0,  0,  0    700,   138,     0,     0,
40fc: 00,00             ??      0,  0      0,

40fe: 34,00             word  34

4100: 00,00,68,01,7c,00,00,00 ??   0,  0,104,  1,124,  0,  0,  0      0,   360,   124,     0,
4108: 0c,80,e9,85       ??     12,128,233,133 -32756,-31255,
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Tue Mar 14, 2017 10:18 pm

Why only 0.9b boost on chipped OFAC?

Yes, everything is hidden in plain sight.

On the surface at least, some strategies appear to have more subroutines reading AD than others. It would be necessary to achieve clean disassemblies before being certain.

Similar subroutines.

A9L
Code: Select all
  Sub6:
222e: a1,5f,22,30       ldw   R30,225f       R30 = 225f;
2232: fb                ei                   enable ints;
2233: 56,30,00,04       ad3b  R4,0,[R30]     AD_CMD = [R30];
2237: de,22             jlt   225b           if (0 < [R30]) goto 225b;
2239: 33,0a,fd          jnb   B3,Ra,2239     if (!AD_RDY) goto 2239;
223c: fa                di                   disable ints;
223d: ff                nop                 
223e: 51,0f,04,34       an3b  R34,R4,f       R34 = AD_LO & f;
2242: 9a,30,34          cmpb  R34,[R30]     
2245: d7,eb             jne   2232           if (R34 != [R30]) goto 2232;
2247: 51,f0,04,34       an3b  R34,R4,f0      R34 = AD_LO & f0;
224b: b0,05,35          ldb   R35,R5         R35 = AD_HI;
224e: 07,30             incw  R30            R30++;
2250: b2,31,32          ldb   R32,[R30++]    R32 = [R30++];
2253: b2,31,33          ldb   R33,[R30++]    R33 = [R30++];
2256: c2,32,34          stw   R34,[R32]      [R32] = R34;
2259: 27,d7             sjmp  2232           goto 2232;

225b: 91,40,29          orb   R29,40         R29 |= 40;
225e: f0                ret                  return;


CARD
Code: Select all
  Sub115:
4328: 29,24             scall 444e           Sub173(3a,f0,c,1,17,1);
432a: 3a,f0,0c,01,17,01 #args 
4330: 39,2c,19          jb    B1,R2c,434c    if (!B1_R2c)  {
4333: 29,19             scall 444e           Sub173(c,1,3c,f0,18,1);
4335: 0c,01,3c,f0,18,01 #args 
433b: 39,2c,0e          jb    B1,R2c,434c    if (!B1_R2c)  {
433e: a0,30,32          ldw   R32,R30        R32 = R30;
4341: ef,f6,03          call  473a           Sub185(c,1,aa,f0,a8,f0,16,1);
4344: 0c,01,aa,f0,a8,f0,16,01 #args          } }
434c: 32,0c,1c          jnb   B2,Rc,436b     if (!B2_HSI_MASK) goto 436b;
434f: b3,6a,b7,42       ldb   R42,[R6a+b7]   R42 = [R6a+b7];
4353: 9b,76,49,42       cmpb  R42,[R76+49]   
4357: d1,07             jleu  4360           if ((uns) R42 > [R76+49] )  {
4359: ef,ca,03          call  4726           Sub164(26,1);
435c: 26,01             #args 
435e: 20,0b             sjmp  436b           goto 436b; }

4360: ef,d7,03          call  473a           Sub185(3c,5,36,f1,38,f1,26,1);
4363: 3c,05,36,f1,38,f1,26,01 #args 
436b: fa                di                   disable ints;
436c: ff                nop                 
436d: b1,06,04          ldb   R4,6           AD_CMD = 6;
4370: 33,0a,fd          jnb   B3,Ra,4370     if (!AD_RDY) goto 4370;
4373: 51,f0,04,42       an3b  R42,R4,f0      R42 = AD_LO & f0;
4377: b0,05,43          ldb   R43,R5         R43 = AD_HI;
437a: 8b,76,3d,42       cmpw  R42,[R76+3d]   
437e: d3,13             jnc   4393           if ((uns) R42 < [R76+3d]) goto 4393;
4380: 8b,76,43,42       cmpw  R42,[R76+43]   
4384: d3,06             jnc   438c           if ((uns) R42 >= [R76+43])  {
4386: a1,58,01,1a       ldw   R1a,158        R1a = 158;
438a: 20,04             sjmp  4390           goto 4390; }

438c: a1,59,01,1a       ldw   R1a,159        R1a = 159;
4390: ef,97,03          call  472a           Sub186();
4393: fb                ei                   enable ints;
4394: c7,6c,91,00       stb   0,[R6c+91]     [R6c+91] = 0;
4398: 17,38             incb  R38            R38++;
439a: f0                ret                  return;


  Sub6:
53af: a1,e0,53,30       ldw   R30,53e0       R30 = 53e0;
53b3: fb                ei                   enable ints;
53b4: 56,30,00,04       ad3b  R4,0,[R30]     AD_CMD = [R30];
53b8: de,22             jlt   53dc           if (0 < [R30]) goto 53dc;
53ba: 33,0a,fd          jnb   B3,Ra,53ba     if (!AD_RDY) goto 53ba;
53bd: fa                di                   disable ints;
53be: ff                nop                 
53bf: 51,0f,04,34       an3b  R34,R4,f       R34 = AD_LO & f;
53c3: 9a,30,34          cmpb  R34,[R30]     
53c6: d7,eb             jne   53b3           if (R34 != [R30]) goto 53b3;
53c8: 51,f0,04,34       an3b  R34,R4,f0      R34 = AD_LO & f0;
53cc: b0,05,35          ldb   R35,R5         R35 = AD_HI;
53cf: 07,30             incw  R30            R30++;
53d1: b2,31,32          ldb   R32,[R30++]    R32 = [R30++];
53d4: b2,31,33          ldb   R33,[R30++]    R33 = [R30++];
53d7: c2,32,34          stw   R34,[R32]      [R32] = R34;
53da: 27,d7             sjmp  53b3           goto 53b3;

53dc: 91,40,29          orb   R29,40         R29 |= 40;
53df: f0                ret                  return;

Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Wed Mar 15, 2017 12:47 pm

With Stage 1 or Stage 2 chips (classical versions) there is a kind of cut off after 0.9b, like at 0.7b when no chip is used.
It seems that this Ford digital MAP sensor has created some complications for tuners.
It was, I think, the same thing for Escort T25, with difficulty to go over 280hp, even with a bigger turbo. I can be wrong, my knowledge is really light on this version.

To come back to the loops used to fill in registers, yes it is a bit complicated, until method is identified. Now I know it.
Firstly I have thought, that the code was provided based on EEC hardware, it was partially wrong, but a good thing to start with.
For VM120, 8GEA uses a real simple loop to do it :
Code: Select all
425a: 11,34             clrb  R34            R34 = 0;
425c: a1,5e,01,30       ldw   R30,15e        R30 = 15e;
4260: fa                di                   disable ints;
4261: ff                nop                 
4262: b0,34,04          ldb   R4,R34         AD_CMD = R34;
4265: 33,0a,fd          jnb   B3,Ra,4265     if (!AD_RDY) goto 4265;
4268: b0,04,32          ldb   R32,R4         R32 = AD_LO;
426b: b0,05,33          ldb   R33,R5         R33 = AD_HI;
426e: fb                ei                   enable ints;
426f: 61,c0,ff,32       an2w  R32,ffc0       R32 &= ffc0;
4273: 08,01,32          shrw  R32,1          R32 = R32 / 2;
4276: c2,31,32          stw   R32,[R30++]    [R30++] = R32;
4279: 17,34             incb  R34            R34++;
427b: 99,0c,34          cmpb  R34,c         
427e: d1,e0             jleu  4260           if ((uns) R34 <= c) goto 4260;

Loop on 0FAB, still on VM120 is a bit more complicated, but principle is the same.
Related table is not exactly the same for same hardware, but there is a link with hardware.
0FAB and 8GEA are both reading 12 analog inputs, even if they will not be all used after this (some empty pins are dedicated for this).
Channels and registry addresses are found and calculated from this table in the same way. 0FAB table contains just a default value in addition.

On hardware SD1XX (1AFA, 1ADA), only 3 analog inputs are taken into account with the same type of loop.

It is a bit early to generalize the principle, but it seems that hardware (family) codes are linked, with real available connections to the CPU.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Wed Mar 15, 2017 5:03 pm

The digital MAP only has the range as an issue if you want to exceed 2.5b. Making a higher pressure version is on my todo list. At 280hp on a T25, the injectors are flat out, hitting 100% on cool days. The MAF also needs replacement at higher HP levels.

The lack of effort by the chip tuners is really apparent when looking at what they changed to get 280hp. It appears they just dug around until they found a table to turn up the boost or turn off boost control. With the complete definition from sailorbob more than 280 is a matter of changing injectors, turbo, MAF and last in order is MAP. Fuel pump and regulator may need changing depending on injectors.

The code is strategy dependant first and hardware second. Of course the strategy code must reflect the wireing pinouts.

So I imagine 1AFA and 1ADA has other loops for the other AI's.

I don't think the 3 numbers in the hardware code give much. Take SMD-190 and SMD-490, both are GHAJ0 strategy using the same io count with a few pins swapped around. 490 has more internal PATS. Both have a white riser card. SMD-457 has more analog ins connected but no riser card. SMD-586 has more output chips but no riser card. There are USA SMD 200 series as well.

Sequential Maf D? What's the D, what do other hardware letter codes describe?
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Thu Mar 16, 2017 5:54 pm

I have still not found other loops in 1AFA and 1ADA binaries, but by decomposing the accessed table, I can find as many links as 0FAB or 8GEA, between registers and channels.
Just the time to refine SAD commands.
This is more logical, but will complicate my comparison. So, yes, the link between hardware code and AI's seems to be totally false.
I still not have a photo for the SD111 (1AFA), still in the car and nothing for SD101(1ADA), but I will provide binaries.
They are using the same strategy, with different hardware. I will probably try the binary on a SD130, just to see if it is working.
Numbers are like revisions, I think. The higher it is, better are the components. Why SD101 or SD111, because SD100 and SD110 were not working properly, I suppose.
SD111 should have better AI's converters, that is why I will never try to downgrade by testing 0FAB (VM120) on a VM115 ou VM100.
Another information, 1AFA loom can be directly connected to 0FAC (VM120), just one EDIS connection to cut (not used on VM120) and 1 missing cable for amal boost valve. Pin Out seems to be exactly the same.
VMXXX was probably for the first EFI generation, for a real limited number of vehicles, SDXXX is the same thing, but for the following vehicles, all using EFI.
SMDXXX was for the next generation.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby Pym » Sun Mar 19, 2017 1:18 am

Now, I can confirm that 0FAB is using strategy 0SLTXA.
And 0FAC is using a different strategy 0SLTXC. I was right on the difference.
Last character of strategy indicates a small difference, only on last Calibration Pointer (2030).
Last Calibration block (#8) is at least in this case, related with A/D Volts transfer functions and A/D Channels to register mapping.
If I was able to use relative addresses in my definition files, I could say 0SLTX is a single strategy, but I think TunerPro does not permit it.
I am still trying to understand why 0FAB has 11 predefined A/D channels (10 are used) (0FAC has 10 (9 are used)).
For me 0FAB should only use 5 (MAP, TPS, ACT, ECT, CO Pot.). I think VSS should be digital.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 157
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Ford EU EEC IV&V specificities

Unread postby jsa » Sun Mar 19, 2017 1:37 pm

Yes OSLTXA is shown toward the end of the file when viewed as ascii.

I don't know much about tunerpro, Decipha would know.

No HEGO on the car?

Things like octane adjust can be on analog channels, even though they are only 2 state inputs.

One analog channel is used for internal reference.

Yes, VSS is digital.

How many of the analog channels are physically connected from 8061 to loom pins or something internal?
Cheers
John
jsa
Power Poster
 
Posts: 345
Joined: Thu Jan 16, 2014 1:44 am
Location: In the shed or On the Computer, 'straya
Name: John
Vehicle Information: Escort RS Cosworth
EEC-IV GHAJ0 ANTI or COSY

Next

Return to Ford Euro & Aussie Tuning

Who is online

Users browsing this forum: No registered users and 1 guest