EvoScan w/LC-1 Problems/Warning!
EvoScan w/LC-1 Problems/Warning!
I am finally getting to work with EvoScan and my LC-1/XD-16 Wideband.
As many others have stated, it is not working correctly. However even worse, it reprogrammed my XD-16 gauge!!!!!!!!!!
So a word to the wise, if you do not want to risk having your XD-16 reprogrammed wait until the problems are sorted out. I believe Ludikraut had the same problem.
To clarify a bit more, I was having a problem with my USB to serial cable. It was recognized by the system as my GPS device. This may or may not have been the problem. But since Ludikraut reported a similar issue I thought I would get the word out.
I initally thought it (EvoScan or my USB to Serial) had messed with the LC-1 but I used LogWorks to verify the problem. It was thankfully reading the AFRs normally.
As a final note my afrs in EvoScan are 47 at idle. I have a feeling that there is an error in the device recognition (it sees the LC-1 as the LM-1) or there is an error in the sub-packet info. There is a pretty significant difference in the way that the LM-1 and LC-1 communicate the data. The LC-1 uses two "words" and the LM-1 uses 7 "words" among other differences.
UPDATE:
It looks like evoscan or my usb to serial has "f"ed with my LC-1. I am researching my next steps. I may have to reinstall the firmware (now isn't that fun
). My readout after trying to recalibrate is going nuts bouncing back and forth between % and Lambda. When I looked at the settings it had gone to a "custom" setting instead of the 14:7 stoicometric. This sucks.
As many others have stated, it is not working correctly. However even worse, it reprogrammed my XD-16 gauge!!!!!!!!!!
So a word to the wise, if you do not want to risk having your XD-16 reprogrammed wait until the problems are sorted out. I believe Ludikraut had the same problem.
To clarify a bit more, I was having a problem with my USB to serial cable. It was recognized by the system as my GPS device. This may or may not have been the problem. But since Ludikraut reported a similar issue I thought I would get the word out.
I initally thought it (EvoScan or my USB to Serial) had messed with the LC-1 but I used LogWorks to verify the problem. It was thankfully reading the AFRs normally.
As a final note my afrs in EvoScan are 47 at idle. I have a feeling that there is an error in the device recognition (it sees the LC-1 as the LM-1) or there is an error in the sub-packet info. There is a pretty significant difference in the way that the LM-1 and LC-1 communicate the data. The LC-1 uses two "words" and the LM-1 uses 7 "words" among other differences.
UPDATE:
It looks like evoscan or my usb to serial has "f"ed with my LC-1. I am researching my next steps. I may have to reinstall the firmware (now isn't that fun
). My readout after trying to recalibrate is going nuts bouncing back and forth between % and Lambda. When I looked at the settings it had gone to a "custom" setting instead of the 14:7 stoicometric. This sucks.
Last edited by chmodlf; Sep 17, 2006 at 03:08 PM.
