Tuning a 93 3.4 Firebird

[ForcedFirebird]

yes, it is kind of convenient in that it does all of the offsetting for you.

The youth of today is entirely TOO lazy

[tkoforpresident]

ok. I will try again.

What about the whole control panel usb thing?

[robertisaar]

yes, it is kind of convenient in that it does all of the offsetting for you.

[ForcedFirebird]

for the burning: you are using the menu that pops up in TP, right?

go to the left, select which chip you're using, hit erase, load the file you want burned, DO NOT touch the numbers on the right, hit program, then hit verify.

if all goes well, the verification will succeed.

I am not familiar with the Moates BURN, but when you burn 256k worth of memory on a 512 chip, then you have to put that info on the END of the chip - does the BURN do that automatically?

[robertisaar]

for the burning: you are using the menu that pops up in TP, right?

go to the left, select which chip you're using, hit erase, load the file you want burned, DO NOT touch the numbers on the right, hit program, then hit verify.

if all goes well, the verification will succeed.

[tkoforpresident]

OK, a couple of issues...


1. Where do i go into the control panel to find the "port #" for my usb ? And where do i input that # in tuner pro?

2.I tried burning my first tune onto a chip and while i believe the burn succeeded i am having some doubts as well. I used 08000 in the "start address", selected chip size "512" and burned my updated .bin onto the chip after uploading it into the buffer. I did a blank check on the chip first before i tried to burn it and it did in fact come up blank like it was supposed to. It said "burn successful" which was neato and then i switched the chip size over to "256 read only", once again using the "08000" start address and then hit "verify chip with buffer" and then that came up as succesfully verified. So far so good right?

Finally, i decided that if my tune had succesfully loaded onto the chip then i could "read" the chip again and save the buffer to a file, open it in tuner pro, and hopefully see the same tune as the one i've been working on. this however, was not the case. As soon as i had opened the recently "read and saved" .bin all the tables i had changed were different (back to stock i think) and even the speed kill limiter was set at an odd 61mph

did i burn the chip correctly? Or did it somehow revert back to the stock $a1 .bin, or am i spazzing out for nothing?

anyhow, i could use some guidance...

[tkoforpresident]

thanks for the help Robert

I can't wait to see how whacko my engine is running lol

[robertisaar]

record, red button, it's the same thing, just that after your initial setup, it's faster to hit the red button...

[tkoforpresident]

so, don't just go to "datalog" and select "record"... I have to hit a red button instead? I'm assuming its at the top of TP ?

[robertisaar]

depends... if you can't keep it running, hold some throttle on it. you might as well log from start-up, that way if there is something odd related to the temp of the motor, it becomes apparent.

don't forget the little red record button... i made that mistake when i was new to this.

[tkoforpresident]

ok thanks. I'll give it a go and hope for the best

few quickies however...

how long should i datalog for?

should i rev the engine or just let it idle?

should i start data logging right away or wait til it's warmed up?

[robertisaar]

more or less, thats the exact procedure.... and once it's loaded, press Ctrl + F4 and it connects...

[tkoforpresident]

so is it as simple as "selecting .ads" in tunerpro before data logging and then inputting the usb port # in tunerpro's settings?

[tkoforpresident]

Did you install the USB driver I pointed you to?

yup, thats installed and running.

[ForcedFirebird]

Did you install the USB driver I pointed you to?