X431 Auto Diag

X431 Auto Diag, based on mobile intelligent terminal design, research and development, and utilizing DBSCar, achieves X431 series product diagnostic functions, including DTC, data stream reading, action test and special functions, etc. It integrates much more application and service taking the advantage of intelligent operation system.
“Made for iPhone” and “Made for iPad” mean that an electronic accessory has been designed to connect specifically to iPhone or iPad, respectively, and has been certified by the developer to meet Apple performance standards.
Apple is not responsible for the operation of this device or its compliance with safety and regulatory standards. Please note that the use of the accessory with iPhone or iPad may affect wireless performance.
iPad, iPhone are trademarks of Apple Inc., registered in the US and other countries.
Launch DBScar: This connector applies to 16PIN OBD2 vehicles.
For competitive Launch Scanners prices, please visit shopobd2.com.

How to match ignition key and remote control key on Nissan with scan tool?

1. Key initialization 

Initialize the car key under following conditions: 
(1) For earlier models, whose ECU do not  support C/U INITIALIZATION, and Scan tool 
can only read DTCs and clear DTCs from NA TS. For such models, the car key can be 
initialized without decoder.   
Operating steps: turn the ignition key to ON  position and wait at least 5sec, then pull out the key and wait at least 5sec, after that, t he ignition key will be initialized automatically. 
(2) For newer models, the initialization  should be performed with scanner when the 
following conditions meet: 
(2.1) If the BCM is replaced, to initialize  all ignition keys or door keys by decoder.   
(2.2) If replace a used ECM, to in itialize all keys by decoder.   
(2.3) If replace a new ECM, just turn the i gnition key on and wait 5sec and then turn off, the ignition key will be initia lized automatically. If the engine can’t be started, then the ignition key shall be initialized by decoder. 
All existed ID numbers will be cleared as long as initialization performed. Therefore, it is necessary to register all the keys again.  Otherwise, the engine  can’t be started, and "DIFFERENCE OF KEY" or "LOCK MODE  will be appeared on the display of scanner 
when performing scan on OBD."   
Before initializing the car key, the PIN codes shall be obtained. Following is the 
explanation of PIN codes: 
PIN codes can be separated into fixed code and random code, which can be differentiated 
from the printed characters on label  which sticked on NATS control unit. 
Fixed code: if the label is prin ted with characters [A] or no  characters, then the PIN code is a fixed code. 5523 is default, which is mainly applied on some 2000-2004 models, such as Cefiro A33, SUNNY and the other common models.   
Random code(4 digits): can be obtained from Nissan Company. Each car has its unique 
PIN codes. Before obtaining the PIN, customer must firstly provide a 5-digits identification code(consisted of numbe rs and letters)written on BCM,  or read it from related BCM subsystem via Scan tool. 

After obtained PIN code, Scan tool can be used to initialize the ignition key by accessing NATS system and perform appropriate DTCs diagnosis or key replacement via 
re-programming operation. For details, please refer to steps below:   
1. Select "C/U INITIALIZATION" mode;   
2. Turn the ignition key to "ON" position;   
3. Input password (PIN code);   
4. Press "START" button to start the control unit initialization process; 
5. "INITIALIZATION COMPLETED" indicates t hat the initialization  of the IMMU and ECM 
is finished;   
If the fifth step shows "INITIALIZATION STOPPED, or FAILED", it indicates the 
initialization by decoder uncompleted or failed.   
6. Turn the ignition switch to "OFF" position and pull out the key.   
7. Turn the ignition switch to "OFF" or "ON" position;   
8. Read DTCs;   
9. Replace IMMU if displaying “IMMU”, and then use X-431 or CONSULT-II to perform C/U 
INTIALIZATION". 
Perform "C/U INTIALIZATION again if displaying “No DTCs”

2. Ignition key registration 

1. Insert the 1st key into ignition switch, and tu rn to "ON" position to remain for more than 5sec, and then turn the ignition key to "OFF"  position and pull out the ignition key;   
2. After 5sec, when the anti-theft indicator fl ashing, insert the 2nd key, and turn to "ON" position to remain for more than 5sec, and then turn  the ignition key to "OFF" position and pull out the ignition key;   
3. Repeat the above-mentioned steps which can match up to five keys;   
4. Open the door or start the engine to exit the key registration; 
5. Confirm each key (remote controller) can start the engine as the normal. 

