The bins are 32.0 kb of info
The bins are 32.0 kb of info
Looking around the web, it doesn't appear that the Burn2 supports the 2764 chip. I think the bin file should be around 8K.
right from there website. USB Chip Programmer works with the AT29C256, 27SF512, and AM29F040 chips.
The stock ecu fuel map is 32k and I did read somewhere that this aftermarket company did first do there fuel chips with 8k and then later on upgraded to 16k or 32k. How does the 2764 chip differ from the 256 & 512 chips I am using? And do you know if the Batronix BX32P reader will read the 2764 chips? thanks for the help.Originally Posted by 1320_john
Last edited by racingjoe66; 02-08-2017 at 11:37 PM.
Most of the pins align from chip to chip; they use the same address and data pins in the same locations up to A12. On pins 1, 26 and 27; they added additional address pins to access the extra memory. On the smaller chips, those pins have functions like Vpp, P_bar. Download the datasheets for all of them and it will give you an idea. The information you want may be in the bin file. Maybe open it with a hex editor and see if you can cut it into 8K chunks, then look at each chunk to see if the data is correct. I assume you have a fuel map editor? Or do you use TunerPro?
I am useing tunerpro. I am not tech savy enough to know the pins n this n that, sorry :( If I sent you a copy of the bin any chance you might be able to look at it? Or would it even make a difference looking at this bin since the burn2 doesn't seem to support the 2764 chip its on?
Last edited by racingjoe66; 02-08-2017 at 11:50 PM.
Post the bin up here and I'll try to parse it.
Hopefully this works
Try these...
Now all the main fuel map values are 7.97 and the tps values are all 159.4 and the rpm values are all 12750
Here is a list of the chips the Batronix BX32P I am looking at can handle. It list several 2764 chips. If I got this reader then should I be able to read these 2 chips with no issues? Or is it possible I could still have issues? thankshttp://www.batronix.com/pdf/BX32PBarlino-II-DeviceList.pdf
I thought that would have worked. The file you posted is 32KB long. The first 16KB was just fill data. The 2nd 16KB had data. It had the same image 2 times, as you would expect. I used the diff command to verify that the two images matched. I can't guarantee buying another programmer will get you the results you want. I'm sorry this didn't work. Try downloading the Bless hex editor and poke around the file then compare to other files you might have. Can you post a picture of this secret decoder ring/box?
I have attached 3 pictures of the decoder box. I just took the pics. I was hoping it would have worked too :) Would it help if I attached a bin of a stock chip I am able to read so you can see it? I am not tech savy to be poking around the files on these and trying to figure things out unfortantly.
I tried reading the chip with my burn2 using the 27c128 option and was able to get the same readings in the tunerpro program as the bin you sent me showed......
I parsed the second bin you posted then looked for similarities to the 8K bin. The second bin has 16K of data and 16K of fill. The upper and lower 8K differ significantly. Best I can figure, somehow the ECM knows the difference between an 8K bin and a 16K bin and the tables are in different locations. There are various ways it could sense. An ID can be programmed into the PROM (most likely), or the uP could verify that the 8K PROM repeats in memory. How many wires are on that module? Where does it plug in? Does it plug in place of a sensor? Does the ECU have a part number? Maybe you can find out more by doing an internet search on the part number. Lastly, did you verify that there is only one xdf file for this application? Right now, I would assume that the 8K and 16K chips have different maps.
Posting Permissions
Reply With Quote
Bookmarks