MOBILITY ADO has an internal development system called "computer on board", which has operated for more than 5 years and is constantly seeking to improve. For its operation it is necessary to interact with engine data, and for this, MOBILITY ADO had a foreign supplier which, as of 2016, stopped supplying the product that was used for said interconnection.
In the month of February of 2017, an opportunity for collaboration with didcom is presented, this in view of the need to have a provider that could develop custom hardware, in this case an electronic interface with engine data connection, which had as its main function interact locally with an internal system called computer on board, which manages the regulation of the operation and sale of ticket on board.
“The challenge was great, we had to develop new hardware to replace a discontinued one. The existing products in the warehouse were running out so we had to be fast”
Based on the functionality requirement provided by MOBILITY ADO, the breakdown of the activities had to be analyzed with the didcom engineering team, so the project was divided into 2 areas.
It had to fulfill very specific functions and especially necessary for the computer board system to operate correctly.
The development should consider an improvement of great importance with respect to the previous supplier: the new product must be multiprotocol, that is, to be compatible with the different bus manufacturing brands with which the service is offered and obtain the necessary engine data for its correct implementation, this with the purpose of standardizing the results independent of the unit model, since the fleet consists of units of different manufacture brands.
“The new hardware had to work with multiple vehicles of different manufacture brands (multiprotocol)”
Another challenge to overcome was the time factor, since the on-board computer system was in constant use, and the products available from the previous supplier were being depleted in warehouses, so communication and exchange of information should be accelerated and coordinated efficiently. information between MOBILITY ADO and didcom to be able to make the development process efficient, functionality evaluations, field implementation, improvement detection, and thus shorten any possible lag to guarantee the results and move on to the production stage.
A new product was developed which was called “DBI Multiprotocol”. An electronic device capable of physically connecting the computer on board and the automotive protocol of the unit, having as its main feature a functional communication, thus converting the source data of the unit to a destination data interpreted only by the computer on board.
This solution required that didcom engineers specialized in hardware and software areas work together to investigate and design the product that would meet the needs of the client.
The proof of concept took a period of 2 months, at which time the necessary maturity of functionality was reached, turning the proposed prototype into a functional product.
The Multiprotocol DBI began to be implemented immediately in different buses of different brands, being able to cover the operation of the computer on board system in the different routes that are established.
What engine data is obtained?:
- Fuel Used
- Average Fuel Economy Km/L
- Accelerator Percentage
- Vehicle speed
- Coolant temperature
- Engine oil temperature
These parameters are necessary to evaluate the driving in real time through the onboard computer, and notify the driver of any eventuality of operation outside the established range.