If the remote control keys can start the  engine, pay attention to whether the remote 
controller can open and lock the door. Otherwise , the remote controller must be matched. 
There are two matching methods below: 

Method 1:   

1. Close all the doors(the operator shall be inside the car), and lock the driver's door  
2. Within 10 seconds, insert the ignition ke y and pull out, which shall be repeated for more than six times;   
3. Hazard warning lights will flash twice;   
4. Turn the ignition switch to ACC position;   
5. At this time, press any one button on the new remote controller once. (Hazard warning 
lights will flash twice);   
6. If copy another anti-theft remote controller, turn the "LOCK" button on driver’s side to "UNLOCK" and then to "LOCK", then repeat step 5;   
7. If matching is completed, just open the car door and pull out the ignition key.

Method 2:   

1. After opened the trunk, close and lock all the doors;   
2. Within 10 seconds, insert the ignition ke y and pull out, which shall be repeated for more than six times; 
3. Open the driver's door and then lock;   
4. At this time, press "LOCK" button onc e on new anti-theft remote controller;   
5. If copy another anti-theft remote control keys, to repeat the steps 2-4. 

Intelligent Key Registration: 

1. Before the registration of intelligent ke y, firstly register the ignition key.   
2. Turn the ignition key to ON position, register the intelligent key via REGIST I-KEY ID 
function of I-KEY system. During the registration, the intelligent key shall be inside the car. Besides, press any one button on intelligent key.

Notes: difference between intelligent key and remote control key. 
Remote control key: starts the engine by remote control the ignition key chip inside, 
therefore, after the ignition ke y registration, just insert the ignition key inside the remote control key can start the vehicle via remote controlling. Such as: TIIDA of 2007 and 2008. 
However, after such key matching is completed, the remote controller shall be matched for 
door opening and locking.   
Intelligent Key: such key has its own intelligent  chip inside, therefore, after the ignition key registration, the intelligent key also must be matched before starting the engine. Refer to Intelligent Key Registration for matching method. 

DTCs of NATS

