This is a custom product development project for Automotive Industry. The software developed for diagnostic services as per the project specification. The hardware designed to establish wireless bridge for the diagnostic IES services with delay as less as 25 ms. The system is designed for the operation distance of up to 30 metres. 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.
The system works in the 433MHz, 10 dbm range frequency. When a car’s sensors decide that something is amiss, they trigger a message known as a “trouble code,” which may manifest as a “check engine” light or another warning on the dashboard. OBD scanners can check these trouble codes to determine exactly what’s wrong, and clear them from the computer’s memory once the problem is fixed. The trouble codes are just that, though: Codes. Trouble codes start with a letter and include four or five numbers, which together point to the specific subsystem and what problem it is experiencing. The development also resulted in the development of scanning tools.
A connected car is a car that is one that can communicate bidirectionally with other systems outside of the car (LAN). This allows the car to share internet access, and hence data, with other devices both inside and outside the vehicle. We design, develop & prototype automotive electronics related to telemetry, OBD & wireless interface devices as per the customer requirement.
EQUVERA RESPONDS TO COVID 19. CHECK OUR OUR PRODUCTS PAGE. Dismiss