Craig Moates

I've been having some trouble with recent programming. For instance:
- I can get good, solid, uninterrupted ALDL data from my stock chip (ACXS 87 305TPI T/A).
- A copy of this chip, placed onto an AM27C128 155ns chip, will lose communication periodically and seems problematic.
- Alterations of other code (Corvette) exhibit similar behavior.

I thought it might have been my interface wiring, but I've recently differentiated the chip-selectivity of the problems. The performance was actually tripping up the other day - like Inj PW kept swinging.

I have a couple of 512's @ 120ns, and I will try those to see if it is a chip speed issue. I have some 150's, too, and I recall they were giving some trouble as well.

Bottom line question: What chips and what speed are you guys using with success? Do I need to get some faster ones? Anyone had this kind of problem? Maybe I'm imagining it & it's not the chips at all...

Thanks,
Craig

TRAXION

Craig,

Here's my experience - chips of 250ns and slower seem to work AOK as long as they are of the correct type and from a quality manufacturer. Have you tried a longer programming pulse from the programmer to see if that made a difference. Theoretically, it should not. But, it seems that many of the slower chips require more programming time as per the manufacturer's recommendations. Just a thought.

Tim

------------------
TRAXION's 1990 IROC-Z
Best Time = 12.587 @ 107.97mph (1.710 60ftr) on the long runner setup.
All Natural. No Force. No Drugs. Stock Bottom End. Stock Body Panels. Stock Wheels. No Weight Reduction.
Gunning for NA 11's with the MiniRam II and Hooker LT Headers.
-=ICON Motorsports=-
Moderator: PROM board at thirdgen.org

Craig Moates

Thanks for the advice. I tried it. Set the Pocket Programmer from 1 to 5 passes, and from 50 to 900 pulse length. So far, it actually seems to have stabilized the chip operation. Still using the AMD 150's, but it does seem to have made an improvement.

Being an engineer, I can't change just one thing at a time. Coincident with this attempt, I changed the software so that it buffers the data and only writes to disk every 5-10 seconds rather than at each (7Hz) acquisition. This may have freed up the 486 laptop comm port, but I don't think so. I seem to recall seeing the problem even when the disk logging was off. I think the longer, 'harder' chip programming helped.

Thanks again!
-Craig Moates

David 91RS/Z28

Craig, I see your from BR also! What kind of chip are you working on for what type of car? I am just getting started in the prom burning world. I just finished building my engine and need some custom tuning done, so I decided to tackle this myself and ordered all the hardware to get started. I will be using the TunerCat software. By the way, I work for ThunderRacing, stop by or give me a call at 754-7223.