tweaked_1973

Hello all,

I will start by saying that I am new to reading and burning PROMs not to wrenching. I have been a master tech since 1993. Nuts, bolts, wiring and sensors come easy to me, but lines of code are a definite weakness.

Here are my issues. I have put SD TPI into my car, and followed the typical routine, but kept all emissions. Changed the pump to a 92 Camaro pump with 3/8 feed and 5/16 return line, running 40 psi fuel at idle. EGR is closed, other than that the only mods are 1.6 roller rockers and Edelbrock TES headers and a K&N.

Since I did not have a stock chip I went online and purchased one that I figured would be close enough with VATS removed and the guy said he would make it run right, he was wrong. Now you can see how I got here. The car ran very rich and had a rough idle, and tried fouling the plugs. I decided to learn about burning PROMS, did a lot of checking on here, and finally bought the Moates Burn 2, the Memcal readout header and the chip adapter. I figured I would play with the tune until I got it right using a chip and the chip adapter and then hard burn it to the PROM in the memcal once it was proper.

I have 2 memcals. The one I bought and a "Race" tune that was in the ECM that I got with the engine. Following the instructions from Moates it seems like I can read the bins but when I save them it says that they are only 1kb, which can not be right. I figured I could build on what I have. To make matters worse when I download a bin and make any modifications in Tuner Pro V it gives me a check sum error.

If any of you guys could give some insight I would greatly appreciate it.

Six_Shooter

iTrader: (2)

Depending on the application the bins can be from 4 Kb to 32 Kb. So you're defienitly getting an error here.

Are you using the "Moates PROM I/O" interface in TunerPro, or Moates "Flash 'n' Burn" Utility to read the PROMs?

First thing is to get to reading a PROM properly, then worry about the check sum error.

What is the application?

Tuned Performance

iTrader: (92)

Like six_shooter stated you need to elaborate on the information. If you are wanting to change the 27c256 in the memcal you cannot do this with a burn or burn2 these are us erasable eproms 32kb. when you are burning to a flash check your offset

gp90gta

iTrader: (1)

You will also need to know about offsets.

http://support.moates.net/2010/04/05...using-offsets/

tweaked_1973

Thanks Six Shooter,
I am using Moates Flash and Burn with the Burn 2 and Memcal reader header. The ECM and engine combo came from a 1991 305 SD TPI Camaro 5 speed with 3.73 gears. My "custom" chip was for an automatic. Both memcals still have the old eprom with the quarts window in them.
I have tried several of the chip types from the pull down, 29f040 takes a lot longer to read, but still shows 1kb. From what I have read I thought it should be 27C256, but that goes really fast.

tweaked_1973

Thanks, I am still taking baby steps. I have the Moates Memory adapter with a ZIF that came with two EEproms. I thought I had read that the old chips could be wiped with a special UV chip eraser and then reprogrammed. If need be I will just leave the Moates adapter in once I get the tune correct, or even close for that matter.

tweaked_1973

Thanks GP. I had read some on offsets. I had hoped this would be quick and easy to at least get started. I know that it takes years to be a proficient tuner. I figured I would go step by step never thinking I was going to trip up so early.

Tuned Performance

iTrader: (92)

if your using a piggyback buy a sst 29sf512 from moates and get a ATNX bcc at the attached link.

http://www.gearhead-efi.com/Fuel-Inj...Information-8D

Tuned Performance

iTrader: (92)

don't use a zif long term dip is ok

tweaked_1973

Tuned-- Moates sent me 2 of the 27SF512 when I got the ZIF and the piggyback. Will they work for the short term? If so I will use them for now and remove the PROM from the memcal once I get everything done and install the correct unit right to the memcal if you think that will work.

Tuned Performance

iTrader: (92)

If you are wanting to reprogram the uv 27c256 I can help you with that or you can solder in a moates d2. the zif works for testing and tuning but often fails over time and if the eprom connection gets bad you go into limp home mode.

Six_Shooter

iTrader: (2)

You're overthinking the long term solution.

The G1 adapter with an EEPROM plugged directly into, along with the original MEMCAL plugged into the side for LHM, and CALPAK, ARE a long term solution.

I've been using a G1 in my car for about 4 years now, without issue, though I am using a Ostrich 2.0 as well, but essentially the same as what you're running.

Getting a 1Kb bin just doesn't make sense.

I have found an issue with the F'N'B utility built into the latest TP RT V5 build (7774).

Are you aligning the PROM to the bottom of the ZIF socket wit the notch or number 1 pin pointed towards the handle?

I'm having an issue right now, where only 1 byte is written to file (using a BURN2 and F'N'B)... Hmmm

Six_Shooter

iTrader: (2)

Solved the problem of saving only 1 byte to file.

You need to manually set the buffer offset addresses when saving. You should be able to use the same settings that show up automatically in the Chip Addressing boxes above the Buffer Addresses. The only time I see this as an issue is when you are reading a large chip with a small file, that has been offset to the end of the chip, such as when, using a 27SF512 EEPROM, with a 32 KB bin, such as an $8D bin, that will have addressing of start: 8000 end: FFF0

When programming with the BURN2, the offset addresses should be set automatically.

tweaked_1973

You guys are great. The chip was installed exactly the way Moates said. I corrected it so that the chip and buffer values were the same and got a good read. Still have the check sum error though when I try to save.

Now I can look at what the "special" chip has for the values. So far I have found that the injector constant was 19.8 which may contribute to my BLM and INT trying to remove as much fuel as possible and hitting the limit. I will compare it to the ATNX just for building a little knowledge.

Once I get the "final tune" I think I would like to either reburn this chip or hard mount a chip on the memcal. Just my experience with automotive in general, power generation and controls is that every connection is a possibility for a bad connection. With my luck I would get a fault at the worst possible time, like with my wife driving it.

Oddly enough when I started learning about cars I took to the electrical aspect of it pretty easily, but never got much exposure to the programming aspect except for doing ladder logic and controls for power generation.

Thanks again.

tweaked_1973

I have managed to find a way to have the checksum error not pop up on save. I had used the Super_8dm2.ecu to look at the bin, but every save would give a check sum error. I guess because Tuner Pro is not .ecu based, but can import it. When I open the $8D.xdf and save the file I do not get a checksum error.

I can imagine that most on this forum have the experience that they likely do not have issues, but maybe the next guy like me reading up on things will get some benefit out of this.

I tried a test chip this morning with a few small tweaks on flags and idle speed, not to just go for a few road tests with the old Snap On scanner hooked up to see how she does and tweak from there. I could not have done it without your help.