EEC V file conversion
-
jsa
- Posts: 450
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
I think there is a write up on reading the bin from your PCM using TP and a blank XDF.
Yes you could create a partial def to read your PCM.
Yes you could create a partial def to read your PCM.
-
BOOSTEDEVERYTHING
- Posts: 437
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
I tried it that way, I just can not get it to read well like that. I got the read I have with my old burn 1 and adapters using the old Moates software. Would be nice to get a clean read with tunerpro so I have a good file to start with. The software it is tuned with now is horrible. The old SNIPER/DELTAFORCE stuff. Half of the things I try to change do not seem to affect it, that's why I am trying to learn the disassembly end of it. I would like a better understanding and also be able to build my own def files and hopefully even change or add code to the bin in the future. Like fan control or something like that. I am trying to build a pwm fan controller with an arduino but am failing really well with that right now. LOLI think there is a write up on reading the bin from your PCM using TP and a blank XDF
-
jsa
- Posts: 450
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
You should be able to get a clean read, using a blank or the old moates software.
By all means have a go with your own definition, but it may equally fail to read until the reasons for previous failures are understood.
Keep in mind that both software and hardware will have to be in place for fan control. Once editing the bin for fan control, the EEC will need to have spare points available and the components in place. You may need to add components.
By all means have a go with your own definition, but it may equally fail to read until the reasons for previous failures are understood.
Keep in mind that both software and hardware will have to be in place for fan control. Once editing the bin for fan control, the EEC will need to have spare points available and the components in place. You may need to add components.
-
BOOSTEDEVERYTHING
- Posts: 437
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
Is there a component ID write up or documentation that may tell me what to look for as far as EEC Hardware identification goes? I have the hardware manual, but is there a way for someone new at this to id the actual hardware components? I have looked into it a bunch with googles help but have failed to find much.
I did get the good read with the moates software. Was just hoping to be able to read it with BE or Tunerpro, just to make it a bit easier to have a base to edit in the software I want to use. Maybe I downloaded the wrong Blank Def files. Do you happen to have one that will work with tunerpro or BE? Thanks
I did get the good read with the moates software. Was just hoping to be able to read it with BE or Tunerpro, just to make it a bit easier to have a base to edit in the software I want to use. Maybe I downloaded the wrong Blank Def files. Do you happen to have one that will work with tunerpro or BE? Thanks
-
jsa
- Posts: 450
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
This is a blank BE def for reading.
-
BOOSTEDEVERYTHING
- Posts: 437
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
Thank You. I will give it a shot. I will need to have a def file to be able to datalog anything at all, is that correct? Is there a base OBD2 type datalogging def I can use Just to verify the basic stuff is operating correctly. I am putting a new PCM in the truck. The one I had in it is a reman and is acting up at times and nt wanting to start. But I do not have any more credits on my old Sniper tuning software to be able to put the tuned file on this new pcm. I am hoping I can read the tuned file out with my moates stuff and put in on a quaterhorse and install that until I can get a def file built to be able to tune and datalog the rest of it.
-
jsa
- Posts: 450
- Joined: 2021 Feb 16, 15:46
- Location: Australia
- Vehicle Information: 95 Escort RS Cosworth
2.0 YBP
CARD / QUIK / COSY / ANTI
GHAJ0
SMD-190 / SMD-490 EEC-IV
Binary Editor
ForDiag
Re: EEC V file conversion
For BE, a def file with logging patch code is needed for the QH. That has nothing to do with OBD2 logging.
For TP, an ADX file is needed for logging with the QH.
That has nothing to do with OBD2 logging.
I have no experience with OBD2 logging, but that requires a Mongoose or similar.
Yes you can read your bin and run it on the QH in a replacement ECU.
For TP, an ADX file is needed for logging with the QH.
That has nothing to do with OBD2 logging.
I have no experience with OBD2 logging, but that requires a Mongoose or similar.
Yes you can read your bin and run it on the QH in a replacement ECU.
-
Jamie from oz
- Posts: 54
- Joined: 2022 Jul 08, 04:54
- Location: South Australia
- Vehicle Information: 1995 ford falcon ute 5.0 windsor efi
Re: EEC V file conversion
Not sure if you have a generic obd2 adapter that you can use with forscan.
I can data log some of the later eec-v in Australian au falcons with forscan and a elm327 or tactrix open port 2 or vgate fs.
This is only for datalogging generic obd2 not tuning the ecu and not with the QH.
I can data log some of the later eec-v in Australian au falcons with forscan and a elm327 or tactrix open port 2 or vgate fs.
This is only for datalogging generic obd2 not tuning the ecu and not with the QH.
-
BOOSTEDEVERYTHING
- Posts: 437
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
Yes. I have access to IDS so I will just use that. Wasn’t sure if there was a generic adx that had the basic stuff in it already that I could just use with the quarterhorse to make things a bit easier. I’ll just use ids and make it work. lol.
-
BOOSTEDEVERYTHING
- Posts: 437
- Joined: 2023 Sep 06, 13:11
- Location: Charlotte NC , USA
- Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0
2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Re: EEC V file conversion
I am having an issue with EQE3. In my message file I have this...
sym 0eeb6 "Sub_0eeb6" # auto
sym 0ef0d "Sub_0ef0d" # auto
sym 0ef41 "Sub_0ef41" # auto
sym 0ef51 "Sub_0ef51" # auto
And in my LST file I have this......
Should Sub_0ef41 be a Subroutine on its own, or is that a mistake in the msg file? Or do I need to add something to the dir file to make SAD scan that individual address? This is SAD 4.012. Thanks
sym 0eeb6 "Sub_0eeb6" # auto
sym 0ef0d "Sub_0ef0d" # auto
sym 0ef41 "Sub_0ef41" # auto
sym 0ef51 "Sub_0ef51" # auto
And in my LST file I have this......
Code: Select all
Sub_0ef0d:
0ef0d: f2 pushp push(PSW);
0ef0e: 10,08 rombk 8
0ef10: ef,86,8f call 87e99 Sub_87e99_ROM_BANK_CNTRL? (
0ef13: 07 #arg 1 7 );
0ef14: 12,30 cplb R30 TEMP6L = ~TEMP6L;
0ef16: 52,2e,30,46 an3b R46,R30,[R2e] TMP0L = TEMP6L & [TEMP5L];
0ef1a: 12,30 cplb R30 TEMP6L = ~TEMP6L;
0ef1c: 88,2c,2a cmpw R2a,R2c
0ef1f: db,2b jc 0ef4c if (TEMP3L < TEMP4L) {
0ef21: a2,2b,3e ldw R3e,[R2a++] TMP6L = [TEMP3L];
0ef24: 51,0f,3e,40 an3b R40,R3e,f TMP7L = TMP6L & f;
0ef28: 71,f0,3e an2b R3e,f0 TMP6L &= f0;
0ef2b: 3e,3e,16 jb B6,R3e,0ef44 if (B6_TMP6L = 0) {
0ef2e: 99,01,40 cmpb R40,1
0ef31: d3,11 jnc 0ef44 if (TMP7L >= 1) {
0ef33: 99,05,40 cmpb R40,5
0ef36: d9,0c jgtu 0ef44 if (TMP7L <= 5) {
0ef38: 17,40 incb R40 TMP7L++;
0ef3a: 91,40,3e orb R3e,40 B6_TMP6L = 1;
0ef3d: 90,40,3e orb R3e,R40 TMP6L |= TMP7L;
0ef40: c3,2a,fe,3e stw R3e,[R2a+fe] [TEMP3L-2] = TMP6L; } } }
0ef44: 34,3e,03 jnb B4,R3e,0ef4a if (B4_TMP6L = 1) {
0ef47: 90,30,46 orb R46,R30 TMP0L |= TEMP6L; }
0ef4a: 27,d0 sjmp 0ef1c goto 0ef1c; }
0ef4c: c6,2e,46 stb R46,[R2e] [TEMP5L] = TMP0L;
0ef4f: f3 popp PSW = pop();
0ef50: f0 ret return;