J2534 Serial Number
Tabby Vandermoon
Tutorial for Purchasing NERS Software
The software was updated March 6, 2024 to version 04.05.00. This version must be used when connecting to vehicle, and no previous versions will operate. NERS will be sunset on August 31, 2024 and will no longer function after that date. User can transition to CONSULT-III plus R2R or CONSULT-III plus software for reprogramming, blank programming, and VIN writing needs.
This NERS software supports reprogrammable Engine and Transmission control units from 1999 to 2019 model year vehicles, and 2005 MY and later VIN writing into ECUs, when using a Nissan validated pass-through device. This software only provides ECU reprogramming, blank programming, and VIN writing capability. It does not provide diagnostic or key programming capability. For Engine and Transmission control unit reprogramming and VIN writing capability on 2020 MY & newer, please use CONSULT-III plus or CONSULT-III plus R2R software.
Purchase of ECU data enables file download access for a period of 24 hours, after which time the file will no longer appear in your list of purchased data files. Be sure to download all data files immediately following your purchase.
When you purchase a J-2534 reprogramming file, you will get a zip file containing a data file (.dat, .pdx, .xcal, .7z), a .csv or .xml file and a Reprog_readme.pdf. Please review the readme file for information on where to place the files in your PC.
In order for you to locate the proper ECU file, you will need to look up the applicable Technical Services Bulletin(TSB) for your vehicle. Instructions in the TSB will pinpoint and advise you of the ECU part # to enter below.
Special Note: Nissan and Infiniti vehicle uses a high level of security when Re/programming or Configuration is performed to the vehicle ECUs. With the release of NERS software version 04.00.01 or greater, technicians will be required to login with their Nissan or Infiniti Techinfo website user ID and password to perform Re/programming and Configuration in NERS.
Login Instruction Guide
When you purchase a J-2534 Blank programming file, you will get a zip file containing a data file (.dat, .pdx, .xcal, .7z), a .csv or .xml file and a Reprog_readme.pdf. Please review the readme file for information on where to place the files in your PC.
How to find the proper J-2534 Blank Programming ECU file: Obtain the blank ECU part number when you purchase the replacement ECU. Enter this blank ECU part number in the field below. or Using a diagnostic scan tool, retrieve the blank ECU part number from the new ECU. Enter this blank ECU part number in the field below. Please note: Take care after making your selection that the listed vehicle information matches the vehicle you are programming.
J2534 is a concept that enables flash programming of an emission related ECU regardless of the communication protocol that is used by the ECU. The purpose is that only one tool (hardware device), often referred to as the pass-thru device, should be needed for all kind of ECUs. The connection between the J2534 device and the ECU is a SAE J1962 connector. The J2534 hardware device is to be connected to a standard PC which holds the Application Program Interface (API) from the vehicle manufacturer (Figure 1). The connection between the PC and the J2534 hardware device is up to the manufacturer of the tool, but USB is probably the most common. A J2534 API DLL is provided from the hardware tool developer which handles the communication to the PC. The J2534 document withholds requirements for the hardware and software of a J2534 tool. The communication protocols supported are; ISO9141, ISO14230 (KWP2000), J1850, CAN (ISO11898), ISO15765 and SAE J2610. In 2005 J1939 was also included.
Vehicles become more and more complex and almost every function is controlled by an Electronic Control Unit (ECU). The ECUs are often connected onto a communication bus to be able to share data between each other. The most common protocol is CAN, but there are other protocols. There are many Vehicle manufactures and almost as many different communication protocols. Every vehicle manufacturer has a tool for analyzing and reprogramming their product, and this tool is often expensive. This makes it difficult for a car, bus or truck workshop to analyze and repair all kind of vehicles.
U.S. Environmental Protection Agency (EPA) and the California Air Resources Board (ARB) have been trying to get vehicle manufactures to support common emission-related services for the aftermarket. The Society of Automotive Engineers (SAE) created the J2534 standard, in 2002, to promote the EPA and ARB in their work.
The J2534 hardware works like a gateway between the vehicle ECU and the PC. This pass-thru device translates messages sent from the PC into messages of the protocol being used in the vehicle ECU. J2534 supports the following protocols:
The connection between the PC and the J2534 hardware can freely chosen by the manufacturer of the device i.e. RS-232, USB or maybe a wireless interface. The vehicle manufacturers programming application is not dependant on the hardware connection. Therefore any device can be used for programming any vehicle regardless of the manufacturer.
The J2534 hardware interface should be able to provide a supply voltage between 5 and 20 volts to the J1962 connector. The power supply should use one of the pins 6, 9, 11, 12, 13 or 14 of the connector and this choice should be selectable in the software. The maximum source current is 200mA and the settling time should be within 1ms.
The J2534 hardware interface should have enough memory to buffer 4Kb of transmit messages and 4Kb of received messages. And the processor must naturally be fast enough to process all messages so that no messages are lost.
Each vehicle manufacturer will have an own API software used for analyzing and programming of their vehicles. If their vehicles only use i.e. ISO 9141, no other protocols have to be supported by the application. It is important that this application conform to the functions in the J2534 API.
This application will have complete information of the ECUs that are supported by the application. This application also includes a user interface where choices can be made depending on the ECU and what action to perform.
A vehicle repair workshop that wants to analyze and re-program vehicles from different manufactures must have an API for each. This API can be downloaded from the internet or installed from a CD or DVD. How this API is provided depend on the manufacturer, but they do charge the customer (repair workshop) ordering it. The price differs a lot between manufacturers, a one year subscription costs between $75 and $2500.
The intention is that every J2534 tool should to be capable of communicating with all protocols supported by the J2534 standard. The application provided by the vehicle manufacturers use commands described in J2534 standard to connect to a hardware tool (of any brand). The connection and initialization gives the hardware tool information of which protocol that is used. Thereafter it is up to the hardware tool to manage the connection to the vehicle with de desired protocol. The PC application will send messages in the earlier determined protocol format to the hardware tool which buffers the messages and transmits the messages in the order they were received.
The J2534 API consists of a number of functions for communication which must be supported by both hardware tool and vehicle manufacturer application. For the PC application developer this means that all commands and messages must made with the functions defined in the API. See table 1 below.
The first command that is sent is the PassThruConnect which establish the connection between the PC application and the J2534 hardware tool. This command includes information about which protocol to use, standard or extended CAN identifier or if ISO15765 is used. The command also includes a channel identification which will be used for all following communication. If the connection was successful, a STATUS_NOERROR value is returned, which indicates that the function has been successfully performed. Before any messages can be sent an initialization has to be made, PassThruIoctl, where parameters like node address, baud rate or protocol specific parameters are set.
All messages sent from the PC application follow the same structure which consists of: protocol type (i.e. J1850, CAN, J9141), receive message status, transmit message flags, received message timestamp (microseconds), data size in bytes, extra data index (start position of extra data in received message i.e. IFR, CRC, checksum), and last but not least an array of data bytes (the received message). It is possible to send CAN messages longer than 8 bytes using ISO15765 commands if this feature was selected upon connection.
The J2534 API DLL provides a linkage between the API functions and the hardware tool. Since the PC application should not have to care about which communication protocol is being used between the PC and the hardware tool. Each manufacturer of a hardware tool has a DLL-file with a unique name. This way it is possible for the software application on the PC to distinguish which hardware tool to connect. It is important that the developer of the firmware in the hardware tool follows the API and name the functions exactly as in the J2534 description. Otherwise it will be impossible for the PC application to find the functions in the DLL when performing the linkage.
e59dfda104