did this get resolved?

is you DIYPNP 3 (whatever the hell that may be) setup to reiceve the o2 input directly from the ECU harness and not the external wiring pigtail?

Any follow-up on this problem? I've got a somewhat similar issue where tunerstudio WAS displaying my afr just fine (matched up with the wbo2 gauge), now it's at a static 0.01v.

For reference the 0v-5v yellow wire (innovative mtx-l) is connected to the stock o2 wire in the engine bay. 12v is to the switched radio wire, ground is the ECU ground, brown simulated narrowband wire is taped off and not connected to anything.

What could cause the o2 voltage to be read by TS once, and then not read another time?

Any help would be appreciated...

Innovate Motor Sports On-Line Store

Can this be used to connect the wideband to the ECU?

No the serial port on megasquirt is only to communicate with the PC. To get a digital input from a wideband you'll need to get either the tinyIOx board by JBPerf or reverants Wideband CAN board

You may want to connect a notebook directly to the Innovative unit (if it has one).
I had either an LC1 or LC2 decide to display 0 or 5 volt values to the gauge and Tuner Studio, even though everything was wired correctly.

Hooking a notebook up to the Innovative unit and going through all the menus/etc. resolved the issue, even though nothing was changed. I was going to attempt a firmware update/reload but discovered there weren't any available from Innovative.

And, free air calibration worked just fine, just couldn't get the unit to display anything other than 10.0 or 24.0 once things were started up.

Im still having the same issue. According to the diyautotune website (https://www.diyautotune.com/support/...r/tunerstudio/) I need to have the microsquirt_full deactivated, and the microsquirt_module activated, in project properties, however I dont have either of these drop down menus in tunerstudio.

you have to reflash the firmware.

Im trying to boot up the firmware 1.4.0 but Ikeep getting the message "ECU hardware type was detected, but did not find matching firmware files
in current directory. You will have to choose it." which file do i use?