Have a serial to usb converter...have a prolific driver correctly installed

Have tried to log both my evos and friends Evo yet it wont work

1) Evoscan shows the comport and I get to pick it

2) I have opened my comport manager and usually and it shows its connects

3) I go to advance comport setting and even tried changing it to a different comport to no success

4) Tried using rear o2 sensor all formulas suck and are way off

 

which brand usb to rs232 converter are you using?

 

prolific

 

try using a terminal emulator like Tera Term to confirm that you are getting serial data from the UEGO. Just run Tera Term and select the comport that the UEGO is on. If it's working correctly you should see a readout in the emulator. If not there's something wrong with your sensor or converter

 

I ran tera term and verified the gauge is working. I still cannot get it to log into evoscan though. I have even tried aem serial software as well and keep getting a port issue and other errors. Any advice on what to check in evoscan and how to set it properly to work with the gauge. I am using version 2.9.

 

2.9 would be the best to use for now. Do you have anything against logging it via your stock ecu? If you dont want to do that, I would recommend getting a Belkin F5U409 USB-Serial Adapter. These are the ones Ive always ran with EvoScan for the last 10 years. Tried and true. Some of the other brands drivers dont work well with the software. Ive went through a few different brands to understand this.

 

i was never happy with evoscan so i figured out how to use my openport 2.0 to standalone log. it works a million times better than i ever got from evoscan and it logs my aem uego via the serial port.

 

Try mitsulogger to rule out its not a cable issue. I had issues when I upgraded to windows 10 but just needed to uninstall and reinstall the right drivers.

 

Dare I ask why you were not happy with evoscan? Or did you did not know how to work it?

 

Hey guys thanks for the responses. So i finally figured out the issue after troubleshooting every possible hardware and software aspect. The issue the the newest version of openport has issues communicating with evoscan. Hamish told me to use openport version 1.43.3252 and it instantly fixed my issue once the 9600 baud version aem gauge in the drop down. i am going to test configuring my connection to a higher baud rate and also selecting and higher baud rate on the gauge drop down to see if that helps improve response times.
New issue though. I have no narrowband O2 sensor so i keep getting a CEL. I hear that the front O2 sensor is required in order to control fuel dumping within the ECU. TO me this makes sense since the wideband is only used for logging and tuning the bad part is having to modify stuff again and then hardwiring a narrowband O2 sensor. If im wrong please correct me.

 

the windows tablet is downright ****, the software was slow and clunky, dont like carrying around a laptop, etc etc
with the openport 2.0 i plug it in and go. kind of hard to go back now. i still use evoscan for clearing codes though.