NEXAS NL101 OBD2 Scanner Check Engine Light Car Code Reader Diagnostic Scan Tool Fault Code Scanner with Battery Test for OBDII Car After 1996 [Upgrade Version] including Black Protective Case

NEXAS NL101 OBD2 Scanner Check Engine Light Car Code Reader Automotive Diagnostic Tool Fault Code Scanner, Car Check Engine

The NEXAS NL101 is specially developed for car, min van and light vehicles, which supports all 10 modes of OBDII test (EVAP, O2 Sensor, I/M Readiness, MIL Status, VIN Info, and On-board monitors testing etc.) for a complete diagnosis and enables users to read DTCs, clear DTCs and view the live engine data stream with a live color graphing. It covers a wide range of vehicles since it offers multiple data bus protocols, such as CAN, J1850 PWM, J1850 VPW, ISO9141 and KWP2000.

NL101 obd2 scanner works on all cars, mini vans and light duty vehicles (OBDII & CAN) from 1996 and latest:

1. American cars released from 1996 years
2. European cars released from 2000 years
3. Asian cars released after 2008 years, Especially Japanese cars released after 2008 years !!!!!!

As an unique feature while other OBD scanner dose not have, NL101 could quickly check the vehicle’s battery health, read out the current battery value and give out 6 levels of battery warnings for your knowledge.

Notice: NL101 may automatically reset while being disturbed by strong static electricity. THIS IS A NORMAL REACTION.

Top Reasons to Choose NL101:

1. OBD/EOBD 2 modules in 1.
2. Live data show in Graph, the data are straightforward to know.
3. Battery check, it is seldom to have in the same product.
4. Multi-Languages, English, Spanish, French, Deutsch, Italian, Russian, Portuguese, Finnish and etc.
5. Including A Black Protection Case for You, you don't need to pay for it, but most OBDii Scanners on the market need to, that is the other product doesn't have.

OBD II Modes of Operation:

Here is a basic introduction to the OBD II communication protocol. Mode byte: The first byte in the stream is the mode number. There are 10 modes for diagnostic requests. The first byte in the response data bytes is this same number plus 64. For example, a mode 1 request would have the first data byte = 1, and the response would have the first data byte = 65. Here is a brief description of the modes:

• Mode 01 – Identifies the Powertrain information and shows current data available to the scan tool. This data includes: DTC set, status of on-board tests, and vehicle data such as engine RPM, temperatures, ignition advance, speed, air flow rates, and closed loop status for fuel system.
• Mode 02 – Displays Freeze Frame data. Same data as in mode 1,but it was captured and stored when a malfunction occurred and a DTC was set. Some of the PIDs for mode one are not implemented in this mode.
• Mode 03 – Displays the type of powertrain or emission related DTCs stored by a 5 digit code identifying the faults. There may be more than one response message if there are more trouble codes than will fit in the data bytes of the response message, or if there are more than one ECU computer responding.
• Mode 04 – Used to clear DTCs and Freeze Frame data. This clears all diagnostic trouble codes that may be set including freeze frame data and readiness monitors.
• Mode 05 – Displays oxygen sensor test results. This mode displays the oxygen sensor monitor screen and the test results gathered about the oxygen sensor. There are ten numbers available for diagnostics: (01) Rich-to-Lean O2 sensor threshold voltage. (02) Lean-to-Rich O2 sensor threshold voltage. (03) Low sensor voltage threshold for switch time measurement. (04) High sensor voltage threshold for switch time measurement. (05) Rich-to-Lean switch time in ms. (06) Lean-to-Rich switch time in ms. (07) Minimum voltage for test. (08) Maximum voltage for test. (09) Time between voltage transitions in ms.
• Mode 06 – Non-continuously Monitored Systems test results. There are typically a minimum value, a maximum value, and a current value for each non-continuous monitor. This data is optional, and it is defined by a given vehicle maker if it’s used.
• Mode 07 – A request for DTCs (pending) from Continuously Monitored Systems after a single driving cycle has been performed to determine if repair has fixed a problem. This is used by service technicians to verify repair was performed properly and after clearing diagnostic trouble codes.
• Mode 08 – This special Control Mode requests control of the on-board system, test, or component bi-directionally (where applicable). This mode is manufacturer specific.
• Mode 09 – Reports vehicle information. This information includes vehicle VIN number and calibration information stored in the vehicle ECUs.
• Mode 0A – Requests Emission-Related Diagnostic Trouble Codes with Permanent Status. This mode is required for all emissions-related DTCs.The presence of permanent DTCs at an inspection without the MIL illuminated is an indication that a proper repair was not verified by the on-board monitoring system.

NEXAS NL101 OBD2 Automotive Scanner Engine EVAP Battery OBDII Scanner Professional EOBD OBD Car Diagnostic Tool

When more than one vehicle control module is detected by the scan tool, you will be prompted to select the module where the data may be retrieved. The most often to be selected are the Power train Control Module [PCM] and Transmission Control Module [TCM].

CAUTION: Don’t connect or disconnect any test equipment with ignition on or engine running.

1. Turn the ignition off.
2. Locate the vehicle’s 16-pin Data Link Connector (DLC).
3. Plug the scan tool cable connector into the vehicle’s DLC.
4. Turn the ignition on. Engine can be off or running.
5. Turn on the scan tool. Use the "UP/DOWN" scroll button to select OBDII/EOBD from the Main Screen.
6. Press the "OK" button to wait for the Menu to appear. A sequence of messages displaying the OBDII protocols will be observed on the display until the vehicle protocol is detected.
7. View a summary of system status (MIL status, DTC counts, Monitor status) on screen. Press [OK].

