first off im new to prom burning, so bear with me a little please

heres my setup
88 iroc, 305, Holley Stealth Ram, 24lb injectors, 58mm TB
using tunerpro & a pocket programmer II, with a 27sf512 chip
using moates adapater

when i burn a chip the car wont start (i currently have the stock chip left out for this testing purpose)

ive verified that the chip has been burned, by checking the hex data

ive tried 2 different bins, just in case arap.bin & 89350TPI1.bin

now as i understand it, in tunerpro i need to stack the chip, as its a 64k chip, ive set the bin & block size both to 16k & set the chip size to 64k & filled the 4 blocks with the bin file, it says it stacked, and ive saved the bin file with a new checksum (removed vats & egr)

so im thinking/guessing its either im not stacking it correctly or theres an offset, but when i checked moates site it says there is no offset.

of ive tried 2 different chips too, the car runs with the stock chip & i even verified that i have the chip in correctly, just in case

ive got the 165 computer as well & using the $6E ecu file

any suggestions/advice would be greatly appreaciated

thanxs, Shawn

 

I can't get it to work either. Do you get an error message when switching to the 27sf512 chip in the pocket programmer 2 saying this chip is not supported like I do?

 

yes, but i called intronixs & thats the way they coded the software, its meant as a warning to Pocket programmer 1 owners, so we can ignore it

 

Is you check engine light blinking real fast?

 

no, it stays constant & the fans start immediately

 

i tried setting the device start at 8000, still no start
ill have to try to pull the code tommorow night to see if that sheds any light

 

This may sound like a dumb question, but are you sure you're putting the chip in the right way?

 

actually i thought of that too, as im new, i switched it just to make sure

nothing wrong with KISS

i decided to pull the code tonight, its code 12
i counted after the 3 normal 12's that come up, i counted it 6 times total

 

E-mail me your stacked bin file and I'll verify it.

 

sent away & thanxs

 

A code 12 means the car is in diagnostic mode. If there were no codes after that, then you have no codes.

 

2 of my fellow crew mates in the cascade crew couldnt get the 27SF512 chips to work in their cars & so far nothing has worked on mine
according to moates the offset should be start of device = C000 and end = FFFF & he said to burn it at 16k in size, i did & the chip verifies, but still wont start

 

I'd like to know what the issue is when you find out, please post back when you do.

 

I'm not sure if this will help...I'm also just beginning. I have a 1227165 ECM in a 1988 IROC 305TPI 700R4.
I did my first burn using Moates adapter with a 27SF512 (Flash).
I read and saved my stock ACXS 16K bin using Moates HDR1 adapter and a Wilem burner.
Modified a few minor settings using TunerCat ECM_32B ware and saved as ACXS.001 modified bin.
Using the Wilem Eprom burner set to correct eprom and 16K bin size. Erased new eprom, loaded my modified bin and burned using 00C000>00FFFF start-end offset, verfied OK. Inserted chip at bottom of the ZIF burner socket with top of eprom towards ZIF lever.
I log using DataMaster 32x32
I have done three burns without a problem.

Using TunerPro I had a few data errors when I compared my stock ACXS bin to the modified bin using the $6E.ecu....? I then tried using a 32Bv001.ecu (moates.net/fileman) with TunerPro and lost the reading errors...? I for one would like to know whether the $6E.ecu edit is OK...anyone?

 

well a friend came over yesterday & we tried using his 27SF512 chips & moates burn1, same problem
we used diff offsets per moates site & diff bin size, stacked, no stacked
we tried 3 diff bin files
i have been using the 6E ecu file too
if we have 1 of the chips in the adapter socket, she wont fire, but if we pull it, she will run in limp mode
im seriously starting to think its the chips, not working in my car

 

well a friend came over yesterday & we tried using his 27SF512 chips & moates burn1, same problem
we used diff offsets per moates site & diff bin size, stacked, no stacked
we tried 3 diff bin files
i have been using the 6E ecu file too
if we have 1 of the chips in the adapter socket (also tested his adapter), she wont fire, but if we pull it, she will run in limp mode
im seriously starting to think its the chips, not working in my car or the $6E ecu file
any other ideas/suggestions ?

 

well i started to think about my problem this am & realized the following
what are the constants of the equation here
ive tried 3 diff bin files
4 diff chips (all 27SF512's)
2 diff programmers, a PPII & moates
2 diff adapters (just to rule it out)
the constants are the same style of chips & the same $6E ecu file
so i tried using the $32b just to see what the effect was
and the car tried to start the whole time i was turning the key, it had never done that before, so im thinking it may be the $6E ecu file is my problem, i think it came with tunerpro or i got it from moates site, but not sure
does anyone have a working copy of the $6E file they could send to me, so i can test this theory out, im wondering if something hasnt been changed in the copy i have
thanxs, Shawn

 

I sent you a copy of a bin that a friend of mine is running. It's not an HSR car, but the rest matches up so it should be close enough to crank.

 

oh thanxs so VERY much, she fired up, so it is the $6E file & as ive been thinking about it, i think ive been using the one that came with tunerpro

im new to this, now does the bin file u sent me already incorporate the ecu file that your friend used or ??
im not sure how they are used in conjunction

when tuning in the future, if i just use that bin file as a base, it will use his ecu file correct ?

thanxs so much your Greatness

 

The ECU (or XDF if you're using TunerPro 4) is what lets you read the bin. The bin is the actual code that the ECM uses. It's kinda like a translator.....the code (bin) is in ECM-ese (hexadecimal) and you need to translate it to English to be able to read it. Different ECMs and systems have different codes, i.e. $6E and $8D and $58, so you need the appropriate translator (ECU) to read them. All I sent you was a known-good bin. You'll still need a good $6E ECU to read/modify it. The one that Mark includes with TunerPro is fairly good.



Did you have the VATS flag disabled in your other bin? I'm thinking that's what was causing the whole problem.

 

if im understanding how to do it right, yes it was disabled

 

It's as simple as unchecking the "VATS enable" bit in the option word flags.

 

then yes it was disabled
but i also tried a stock arap.bin file too

 

I know this is old but I didn't ask; have you tried erasing them first before programming them? I had to do this when I was programming using offsets (smaller bin loading to the "back" of the chip).