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

[mojo3120]

I honestly wouldn't know from looking at the code... We'll just have to try it and see if it does the trick. Is that your link? You have any info on the file?

Yea that's my link.

I think it's the file from this thread EVOSCAN xml settings file for the 3S - 3000GT/Stealth International Message Center

All the links over there are dead. I can't remember where exactly I got it, just remember it wasn't easy to find.

[RealMcCoy]

Yea that's my link.

I think it's the file from this thread EVOSCAN xml settings file for the 3S - 3000GT/Stealth International Message Center

All the links over there are dead. I can't remember where exactly I got it, just remember it wasn't easy to find.

Yea, that thread is where I learned about it's existence, but all the links were dead by the time I found it... Have you been able to use it with 2.8? or do you need an earlier version?

[RealMcCoy]

So what kind of sample rates has everyone been getting with Evoscan? I bailed on MMcd and the palm because I was only getting 2hz. I just discovered last night that my Evoscan is sampling at the same rate... I'm only getting two samples per second. I discovered it when I found a section of graph where the RPM and boost changed during a shift, but it missed the throttle lift completely. Started looking at the time stamps and realized what was going on...

[Jimvr4]

So what kind of sample rates has everyone been getting with Evoscan? I bailed on MMcd and the palm because I was only getting 2hz. I just discovered last night that my Evoscan is sampling at the same rate... I'm only getting two samples per second. I discovered it when I found a section of graph where the RPM and boost changed during a shift, but it missed the throttle lift completely. Started looking at the time stamps and realized what was going on...

On my own USB to ISO9141 converter and my 95 hybrid ECU I get about 60 samples per second. The same cable on a 96 ECU only gets like 15 samples per second. I can't connect to a 1st gen with my setup though.

[BlackStealth]

RealMcCoy, I noticed on your video you had the ScreenRefresh=3 (smallest delay possible), the default is around 24. I've tied the intake temperature request, and coolant temperature request to this ScreenRefresh rate. What this means is that the lcdboostcontroller is requesting to the ECU like this:

Knock request, (user datalog request), RPM request, (user datalog request), Intake request, (user datalog request), Coolant request, (user datalog request), ...

The Intake request and Coolant request are being forced to sample frequently instead of infrequently. I will re-write the code so they're tied to a timestamp instead, so ScreenRefresh rate has no impact.

If the datalogger software doesn't request (Knock, RPM, Intake temp, coolant temp) then it will log slower because two devices are talking to the ECU and neither have common requests. However, if the datalogger software requests (Knock, RPM, Intake temp, coolant temp) it will have an immediate reply because those requests are stored.

If you want very high speed datalogging, the raw Text Mode datalog option will spit out data even faster, especially Boost and WBO2 data (because they're not restricted). At the moment I use a terminal software to capture the text data, but it would be even nicer if someone wrote a program to capture this data live and present the data in a graphical manner. Boost and WBO2 have very high resolution, and the rest of the ECU data would be limited to the constraints of the MUT/OBD1 communication protocol (60 samples/sec or whatever it can push out).

[BlackStealth]

I made a small update (v2.15), Coolant and Intake temperatures scan every 1 second regardless of what ScreenRefresh is set to. This allows other higher priority requests more access to the ECU.

[green-lantern]

New firmware2.07 is up on http://www.lcdboostcontroller.com .
Here's a list of changes that aren't in the manual yet.

Inside the setup config menus:

WBO2 input=none
(WBO2 is replaced with NBO2 in main screen).


Push to toggle
startup color
7 total colors to choose from (Red, Green, Blue, Cyan, Yellow, Purple, White).


PSIsensor=Intrnl (Internal 2.5bar 0-36.3psi sensor)
=Gr4Bar (Greddy 4 bar pressure sensor)
=GM3Bar (GM 3 bar pressure sensor)


Datalog=Off (no datalog operations)
=passthru (allows external dataloggers such as HHH, Evoscan)
=TxtMode1 (57.6k serial, timestamp, PSI, WBO2, Knock, RPM)
=TxtMode2 (57.6k serial, timestamp, PSI, WBO2, Knock, RPM, EngineLoad)
=TxtMode3 (57.6k serial, timestamp, PSI, WBO2, Knock, RPM, EngineLoad, Timing)
A free program called CoolTerm can be used to monitor the serial port at 57.6k baud (8N1).


PassThru=1953 baud (OBD1 speed)
=57600 baud (HHH, Evoscan)
=15625 baud (Evoscan)


AudioBuzzer=On (Alert audio on)
=Off (Alert audio off)


98/99 3000GT=Yes (support for different rear fuel trim codes)
=No


Test solenoid = Activates boost solenoid at 50% duty cycle for 2 seconds.


Test Buzzer = Activates audio buzzer for 1 second.


Calibration=xxx

Factory calibration can be tweaked for more reliable 57.6K serial connection.
When editing the calibration number, the datalogging port will broadcast a string of
"0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklm nopqrstuvwxyz" continously. If the string appears incorrectly, your calibration number is no good. Generally there are 16 valid calibration numbers, the ideal calibration number is not the highest value but the third highest. A free program called CoolTerm can be used to monitor the serial port at 57600 baud (8N1).


On the "WBO2 PSI KNOCK" main screen, if you quickly press the button it will toggle the display from bright to dim. Pressing again will make it bright again. Holding the button down longer (1 second) will toggle the display colors.


On the "Throttle Airflow" screen, pushing the button quickly will allow you to cycle through the colors faster.

Is there any other changes that aren't in the manual?

[BlackStealth]

Is there any other changes that aren't in the manual?

I believe the user manual is up to date. I plan on making a separate generation 2 installation manual because of the minor differences.

[Simace]

Any word on the bluetooth option? Is it expected to work with MMCD for Android?

[BlackStealth]

I have one bluetooth module and a batch of bluetooth circuit boards to fit as an expansion card. My early bluetooth prototype communicated no problems to a terminal program on the PC via bluetooth. As for testing it further, it's in limbo at the moment. I don't have access to an Android at the moment.