{'fraction_non_alphanumeric': 0.03125, 'fraction_numerical': 0.002533783783783784, 'mean_word_length': 5.076923076923077, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
DEVELOPMENT OF OBD-II DRIVER INFORMATION SYSTEM

An on-board diagnostic II (OBD-II) is a standard diagnostic software management that is installed in a power train control module (PCM). It provides some useful data to the driver. There are four different devices using the OBD-II protocol exists in the market. These devices are used as a driver information system. They are personal digital assistant (PDA) Dyno/OBD-II scan tool, CarChip Fleet, DriveRight 600, and ScanGauge. Each of these four devices has some limitation in term of supporting all features for live data monitoring, trip information, diagnostic trouble code (DTC) scanning system, and data logging system. Thus, there is a need for a device that supports all these features together with scheduled maintenance reminder. This paper describes the design and development of driver information based on OBD-II protocol using embedded system architecture. Its hardware and software systems were designed based on four design considerations: upgrade capability, high data storage capacity, back-up capability, and user friendly. The proposed system was successfully interfaced and tested with the PCM of Hyundai Getz car.