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

[fastbikes76]

Other comments:
(1) When you install FTDI drivers, you will need to reboot windows, it won't work correctly until you do.
(2) When you want to use Evoscan, first allow LCDBC connect to the ECU and then use Evoscan to connect. Should the LCDBC get disconnected from the ECU, Evoscan will continue to receive data from the LCDBC; the data will be static except for Boost and WBO2 info. When LCDBC attempts to reconnect to ECU it will ignore Evoscan requests at that moment and then resume.
(3) When you adjusted the screen refresh rate to 2, this already indicates there's a problem with communication between LCDBC and ECU. If the LCDBC cannot get info from the ECU, it won't have anything to update the screen with.
(4) Previous versions of LCDBC used Texas Instruments MAX232EIN chips and never had a problem with those. Now that I use Maximum MAX232EPE+ chips we have our first bad chip, and hopefully last.
(5) Evoscan calculates Coolant and Air temperatures incorrectly for our cars; LCDBC uses an internal table to report correct values.
(6) "Can I replace the 2N3904 with a BC337 and the 2N3906 with a BC327?" Yes.

Once again , thanks for taking the time to work toward a solution for us. Hopefully the adapter takes away any noise and stops the disruptions.

A few points too note..

1) windows was rebooted with no difference

2) I tried it this way with zero success. The ONLY way I can connect is using the 10 steps I listed earlier. Using my method I can connect EVERY time, using your method it has not connected even once.

3) I agree there is a communication issue between LCDBC and ECU, however I have zero issues connecting evoscan to my ECU direct from obd2 port and no issues logging as well as no issues with slow info or data from ECU. The only time info is slowed down from ECU is via LCDBC

4) I hope so too

5) thanks for clearing that up, I shall take note of the LCDBC reading instead

6) no relevance too me.


Kind regards
Elton

[Unlogic]

Here is the OBD2/MUT adapter I am working on. It includes a 33uH and 82pF components for a band pass filter to further reject noise. I will have these PCB made ASAP.

That looks great, can't wait until it's ready!

As a stopgap measure I started building my own filter tonight based on the electrical diagram you posted earlier. I figured out that the 2N3904 could be replaced by a BC547B and the 2N3906 by a BC327 which I managed to source locally.

However I just wanted to double check before I start cutting the PCB and chop up the serial extension cable I bought. Does the filter run in parallel with the normal wiring of the serial cable or should I cut all the wires in my serial cable and only run those listed in the diagram?







PS. I'll remove R1 from the board.

[BlackStealth]

fastbikes76: Awesome, you have a cable that connects all the time. Which cable is it? I will dissect it to discover it's secret.

[Unlogic]

I just wanted to double check before I start cutting the PCB and chop up the serial extension cable I bought. Does the filter run in parallel with the normal wiring of the serial cable or should I cut all the wires in my serial cable and only run those listed in the diagram?

I've been staring at the diagram without figuring this one out for 30 minutes now. Got a hint for me Blackstealth?

[BlackStealth]

Here's an updated circuit. The DB9 pin out information can be misleading, I am pretty sure those pin out numbers are from a solder cup point of view (not the connector face). Better yet, check to see if your DB9 connectors have tiny numbers labelled to prevent a mix up.

When this adapter is completed, it goes in between the OBD2/MUT cable and LCDBC device. Next you need to change two jumpers: remove the criss-cross cable, and move the red jumpers to select "OBD1". This essentially tells the LCDBC not to use the built in OBD2/MUT chip anymore from pin 4 and to use serial data from pins 2 and 3 instead. A MAX232 serial chip will have to be in place.

[Unlogic]

Thanks!

I'll finish the filter tomorrow and give it a try as soon as the new MAX232 chips arrive.

[fastbikes76]

fastbikes76: Awesome, you have a cable that connects all the time. Which cable is it? I will dissect it to discover it's secret.

This is the serial/USB cable I have just bought

FTDI USB to RS232 Serial Adapter Converter, 1.2m long screened cable HAM Radio | eBay

IN the interest of scienc ei have just tried again buy doing the following...

A full shutdown and restart of my laptop.

Started car and waited for LCDBC to connect
Then tried to connect Evoscan.

Doing it the proper way I get an error telling me to turn the car off and try again ???

I then turned ignition off, connected evoscan which connected first time instantly, stopped evoscan and then started car...once lcdbc had connected I start evoscan again and can log perfectly.

As before the ONLY way to connect evoscan is too follow my 10 step listed earlier and it will connect first time every time. If you try connect the normal manner it just throws up an error. Also if you try connecting evoscan with the ignition off and NOT first trying to connect with it on first, then evoscan wont connect either. It seems my sequence has to be followed for it too work faultlessly



Cheers
Elton

[fastbikes76]

Ok so I went for a drive today and it will log through evoscan BUT the info gets all corrupt half way through a log .. It seems mainly as you start getting into the upper rpm and on full boost. I haven't been able to do a single clean log through the LCDBC but evoscan work perfectly on its own.

I am still getting the disconnects and no reconnect as before.

If anyone wants a log from the evoscan showing the bad info just tell me how and where to send it.

Cheers
Elton

[Unlogic]

I have made some progress today on some of the issues we've been encountering with that latest version of the LCDBC.

First I installed a new MAX232AEPE chip and that seems to have brought my extension serial port to life cause the 3.11 update flashed on the first attempt.





Next I finished the filter/adapter circuit I started working on earlier this week (note without the band-pass stuff).



With the LCDBC upgraded to version 3.11 and the filter in place the disconnects and false knock reading have been significantly reduced. Whats even better is that when it disconnects it always manages to reconnect automatically by itself.

However I still see occasional slowdowns lasting for several seconds. There seems to be a pattern to this issue, I'll see if I can film it next time it starts happening.

Tomorrow I'll try to do some testing with CoolTerm or EvoScan to verify if the new MAX232A chip solves the connections issues fastbikes have been encountering.

[NickS VR4]

I have made some progress today on some of the issues we've been encountering with that latest version of the LCDBC.

First I installed a new MAX232AEPE chip and that seems to have brought my extension serial port to life cause the 3.11 update flashed on the first attempt.





Next I finished the filter/adapter circuit I started working on earlier this week (note without the band-pass stuff).



With the LCDBC upgraded to version 3.11 and the filter in place the disconnects and false knock reading have been significantly reduced. Whats even better is that when it disconnects it always manages to reconnect automatically by itself.

However I still see occasional slowdowns lasting for several seconds. There seems to be a pattern to this issue, I'll see if I can film it next time it starts happening.

Tomorrow I'll try to do some testing with CoolTerm or EvoScan to verify if the new MAX232A chip solves the connections issues fastbikes have been encountering.

Haven't been following. Is this chip the 20mhz one I bought from here? Everything is still in a box. I'll check later.

Sent from my Galaxy Nexus using Tapatalk 4