Working on a 93 LT1, 16159278 computer with a stock BDZL bin. It has had two other guys burn their own bin using tunercat. Im using tunerpro rt. When I load the stock bin data looks good. When I load their programs data is all over the place. For example the main spark table data goes from -2 all the way up to 200 plus. But its not smooth or a pattern of any type, just random.
Has anyone seen this?
Ill post some screen shot when I figure out how.

 

Bad definition file?

 

I thought so but the car does run on them, actually better than the stock, but car got a cam swap and intake so it needs some work.
As far off as the values are I wouldn't think it would run.

 

Ok so I played with it some more and the bin that that data is all skewed, runs ok. If I try to burn it onto another chip it wont work, goes into limp mode. So I played some more, all my burns are going into limp, also cannot emulate. Using autoprom with tunerpro rt. I'm using the da3 def, also tried da2 for giggles, same result. The stock bin is on a flash drive along with a third bin that also has weird data.
So am I correct in assuming my def file is ok but I have a problem burning. How do I check this?
If I verify good chip against buffer its ok, burn another to same and it verifies but goes into limp. Also tried multiple new chips with no success.
Thanks in advance for the help.

 

Hers the data I get when I read the chip, and it runs ok on this
mainspark.JPG
mainve.JPG

 

I would say that you aren't reading the PROM correctly. Try reading the top half of the PROM, it may be a 512kb PROM, which that BIN is 256kb in size.

RBob.

 

I used the offset data off of moates.net. I set it up as a 64k cause thats what my computer said the file size was. The moates data only ran up to 64k. What would the settings be for 256k. Or am I totally screwed up in understanding you. It is a 27SF512 PROM though. Thanks for you help again. By the way this is my first lt1, as if its not obvious. I've only messed with 7747 computers so far.

 

I've tried all the offsets listed on the moates site with no success. Do I have the wrong offset data, or am I missing something else?

 

The 64 KB is in bytes, the 256 kb & 512 kb is in bits.

32 KB = 256 kb
64 KB = 512 kb

Read the PROM from 0x8000 through 0xFFFF for the top half.

RBob.

 

Thanks for your help RBob. That's exactly what it was. I'm not real computer savy obviously. So if you get some time would you mind explaining the difference between bits and bytes.