Can someone confirm, the max voltage a chipped pm6 can handle on the O2 line is 3.8v?

I have a new-to-me lm-1, and dont want to melt anything while I am logging.

If anyone has best practices, like a good lower voltage to use that still provides good resolution, I am all ears. Thanks..

 

You won't melt anything by giving it a little more voltage than it can read accurately.

 

from what ive read, it wont read anything over 3.8 volts....but you can still send it 5 volts, it just cuts it to 3.8.

(disclaimer) this is from memory and im not sure if its 100% correct...or if its even for the pm6. i dont remember if i've ever had my lc-1 set like that before...

when i used to use the analog output for logging o2, i had it set at 20 afr=2.0 v and 8 afr=0.8 v. i mainly had it set like that for my hm "voltmeter" gauge.

now i just log o2 digitally through the serial line into ecucontrol...works perfectly every time. i am using the innovate db (nordskog) gauge with the analog output now...thats basically dead nuts also (it uses the default analog out settings).

i wouldnt even bother trying it... depending on what you are using to datalog, just set up an easy linear function that matches your datalogger formulas and lm programmer.

 

the input can handle just under battery voltage before any damage occurs, but the input clamps the voltage at a max of 3.8V. This can be modified to increase the clamp to 5V. But typically not necessary since the desired A/Fs are not in the 3.8+V range. (or even close to it)

 

as a follow up to my previous question, I had the wideband hooked up, and I wired it so the first analog out channel is plugged in to the stock narrowband wiring.

The car ran like crap, and i was getting some very scary A/F numbers, like 20:1 in mid throttle. I swapped all the wiring out again, and went back to the stock narrowband, and the car runs like nothing happened. The ecu is running the stock pm6 code copied into the ng60 rom, so i am nearly certain that AFR is wrong, and my car has about 15k miles on that chip with no knock or anything, so i don't think its the chip.

I keep thinking that i had the channel one analog voltage constraints off, causing the ecu to flip out, but i double checked and it was supposed to output 1.098 v at ~0.96 lambda, and .1xx v at 1.03 lambda.

My 2 thoughts on the problem are: one, the voltage ouput constraints were wrong, although i think i used the stock setting on the LM-1, and my second idea is i should actually have the 02 turned off in turboedit. I did mess around with the narrowband voltage constraints to more accurately mirror the narrowband graph here http://mycomputerninja.com/~jo....html but i don't think they were much different from that top graph, and the direction of slope was definitely right.

I do have 2 o2 bungs, and i am running the pm6, so i could just plug in the wideband and leave the narrowband intact, but i would like to datalog the car through ecucontrol so i have all the data together on the same refresh intervals.

 

check how its all grounded... read the tips on the innovative forms...

 

thanks. i will.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by sanimalp &raquo;</TD></TR><TR><TD CLASS="quote">as a follow up to my previous question, I had the wideband hooked up, and I wired it so the first analog out channel is plugged in to the stock narrowband wiring.

The car ran like crap, and i was getting some very scary A/F numbers, like 20:1 in mid throttle. I swapped all the wiring out again, and went back to the stock narrowband, and the car runs like nothing happened. The ecu is running the stock pm6 code copied into the ng60 rom, so i am nearly certain that AFR is wrong, and my car has about 15k miles on that chip with no knock or anything, so i don't think its the chip.

I keep thinking that i had the channel one analog voltage constraints off, causing the ecu to flip out, but i double checked and it was supposed to output 1.098 v at ~0.96 lambda, and .1xx v at 1.03 lambda.

My 2 thoughts on the problem are: one, the voltage ouput constraints were wrong, although i think i used the stock setting on the LM-1, and my second idea is i should actually have the 02 turned off in turboedit. I did mess around with the narrowband voltage constraints to more accurately mirror the narrowband graph here http://mycomputerninja.com/~jo....html but i don't think they were much different from that top graph, and the direction of slope was definitely right.

I do have 2 o2 bungs, and i am running the pm6, so i could just plug in the wideband and leave the narrowband intact, but i would like to datalog the car through ecucontrol so i have all the data together on the same refresh intervals.
</TD></TR></TABLE>

if your plugging in the analog output (brown wb wire) into the stock o2 pin, then you should have the stock o2 sensor unplugged and have the o2 disabled in TE. otherwise it will adjust fuel until it gets the .5v that its aiming for..to a certain extent.

if your using ecucontrol and you have 2 serial or usb ports, id suggest trying the newer ecucontrol. you can connect to up to 8 innovate devices, and the ecu without having to screw around with unplugging the o2. it logs the innovate values right in series with teh ecu so your refresh intervals are basically the same as using the analog output.

http://forum.pgmfi.org/viewtopic.php?f=60&t=14776

i have had success logging/map tracing afr and egt along will all the factory sensors...using an lc-1 and tc-4 from innovate.

 

alright, minor update. I wired up the ground for the analog out, which is something i didn't do originally, and had basically the exact same experience. Really really lean readings in mid throttle. I am starting to think the o2 sensor i have is bad, because i bought the lm-1 second hand, and the sensor is of unknown age.

I dont know if i should try to figure out the voltage offset first, or just buy a new sensor and try once again.