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

FeaRpb: nice install.

Firmware 3.01 is now made available. I made an emphasis on datalogging, such that you can pick whatever you like to datalog and it won't slow down. It will maintain high speed. I also took advantage of some parallel processing such that when Boost, WBO2, Oil Pressure or EGT sensor is being measured it does not halt the microprocessor, so the microprocessor can keep on working. Chrome 2.0 mod is supported for 98/99 flashECU users. This means the special 2-Byte Airflow and 2-Byte Load are supported. The Load vs Dutycycle will automatically switch to 2-Byte load when Chrome ECU is selected in the setup config.

I think your user manual is dated.

Under the Setup Config in the manual it seems to have different things listed than what are actually in the config menu. Or maybe I am just crazy..

Quote:

---

Originally Posted by FeaRpb

I think your user manual is dated.

Under the Setup Config in the manual it seems to have different things listed than what are actually in the config menu. Or maybe I am just crazy..

---

Yup, you're correct, it's dated.

Do you have any plans on updating it? And also, the website seems to be down.

Quote:

---

Originally Posted by FeaRpb

Do you have any plans on updating it? And also, the website seems to be down.

---

I update it from time to time. The website does not belong to me, it belongs to a user on here. Hopefully it comes back online soon.

Well I couldn't wait anymore for the original website to come back up again, so here's another website for updates:

http://www.lcdbc.xp3.biz

The new processor and firmware fixed the problems with MMcd... It absolutely screams along now. I was getting 35 hz logging 11 items. That's about 385 samples per second. That's at least three times faster than I've ever seen it communicate with the 1st gen directly.

I'm assuming the LCDBC doesn't communicate with the 1st gen ECU that fast...? It's just now able to pass info on to the logger without interrupting the primary communication? I'm probably getting some duplicate readings when the logger requests info that hasn't been re-sampled yet?

Still don't know how to log WBO2 and Boost... But it's not a big deal to me yet. I can log boost through EGRT, and I don't have a WBO2 yet.

Yes you're correct that the samples are too fast for OBD1. This is what I have done:
(1) LCDBC makes requests to OBD1 ECU (~ 72 samples/sec, whatever the maximum OBD1 ECU can produce).
(2) LCDBC stores the results into memory
(3) LCDBC accepts new requests from datalogger device, and adds it to it's list of "items to datalog" from ECU.
(4) While the LCDBC waits for response from OBD1 ECU, it checks to see if dataloger device is asking. It replies with an answer stored from memory instead of waiting. This is where crazy speed increase comes from.

So in short, yes the sample speed are too fast. I can introduce a delay at step 4 to bring the sample speed back down. I was just waiting for feedback if I should do that or not.

Im not sure if this is a feature or not, but is there a low boost and high boost setting? If not, how hard would it be to make one?

Quote:

---

Originally Posted by BlackStealth

Well I couldn't wait anymore for the original website to come back up again, so here's another website for updates:

http://www.lcdbc.xp3.biz

---

I'm planning on posting my install stuff here soon when I get a chance. If you want you can use the info in it for a new manual or just link to it. IDC whatever you want to do.