Anyone worked with the 16196397 yet?

[Xnke]

It's a homemade one, based off the tutorial here. It's worked fine in other cars, and works fine to flash the PCM, and it works fine as long as the engine isn't running. I think I might have a grounding issue or something somewhere, I'll check it out today.

[RobertISaar]

the 24X sensor value should stop updating after the PCM starts to ignore it(~1250RPM for a FWD calibration and I think 2000ish for RWD). why GM chose to split those RPM thresholds, I don't know.

I've had some FTDI boards act funny before, but it usually takes some abuse before that happens. my ALDLCable.com version lasted about a year before it started getting wonky, then I built my own. unfortunately, due to the 8192 baud speed, options are somewhat limited. the CP2102 can be made to work, but I can't really say if it's any better. at this point, my USB ports themselves are getting kind of worn out and contributing to me shallow breathing during a flash.

with a 2.1MHz clock speed, even a 250nS PROM is going to be more than fast enough for a nearly 500nS cycle. stock PROMs should be 120nS though.

the hell is it with the patch function lately? I've never seen it do that before, let alone twice with one BIN. i'll have to see if Mark can replicate it and verify it as an actual bug rather than us screwing something up.

the data given out after a crank attempt looks like typical mode 0 data(trip computer and some digital dash stuff). then for engine running, the "response" literally filling up the data queue with repeating values is certainly something else causing interference, but being that repeatable is odd, I would expect some dithering of the signal.

[Xnke]

It has got to be something to do the truck wiring. I cant find any serious noise, the ICM tests fine, the alternator tests fine, the best battery tests fine, but no dice.

Going to go through all the grounds and all the supply lines again, and see if I have a loose ground or something. I started down that road and had to stop due to the rain.

[Xnke]

Ok, so the truck runs continuously now-but it's so super rich it chokes out. No big deal, just flash an update tune...Nope. Bricked another PCM.

Turns out it's my laptop's USB ports that are the issue. They're flaking out left and right.

So, I've got a TL866 programmer, and MicroPro. I've got a BIN file that I'd like to flash to the two chips. How do I go about splitting the file and programming it? Apparently this is going to be a regular thing for a bit...

I've got another laptop that I'll set up to run tonight. It's so close to being drivable! If I can get it leaned out enough to idle and datalog, it'll be a quick job to tune it up, just gotta get this flash programming under control.

[Xnke]

So, programming the chips, no problem. How to split the bin, AND, which chip goes where...there's the issue.

[RobertISaar]

splitting the BIN is easy, I just use tunerpro. with tunerpro open, press F5(or go through menus for Tools->BIN stacker/splitter), put into split mode via radio button, select path for the BIN you want split, set BIN size and block size to 32KB with chip size of 64KB. "browse" for a save location for positions 0 and 1(0 should be E-side, 1 should be T-side), press split and you should have 2 32KB BIN files wherever you set it up to save.

as for which BIN does which half: see the knock filter? that's the e-side.

[Xnke]

Awesome. Tomarrow I have to go clean up the lab-it's a wreck. John will not be happy....

I also have to figure out a new laptop situation, as I'm not going to continue trying to work with a laptop that can't keep the USB ports going. The FTDI cable fails to start 9 times out of 10 or more, but plugging the cable into an alternate laptop has it working every single time. The issue seems to be with my laptop, not the cable.