Can Anyone ID and Recommend XDF
-
Newbie
- Posts: 48
- Joined: Thu Oct 22, 2009 9:26 pm
Can Anyone ID and Recommend XDF
I have been supplied a read from a 27c512 from from a VN 5l Custom memcal It appears to be 2 stacked 32k bins. Would anybody have a XDF to suit. Mainly just want to see what has been done in tune as it runs poorly
You do not have the required permissions to view the files attached to this post.
-
Holden202T
- Posts: 10435
- Joined: Sat Feb 28, 2009 11:05 am
- Location: Tenambit, NSW
Re: Can Anyone ID and Recommend XDF
i'm not 100% sure its a good read from the chip .... either way half of the file is blank and i can't make any sense out of it!
No matter what the question is, the answer is always more horsepower! 
Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread

Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread
-
Newbie
- Posts: 48
- Joined: Thu Oct 22, 2009 9:26 pm
Re: Can Anyone ID and Recommend XDF
It appears as though it is all written on second half of chip. The read appears fine when opened in hex editor it did have a signiture at end of both bins but i xxxx them to not advertise it
-
delcowizzid
- Posts: 5709
- Joined: Sat Feb 28, 2009 10:38 am
- Yahoo Messenger: [email protected]
- Location: Wellington NZ
Re: Can Anyone ID and Recommend XDF
looks like a come memcal but theres no tables in it maybe bad read
If Its Got Gas Or Ass Count Me In.if it cant be fixed with a hammer you have an electrical problem
-
VL400
- Posts: 4991
- Joined: Sun Mar 01, 2009 4:54 am
- cars: VL Calais and Toyota Landcruiser. Plus some toys :)
- Location: Perth, WA
Re: Can Anyone ID and Recommend XDF
And removing the code identification stops the code from working too
I know what code this is but lost heaps of stuff (including a partial XDF) when a hard drive crashed awhile back. Its to suit a crow stage 3 cam.
Also your bin read has some address offset issues, the first part of the code should start at 0xC000 and the message you XXX'd out should be at 0xFF00. Its also missed the calibration area. I have the original 16k bin if you want it.
Also your bin read has some address offset issues, the first part of the code should start at 0xC000 and the message you XXX'd out should be at 0xFF00. Its also missed the calibration area. I have the original 16k bin if you want it.