OEM VIN READING
NC1701 FEATURE INCLUDED AS STANDARD
WHAT IS IT?
As standard, NC1701 provides OEM VIN reading capability. This means clients have the potential to read VINs when not available through standard OBDII requests.
The majority of CAN connected telematic devices only use generic OBD2 commands to try to read the vehicle VIN. In many cases this is insufficient as the vehicle manufacturers do not always implement this part of the OBD2 standard.
HOW IT WORKS
Nebula Systems have developed their own VIN reading algorithm which sits within NC1701’s base firmware. This enables the NC1701 to read VIN via OEM protocols.
We use the VIN to identify the individual vehicle an NC1701 enabled device is connected to. On first connection, the VIN is sent back to our MECH5 cloud where it is decoded into Make/Model/Year. This is the initial identification step required to then match and download a Configuration File back to the chip.
It is the Config File that contains all the instructions to access and retrieve OEM PIDs or DTCs.
In some very special cases, the VIN is not actually stored in any ECU on the car and is not readable from the CAN bus either. In this circumstance, our hardware partner or their fleet clients, can manually input the VIN and lock it to a telematic device IMEI number.