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

[BlackStealth]

I found the correct version of the uprated MAX232A chip here:

https://www.elfa.se/elfa3~se_en/elfa...=MAX232AEPE%2B

Should I order some new capacitors as well in case thats the reason why the chip fried in the first place?

Yes that IC will work. Four 1uF (SMD 1206 size) are used, it's up to you. Again make sure the parts work below 0C. Does your replacement voltage regulator work below 0C? I will send you a couple MAX232EPE+ and a replacement LM7805 in the mail.

Edit: Also when the boxed version LCDBC communicates OBD2/MUT it does not use the MAX232 chip. The jumpers select whether to use MAX232 for OBD1 communication, or use the OBD2/MUT IC.

[Unlogic]

I ended up not using the replacement voltage regulators cause they all overheated just as fast the fairchild version. Instead I mounted a heatsink on the fairchild voltage regulator which kept it from overheating although it still got really hot until I removed the MAX232 chip.

I hadn't noticed that capacitors were surface mounted. Since I don't have the equipment to replace those I'll leave the old ones in place and hope they are still okay.

If the MAX232 chip isn't used for the MUT logging then we still have a gremlin to hunt down cause I shortened the cables to the main serial port as much as I could and added a ferrite core but I still got the same disconnect/unable to reconnect problem just as before. The disconnects seem to happen at the same time interval ~5 minutes after the box is turned on. Restarting the box always solves the problem.

Could it be a software problem or some kind of static charge building up in the hardware?

[fastbikes76]

If the MAX232 chip isn't used for the MUT logging then we still have a gremlin to hunt down cause I shortened the cables to the main serial port as much as I could and added a ferrite core but I still got the same disconnect/unable to reconnect problem just as before. The disconnects seem to have at the same time interval ~5 minutes after the box is turned on. Restarting the box always solves the problem.

Could it be a software problem or some kind of static charge building up in the hardware?

Exact symptoms as me.

8-)

[BlackStealth]

As soon as I finish building an enhanced OBD2/MUT cable I will test it for more than 5 minutes to see if I can get the same thing to happen.

[fastbikes76]

Hi ,

Can you tell me what cable I need to log from the LCDBC direct to my laptop please ?? I normally use a OBDII to USB cable which works fine, now I want to log through the unit so I am log afr's etc

Here I a pic of the ports on my laptop
ImageUploadedByTapatalk1378057342.328469.jpg

Cheers
Elton

[Unlogic]

I theory you should be fine with just a normal USB-Serial adapter (such as this one).

However I didn't manage to get it working before the serial chip LCDBC in my unit started misbehaving.

[fastbikes76]

I theory you should be fine with just a normal USB-Serial adapter (such as this one).



However I didn't manage to get it working before the serial chip LCDBC in my unit started misbehaving.

Ah , you a star mate.

Now can you find me the picture in this thread that show what you change in evoscan to log wideband and boost ??

I can't chuffing find it ! Lol

[Unlogic]

Those pictures are in the manual I think. Have a look here: http://www.lcdbc.xp3.biz

[fastbikes76]

OK, so I have V2.9 and the V2.7 in the pics is different form what I have in my list ?

Can anyone with V2.9 tell me which functions I alter to log WB and boost ?

I do see one that says.... .Boost (MAP), request 38, function 0.01334*x , units BAR
and another is .............. AFR Map, request 32, function (14.7*128)/x , units AFR

Would those be the ones I change in V2.9 ??

Cheers for the idiots guide Lol

EDIT,

I also have a cable this cable http://www.ebay.co.uk/itm/USB-2-0-TO...item336fcb4ab9

It wont connect to Evoscan ? I guess its not the right one then ?

[BlackStealth]

Evoscan is picky software, in that it requires you to use an FTDI-based chipset USB-to-serial adapter. If you have HHH OBD1 it will work with any USB-to-serial adapter when in 57.6k mode.

I created two new entries in Evoscan to datalog Boost and WBO2 data from the LCDBC -- that is why you can't find them. You need to edit them in.