Well I successfully stacked the chip my car has been running on and copied it to a 29c256 chip. Car runs just as if did on the 2732A chip.

So I took that bin and made a few edits to the fuel table and burned it to the chip with offset. Chip did not work. Ran like crap and check engine light flashes on and off real fast. This happend on the first chip and Dewey told me to use the stacker. So I burned another new chip using the stacker and got the same result after putting it in the car.

If I am going to stack, what addresses should be in the buffer and the chip section of the flash and burn program? I think that may be my problem with the stacking.

As far as the offset, I read up on the boards and thought I was using the right address. I was using 000000/000FFF and 007000/007FFF and it did not work.

Any help would be appreciated.

 

Are you using the 007000-007FFF in the chip address and the other in the buffer. I done just that here while back, did not notice aft. a computer problem. Put em in the right place, worked. hope that helps

 

Yep, 000000/000FFF in the buffer and 007000/007FFF in the chip and could not get it to work.

 

Did you modify the bin after it was stacked and then stack it again or did you modify the original size bin and then stack it as you did when it worked the first time?

Mark

 

I'm not sure what you mean my modify.

I did exactly what I did the first time.

I'm just not sure I have the start and end address corrent in the buffer and chip.

 

IIRC, with the moates adapter, the last 4K block in the chip is used. In that case, the start of the buffer should be set to 0x00000 and the start of the chip or device should be set to 0x07000. You shouldnt need to make any modifications to the bin if your tuning software is still calculating the checksum. Its possible that the checksum is being calculated incorrectly or the chip/adapter are faulty.

 

Modify, as in edit is what I meant, no change to the bin size. I use TunerPro with moates adapters and SF512 chips. Using the stacker tool it is bin size of 16K, chip size and block size of 64K. Try using same bin size and chip size of 32K for your 29C256 chip.

If your original chip is a 2732A, try using 8K bin size, 32K chip/block size.

My original question was to try to determine if somehow you stacked the bin twice. First when you went to the 29C256, then opened that file, edited, closed and stacked again.

 

Maybe I have the data across the top wrong. I have bin size 4k, chip size 32k and block size 4k. For a 29C256 chip, is that right?

 

As far as stacking the bin twice, I don't think so. The end result bin file was 32k after stacking.

 

QUOTE]If I am going to stack, what addresses should be in the buffer and the chip section of the flash and burn program? I think that may be my problem with the stacking. [/QUOTE]


I missed this bit of info the first time I read your post. IF your going to stack then the chip start address should be 00000, because your stacked bin is already the 32K that is required. If your not going to stack then you use the offsets that your were using. Just triple check the size of your bin that your uploading to your buffer to burn. I bet you got confused in which one was stacked and which one wasn't. I believe you have to restack every time if you are going to burn chips that way, thats why I just use the 4K bin file, offset to the last slot in the chip.

 

Bill,

When you modify, you cannot open a stacked bin to modify, it will nto work right if you do so. If you are taking a 4k bin, and modifing, then you either need to stack, to a 32k, or re-address to burn the 4k bin. either should work. just out of curiosity, what did you actulay change in the bin?

 

Well I don't think I restacked a 32k bin but I'll check. As far as the start point for the offset, I have tried it several time and it still is not working. When I put the offset chip in it runs like crap and the check engine light flashes real fast. I am using a chip start and end address of 007000/007FFF and a buffer start and end address of 000000/000FFF.

The only thing I changed was the base timing. They had it set to zero on the chip when it is actually set to 6* advance on the car. So I changed the chip to 6* advance. I also reworked the VE tables. Data logging says I a still a bit rich. That's all I changed. Nothing more.

What about the values across the top of the stack window. The bin is 4k and the chip is 32k but what should the block size be. I was using 4k.

 

Try making it match the chip size at 32K, that's what mine is set at when stacking.

 

the block size should work at 4k.

If you have problems still, e-mail me the bin, i'll give it is a looksy

 

OK. So I started over from scratch. I copied the chip from the dyno tune. It's a 4k file on a 2732A chip.

I loaded that file into TunerPro and edited the fuel table and the base timing. Then copied it to a 32k chip using both stacking to one chip and offset to another and neither one worked in the car.

I don't know what is going on.

 

Does the base unedited file work? If it did but doesnt now then it sounds like a possible hardware problem. Otherwise, if only the unedited one works then its a fault with the definition file or tuning software corrupting the bin or not writing the correct checksum.

The other option to see if the computer can see the bin at all is to write '$AA' in place of the mask ID. I wouldnt drive the car but if the SES stops flashing and only gives one blink then you know the bin is in the right spot.

Teh reason not to use the car is that if the code on the chip is corrupt or cant be read properly, the computer can do some wacky stuff. Things like it randomly toggling the outputs and writing random pulsewidths to the inj. drivers. I had this happen out on the road. When the computer tried to execute teh corrupt code it was like the car was possessed by the devil.

 

i hate to say this but check the jumpers on the adapter.

 

The unedited copy works just fine. What I should do is try to burn another unedited copy to a new chip and see if it works.

Dimented,

The mask id, isn't that one of the selections in the uppper left hand box in Tuner Pro? I can change it to "$AA" right there?

I could be the burner, but the Flash and Burn probram says the burn is working ok and I already burned one chip the is running fine in the car.

So I try burning a copy of the chip that is running the car now and if that works then I would say its something in the Tuner Pro program. Possible the check digit or something like that.

 

When you save the bin you've edited does tunerpro prompt you to save a new calculated Checksum?

Also, what ecu definition file are you using? I know there's an incorrect one floating around that I think has the VE table reversed or something like that.

 

Jon Prevost gave me a good ecu file. And when I make changes Tuner Pro does asked to calculate check sum, but it has not done it every time. I'll pay particular attention to that. Should it ask everytime a change something in the VE table?

 

For me, TunerPro has always asked for checksum update. Sounds like that could have been your problem, the flashing SES light and all.

 

ARE YOU SURE ? I only doubt that becuase AFAIK there was no way the ECU could be fixed in TunerPro v3
It was an inherent problem in the ECU file format that will be finally adressed in Tuner Pro 4

https://www.thirdgen.org/techbb2/sho...hreadid=248062

 

 

Yeah I know about the problems with the columns. I was using a good one.

 

IIRC, the 'columns' only have up to three caracters, so the 'RPMs' will be cut off, but itll still work. I ran into this when you sent me your bin, Azvolfan. I had to reverse the rows and columns in the ECU file I was using in order to display the VE table correctly. All of the tuning programs have bugs in them. Even tuner cats takes a dump on me every once in a while.

The checksum must be calculated every time, or the computer will halt and reset instead of running the code loops when it gets a mismatch.

 

I think that's the problem then. Is there any way to force the program to recalculate the check sum?

 

It won't recalc the checksum after every change, it should tell you it has done so, once you save the new bin. It would be rather annoying if it did it after every change.

 

Dimented,

My mask id says 97. I should just put a $AA instead?