Any VG owners running Nistune?
Once you have the wideband installed and set up to report the way you want it to, you won't need to be wired in to the sensor o2 sensor at all.
Nistune will read what the wideband reports. Nistune will be the only thing you are wired in to. The only thing Nistune doesn't do is 'change' the way the o2 operates, but it still reads the data.
Nistune will read what the wideband reports. Nistune will be the only thing you are wired in to. The only thing Nistune doesn't do is 'change' the way the o2 operates, but it still reads the data.
ok so i have to do a few runs w/ the WBO2...then take the output file...merge that into nistune software and plug nistune to the car?
ok let me throw some real world situation here.
nistune is in the car and it's connected to the laptop via USB cable and i use nistune to interface with the ECU.
WBO2..say the zeitronics and it's connected to a laptop via serial cable and i'm running their software on the laptop.
so i have two cable input to the laptop and two software running.
so the question is....does Nistune interface with the Zeitronics where i can run Nistune's software and it'll pick up the signal from the Zeitronics WBO2 or do i have to run the two programs separate? keep in mind this is during tuning stage so i would like to have both running (nistune and WBO2). how does nistune work with the WBO2?
ok let me throw some real world situation here.
nistune is in the car and it's connected to the laptop via USB cable and i use nistune to interface with the ECU.
WBO2..say the zeitronics and it's connected to a laptop via serial cable and i'm running their software on the laptop.
so i have two cable input to the laptop and two software running.
so the question is....does Nistune interface with the Zeitronics where i can run Nistune's software and it'll pick up the signal from the Zeitronics WBO2 or do i have to run the two programs separate? keep in mind this is during tuning stage so i would like to have both running (nistune and WBO2). how does nistune work with the WBO2?
- Install WBO2.
- Run software that comes with WB02.
- Unplug from WB02/turn off 02 software
- Plug in NIStune.
- NIStune is reading your ECU now
... and ECU is reading information your WB02 transmits (same as it does with your regular 02)
Once you have the WB installed and set up the way you want it, you don't need to be running any software simultaneously alongside NIStune. That's why NIStune has listed compatible wideband sensors on their site - NIStune is able to read information from them.
Any changes to the car you make are strictly via hand installed mods, or ECU tweaks from within NIStune. You tell NIStune what you have done, such as install larger injectors, or command the ECU to perform a specific way, such as changing the fuel map.
The WB is doing it's thing strictly by reading what it sees based on the changes you have made to the vehicle and then reports it back to NIStune. You don't need the WB software to see what it's seeing.
Last edited by hadman; Oct 29, 2008 at 09:30 AM.
I had the same WBo2 questions you did when I was first inquiring about NIStune. Here's what I was told.
ME: Does the new wideband sensor replace the old sensor, or is it preferred to weld in the new sensor while retaining the old sensor? I'm not sure if removing my stock sensor will trip a code or not.
Also, I understand the NIStune software reads info from the wideband sensor, but doesn't actually alter the a/f - correct? This is to be performed with the software that comes with the LC-1?
NIStune: We normally only use the wideband for doing the tuning and keep the stock O2 sensor.
Removing stock sensor should not cause any codes. You can monitor O2 voltage in the software to see if it works.
NIStune will read the sensor information and display it only. Changing the AFRs is up to you. Good place to get started is with the tuning guide that Pete has put together. See the main forum area for more info.
ME: Does the new wideband sensor replace the old sensor, or is it preferred to weld in the new sensor while retaining the old sensor? I'm not sure if removing my stock sensor will trip a code or not.
Also, I understand the NIStune software reads info from the wideband sensor, but doesn't actually alter the a/f - correct? This is to be performed with the software that comes with the LC-1?
NIStune: We normally only use the wideband for doing the tuning and keep the stock O2 sensor.
Removing stock sensor should not cause any codes. You can monitor O2 voltage in the software to see if it works.
NIStune will read the sensor information and display it only. Changing the AFRs is up to you. Good place to get started is with the tuning guide that Pete has put together. See the main forum area for more info.
Let's see if I can counter real-world style to help draw the picture...
- Install WBO2.
- Run software that comes with WB02.
- Unplug from WB02/turn off 02 software
- Plug in NIStune.
- NIStune is reading your ECU now
... and ECU is reading information your WB02 transmits (same as it does with your regular 02)
Once you have the WB installed and set up the way you want it, you don't need to be running any software simultaneously alongside NIStune. That's why NIStune has listed compatible wideband sensors on their site - NIStune is able to read information from them.
Any changes to the car you make are strictly via hand installed mods, or ECU tweaks from within NIStune. You tell NIStune what you have done, such as install larger injectors, or command the ECU to perform a specific way, such as changing the fuel map.
The WB is doing it's thing strictly by reading what it sees based on the changes you have made to the vehicle and then reports it back to NIStune. You don't need the WB software to see what it's seeing.
- Install WBO2.
- Run software that comes with WB02.
- Unplug from WB02/turn off 02 software
- Plug in NIStune.
- NIStune is reading your ECU now
... and ECU is reading information your WB02 transmits (same as it does with your regular 02)
Once you have the WB installed and set up the way you want it, you don't need to be running any software simultaneously alongside NIStune. That's why NIStune has listed compatible wideband sensors on their site - NIStune is able to read information from them.
Any changes to the car you make are strictly via hand installed mods, or ECU tweaks from within NIStune. You tell NIStune what you have done, such as install larger injectors, or command the ECU to perform a specific way, such as changing the fuel map.
The WB is doing it's thing strictly by reading what it sees based on the changes you have made to the vehicle and then reports it back to NIStune. You don't need the WB software to see what it's seeing.
I think the problem you have in your head, and correct me if I'm wrong, is that you think you need to keep tweaking something on the WBO2 as you continue to tune. You don't. Once it's initially set up, it's only job is to report how the various mods you have made have effected the air/fuel ratio.
The WB doesn't change the a/f, it only reads it, and/or data logs it.
NIStune doesn't talk to the WB, it only listens.
Junior Member
Joined: Oct 2001
Posts: 23
NIStune installs in the ECU as a daughter card. There is a bi-directional USB connection to the laptop.
The WBo2 is a separate box, that in my case also sees rpm, tps, boost, egt, and a user defined input. These inputs come directly from the ECU wiring harness. The Zeitronix has an output which can be plugged into the ECU to emulate the stock o2 sensor. I don't do this. I've installed a separate bung for the WBo2 sensor. There is a serial cable from the Zeitronix that I convert to USB to plug into my laptop. Data is only coming from the WBo2, not going back to it. The Zeitronix comes with software; I've used it once. Lastly, I have their display up on the dash.
With both USB signals coming in, NIStune can display all the data, and log it. This is key, as all your engine data is collected in one file, and displayed on one screen. The data from the WBo2 is used to understand what the ECU is providing the engine, and monitor/verify the changes to mapping you'll make. The log file can be played back later with all inputs displayed as they were recorded.
There is an "auto-tune" feature in beta that may be able to adjust your fuel maps based on feedback from the WBo2. I've not tried this, though it seems to be working for some. It is not a magic bullet, or maybe it is, one that could put a hole in your block... Not to dis Matt, cuz he's doing an awesome job, but I'm a little hesitant about letting the software do the tuning for me.
Hopefully this clears things up.
The WBo2 is a separate box, that in my case also sees rpm, tps, boost, egt, and a user defined input. These inputs come directly from the ECU wiring harness. The Zeitronix has an output which can be plugged into the ECU to emulate the stock o2 sensor. I don't do this. I've installed a separate bung for the WBo2 sensor. There is a serial cable from the Zeitronix that I convert to USB to plug into my laptop. Data is only coming from the WBo2, not going back to it. The Zeitronix comes with software; I've used it once. Lastly, I have their display up on the dash.
With both USB signals coming in, NIStune can display all the data, and log it. This is key, as all your engine data is collected in one file, and displayed on one screen. The data from the WBo2 is used to understand what the ECU is providing the engine, and monitor/verify the changes to mapping you'll make. The log file can be played back later with all inputs displayed as they were recorded.
There is an "auto-tune" feature in beta that may be able to adjust your fuel maps based on feedback from the WBo2. I've not tried this, though it seems to be working for some. It is not a magic bullet, or maybe it is, one that could put a hole in your block... Not to dis Matt, cuz he's doing an awesome job, but I'm a little hesitant about letting the software do the tuning for me.
Hopefully this clears things up.
Yes.
No you don't need to leave it connected. You set up the WB and disconnect.
I think the problem you have in your head, and correct me if I'm wrong, is that you think you need to keep tweaking something on the WBO2 as you continue to tune. You don't. Once it's initially set up, it's only job is to report how the various mods you have made have effected the air/fuel ratio.
The WB doesn't change the a/f, it only reads it, and/or data logs it.
NIStune doesn't talk to the WB, it only listens.
No you don't need to leave it connected. You set up the WB and disconnect.
I think the problem you have in your head, and correct me if I'm wrong, is that you think you need to keep tweaking something on the WBO2 as you continue to tune. You don't. Once it's initially set up, it's only job is to report how the various mods you have made have effected the air/fuel ratio.
The WB doesn't change the a/f, it only reads it, and/or data logs it.
NIStune doesn't talk to the WB, it only listens.
if i disconnect the WBO2 how does Nistune pick up the A/F readings while i'm driving and datalog?
thanks for your help...i just want to make sure i'm getting this 100% right before i throw down a few hundred for this stuff.
NIStune installs in the ECU as a daughter card. There is a bi-directional USB connection to the laptop.
The WBo2 is a separate box, that in my case also sees rpm, tps, boost, egt, and a user defined input. These inputs come directly from the ECU wiring harness. The Zeitronix has an output which can be plugged into the ECU to emulate the stock o2 sensor. I don't do this. I've installed a separate bung for the WBo2 sensor. There is a serial cable from the Zeitronix that I convert to USB to plug into my laptop. Data is only coming from the WBo2, not going back to it. The Zeitronix comes with software; I've used it once. Lastly, I have their display up on the dash.
The WBo2 is a separate box, that in my case also sees rpm, tps, boost, egt, and a user defined input. These inputs come directly from the ECU wiring harness. The Zeitronix has an output which can be plugged into the ECU to emulate the stock o2 sensor. I don't do this. I've installed a separate bung for the WBo2 sensor. There is a serial cable from the Zeitronix that I convert to USB to plug into my laptop. Data is only coming from the WBo2, not going back to it. The Zeitronix comes with software; I've used it once. Lastly, I have their display up on the dash.
so technically there are two USB cables going to the laptop. i'm going to run a separate bung for the WBO2 so i'm leaving the stock O2 in it's place.
so it's....(excuse crude ascii art)
WBO2----usb(input)--->> laptop<<---usb(input)----Nistune
Nistune software will be able to pull in the signals from the WBO2 and merge it together w/ it's software/interface?
With both USB signals coming in, NIStune can display all the data, and log it. This is key, as all your engine data is collected in one file, and displayed on one screen. The data from the WBo2 is used to understand what the ECU is providing the engine, and monitor/verify the changes to mapping you'll make. The log file can be played back later with all inputs displayed as they were recorded.
There is an "auto-tune" feature in beta that may be able to adjust your fuel maps based on feedback from the WBo2. I've not tried this, though it seems to be working for some. It is not a magic bullet, or maybe it is, one that could put a hole in your block... Not to dis Matt, cuz he's doing an awesome job, but I'm a little hesitant about letting the software do the tuning for me.
Hopefully this clears things up.
Hopefully this clears things up.
thanks for the information.
Anyway, glad you got the answer you need. And yes, you'll weld in a second bung for the wideband unit, leaving the oem sensor intact.
Yes, and yes. Sorry if I confused you on that Dan. I thought your concern was focused on needing to continually tweak the performance of the actual wbo2 unit itself and needing to run the respective programs in parallel for that specific reason.
Anyway, glad you got the answer you need. And yes, you'll weld in a second bung for the wideband unit, leaving the oem sensor intact.
Anyway, glad you got the answer you need. And yes, you'll weld in a second bung for the wideband unit, leaving the oem sensor intact.
got the bung welded in so that's no prob.
thanks for helping me w/ my questions...really appreciate it.
Thread
Thread Starter
Forum
Replies
Last Post
hez8813
5th Generation Maxima (2000-2003)
11
Mar 12, 2020 12:06 AM
ballerchris510
3rd Generation Maxima (1989-1994)
9
Sep 10, 2015 09:35 PM
