I noticed that AHISL in my .bin was ~240 but it ran fine. Changing it to the right # resulted in a no start. The FBGI0_200510.xdf shows the right value.
FBGI0_200510.xdf AHISL address: 21FFE
FBGI0_210226.xdf AHISL address: 2FFFE
I deleted and downloaded FBGI0_210226 again because I've been editing an .xdf with multiple tunerpro windows open and might have edited in the wrong window. Can anyone confirm this? I was thinking Decipha kept ahisl in a ram address on his stuff and the 2nd one isn't in ram.
Possible address error for AHISL
-
- Supporting Member 2
- Posts: 12
- Joined: 2022 Jun 28, 23:10
- Location: Birmingham AL
- Vehicle Information: Stock 04 heritage F150. 4.6,4r70w
-
- Posts: 5033
- Joined: 2021 Feb 15, 12:23
- Location: Metairie, LA
- Vehicle Information: Work Truck
'19 F-150 3.3L
Re: Possible address error for AHISL
no the high slope cant be ram
that is the correct address for all eec-v.
240 means your using the outdated datalogging patch code
set your high slope and enable datalogging and off you go
that is the correct address for all eec-v.
240 means your using the outdated datalogging patch code
set your high slope and enable datalogging and off you go