My LCD screen project, boost, WBO2, Knock, etc

[DrGonzo]

Connector is screwed all the way in. Already tried reseating the chip and that did nothing.

[BlackStealth]

This picture here is of your gen2 LCDBC unit & your modified OBD1 connector (ie. extra 12 volt power from Jester's kit).

When the LCDBC DB9 connector (pin 9) receives 12 volt power, it activates the OBD2/MUT circuit inside. You could solder a jumper wire on the LCDBC circuit board to power it up always (ie. always selects OBD2/MUT circuit). To clarify I put a 12V white label on the diagram on top of the DC Jack to indicate where 12 volts can be found (the bottom of the DC Jack). So solder a jumper wire between there and DB9 (pin9).

The OBD2/MUT cable or the custom cable I made you have no electronics inside. The LCDBC circuit board contains the electronics required for OBD2/MUT communication. If you so desire, you can wire directly and eliminate any bad connections.

[DrGonzo]

So are you thinking this is a power issue to enable the OBD2/MUT circuit? I'll try adding in the jumper and seeing if that helps at all and will let you know.

[DrGonzo]

So I got the jumper added and got it all back together. With just the key in the on position it is working fine. It was too late by the time I got it completed to open the garage door to run the car without waking the wife up so I wasn;t able to test with the car actually running. I'll try to run that test tonight. So I am guessing it was a sporadic power issue coming in from the ODB1 connection. So I'll need to check the wiring to see where it is drawing it's power from and run a few tests on it. May just be a loose power connection.

[DrGonzo]

Took the car out for a drive today to see how it was running in preparation for BRG. Got the TFT logger hooked up also. TFT was showing the LCD was connected when I first started driving. Again about 10-15 min the LCD locked up and nothing would update and I couldn't go to the next screen. The TFT was showing that the LCD was no longer connected, but it continued to log. So the new cable I bought, the power jumper, nothing has corrected the issues I am seeing with this unit. If this is some sort of communication issue like every think, then why does the LCD logic not have a retry built in that if is stops receiving data to try and reconnect. I would rather see a period reconnect notice then the whole thing locking up and me having to kill the car to get it to work again. The TFT logger also needs to have the same logic that if it stops receiving data to stop logging and then try to reconnect.

At this point I think there is something wrong with this unit and would like to send it to you to test out. I wouldn't be able to mail it out until I get back fro BRG in a week and a half. Just let me know what I can do to resolve these issues. Thanks again.

[BlackStealth]

The current software does in fact have a routine to "reconnect" after not communicating. It sounds to me the microprocessor is locked up and not running. Perhaps the power was momentarily interrupted and puts the microprocessor in this zombie like state.

There is a hardware feature called "watchdog reset", I'll go write some software to enable it.

[DrGonzo]

Do you think it could be a faulty ship? What if I were to put the old chip back in and test it. That would eliminate it being a chip issue. What was the last version that worked with the older chip?

[BlackStealth]

It may be either a clean power supply issue, or faulty chip.

Here's a software update for you to try out. If there is no activity on the microprocessor for 8 seconds, it does a hardware reset.
http://lcdbc.xp3.biz/updates/UPDATE356.zip

If you do decide to re-install your old microprocessor, do not update the software (as it might not be for your old micro edition, and I do not have software for the old one anymore).

[DrGonzo]

I'll try out both options in the next day or so and let you know. Thanks again!

[DrGonzo]

OK I swapped the chip out and that seemed to have done the trick. I was able to go for a test drive today and no issues with it at all. The car on the other had decided to die and left me stranded for a bit which on comes my second issue.

I had the TFT logger hooked up and logging when the car basically shit itself. got home to look over the logs and yeah something is up with it. Look at line 332 and go from there. The car was not knocking and the RPM's were not less than 1000. I did a 15 min cruise on these log file and just went out to test the brakes. So no real load on the engine. Toward the end I did some quick pulls due to traffic and that is when the car died. Assuming fuelling issue but with these logs there is no way to tell.....

GonzoLog4.zip