Module: eOBD / OBD PID scanner

Introduction

The eOBD / OBD II PID scanner module offers the support of 5 additional PIDs. This chapter describes how to configure the module and how to decode the new fields notified to your back-end server.

Module configuration

First of all, the module has be linked to your Munic Box. Then, the module must be configured with:

  • module activation on the device side. Note that it is independent from the license activation.
  • the polling period
  • the requested PIDs (maximum of 5)

Finally, Munic Box will request these 5 PIDs periodically and send them to your server.

Parameters Units Default
Module status Activated / De-activated De-activated
Period Seconds 60
Mode and pid of the first request Integer (in hex format) None
Mode and pid of the second request Integer (in hex format) None
Mode and pid of the third request Integer (in hex format) None
Mode and pid of the fourth request Integer (in hex format) None
Mode and pid of the fifth request Integer (in hex format) None

Fields description

The results of each OBD request are stored in the following fields:

Field name Description Type Size
MDI_OBD_PID_1 Result of the first request encoded in base64 String 255
MDI_OBD_PID_2 Result of the second request encoded in base64 String 255
MDI_OBD_PID_3 Result of the third request encoded in base64 String 255
MDI_OBD_PID_4 Result of the fourth request encoded in base64 String 255
MDI_OBD_PID_5 Result of the fifth request encoded in base64 String 255

Each field returns (encoded in base64):

  • the value of the requested PID
  • the "No Data" string when the PID is not supported by the vehicle
  • the "Data Request Fail" string otherwise. It is the case when the PID is requested while the OBD bus is off (ignition off).