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

[BlackStealth]

I can have the LCDBC request "Load" from the ECU, and have a "Load vs Duty cycle table". I guess we would have to look at the flash ECU's table to get an idea of what to put in there.

[j2k4]

I have make the hand-held control I mentioned earlier - linky v v v so as to keep this thread uncluttered.

http://www.3sgto.org/f11/polyester-r...tml#post196565

[Jesters Deadd]

Antero.. I also have been getting noise over my obd11 on my LCDBC. My coolant temp will shoot up for no reason and give me a coolant warning then go back to normal... I would also like the improved circuit board.

[green-lantern]

Just like to say mine has been working great. that is all.

[j2k4]

Just like to say mine has been working great. that is all.

Good, because I will have questions soon.

[green-lantern]

Ha ha no prob

[BlackStealth]

Do you have any other ideas for gear based boost Antero?

Couple questions:
1. Are you using MUT protocol and which year model?
2. If you're using 98/99 year model, did you want to use the 2-byte load?
3. What did you want for scaling intervals? Assuming 1-byte load, it has a maximum of 160. So perhaps, 60,80,100,120,140,160? This will be similar to the temperature vs DutyCycle table that already exists, except it will be Load vs DutyCycle. My guess the trend will be a reduced DutyCycle correction as you approach closer to 160.

[TurboSinceBirth]

Couple questions:
1. Are you using MUT protocol and which year model?
2. If you're using 98/99 year model, did you want to use the 2-byte load?
3. What did you want for scaling intervals? Assuming 1-byte load, it has a maximum of 160. So perhaps, 60,80,100,120,140,160? This will be similar to the temperature vs DutyCycle table that already exists, except it will be Load vs DutyCycle. My guess the trend will be a reduced DutyCycle correction as you approach closer to 160.

1. Yes. 95 for right now but here very soon it will be a 98/99 flashed ECU because I'm past the comfortable limit with my setup necessitating the change.
2. I would like to use 2-byte load once I swap the flashed ECU in.
3. I'm not sure yet. When I get a good datalog I'll probably know depending on what load I hit but probably at least 250 if I had to guess where I was at if I had a working 2-byte load.

[BlackStealth]

Firmware 3.0 is out, but this is only for those with the newer 16/20mhz microprocessor ($20 shipping included). (1) Datalogging speed has been enhanced greatly:

8Mhz processor before: 100 frames/sec on Evoscan v2.6 and 99 ECU.
20Mhz processor after: 278 frames/sec.

(2) Knock and Coolant temperature alerts now use two readings (to avoid false-positive).
(3) New: ECU Load vs Dutycycle table.

[NickS VR4]

Firmware 3.0 is out, but this is only for those with the newer 16/20mhz microprocessor ($20 shipping included). (1) Datalogging speed has been enhanced greatly:

8Mhz processor before: 100 frames/sec on Evoscan v2.6 and 99 ECU.
20Mhz processor after: 278 frames/sec.

(2) Knock and Coolant temperature alerts now use two readings (to avoid false-positive).
(3) New: ECU Load vs Dutycycle table.

The pros for a 94/95 Hybrid ECU would be the more stable connection? Any other benefits? Better for boost control? $20 shipped to US, correct?