RomRaider

I can connect my lc-1 to logworks, and it reads the wideband properly.

i connect my lc-1 to romraider logger, select com port, and check the device box.

data shows up, at idle it reads 4.7 not 14.7. i'm very confused.

when the car was off and my gauge was reading 20.4 the logger was reading 14.7.

i made sure that this was one of thenewest versions.

version 0.5.0 build 83

any ideas?

On my car (07 2.5i), when the car is "off" (i.e., the ECU is no longer sending data to the laptop) RR will display the last data it received for all the selected parameters. The LC-1 might be showing 20.4 because its still monitoring the sensor and displaying data. Just my hypothesis.

this is happening no matter what state the car is in, on, idling, cruising.

it's giving me values that dont make sense. like 4.xx 3.xxx while my gauge is reading normal, 14, 13's etc.

I got the same miss readings on mine. It was suggested that I pull the sensor out and do a free air recalibration. Now it works a ok…just a thought

Use LM-1 programmer and make sure that the calibration is set to gasoline. Sometimes it changes itself to custom.

Bingo.

I had the same problem with mine. I messed with it for a week before calling Innovate for help. I had installed it correctly according to the instructions and had performed several heater and free air calibrations and it still wasn't reading correctly. The trick was to go into LM Programmer and change the fuel type to something other than gasoline. Then cycle the unit and change it back to gas, then do a free air cailbration. Here's the steps I did to fix it.


1. Remove o2 sensor from exhaust and set it on something or let it hang in the air (make sure it's not touching anything that would be damaged when it heats up)

2. Turn the key to on (but don't start the car obviously) and connect your laptop to the LC-1 and run the LM Programmer software (comes w/ LogWorks on the CD that was included in your kit or can be downloaded from the Innovate web site)

3. Change fuel type to anything other than gasoline and save the settings.

4. Turn off the key and wait 10 seconds.

5. Turn the key back on and connect the LM Programmer software again and this time set it to gasoline, save and exit.

7. Turn off the key and wait 10 seconds.

8. Turn the key back on and this time run LogWorks and connect to the LC-1 (if you haven't used it before it will need to setup a gauge - just let it do the automatic setup).

9. Now while watching the gauge in LogWorks, force a free air calibration (use the button if you installed it, otherwise just ground the black wire for 3 seconds). You will see confirmation that the sensor is calibrating on screen, this way you can visually confirm it happened with no errors. Note: You can calibrate it without using LogWorks but you won't know if it worked so I prefer using the software.

10. Turn off the key and carefully re-install the sensor (it will be hot).

i'll work on recalibrating it, i think alot of you are misunderstanding the problem.


my gauge reads 14.7 at idle.

logging in romraider reads some number between 3.xx and 5.xx (yes afr is checked)

logging using logworks 3.0 gives me the same numbers that my gauge is seeing.

i cannot connect to the thing using LM programmer, but if i use logworks, and select gasoline as the fuel type, the numbers are right on. so it should be set for gasoline

time for a recal, hope that fixes it.

I am having the exact same problem...data is accurate in logworks but not in romraider and readings are 4.3-4.7 at idle. Its almost as if RR is exactly 10 points off. I'm surprised more people aren't seeing this as well. I'll post if I figure it out. Any ideas?

PS: I have been able to successfully calibrate the sensor, use logworks, and LM programmer to confirm its on the gas (14.7 stoich) settings. Its just RR that has the issue.

LC-1 's need calibrating regularly in my experience.

I tend to do a full heater/free air calibration every few weeks to make sure it is not going awry.

This has happened to me before - but I interpreted this as a glitch from selecting the LC-1 before it has heated up correctly.

Have you got the LED indicator connected? If not, you will find it hard to work out what may be occurring. When the LED indicator is connected, and this happens (odd readings of 4 etc) you will notice that the indicator is still blinking (flashing), which indicates the LC-1 sensor is not at opperating temp.

If you wait until the LED indicator is solid/stays-on and then select the LC-1 pl;ugin, the com port, and then check the LC-1 parameter in the logger it should work without probs.





Note: I could be wrong in drawing my conclusion, but the LED indicator was blinking when it happened to me, and when the LED indicator is solid the LC-1 works without any problems.

again, the readout is correct in logworks, but incorrect in romraider.

the sensor is at temp.

Do you have the indicator connected?

yup, indicator LED is working. The sensor is heated and LED is solid before selecting in Romraider. Also, the sensor is properly calibrated and reads accurately in logworks. It really is just a Romraider problem, hence the post in RR troubleshooting. If anyone's figured this out, please post up.

Uninstall the version of romraider you have and install the latest beta version HERE

Hey, I would highly suggest you mess around with the LM Programmer because mine was switched to custom setting instead of gas and lambda read out instead of afr. so if you havent done that yet then you need to because i was having the same problem as you exactly and i figured out that it wasnt romraiders fault because i used evoscan too and it was reading the same thing as RR. Now everything is working correctly for me, im not sure if im going to have to select the com ports everytime though but im guessing i am.