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

[CoopKill]

I looked at some 94 ECU MUT datalogs and it revealed something interesting. When the ECU hasn't had a request for data for a while, it will reply back with the answer almost immediately (0.1 mS - 1mS); however if the ECU just serviced a request not too long ago, it will wait ~11.4 mS before responding. By adding those extra delays, the ECU will reply back with an answer almost immediately making it much harder for noise to make an impact.

fastbike76, it's going to take 2-4 weeks for China mail to arrive here with the USB OBD2/MUT cable; you can eliminate this wait if you sacrifice your cable. The components need to come off the PCB in order to see all the traces, a hair blow dryer will melt the solder, and the parts can be scraped off. Or we can wait until I get my cable.

Would this be the cause of my disconnect issues on the 94? I've not gotten it back together with the 99 ecu, so should not be an issue any longer. Just currious...

[fastbikes76]

Would this be the cause of my disconnect issues on the 94? I've not gotten it back together with the 99 ecu, so should not be an issue any longer. Just currious...

Do the software update listed in the first post on page 106 . The version 3.11 stopped my disconnects, and allowed a reconnect straight away when I stalled.


The delay update is for corrupted Evoscan logs or if the LCDBC sort of freezes or gives random info during a hard pull. I found on my car setting the delay to 20ms worked best.

Cheers
Elton

[Unlogic]

Went for a drive yesterday and I did some testing along the way. Think I'm gonna try to remove the filter I built and go back to using the integrated OBD chip cause no matter which delay I try I still can't get any reliable readings over about 4k rpm.

[TurboSinceBirth]

Went for a drive yesterday and I did some testing along the way. Think I'm gonna try to remove the filter I built and go back to using the integrated OBD chip cause no matter which delay I try I still can't get any reliable readings over about 4k rpm.

I was never able to get reliable datalogs above 3k rpms through the LCDBC so I can't say that you'll be able to. I didn't try the OBDII noise cancelling cable or the newest firmware to see if that resolved the issues because my car hasn't been road worthy since. I hope you figure something out though. I prefer seeing the LCDBC in my periphery during a pull than trying to stare over at a laptop during a pull which can be very dangerous and is stupid.

[Unlogic]

Any new progress BlackStealth?

It would be so sweet if this little widget would work at higher RPM's.

[fastbikes76]

Ive not done any more testing as my car is out of action with clutch issues...Hopefully though a better cable will be upon us soon

[j2k4]

Don't want to derail this, but I made a thread about the goofy "phantom knock" problem I was having a while back - finally got down to cases and it looks like I've fixed it:

http://www.3sgto.org/3000gt-stealth-...d-phantom.html

[BlackStealth]

Unlogic, shipping from China can sometimes take 4 weeks -- I can't do anything until it arrives.

J2K4: Interesting that CV-joint contributed to false knock, glad you got that problem solved.

[Unlogic]

Any updates?

[BlackStealth]

Any updates?

The second OBD2/MUT cable I received from China again is not exactly the same as fastbikes; it has fewer components.

I had an owner of a 94 RT/TT stop by a few weeks earlier that wanted his ECU codes scanned using the LCDBC boxed version. To my surprise, it was sluggish at refreshing ECU datalog values, so this tells me this vehicle has the same issue as yours and fastbikes (corrupted OBD2/MUT data). I will ask him to come over again so I can test with second OBD2/MUT cable and see if this cable is equivalent to fastbikes.

Also, I had to make repairs to the 94 RT/TT ECU because the capacitors were giving him trouble, as they were the original 20 year old capacitors. By any chance are you still on your original ECU capacitors?