- National Instruments

- National Instruments
NOx Sensor Kit User’s Manual
cRIO Module Platform
D000018 Rev A
D000019 Rev A
August 2010
Drivven, Inc. • 12001 Network Blvd, Bldg E, Suite 110 • San Antonio, Texas 78249 • USA
Phone : 210.248.9308
Web : www.drivven.com , E-mail : [email protected]
Drivven, Inc.
NOx Sensor Module Kit
Contents Introduction ...................................................................................................................................... 3 System Diagram .............................................................................................................................. 4 Hardware ......................................................................................................................................... 5 Powering the Hardware ................................................................................................................... 5 Continental Smart NOx Sensor Module Specifications.................................................................... 6 cRIO Platform Compatibility ............................................................................................................ 9 Software......................................................................................................................................... 10 Creating a LabVIEW Project.......................................................................................................... 11 Exploring the cRIO Example Project ............................................................................................. 13 cRIO Sub VI Documentation ......................................................................................................... 18 Wiring Harness Documentation ..................................................................................................... 22 © Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
2
Drivven, Inc.
NOx Sensor Module Kit
Introduction
The Drivven cRIO and USB NOx Sensor Module Kits provides an interface for one or two NOx
and O2 exhaust gas sensors.
Features:
¾
¾
¾
¾
¾
¾
¾
¾
¾
1-Ch. or 2 Ch. system
Two signals output:
o NOx concentration (ppm)
o O2 concentration (%)
Sensor controller supply voltage of 12V to 32V
Reverse battery protection on sensor controller module
Wide range of applications:
o Gasoline / Diesel
o Passenger car / Truck
Helps to achieve emissions requirements
Includes sensor controller module harness
Multiple platform support including USB and cRIO
cRIO module based platform provides
o LabVIEW FPGA and RT VIs included for quick integration with application
o Integration with existing PXI or cRIO chassis hardware
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
3
Drivven, Inc.
NOx Sensor Module Kit
System Diagram
Figure 1 cRIO System Drawing
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
4
Drivven, Inc.
NOx Sensor Module Kit
Hardware
The cRIO based kit provides the following hardware:
1** Continental Smart NOx Sensor with integrated sensor controller module
1** Sensor bung
1 Connector kit for NOx sensor controller module
1 National Instruments NI-9853 CompactRIO CAN module
**quantity of 2 if part # D000019
The Drivven NOx software toolkit is only compatible with the Continental Uninox Smart NOx
Sensor having a part number of 5WK96622A. There are many additional Continental NOx sensor
modules, found in various OEM engine applications, which communicate over CAN. They likely
have a different part number, which means they will not be compatible with this kit because each
of the OEM sensors are programmed with proprietary communication protocols. Drivven cannot
support those sensors. The NOx sensor modules provided by Drivven are engineering samples
procured directly from Continental. If you already have the correct sensor module, then you may
purchase the NOx sensor module kit without the included sensor module. Please contact Drivven
for a quote.
The wiring harness that is included with the USB NOx kit is a five foot cable that connects to the
NOx Sensor Control Module and then splits into two cables for the NI-9853 module and an
external power supply. The first cable connects to the NI-9853 with a female DB-9 connector. A
terminating resistor of approximately 120 ohms is hidden inside this cable near the NOx Sensor
Control Module, between the CAN High and CAN Low wires. The second cable provides three
un-terminated leads for connecting to a power supply (2 leads) and for address selection of the
NOx sensor module (1 lead). If the cable is to be extended, CAN network wiring guidelines must
be followed. Please refer to the operating instructions provided with the NI-9853 CAN module for
more details.
Powering the Hardware
The NOx Sensor Controller Module requires power from a range of 12V to 16V with a continuous
current of 0.6A and a peak current of 12A. The maximum power requirement is 20W.
For power requirements of the NI 9853, please refer to the National Instruments operating
instructions provided with the hardware.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
5
Drivven, Inc.
NOx Sensor Module Kit
Continental Smart NOx Sensor Module Specifications
Table 2. NOx Sensor Performance Specifications
Output
Measurement
Accuracy
Type
Range
NOx
O2
0 – 3000 ppm
-12 – 21 [%]
@ 0 ppm:
±10 ppm
@ 100 – 1500 ppm: ±10%
@ 1500 – 3000 ppm: undefined
@ λ=0.90: ±1.4% (fresh)
@ 0% (λ=1.00): ±0.13% (fresh)
@ 0% (λ=1.00): ±0.25% (aged)
@13% (λ=2.65): ±0.32% (fresh)
Response Time
(33-66%)
Data Update
Rate
1300 ms (fresh)
1650 ms (aged)
1000 ms (fresh)
1300 ms (aged)
50 ms interval
@ 250 kBaud
NOx Sensor Light-off times (Conditions: Air T = 25 ±5°C, BattV = 28V, Heater turned ON)
< 100 sec
NOx
< 80 sec
O2
NOx Sensor Preheating Function
If power supply is on, the sensor is in preheating mode until the Heater Boolean is set to TRUE.
If the Heater Boolean is set to FALSE, the sensor returns to preheating mode. The preheating
mode protects the sensor from mechanical cracks caused by water splash.
NOx Sensor Operating Temperature Ranges
Minimum sensor module controller temperature
-40°C
Maximum sensor module controller temperature
105°C
Sensor module controller temperature range of 85°C to 100°C allowed for up to 10 minutes
Minimum storage temperature
Maximum storage temperature
Maximum storage time
-40°C
120°C
2 years
Maximum exhaust gas temperature
Exhaust gas temperature of 950°C allowed up to 100 hours
800°C
Maximum sensor hexagon screw temperature
620°C
Sensor hexagon screw temperature of 650°C allowed for up to 100 hours
Maximum sensor grommet temperature
200°C
Sensor grommet temperature of 230°C allowed for up to 100 hours
Minimum preheating sensor temperature
Maximum preheating sensor temperature
80°C
120°C
Lifespan approved by life cycle pattern
2000 hours or 120K miles
NOx Sensor Electrical Characteristics
NOx Sensor Supply Voltage
Minimum supply voltage
Maximum supply voltage
If supply voltage > 32 V, sensor is not operated
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
12 V
16V
6
Drivven, Inc.
NOx Sensor Module Kit
NOx Sensor Supply Current
Average supply current
Peak supply current at switch on
Inrush current
0.6 A
12 A
20 A
Supply Power
Maximum supply power
20 W
NOx Sensor Misc.
Thread Torque
50 Nm
Lubrication
Anti-Seize Compound
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
7
Drivven, Inc.
NOx Sensor Module Kit
Figure 2 Installation Position
Figure 3 Tilt Angle in Gas Flow Direction
NOx Sensor Controller Module Connector
Type of connector
Number of pins
Connector pin assignment
Hirschmann MLK 872-860-501
5
Pin 1: Battery
Pin 2: Ground
Pin 3: CAN Low
Pin 4: CAN High
Pin 5: Address Switch
Pulling pin 5 to ground changes the CAN arbitrary ID of the sensor control module so that two
NOx sensor control modules can be added to the same network.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
8
Drivven, Inc.
NOx Sensor Module Kit
cRIO Platform Compatibility
CompactRIO modules from National Instruments are compatible within two different platforms
from National Instruments. One platform is CompactRIO, consisting of a CompactRIO controller
and CompactRIO chassis as shown in Figure 1a below.
Figure 4 CompactRIO platform compatible with Drivven/NI CompactRIO modules
The other platform is National Instruments PXI which consists of any National Instruments PXI
chassis along with a PXI RT controller and PXI-78xxR R-Series FPGA card. An R-Series
expansion chassis must be connected to the PXI FPGA card via a SHC68-68-RDIO cable. The
CompactRIO modules insert into the R-Series expansion chassis. This platform is shown in
Figure 1b below.
Figure 5 PXI platform compatible with Drivven/NI CompactRIO modules
National Instruments NI 9853 CompactRIO modules are not compatible with the National
Instruments CompactDAQ chassis.
Drivven CompactRIO modules REQUIRE one of the hardware support systems described above
in order to function. The modules may not be used by themselves and/or interfaced to third party
devices at the backplane HD15 connector. These efforts will not be supported by Drivven or
National Instruments.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
9
Drivven, Inc.
NOx Sensor Module Kit
Software
The NOx Sensor cRIO Module Kit is provided with an installer package which may be
downloaded from Drivven’s Sharepoint website after obtaining login access from Drivven. User’s
may go to http://portal.drivven.com/SoftwareDownload and enter the provided username and
password to gain access to the specific product installer packages which have been purchased.
The installer packages are executables which should be run on the intended development
computer, having LabVIEW development tools installed. After installing the package, a “Start>Programs->Drivven->ProductRelease” menu item will be added to the desktop. The specific
product will have an example LabVIEW project appear under the “Examples” menu and the user
manual will appear under the “Manuals” menu. User’s may copy and open the example project to
experiment with the module or use as a starting point for a new application. All software files,
example projects and documentation are installed to:
C:\Program Files\National Instruments\LabVIEW X.X\vi.lib\addons\DrivvenProductRelease\.
When working with block diagrams, user’s will notice a “Drivven” function palette added to the
standard LabVIEW palette, specific for the RT or FPGA target. VIs for a specific Drivven product
will be categorized according to product name. Also, some Drivven products will install RT and
FPGA VIs under a “General” function palette which is intended to be used across multiple
products.
Requirements
The Drivven cRIO based VIs require:
¾ LabVIEW 8.6 Full Development or later
¾ LabVIEW RT Module 8.6 or later
¾ LabVIEW FPGA Module 8.6 or later
¾ NI-RIO 2.4 or later
The NOx Sensor cRIO Module Kit is provided with both a LabVIEW FPGA VI for interfacing to the
NI cRIO 9853 CAN module and a LabVIEW RT VI for interfacing with the FPGA VI and managing
and reporting sensor results.
Figure 6 nox_revx.vi and nox_rt_revx.vi icons with leads
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
10
Drivven, Inc.
NOx Sensor Module Kit
Creating a LabVIEW Project
Drivven recommends working from the provided example application as a starting point for
learning the use of the Drivven software blocks. However, the following section describes starting
a LabVIEW project from scratch and adding a CompactRIO module. For the USB based platform
the LabVIEW example project is not required for operation but it does provide a useful means of
viewing the applicable VIs. The following directions are not applicable for the USB platform
because there is no need to use a real time target when only using the NI-8473.
1.) Install the Drivven software by running the installer executable and accepting the
software license agreement.
2.) Restart LabVIEW, if previously running, and create a new LabVIEW project.
3.) Give the new project a name by clicking the “Save Project” button on the project toolbar.
4.) Right click on the highest item in the project hierarchy (“Project:…”) and navigate to
“New->Targets and Devices…”
5.) Within the “Add Targets and Devices…” dialog, select the appropriate radio button,
depending on whether you already have an existing powered and configured RT target
on the network or if you are adding a new RT target which is not present yet on the
network.
a. Existing Target or Device
i. Expand the appropriate category in the “Targets and Devices” list to see
the discovered targets in that category.
ii. Double-click the desired target to add it to your project.
b. New Target or Device
i. Expand the appropriate category in the “Targets and Devices” list to see
all possible targets within that category.
ii. Double-click the desired target to add it to your project.
6.) If the new RT target is not currently on the network, right-click on the RT target within the
project and open the properties dialog to set the IP address or DNS name if necessary.
7.) Right-click on the RT target within the project and navigate to “New->Targets and
Devices…”
8.) Within the “Add Targets and Devices…” dialog, select the appropriate radio button,
depending on whether you already have an existing FPGA target connected to an
existing RT target or if you are adding a new FPGA target which is not present yet.
a. Existing Target or Device
i. Expand the appropriate category in the “Targets and Devices” list to see
the discovered FPGA targets in that category.
ii. Double-click the desired target to add it to your project.
b. New Target or Device
i. Expand the appropriate category in the “Targets and Devices” list to see
all possible targets within that category
ii. Double-click the desired target to add it to your project.
c. If working with a CompactRIO RT target, then an appropriate CompactRIO
chassis must be added before adding an FPGA target. An FPGA target must be
added to the cRIO chassis in order to force LabVIEW FPGA Interface mode.
Scan Interface mode is not appropriate for working with Drivven products. The
mode can also be set by right-clicking on the cRIO chassis within your project
and opening the properties dialog.
9.) After adding the FPGA target, right-click on the FPGA target within the project and open
the properties dialog to set the resource name if not set correctly already. The resource
name can be found from MAX when connected to the actual remote system.
10.) If the FPGA target is a PXI or PCI card, then an R Series expansion chassis must be
added under the FPGA target. This is done by right-clicking on the FPGA target and
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
11
Drivven, Inc.
NOx Sensor Module Kit
navigating to “New->R Series Expansion Chassis”. Within the following dialog, select the
appropriate FPGA connector to which the chassis will be connected. A unique name for
the chassis may also be specified.
11.) Right click on the R-Series expansion chassis or cRIO FPGA target and navigate to
“New->C Series Modules…”
12.) Select the “New Target or Device” radio button and double-click on the “C Series Module”
in the “Targets and Devices” list. In the following dialog, select the desired Drivven
module at the bottom of the “Module Type” list. The Drivven modules will be appended
there if any Drivven module software has been installed. Select the appropriate module
location. Finally, specify an appropriate name for the module, which will later appear in
the FPGA I/O nodes in the FPGA block diagram. Having meaningful module names is
important for preventing coding mistakes.
13.) After adding a module to the project, a folder will automatically be added to the project
having the same module name given in the module configuration dialog. The folder will
contain the FPGA I/O pins for the module slot. These I/O pins can be selected in the
block diagram when connecting the module VI PinInput and PinOutput clusters to FPGA
I/O nodes. The example application, discussed below, should be consulted for further
details about connecting the PinInput and PinOutput clusters to FPGA I/O nodes. Within
the example projects, notice the FPGA I/O node elements having module name prefixes.
14.) Some Drivven modules can be automatically recognized by LabVIEW when adding cRIO
modules to the project. However, Drivven does not recommend using this feature
because the module names, which are automatically assigned, are not meaningful
(Mod1, Mod2, etc) and can lead to coding mistakes when wiring the Drivven FPGA VIs to
the I/O nodes. Adding the modules to the project manually, as described above, is still
the recommended method.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
12
Drivven, Inc.
NOx Sensor Module Kit
Exploring the cRIO Example Project
Figure 7 Example expanded project explorer of NOx_Example.lvproj
Use the NOx_Example_FPGA.vi as an example to implement a NOx sensor interface into your
own application. Just copy and paste one of the while loops, as shown below in figure 4, into
your application.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
13
Drivven, Inc.
NOx Sensor Module Kit
Figure 8 Example block diagram implementation of NOx VI
Please follow the guidelines below for adding the nox_reva.vi to your FPGA application:
1.)
2.)
3.)
4.)
5.)
6.)
7.)
8.)
The NOx sensor interface vi, nox_reva.vi, should be placed in its own while loop.
Do not place more than one NOx sensor interface vi within the same while loop.
Do not place the NOx sensor interface within a single cycle loop.
The cRIO 9853 CAN Module properties may be configured by right-clicking on the
module within the project explorer. The properties should be set to the following:
a. Baud Rate = 250 Kbps
b. Auto Start = Checked
c. Listen Only = Unchecked
d. Input Timeout > 50 msec (100 msec recommended)
e. Output Timeout < 10 msec (0 recommended)
f. Input Filter = Receive All
Other CAN nodes may be connected to the same CAN bus, as long as they conform to
the above properties.
Use the CANX Restart button to re-establish connection with the NOx sensor module if
the CAN bus is disconnected and then connected again.
NOx bits must be converted to NOx ppm at the RT level according to:
a. NOx ppm = (bits * 0.05) – 200.
b. Data type of bits is I16.
c. The above conversion is performed by nox_rt_reva.vi.
O2 bits must be converted to O2% at the RT level according to:
a. O2% = (bits * 0.000514) – 12.
b. Data type of bits is U16.
c. The above conversion is performed by nox_rt_reva.vi.
Right click on the NI 9853 module within your project explorer and select Properties. A dialog
will open and allow you to make the CAN module settings listed in item 4 above. The property
dialogs are shown below in figure 5a and 5b.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
14
Drivven, Inc.
NOx Sensor Module Kit
Figure 9 Top level property dialog for NI 9853 module
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
15
Drivven, Inc.
NOx Sensor Module Kit
Figure 10 Advanced property dialog for NI 9853 module
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
16
Drivven, Inc.
NOx Sensor Module Kit
If the CAN connection is expected to be disconnected at times while the NI 9853 CAN module is
active, then it may be necessary to implement a method to reset the CAN channel being used.
Do this by placing a FPGA I/O Method node which resets the CAN channel. The method node
should be placed within a case statement and selected by a Boolean control. This Boolean
control can be operated from the RT level programmatically.
Follow the NOx_Example_RT.vi to properly interface to your FPGA application. Use the
nox_rt_reva.vi to convert the data cluster from the nox_reva.vi to engineering units. It is not
necessary to access the TxID or RxID. They should never change. In fact, they can be replaced
by constants at the FPGA level. They are made available in case the default IDs change in the
NOx sensor module.
Figure 11 Example LabVIEW RT interface to LabVIEW FPGA NOx_Example_FPGA.vi
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
17
Drivven, Inc.
NOx Sensor Module Kit
cRIO Sub VI Documentation
nox_reva.vi
The NOx sensor FPGA VI should be placed in its own while loop (as shown in the example).
Do not place more than one NOx sensor FPGA VI within the same while loop.
Do not place the NOx sensor FPGA VI within a single cycle loop.
The cRIO 9853 CAN Module properties should be set to the following:
Baud Rate = 250 Kbps
Auto Start = Checked
Listen Only = Unchecked
Input Timeout > 50 msec (100 msec recommended)
Output Timeout < 10 msec (0 recommended)
Input Filter = Receive All
Other CAN nodes may be connected to the same CAN bus, as long as they conform to the above
properties.
Use the FPGA CANX Restart method to re-establish connection with the NOx sensor module if
the CAN bus is disconnected and then connected again.
The following conversions are implemented at the RT level by the nox_rt_revx.vi.
NOx ppm = (bits * 0.05) - 200.
O2% = (bits * 0.000514) - 12.
TxID This is the Transmit ID for the NI CAN module.
This is the Receive ID for the NOx module.
By default the NOx module receive ID is 18FEDF00h, corresponding to PGN 65247.
This PGN contains the heater control command.
RxID 1 ID of the CAN message that should be received from the Sensor Control Module
for channel 1.
By default the NOx module transmit ID is 18F00F52h, corresponding to PGN 61455.
This PGN contains the NOx, O2 and status information from the NOx module.
RxID 2 ID of the CAN message that should be received from the Sensor Control Module
for channel 2.
By default the NOx module transmit ID is 18F00E51h, corresponding to PGN 61455.
This PGN contains the NOx, O2 and status information from the NOx module.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
18
Drivven, Inc.
NOx Sensor Module Kit
Sensor 1Enable When TRUE, the primary(channel 1) NOx sensor module is requested
to turn on the sensor heater and begin controlling the sensor to high temperature. When
FALSE, the NOx sensor module is requested to place the heater circuit in preheating
mode and begin controlling to 80 C to 120 C.
Sensor 2Enable When TRUE, the secondary(channel 2) NOx sensor module is
requested to turn on the sensor heater and begin controlling the sensor to high
temperature. When FALSE, the NOx sensor module is requested to place the heater
circuit in preheating mode and begin controlling to 80 C to 120 C.
CAN Error In Receives the error cluster wire from the error output terminal of the FPGA
CAN I/O node (configured as "Read"). Right click on the FPGA CAN I/O Node and click
on Show Error Terminals.
CAN Data In Receives the cluster wire from the FPGA CAN I/O node. The FPGA CAN
I/O node should be configured as "Read".
NOxSensorData1 This cluster contains NOx, O2 and status data for sensor 1. This
terminal should be terminated with a cluster within the FPGA block diagram and made
available to the LabVIEW RT block diagram to be connected to the "NOxSensorData
From FPGA" input terminal of the nox_rt_revx.vi.
NOxSensorData2 This cluster contains NOx, O2 and status data for sensor 2. This
terminal should be terminated with a cluster within the FPGA block diagram and made
available to the LabVIEW RT block diagram to be connected to the "NOxSensorData
From FPGA" input terminal of the nox_rt_revx.vi.
Update CAN Out Must be wired to the selector terminal of a case statement structure.
The TRUE case of the case statement must contain the FPGA CAN I/O node configured
for "Write".
CAN Data Out Output cluster to be wired to the FPGA CAN I/O node. The FPGA CAN
I/O node should be configured as "Write".
RxIDActual This is the actual received ID for the NI CAN module. This is useful to
determine what message IDs are actually being received.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
19
Drivven, Inc.
NOx Sensor Module Kit
nox_rt_reva.vi
This VI is to be implemented at the RT level. It receives data from the FPGA VI
"NOxSensorData" output cluster and properly scales and offsets the results.
NOxSensorDataFromFPGA This terminal should be wired from the "NOxSensorData"
cluster output from the FPGA VI.
NOxSensorData Final processed result from the NOx Sensor.
NOx (ppm) Parts per million of oxides of nitrogen measured in the exhaust gas.
O2 (%) Percent oxygen content of the exhaust gas.
Sensor Supply Status Provides status information about the NOx sensor power
supply.
The following status messages are provided:
NOT IN RANGE
SUPPLY IN RANGE
ERROR
NOT AVAILABLE
Sensor Temperature Status Provides status information about the NOx sensor
heater temperature.
The following status messages are provided:
NOT AT TEMPERATURE
AT TEMPERATURE
ERROR
NOT AVAILABLE
NOx Signal Status Provides status information about the NOx sensor NOx ppm
measurement.
The following status messages are provided:
NOT VALID
VALID
ERROR
NOT AVAILABLE
O2 Signal Status Provides status information about the NOx sensor O2
measurement.
The following status messages are provided:
NOT VALID
VALID
ERROR
NOT AVAILABLE
Heater Mode Status Provides status information about the NOx sensor heater
control mode.
The following status messages are provided:
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
20
Drivven, Inc.
NOx Sensor Module Kit
AUTO MODE
HEATUP SLOPE 3 OR 4
HEATUP SLOPE 1 OR 2
HEATER OFF / PREHEAT
Heater Circuit Status Provides status information about the NOx sensor heater
circuit.
The following status messages are provided:
OPEN WIRE
SHORT CIRCUIT
NO ERROR.
NOx Circuit Status Provides status information about the NOx sensor NOx
measurement circuit.
The following status messages are provided:
OPEN WIRE
SHORT CIRCUIT
NO ERROR.
O2 Circuit Status Provides status information about the NOx sensor O2
measurement circuit.
The following status messages are provided:
OPEN WIRE
SHORT CIRCUIT
NO ERROR.
NOx Sensor Module Present Indicates whether the NOx sensor is powered,
properly connected, and detected on the CAN bus.
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
21
Drivven, Inc.
NOx Sensor Module Kit
Wiring Harness Documentation
1-Sensor Harness
2-Sensor Harness
© Drivven, Inc. 2010 • NOx Sensor cRIO Module Kit User’s Manual
D000018, D000019 • Rev A
22
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement