Wow this is exciting. Just making sure I understand this: The wideband would not replace the narrowband o2. Would still need to delete egr to hook up wideband correct?
Any possibility of replacing the narrowband with a wideband? Reasons not to? Can't get away with deleting egr in California.
Search found 304 matches
- 2021 Mar 06, 23:33
- Forum: Hardware, Programming & Disassembly
- Topic: Stock ECU Closed Loop Wideband Control
- Replies: 28
- Views: 16052
- 2021 Mar 06, 16:53
- Forum: CDAN4 - 96/97 Fords (Most All)
- Topic: Supported?
- Replies: 2
- Views: 4979
Re: Supported?
Ok thanks for explaining that. I'll let him know. I was confused by the "not supported" next to some of the items in the new downloads section.
- 2021 Mar 06, 15:10
- Forum: CDAN4 - 96/97 Fords (Most All)
- Topic: Supported?
- Replies: 2
- Views: 4979
Supported?
Asking for one of the fordsix guys. It's a 96 f150 with a 4.9 and e4od. Do we need a pic of the ecu to determine? He wants to mod it and keep his auto trans. I'd suggest he become a premium member if supported.
https://fordsix.com/threads/96-300-perf ... ods.82014/
https://fordsix.com/threads/96-300-perf ... ods.82014/
- 2021 Feb 25, 19:49
- Forum: TunerPro Support
- Topic: Ford Universal ADX
- Replies: 26
- Views: 20717
Re: Ford Universal ADX
Thanks for the input, I am getting there 
B7 confuses me. It is called by the payload from its shadow location of 0DB7 but was never copied there by the patch routine. 0D8D is a similar situation along with 91, B9, DB, 96 and D9. Also Placing the payload names in order are not lining up as documented. I think I need to skip over some of these but not sure which ones an why.
B7 confuses me. It is called by the payload from its shadow location of 0DB7 but was never copied there by the patch routine. 0D8D is a similar situation along with 91, B9, DB, 96 and D9. Also Placing the payload names in order are not lining up as documented. I think I need to skip over some of these but not sure which ones an why.
Code: Select all
ADX PL Name J1X equivalent
01 03 1F 1F 1F1F -
02 03 0D D6 00D6 ATMR1
02 03 03 96 0396 IPSIBR
01 03 0D B6 00B6 ECT B4
01 03 0D B7 ACT B5
02 03 0D 9A 009A AM
02 03 0D CC 00CC SAFTOT
02 03 0D BA 00BA LOAD
02 03 0D B4 00B4 N
02 03 01 24 0124 PERLOAD
02 03 0D 8A 008A RATCH
02 03 01 62 0162 -
02 03 01 F2 01F2 VMAF
02 03 0D BE 00BE IEGR
02 03 0D 96 0096 LAMBSE1
02 03 01 70 0170 KAMRF1
02 03 01 1A 011A IEGO1
02 03 01 54 0154 DASPOT
02 03 0D 92 0092 ISCDC
01 03 0D 8D VSBART_RT
01 03 0D 8D VSBAR
02 03 1F 44 Bitmasks
01 03 0D 91 VBAT
01 03 0D B9 ACT
02 03 0D B2 00B2 TP
01 03 0D A8 00A8 FUEL_APT_LST
01 03 01 5C 015C ISCFLG
02 03 01 6A 016A FUELPW1
01 03 01 5D 00DA PDL
01 03 0D DB AEFUEL
01 03 1F 1F EFTFRR
01 03 02 1B WOTTMR
01 03 1F 1F PIPCTR
01 03 02 28 LAMBSE2
01 03 01 4E 014E KAMRF2
01 03 02 39 IEGO2
02 03 0D 96 -
02 03 01 70 BCSDC
02 03 01 1A NOBART
01 03 1F 1F GR_CM
01 03 1F 5D -
02 03 1F 20 TV_PRES
02 03 1F 20 Bitmasks
01 03 0D D9 SP**AHISL
01 03 1F 1F TOT
01 03 03 5C SPD_RATIO
01 03 1F 1F -
02 07 FF FE SPK_SOURCE
02 03 03 14 0314 Bitmasks
02 03 03 22 0322
02 03 01 6C 016C
01 03 03 98 0398
- 2021 Feb 24, 20:07
- Forum: TunerPro Support
- Topic: Ford Universal ADX
- Replies: 26
- Views: 20717
Re: Ford Universal ADX
Decided to just disassemble A1C and take a look at the known working values to try and make sense of this. I am definitely making some connections now. I can see how 0xD00 is added to the addresses lower than 0x100 and how the payload is referencing those copies in some but not all cases. Are the extra values in the parameter list just garbage left over? If the Payload references values like 0x0D8D(twice) that were not copied by the patch then how could that data be relevant? Placeholders? The only AD channel that is being referenced by the payload is ChB. Is that normal?
A1C AD Channels:
A1C Parameter list:
A1C Payload:
A1C AD Channels:
Code: Select all
3b91: 00,08,01 struct 0, iADC_Ch0
3b94: 01,0e,01 struct 1, iADC_Ch1
3b97: 02,0a,01 struct 2, iADC_Ch2
3b9a: 03,0c,01 struct 3, iADC_Ch3
3b9d: 05,44,03 struct 5, iADC_Ch5
3ba0: 07,1c,01 struct 7, iADC_Ch7
3ba3: 08,10,01 struct 8, iADC_Ch8
3ba6: 09,12,01 struct 9, iADC_Ch9
3ba9: 0a,18,01 struct a, iADC_ChA
3bac: 0b,1a,01 struct b, iADC_ChB
3baf: 0c,14,01 struct c, iADC_ChC
Code: Select all
00D6
0396
00B6
009A
00CC
00BA
00B4
0124
008A
0162
01F2
00BE
0096
0170
011A
0154
0092
008C
0090
00B8
00B2
00A8
015C
016A
00DA
021A
0228
014E
0238
00D8
035C
0314
0322
016C
0398
0000
0027
5D01
009E
4404
00A5
4480
0000
0000
Code: Select all
02 03 0D D6
02 03 03 96
01 03 0D B6
01 03 0D B7
02 03 0D 9A
02 03 0D CC
02 03 0D BA
02 03 0D B4
02 03 01 24
02 03 0D 8A
02 03 01 62
02 03 01 F2
02 03 0D BE
02 03 0D 96
02 03 01 70
02 03 01 1A
02 03 01 54
02 03 0D 92
01 03 0D 8D
01 03 0D 8D
02 03 1F 44
01 03 0D 91
01 03 0D B9
02 03 0D B2
01 03 0D A8
01 03 01 5C
02 03 01 6A
01 03 01 5D
01 03 0D DB
01 03 1F 1F
01 03 02 1B
01 03 1F 1F
01 03 02 28
01 03 01 4E
01 03 02 39
02 03 0D 96
02 03 01 70
02 03 01 1A
01 03 1F 1F
01 03 1F 5D
02 03 1F 20
02 03 1F 20
01 03 0D D9
01 03 1F 1F
01 03 03 5C
01 03 1F 1F
02 07 FF FE
02 03 03 14
02 03 03 22
02 03 01 6C
01 03 03 98
- 2021 Feb 22, 21:28
- Forum: TunerPro Support
- Topic: Ford Universal ADX
- Replies: 26
- Views: 20717
Re: Ford Universal ADX
Ok I think I follow you. Thank you. I am not using the A1C bin. My bin is J1X. Surprisingly the hego voltage is logging correctly though. it sounds like this will take some serious time to figure out. Is there a procedure documented for finding the memory addresses for things that are not in the ADC routine?
- 2021 Feb 22, 19:41
- Forum: TunerPro Support
- Topic: Ford Universal ADX
- Replies: 26
- Views: 20717
Re: Ford Universal ADX
Thanks for the input. I adapted Decipha's DL from the A1C bin and patch to my stock bin using the same parameter list. Are you suggesting that the parameter list needs to be changed? I was under the impression that was not necessary but maybe that is where I went wrong.
- 2021 Feb 22, 18:06
- Forum: TunerPro Support
- Topic: Ford Universal ADX
- Replies: 26
- Views: 20717
Re: Ford Universal ADX
Ok that is good to know, I will try to log directly. I really appreciate your help. FYI the universal ADX has selectable payloads configured for every strategy. A1C Payload Looks like this: I am just adapting for a different box code.
Code: Select all
0x51 0x40 0x01 0x03 0x1F 0x1F 0x02 0x03 0x0D 0xD6 0x02 0x03 0x03 0x96 0x01 0x03 0x0D 0xB6 0x01 0x03 0x0D 0xB7 0x02 0x03 0x0D 0x9A 0x02 0x03 0x0D 0xCC 0x02 0x03 0x0D 0xBA 0x02 0x03 0x0D 0xB4 0x02 0x03 0x01 0x24 0x02 0x03 0x0D 0x8A 0x02 0x03 0x01 0x62 0x02 0x03 0x01 0xF2 0x02 0x03 0x0D 0xBE 0x02 0x03 0x0D 0x96 0x02 0x03 0x01 0x70 0x02 0x03 0x01 0x1A 0x02 0x03 0x01 0x54 0x02 0x03 0x0D 0x92 0x01 0x03 0x0D 0x8D 0x01 0x03 0x0D 0x8D 0x02 0x03 0x1F 0x44 0x01 0x03 0x0D 0x91 0x01 0x03 0x0D 0xB9 0x02 0x03 0x0D 0xB2 0x01 0x03 0x0D 0xA8 0x01 0x03 0x01 0x5C 0x02 0x03 0x01 0x6A 0x01 0x03 0x01 0x5D 0x01 0x03 0x0D 0xDB 0x01 0x03 0x1F 0x1F 0x01 0x03 0x02 0x1B 0x01 0x03 0x1F 0x1F 0x01 0x03 0x02 0x28 0x01 0x03 0x01 0x4E 0x01 0x03 0x02 0x39 0x02 0x03 0x0D 0x96 0x02 0x03 0x01 0x70 0x02 0x03 0x01 0x1A 0x01 0x03 0x1F 0x1F 0x01 0x03 0x1F 0x5D 0x02 0x03 0x1F 0x20 0x02 0x03 0x1F 0x20 0x01 0x03 0x0D 0xD9 0x01 0x03 0x1F 0x1F 0x01 0x03 0x03 0x5C 0x01 0x03 0x1F 0x1F 0x02 0x07 0xFF 0xFE 0x02 0x03 0x03 0x14 0x02 0x03 0x03 0x22 0x02 0x03 0x01 0x6C 0x01 0x03 0x03 0x98 - 2021 Feb 22, 16:13
- Forum: TunerPro Support
- Topic: Ford Universal ADX
- Replies: 26
- Views: 20717
Re: Ford Universal ADX
Thanks, got it. Here is the result:
Please correct me if I am wrong, the above addresses are not directly readable by the QH so they are being copied by the datalogging routine to readable addresses. The ADX is configured to read shadow addresses so the big question is in what order are these shadowed? My Datalogging List function below is a copy from the A1C DL Patch. Can I assume that 010a=00D6? I think I am missing part of the equation. Thanks for all your help.
Code: Select all
3b1e: 01,0e,01 struct 1, iADC_Ch1
3b21: 02,0a,01 struct 2, iADC_Ch2
3b24: 03,0c,01 struct 3, iADC_Ch3
3b27: 07,1c,01 struct 7, iADC_Ch7
3b2a: 08,10,01 struct 8, iADC_Ch8
3b2d: 09,12,01 struct 9, iADC_Ch9
3b30: 0a,18,01 struct a, iADC_ChA
3b33: 0b,1a,01 struct b, iADC_ChB
3b36: 0c,14,01 struct c, iADC_ChCCode: Select all
00D6
0396
00B6
009A
00CC
00BA
00B4
0124
008A
0162
01F2
00BE
0096
0170
011A
0154
0092
008C
0090
00B8
00B2
00A8
015C
016A
00DA
021A
0228
014E
0238
00D8
035C
0314
0322
016C
0398
0000
0027
5D01
009E
4404
00A5
4480
0000
0000
- 2021 Feb 20, 14:43
- Forum: TunerPro Support
- Topic: Ford Universal ADX
- Replies: 26
- Views: 20717
Re: Ford Universal ADX
I am single bank SD and I don't see anything resembling the first example. But I found this:
Code: Select all
Sub_3af0:
3af0: a1,1e,3b,30 ldw R30,3b1e R30 = 3b1e;
3af4: fb ei interrupts ON;
3af5: 56,30,00,04 ad3b R4,R0,[R30] AD_Cmd = [R30];
3af9: de,22 jlt 3b1d if (AD_Cmd >= 0) {
3afb: 33,0a,fd jnb B3,Ra,3afb if (AD_Ready = 0) goto 3afb;
3afe: fa di interrupts OFF;
3aff: ff nop
3b00: 51,0f,04,34 an3b R34,R4,f R34 = AD_Low & f;
3b04: 9a,30,34 cmpb R34,[R30]
3b07: d7,eb jne 3af4 if (R34 != [R30]) goto 3af4;
3b09: 51,f0,04,34 an3b R34,R4,f0 R34 = AD_Low & f0;
3b0d: b0,05,35 ldb R35,R5 R35 = AD_High;
3b10: 07,30 incw R30 R30++;
3b12: b2,31,32 ldb R32,[R30++] R32 = [R30++];
3b15: b2,31,33 ldb R33,[R30++] R33 = [R30++];
3b18: c2,32,34 stw R34,[R32] [R32] = R34;
3b1b: 27,d7 sjmp 3af4 goto 3af4; }
3b1d: f0 ret return;
3b1e: 01 byte 1
3b1f: 0e byte e
3b20: 01 byte 1
3b21: 02 byte 2
3b22: 0a byte a
3b23: 01 byte 1
3b24: 03,0c,01,07,1c,01,08,10,01,09,12,01,0a,18,01,0b ???
3b34: 1a,01,0c,14,01,ff ???