pcmhacking.net

sounds like your not using the right adx for logging ?

this is what i normally have when using the adx thats in the 12P v1.10 zip file.

Thanks Holden202, I was using "$12P-Message6-TP5-fixed dash" I've changed it to "OSE_$12P_v1.09_1BAR_TP5" which gives me ALL of the guages now & all appears to be working using the 2bar bin, mind you the VP didn't like running much, but I was logging. Now I'll have to see why the bins that I burnt yesterday didn't want to run properly.

Make sure you match the ADX (there is one for 1, 2 and 3 Bar) to the type of MAP sensor your using

Thanks VL400, I did notice that was several different ones.
Now out of the frying pan into the fire. I've found what I think is the problem that I had with the bins that burnt yesterday. I burnt several today & they all done the same thing as yesterday, cel light on & fan running & unable to connect with TP5. In my quest to test things, I have put the only known working bin into my chip burner to read the chip & it's now been corrupted. I have tested the burner in the laptop & the home pc, both the same thing. When you red the bin through TP5 every thing reads wrong, tables are maxed out, afr are nothing like they should etc. I think that I may know a bloke locally that has a burner that can help me in the short term whilst I sort something else out. I imagine that the correct path is a NVRAM setup that VL400 has.

I was a bit hasty with my diagnosis. I removed the eprom & fitted it to another memcal & the VP runs, connects to TP5 & logs. So now I've got to work out what I'm looking at.

nice work .... now what you need to do, once you have it logging, click on the record button up the top bar (the red circle beside the play button) and that will save the log from that point on, once you are finished hit the stop button and it will ask you to save the log file.

once you have a log post it up here and we'll be able to assist you in whats going on and also help you work out what your looking at.

Well I did a quick test run yesterday & here is the result. I wired the LM1 to the cars ecu in a previous test, but nothing appeared to change & the "wideband" is stationary. Do I have to disconnect the oem O2 sensor? or am I still not connected properly.

ok from what i can see the wideband input is not getting anything to it, so there must be something on the LM1 side of things, you need to use the LM1 Programmer software with the serial interface and have a look at the analog output options, make sure they are setup right and activated etc.

It's been a while since I done much with this engine. I had a play with the LM-1 & changed some settings, I'm now getting a reading in the History Table/wideband section, but I'm not sure if they are real numbers or bogus, it reads 7.3. The log is a N/A V6 on methanol. When I downloaded the LM-1, it was showing readings between .87-1.0 lambda.
How do I change the Wide Band setting in the "Dash" as it reads between 10-20 AFR or is that the setting.
In this particular log the engine was hunting, which I'm trying to fix.

do you mean the wideband display from $12P to the tunerpro dash? there is an xdf item called "VE Learn Params - WideBand 0v AFR" just type in the AFR you want it to display when your LM1 is inputting 0v to the ecm, then "VE Learn Params - WideBand 5v AFR", just type in the AFR you want it to display when your LM1 is inputting 5V to the ecm.