Web API and Interface Development
Budget: £20 – £250 GBP
OBD Diagnostics Project
We currently have a tracking platform that shows the location of several tracking devices. The devices show location, speed, battery, etc. We are introducing a new OBD tracker device that also gives vehicle diagnostics.
We would like to separate the vehicle diagnostics from the tracking service. Since the tracking device can only send data to one server, all OBD diagnostic trackers will send the data to a newly created server, that server will immediately send an exact duplicate of the data to the tracking platform and then write the data to the vehicle diagnostics database to be used as per below.
The diagnostics server will parse the data string and interpret the data. The data will be made available on a web interface with login (username/password). A simple interface with real-time updates of all diagnostics displayed. The web interface should be able to chart historical data for relevant diagnostic information. (for example, coolant temperature, speed, oil volume, rapid acceleration, fault codes, alarms). The web interface should have the ability to filter data, hide fields, export data to CSV. Alarm codes should give web notifications (based on user choice of alarms, thresholds). The web interface needs to be responsive.
The OBD device we are using uses the Huabao protocol. The protocol document is attached
We currently have a tracking platform that shows the location of several tracking devices. The devices show location, speed, battery, etc. We are introducing a new OBD tracker device that also gives vehicle diagnostics.
We would like to separate the vehicle diagnostics from the tracking service. Since the tracking device can only send data to one server, all OBD diagnostic trackers will send the data to a newly created server, that server will immediately send an exact duplicate of the data to the tracking platform and then write the data to the vehicle diagnostics database to be used as per below.
The diagnostics server will parse the data string and interpret the data. The data will be made available on a web interface with login (username/password). A simple interface with real-time updates of all diagnostics displayed. The web interface should be able to chart historical data for relevant diagnostic information. (for example, coolant temperature, speed, oil volume, rapid acceleration, fault codes, alarms). The web interface should have the ability to filter data, hide fields, export data to CSV. Alarm codes should give web notifications (based on user choice of alarms, thresholds). The web interface needs to be responsive.
The OBD device we are using uses the Huabao protocol. The protocol document is attached