ENHANCED OEM DTC READING
SERVICE LEVEL 2
WHAT IS IT?
This second service level gives our clients the ability to check for OEM DTCs from each and every ECU on any given vehicle.
Historically, most telematic devices that connect to a vehicle’s CAN Bus network, only use generic protocols known as OBDII which only allow access to drive-train ECUs for emissions related data. This standard is known as J1979 and has been around since the 1980s. The problem with this approach is that the data you can access is limited to about 2,500 P0XX generic DTCs and does not give any access to manufacturer DTCs that number into the tens of thousands
NC1701, empowered with Config Files containing OEM protocol information from our MECH5 cloud, has no such restrictions and thus can retrieve all the DTCs, OEM or OBDII, that a vehicle may have.
The following image shows just how many different ECUs NC1701 can access for DTCs
HOW IT WORKS
When a client’s NC1701 enabled telematic device is first connected to a vehicle, NC1701 extracts the VIN using our own VIN reading algorithm, and sends it to our MECH5 cloud.
MECH5 then generates a specific Configuration File for that make and model of car, which contains the instructions to read OEM DTCs from all ECUs in the vehicle. The fully encrypted and secure Config File is then sent back to NC1701.
When implementing this service, clients can choose whether they want to have the DTCs interpreted by a web lookup service to our MECH5 cloud, with the full explanation of the code then accessed via an API, or simply have the codes returned to their own back-end for them to interpret themselves.
We call this service a Full Vehicle Health Check.