If the scan tool fails to communicate with the vehicle’s ECU (Engine Control Unit) more than three times, a “LINKING ERROR!” message shows up on the display.

• Verify that the ignition is ON;
• Check if the scan tool’s OBD II connector is securely connected to the vehicle’s DLC;
• Verify that the vehicle is OBD II compliant;
• Turn the ignition off and wait about 10 seconds. Turn the ignition back to on and repeat the procedure.

I/M Ready Test & I/M Readiness Hot Key:

The Ready Test can be used as a convenient readiness test tool by automotive technicians to determine if the tested vehicle is ready for an emission test. By visual and audible indication, you will learn a vehicle’s monitors readiness. Repairs to the emissions-control systems of a 1996 or newer vehicle cause the vehicle’s computer (ECU) memory to be cleared. The vehicle must go through a drive cycle to allow the ECU to perform a series of tests to ensure that the repair was successful, and before a state mandated emissions test can be conducted. But how will you know when it is ready? With this scan tool, you don’t have to drive around endlessly and continuously coming back to the repair shop for retest if all required tests by the ECU are completed. And you could also do a quick check of the vehicle to determine if it is ready to receive an emission test without the hassle of connecting your vehicle to the analyzer or having to use a complicated scan tool. In the following cases, this function is especially useful.

• You bought a used car and the check engine light had been cleared to mask potential problems.
• You disconnected the battery for tune-ups and other engine repairs, dead battery replacement, car radio installation and car alarm installation.
• You used a scan tool to clear the DTCs.
• Your car has been sent to repair.

I/M refers to Inspection and Maintenance that is legislated by the Government to meet federal clean-air standards. I/M Readiness indicates whether or not the various emissions-related systems on the vehicle are operating properly and are ready for Inspection and Maintenance testing.

The purpose of the I/M Readiness Monitor Status is to indicate which of the vehicle’s Monitors have run and completed their diagnosis and testing, and which ones have not yet run and completed testing and diagnosis of their designated sections of the vehicle’s emissions system.

The I/M Readiness Monitor Status function also can be used (after repair of a fault has been performed) to confirm that the repair has been performed correctly, and/or to check for Monitor Run Status.

Note: N/A means not available on this vehicle; INC means incomplete or not ready and OK means Completed or Monitor Ok.

OBDII SCANNER CODE READER CHECK ENGINE LIGHT SCAN TOOL:

Quickly and accurately to read the engine fault code, built-in DTC look up library to show the DTC definitions, make it easy to determine the cause of the Check Engine Light(MIL), and turn off Check Engine Light by erasing the trouble codes and Monitors reset.

Battery Monitor: NL101 could quickly check the vehicle’s battery health, read out the current battery value and give out 6 levels of warnings for your knowledge:

• A. <10.8V(before Starting): Too Low; Change your battery, otherwise, might not be able to start;
• B. 10.8V-11.8V(before starting): Slightly low; Difficult to start, please turn off other electronics and start vehicle to charge;
• C. 11.8V-12.8V(before starting): Normal;
• D. 12.8V-13.2V(after starting): Too Low; Might not be able to charge the battery, please check other electrical load;
• E. 13.2V-14.8V(after starting): Normal;
• F. >14.8V: Too High; Might damage the battery, please check the engine stabilizer.

Power Supply: The power of the NL101 is provided via the vehicle’s Data Link Connector (DLC). Follow the steps below to power it up:

1. Find DLC on the Vehicle: The DLC is the connector where diagnostic code readers interface with the vehicle’s on-board computer and usually located in the driver’s cab. A plastic DLC cover may be found for some vehicles and you need to remove it before plugging the OBD II cable. If it cannot be found, refer to the vehicle’s service manual for the location.
2. Plug OBD II cable to the vehicle’s DLC.

One Click "Help" for Data Stream & View Freeze Frame:

• This item enables you to view all data stream items and the live waveform of all selected items.Some data stream have the help information ,press the [?] .
• When an emission-related fault occurs, certain vehicle conditions are recorded by the on-board computer. This information is referred to as freeze frame data. Freeze Data is a snapshot of the operating conditions at the time of an emission-related fault.

Note: If DTCs were erased, Freeze Data may not be stored in vehicle memory depending on vehicle.

Location of the Data Link Connector (DLC): The DLC (Data Link Connector) is the standardized 16-cavity connector where diagnostic scan tools interface with the vehicle's on-board computer. The DLC is usually located 12 inches from the center of the instrument panel (dash), under or around the driver side for most vehicles. If Data Link Connector is not located under dashboard, a label should be there telling location. For some Asian and European vehicles, the DLC is located behind the ashtray and the ashtray must be removed to access the connector. If the DLC cannot be found, refer to the vehicle service manual for the location.

Here we list some frequently asked questions and answers relating to NL101:

1. Question 1: System halts when reading data stream. What is the reason? >>> Answer 1: It may be caused by a slackened connector. Please turn off the NL101, firmly connect the connector, and switch on it again.
2. Question 2: Screen of main unit flashes at engine ignition start? >>> Answer 2: Caused by electromagnetic disturbance and this is normal phenomenon.
3. Question 3: There is no response when communicating with on-board computer. >>> Answer 3: Please confirm the proper voltage of power supply and check if the throttle has been closed, the transmission is in the neutral position, and the water is in proper temperature.
4. Question 4: Why are there so many fault codes? >>> Answer 4: Usually, it’s caused by poor connection or fault circuit grounding.