pgmfi.org

Accidentally shorted my chipped ECU.

chipped a spare, could only find 74AC373 local not 74HC373. Everything seemed to work but data logging.

Got some 74HC373 and chipped another one (accidentally lifted some traces under the latch in the one)

Same issue. With ectune, it says "Can't connect (maybe j12/j4 still in place)", without the cable it just says "can't connect". I haven't yet tried crome again but I did have data logging working before flawlessly, even over Bluetooth to tuner view, which won't connect now either.

I am sure j12 is cut (desoldered it completely). I am seein about 240ohm between j12 pins still, anyone confirm this is normal? Same result on two of my ecus.

Another odd thing, if I connect the ground wire (ftdi or diect serial), ectune connects without error,

Pin 2 and 4 of the logging header both have continuity to the 66k. My eeprom appears to be read fine and seems to work.

Things I've tried:
- different laptop (have two identical tuning laptops, both previously worked)
- different ftdi cable
- tried my second (stock) civic
- directly to laptops serial port.
- chipped second ECU
- j12 cut for sure
- pwm boost mod done
- eld wb mod done
- set baud in device manager for each port I tried
- burned new eeprom from scratch on brand new eeprom chip
- checking solder points, reheating junctions
- checked continuity on some pins but not all

Things I haven't tried yet:
- crome chip
- "known working ecu", I have a friend who's car I tuned, going to try connecting my laptop to his ecu
- chipping a third ecu
- snooping on serial data (don't know what to look for)

I found ONE thread on d series org where someone had the same issue, changed laptops and he was fine. Didn't work for me albeit both my laptops are nearly identical, though they both also worked previously.

Any suggestions or help appreciated, I'm not a n00b and I've been tearing my hair out on this for a week.

Most problem is:

Check cn2 circuit / copper track. Are the continuity fine?

or

Ecu not detected EEPROM which ecu run stock mode not from the chip.

If you read my whole post, I said both the cn2 pins tracked back to the micro fine and that I confirmed the eeprom was working.

Turns out it was actually a software issue, odd that the issue crept up out of nowhere and effected *both* my tuning laptops, but I pulled out my older tuning laptop that likes to overheat and it worked.

I should note, when I first connected the laptop (tx/rx only), I got the same error..when I connected the ground too, it connected. It's odd, rs232 isn't differential signaling and I've never had to connect the ground before..

And actually, I just noticed the log I pulled tonight had like 3000 samples/minute versus maybe 150 before.. 15-16ms frame time everytime versus before where it was 16-100ms per frame.

Maybe the gnd helps lots.

Guess it actually was my laptop(s)? Tried a third and it worked.

Though now for some reason I have to connect the gnd or I get the same error, never had to before, but on the upside my data logging went from like 5hz to 66hz