The most common DTCs of NATS are P1610, P1611, P1612, P1614, and P1615, etc. 
Their relative meanings are as follows: 
[P1610]: LOCK MODE (dead lock mode);   
[P1611]: ID DISCORD, IMMU-ECM (the ID signals between IMMU and ECM are 
inconsistent, which  means the system shall be initialized);   
[P1612]: CHAIN OF ECM-IMMU (a fault on NATS communication line between ECM and 
IMMU);  
[P1614]: CHAIN OF IMMU-KEY (a fault on the line between IMMU and KEY which causes 
the BCM can’t receive the key ID signal);   
[P1615]: DIFFERENCE OF KEY (BCM has received  the ID signal of key and identified it 
as the illegal ） 
NATS will enter into dead lock mode if using  an unregistered or invalid key to start the 
engine for more than five times, at this time, even though the correct car key also can not normally start the engine. To unlock the mode,  the system shall be initialized again. If the detected DTCs are related to engine system, the related DTCs  will also display on ECM. 
Before clearing the DTCs memory on NATS, firstly check the DTCs on engine system 
because while deleting the self-diagnostic codes of NATS,  the memory on the "engine" 
self-diagnosis system  will also be cleared.

I got this post from http://www.x431.com.

Video: Launch X431 Diagun III

Launch X431 Diagun III is smart, easy to carry, fully functional and convenient to use. X431 Diagun III + Launch DBScar diagnostic adaptor integrated design, supports wired and Bluetooth wireless diagnosis. It supports English, Portuguese, French, Spanish and Russian.

Launch X431 Diagun III Vehicle List :

Demo, Smart diagnostic software, Smart OBDII

America: America Ford, Chrysler, GM, Acres, INFINITI, Lexus.
Australia: Australia Ford, Holden
Brazil: Brazil GM
India: Indonesia Daihatsu, Indonesia Suzuki, Mahindra, MARUTI,TATA
Japan:Daihatsu, Honda, JP Isuzu, Mazda, Mitsubishi, Nissan, Subaru, Suzuki, Toyota
Europe:Audi,Benz,BMW,Citroen,Europe Ford,Fiat,Jaguar,Lancia,Landrover,Opel,Peugeot,Porsche,Renault,Romeo,Rover,Saab,Seat,Skoda,
Transporter-Class, Volkswagen, Volvo
China:Brilliance,BYD,Changan,ChangCheng,Changhe,Chery,GEELY,Gonow,HaFei,JAC,Jiangling,SGMW,Tianjin,Xiamen Golden,XinKai,ZhongShun,Zhongxing,ZOTYE
Korea: Daewoo,Hyundai,Kia, Ssangyong
Malaysia: Perodua,Proton
Russia: GAZ,VAZ
S.Africa: S.Africa Opel
Thailand: Thailand Isuzu

X431 Diagun III Functions:

Long stand-By time: Can be used continuously 10 hours.
Unique Appearance: Rolling cover design, the DBScar connector is integrated.
Support print function: Support standard USB printer for printing diagnostic result.
Quick Update: Nearly 1,000 software update per year to ensure the functions.
Wireless diagnosis: Main unit can communicate with DBScar connector by Bluetooth(<100m).
Powerful diagnostic: Inherited with all diagnosis function of X-431 with wild software coverage, Asian, European and U.S.

For more launch Scan Tools, please visit shopobd2.com. And you can visit http://www.youtube.com/user/shopobd2 for more OBD2 Scanners' Videos.

Autocom CDP+ for Cars/Trucks and OBD2 2013.01

Best Price Autocom CDP+ for Cars/Trucks and OBD2 2013.01 is the newest version. Now Price: $92.90. And we provide one year free activation, then the activation will charge 8usd/time.

Autocom CDP+ is a quick and reliable diagnostic tool serving as a link between vehicle and computer. It works on both old and new vehicles. Simply connect Autocom CDP+ to the diagnostic socket in the vehicle and it will communicate with the diagnostic software installed on your PC.

With CARS, you are able to perform brand specific diagnostics for cars and light vans from 1988 onwards. A total of 47 different brands. With TRUCKS software package, you are able to perform brand specific diagnostics for light and heavy commercial vehicles, buses and trailers from 1995 onwards.

You can learn the steps to install and active the software of Autocom CDP+ 2013.01 in this video:

And you can find more OBD2 Videos on our YouTube Channel: http://www.youtube.com/user/shopobd2

To learn more Autocom CDP+ Scanners, please visit shopobd2.com. Any questions, please feel free to contract us.

Original Autel MaxiFlash Pro

Original Autel MaxiFlash Pro fully compatible with both SAE J2534-1 and J2534-2 reprogramming standards. It is compatible with Toyota Techstream, Volvo VIDA, Honda HDS, Jaguar-Land Rover IDS and BMW 3G for OEM diagnostics.

Features of Autel MaxiFlash Pro:

1. Performs the standard PassThru J2534 functionality
2. Fast performance ensures quickly reprogramming even the newest controllers
3. Wireless with advanced networking functions
4. Built-in wireless and data storage
5. Rugged design capable of withstanding harsh environments
6. Internet upgradeable and updateable

For more Autel Scanners, please visit shopobd2. And there are many User Manuals for free download. 

NEW: XPROG BOX V5.45 ECU Programmer

XPROG BOX V5.45 is a continuation of the project XPROG and now supports more than 450 units (serial EEPROM's, Microcontrollers (MCU), Electronics Control Units (ECU), DashBoards, Immobilizers, Calculators and others). And it's language is English.

AUTHORIZATIONS 

AUTH-0001 Motorola HC05 family authorization (allows to read/write EEPROM)
AUTH-0002 Motorola HC08 family authorization (allows to read/write EEPROM)
AUTH-0003 Motorola HC11 family authorization (allows to read/write EEPROM)
AUTH-0004 Motorola HC12, 9S12 family authorization (allows to read/write EEPROM and flash memory)
AUTH-0005 Texas Instruments TMS370/TMS374 family authorization (allows to read/write EEPROM)
AUTH-0006 Motorola HC05Bxx and HC05Xxx family bypass security authorization (allows to read/write secured EEPROM and flash memory)
AUTH-0007 ST M35080 authorization. Read/Write/Erase device to delivery state.
AUTH-0008 BMW EWS3 authorization
AUTH-0009 ATmega family authorization (allows to read/write EEPROM and flash memory)
AUTH-0010 MB ZGS001 authorization
AUTH-0011 Motorola HC11EA9/E9 bypass security authorization (allows to bypass security bit and read EEPROM and RAM memory)
AUTH-0012 National CR16 authorization (allows to read/write EEPROM memory)
AUTH-0014 ST7, ST10 family authorization (allows to read/write internal flash)
AUTH-0015 MPC5xx authorization (depending on device program automatically detects MPC5xx, M95xxx device type, flash, external flash and configuration memory size)
AUTH-0018 Motorola HC12, HC912, MC9S12, MC9S12X bypass security authorization (allows to read/write secured EEPROM and flash memory)
AUTH-0020 ARM (Micronas, ...) Family authorization (allows to read/write internal flash and external serial EEPROM)
AUTH-0021 ARM (Micronas, ...) Family bypass security authorization (allows to read/write secured and non-secured internal flash and external serial EEPROM, view/change mileage,chassis number (VIN), serial number and PIN code).
AUTH-0022
XPROG hardware registration

ADAPTERS of XPROG BOX V5.45:

Product Code Description
ADP-0001 TMS370 PLCC28 programming adapter
ADP-0002 TMS370 PLCC44 programming adapter
ADP-0003 TMS370 PLCC68 programming adapter
ADP-0004 Motorola HC05B/X PLCC52 programming adapter
ADP-0005 Motorola HC05B/X QFP64 programming adapter
ADP-0006 ST M35080 in-circuit programming adapter
ADP-0008 TMS374 family in-circuit programming adapter
ADP-0009 MC68HC05V12 programming adapter
ADP-0010 TMS374 on-board programming adapter
ADP-0011 HC11EA9/E9 programming adapter
ADP-0017 HC(S)12 BDM / ARM Micronas in-circuit programming/bypass security adapter
Rev.C+
Processor: INTEL Pentium 60MHz or faster (depends on operating system)
Memory (RAM): 64MB (depends on operating system)
Hard drive: 20MB free space
Communication: One free physical COM or USB port
Operating system: Microsoft Windows NT/ME/2000/XP/VISTA/WIN7

Attention for xprog-box 5.45:

1. Shut off the computer anti-software . if not , will kill the software

2. Close the internet. If not ,will damaged the hardware ,and cannot be repaired without any warranty.

3. Uninstall all the xprog-m, or xprog box software -higher or lower software, make sure that your pc only install our software for our xprog-box 5.45 , our xprog-box hardware cannot work on other lower or higher software. the hardware will be burned and damaged ,cannot be repaired without any warranty if you run our hardware on other software .

4. Never try to UPDATE online or offline, the hardware will be burned damaged if you want to try to upgrade it online or offline from official website, without any warranty.

5. we cannot refund ,cannot exchange, cannot repair if you do not listen to those advice above. It means that you accept those conditions if you have ordered our xprog-box 5.45

And you can visit shopobd2 to learn more information of XPROG BOX V5.45. 

History of OBD

On-board diagnostics, or OBD, is an automotive term referring to a vehicle's self-diagnostic and reporting capability. OBD systems give the vehicle owner or a repair technician access to state of health information for various vehicle sub-systems. The amount of diagnostic information available via OBD has varied widely since the introduction in the early 1980s of on-board vehicle computers, which made OBD possible. Early instances of OBD would simply illuminate a malfunction indicator light, or MIL, if a problem was detected—but would not provide any information as to the nature of the problem. Modern OBD implementations use a standardized digital communications port to provide real-time data in addition to a standardized series of diagnostic trouble codes, or DTCs, which allow one to rapidly identify and remedy malfunctions within the vehicle.

History of OBD:

 1969: Volkswagen introduces the first on-board computer system with scanning capability, in their fuel-injected Type 3 models.
 1975: Datsun 280Z On-board computers begin appearing on consumer vehicles, largely motivated by their need for real-time tuning of fuel injection systems. Simple OBD implementations appear, though there is no standardization in what is monitored or how it is reported.
 1980: General Motors implements a proprietary interface and protocol for testing of the Engine Control Module (ECM) on the vehicle assembly line. The 'assembly line diagnostic link' (ALDL) protocol communicates at 160 baud with Pulse-width modulation (PWM) signaling and monitors very few vehicle systems. Implemented on California vehicles for the 1980 model year, and the rest of the United States in 1981, the ALDL was not intended for use outside the factory. The only available function for the owner is "Blinky Codes". By connecting pins A and B (with ignition key ON and engine OFF), the 'Check Engine Light' (CEL) or 'Service Engine Soon' (SES) blinks out a two-digit number that corresponds to a specific error condition. Cadillac (gasoline) fuel-injected vehicles, however, are equipped with actual on-board diagnostics, providing trouble codes, actuator tests and sensor data through the new digital Electronic Climate Control display. Holding down 'Off' and 'Warmer' for several seconds activates the diagnostic mode without need for an external scan-tool.
 1986: An upgraded version of the ALDL protocol appears which communicates at 8192 baud with half-duplex UART signaling. This protocol is defined in GM XDE-5024B.
 1988: The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and set of diagnostic test signals.
 1991:[1] The California Air Resources Board (CARB) requires that all new vehicles sold in California in 1991 and newer vehicles have some basic OBD capability. These requirements are generally referred to as "OBD-I", though this name is not applied until the introduction of OBD-II. The data link connector and its position are not standardized, nor is the data protocol.
 ~1994: Motivated by a desire for a state-wide emissions testing program, the CARB issues the OBD-II specification and mandates that it be adopted for all cars sold in California starting in model year 1996 (see CCR Title 13 Section 1968.1 and 40 CFR Part 86 Section 86.094). The DTCs and connector suggested by the SAE are incorporated into this specification.
 1996: The OBD-II specification is made mandatory for all cars sold in the United States.
 2001: The European Union makes EOBD mandatory for all gasoline (petrol) vehicles sold in the European Union, starting in MY2001 (see European emission standards Directive 98/69/EC[2]).
 2004: The European Union makes EOBD mandatory for all diesel vehicles sold in the European Union
 2008: All cars sold in the United States are required to use the ISO 15765-4[3] signaling standard (a variant of the Controller Area Network (CAN) bus).[4]
 2008: Certain light vehicles in China are required by the Environmental Protection Administration Office to implement OBD (standard GB18352[5]) by July 1, 2008.[6] Some regional exemptions may apply.
 2010: HDOBD (heavy duty) specification is made mandatory for selected commercial (non-passenger car) engines sold in the United States.

OBD-II:
OBD-II is an improvement over OBD-I in both capability and standardization. The OBD-II standard specifies the type of diagnostic connector and its pinout, the electrical signalling protocols available, and the messaging format. It also provides a candidate list of vehicle parameters to monitor along with how to encode the data for each. There is a pin in the connector that provides power for the scan tool from the vehicle battery, which eliminates the need to connect a scan tool to a power source separately. However, some technicians might still connect the scan tool to an auxiliary power source to protect data in the unusual event that a vehicle experiences a loss of electrical power due to a malfunction. Finally, the OBD-II standard provides an extensible list of DTCs. As a result of this standardization, a single device can query the on-board computer(s) in any vehicle. This OBD-II came in two models OBD-IIA and OBD-IIB. OBD-II standardization was prompted by emissions requirements, and though only emission-related codes and data are required to be transmitted through it, most manufacturers have made the OBD-II Data Link Connector the only one in the vehicle through which all systems are diagnosed and programmed. OBD-II Diagnostic Trouble Codes are 4-digit, preceded by a letter: P for engine and transmission (powertrain), B for body, C for chassis, and U for network.

I got these information from Wikipedia. You can get detail information about OBD tools. And you can visit shopobd2 for kinds of OBD2 Tools. Any questions, please feel free to contract us.