You do have the white connector unplugged, right?

Where is your LC1 grounded, perhaps offsets are effecting the ECU since the laptop is using ECU ground (ultimately engine). Are you grounded to block?

 

I wonder what your code does differently than mine, I haven't had any reports of this happening with Mitsulogger.

I don't toggle the RTS/CTS or DTR signals when I initialize the port.. One of those would definitely set the init pin high.. I also don't poll the port as a com port which could force it to reset. HOWEVER OBD-Scantech does do that, and doesn't trigger the init pin.

 

I had the same problem with .98, Even with the white connector unplugged. .99 works fine though.

 

I have ecu+, logworks and mitsulogger all working. With or without the white plug.
The lc-1 works in ecu+ and logworks.

maybe its a driver thing with the logworks.

 

For some reason the first log I did wont show hp and tq on the graph. I can open the second one and it reads fine and then without changing anything try to open the first and it doesnt show power. The only difference was I opened the graph and clicked on calc. power and tq before logging.

 

I tested it a lot more with EvoScan, and it seems fine,

Disconnect the reflash connector when not using it, because no matter what program, if you plug/unplug the usb cable from the pc while driving it will reset the car ecu, obviously the ftdi driver sending an unknown signal to the vehicle via the reflash connector.

 

Hamish, I have not been able to get the LM-1 working. When logging all the fields under AFR come up empty. It works fine with Mitsulogger, but I just have not been able to get it working with EvoScan.

 

Hamish -- I am running a Zeitronix Wideband w/ Boost sensor. I am able to log AFRs using v.99, but the MAP readings make no sense to me (don't appear to be correct). I should be seeing peak boost of ~24.5 psi at 3500, but am seeing 47.79 (MAP).

What does MAP really represent and what are the units of measure? Where can I see my boost / vacuum? Thanks

 

Sounds like the number is doubled.

 

I think something is wrong with the code, because MAP goes to 47.79 the second I go 100% TPS. Clearly it is not boost ....

 

The fuel trims are mislabeled.

Fuel Trim High should be Fuel Trim Low - Request ID should be 0E currently is 0C

Fuel Trim Low should be Fuel Trim High - Request ID should be 0C currently is 0E

The reason that I noticed this is my fuel trim high never varied from 100. With the new version of EvoScan it was off.

I verified this in Mitsulogger.

The XML defs need to be corrected.

 

i tested evoscan .99 over the weekend and everything seems to work fine for me.

does anyone have any real good guage layout they want to share.

 

ARe you sure that you looked at the request IDs for the high and low fuel trim?

I have a hard time believing that only my install corrupted those xml defs...

But then again I have seen some crazy shizit.

 

Good to know.

This should be included as one of the many other facts pertaining to the "protocol of open port logging" which needs to be listed somewhere.

Hell, I just started my own list

 

you are correct, my low and high fuel trim is also backward.