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

[Chris@Rvengeperformance]

As crazy as it seems, Mitsubishi doesn't have a vehicle speed request for our cars. The request codes I've found are for other Mitsu (ie. Evo). I need vehicle speed in order to calculate/determine which gear you're in. Of course I could introduce a table for engine load vs duty cycle, as this is how the stock boost solenoid/ECU setup is done.

hmm, the scanmaster is able to display MPH, not sure how.

[vTaKwiTHsLiCkS]

Serial to usb from the lcd unit. Same cable that simace uses on his car.

[BlackStealth]

I run an aftermarket ECU here (Adaptronic) Is there anyway this is compatible with something like this?

If your Adaptronic communicates by serial it might be possible. I just need documentation on how to communicate to it. My OBD2 simulator is done, I will be working on Vipec next, and then finish up my MegaSquirt2 version as well. Once those projects are done, I can look into the Adaptronic.

simce came over to help me log my car since I don't have evoscan. He has a modified version for this 99 but it spits out garbage when I hook it to my hybrid ecu. Also the sampling rate is super slow like 32fps while his is around 100fps.

Wondering what version of evoscan the hybrid guys were running?

The 98-99 ECU produce twice the fps vs 94-95 ECUs, so that part is normal.

The early LCDboostcontrollers were not calibrated, I made the mistake to assume the factory calibration was okay when my first unit tested fine and assumed the rest of my microprocessors would be identical when I purchased them altogether in a batch. Unfortunately the calibrations vary greatly. After learning this, I calibrated each unit since then, but the first 20 or so are not calibrated. With your calibration off, this will effect the serial port communication speed (or datalogging). In the setup configuration, there's a section called "Calibration=xxx". This allows you to re-adjust the calibration number. Download and run a program called CoolTerm and set this to 57600 baud, set ignore receive errors and connect. CoolTerm will display the serial output from the lcdboostcontroller. Now what you do is keep incrementing the Calibration number until garbage is displayed on the screen, once you've reached there click back until you find the highest stable calibration number, let's assume it is 170. Subtract 6 from our highest stable calibration number, and that is our ideal calibration number (170-6=164).

hmm, the scanmaster is able to display MPH, not sure how.

The scanmaster uses an extra wire on the diagnostic port to calculate speed by counting the pulses per second. I could do something similar too, but it would be so much nicer if we could just ask the ECU.

[2fnloud]

Blackstealth, I will be most likely contracting you about buying one of these for my AEM set up.

I read through your PDF last night, what would it cost to get a chip for AEM and ECU set ups?

I am not AEM right now, and I could see getting this integrated into my car before I do.

[vTaKwiTHsLiCkS]

The 98-99 ECU produce twice the fps vs 94-95 ECUs, so that part is normal.

The early LCDboostcontrollers were not calibrated, I made the mistake to assume the factory calibration was okay when my first unit tested fine and assumed the rest of my microprocessors would be identical when I purchased them altogether in a batch. Unfortunately the calibrations vary greatly. After learning this, I calibrated each unit since then, but the first 20 or so are not calibrated. With your calibration off, this will effect the serial port communication speed (or datalogging). In the setup configuration, there's a section called "Calibration=xxx". This allows you to re-adjust the calibration number. Download and run a program called CoolTerm and set this to 57600 baud, set ignore receive errors and connect. CoolTerm will display the serial output from the lcdboostcontroller. Now what you do is keep incrementing the Calibration number until garbage is displayed on the screen, once you've reached there click back until you find the highest stable calibration number, let's assume it is 170. Subtract 6 from our highest stable calibration number, and that is our ideal calibration number (170-6=164).

We actually did that yesterday and found out that serial output range was from 162-178. Your instruction manual suggests using the 3rd highest number so we had put it to 175. So I should put it to 172?
Originally the unit came calibrated to 170 and you suggest to me to try +2/-2. I'll try and dig further into this after work tonight.

[CoopKill]

I have had to calibrate as well, but not using the program mentioned. I could only rarely connect, and not for long. I calibrated by upping the number by 4, it connected, but would disconnect regularly. Upped it another 2, and it stays connected, but will disconnect sometimes when the overboost alarm is active.

I will try upping another 2 to see if this corrects the connection issue...

Edit: This is on a Hybrid ECU...

[vTaKwiTHsLiCkS]

I'm having a similar issue where whenever I hit boost, the lcd unit resets and tries to connect. It usually fails..
Very annoying since I pretty much can't see crap whenever I'm boosting. Somtimes resets under normal driving as well.

[BlackStealth]

(1) For those that are getting garbage data or disconnects during boosting, some cars have a grounding issue near the ECU (ground behind the passengers' console carpet). See this article:
Datalogging hell: Me VS. 94-95 electrical system - 3000GT/Stealth International Message Center

(2) As for calibration number, when you find your lowest & highest working calibration numbers and find the average, the average is the correct number. The reason for adding plus 2 to the average is to compensate for winter cold temperature, as temperature has a small influence. So how did I come up with minus 6 when you find the peak calibration number you ask? Every unit I've tested can operate + or -8 from the correct calibration number. I could just as well said add plus 10 when you find the lowest working calibration number. I hope this makes sense.

[Simace]

What I'd like to know is...

Are these two (2) distinct issues? (Logging Speed) (Connectivity) or are they one issue having both effects?

We're probably going to pull my blackbox and try it out on his car as we know it is working flawlessly in my '99. It logs at 100+ within EvoScan and its never had to be calibrated. Hopefully, this will help shed some light as to why this is all happening. Any other suggestions? Cause we have already looked at his ground wires, connections, etc. with no resolution.

[green-lantern]

hmm, the scanmaster is able to display MPH, not sure how.

I don't think mine did.