Contact : info@obduino.ca
| Home | Hardware | Configuration | Tools | Logging |
| Press ... when in ... | real-time display | menu display |
| LEFT | rotate screen (re-press LEFT to skip screen description) | decrease, select YES |
| MIDDLE | go into menu | apply and go to next item |
| RIGHT | rotate brightness | increase, select NO |
| MIDDLE+RIGHT | trip reset | n/a |
| MIDDLE+LEFT | tank trip reset | n/a |
Change display to screen 1, 2 ,3, BIG instant consumption, BIG average consumption. After a shutdown, OBDuino will wake up on the latest screen you used.
Select the brightness level, it goes from 0 (off) to 4 (full). OBDuino will remember it after a shutdown.
When you press middle and right button, a screen appears: Select if you want to reset the data and press middle button to ack.
When you press middle and left button, a screen appears: Select if you want to reset the data and press middle button to ack.
Set the LCD contrast from 0 to 100 in step 10
YES=SI, NO=rods and hogshead
Speed from which the display go from L/100 or MPG, to L/h or GPH.
Size of your tank in litres or gallons.
This percentage will need adjustment after you have checked manually a few tank to better approximate the fuel consumption. When you fill up, compare the number on the pump with the one recorded in the E3:Fuel Use Tank one. For instance on my 07 Elantra I have to use 105% in summer and 110% in winter. Unfortunately you cannot have a rigorously exact number because of variation of gas quality, temperature, etc. so you will notice sometimes that the number is higher and sometimes it is lower. Use an average number.
This percentage will need adjustment after you have checked manually a long distance done with a well calibrated instrument like a GPS. For instance on my Elantra with front tire at 44psi, I use 102%.
For vehicles with a MAP only we have to emulate the MAF. This is the size of the engine, e.g. 33dl for a 3.3 liter one.
When the OBDuino cannot communicate with the ECU anymore, it goes into sleep mode and draws about 8mA. In advanced sleep mode it fully makes the harware go to sleep, taking as low as 0.5mA. It does not work on all cars because on some, even when you shutdown the engine and remove the key, there is still activity on the CAN bus (alarm system, auto-roll windows, etc) that prevent the OBDuino to stay in its advanced sleep mode. If your OBDuino instantaneously restarts after a shutdown and cycles into shutdown/restart, disable Advanced sleep mode.
By default only the DTC (Diagnostic Trouble Codes) that light your CEL (Check Engine Light) are displayed. A DTC can happen because of a badly screwed gas cap for instance and be kept in memory by the ECU, but it will not light the CEL ; it is only if the same code happens drive cycle after drive cycle that it will be copied from pending to fault. A pending code is kept by the ECU for a few cycles, for instance 10, before being cleared automatically if it does not happen again. By enabling this option then pending codes will be displayed, but cannot be cleared.
By selecting yes, the OBDuino unit will be paired with the VIN of the car and will refuse to work if it is plugged on another car.
Choose if you want to configure the PIDs in the various screens.
(if you have selected YES at the previous item)
Select the PID you want to be displayed on screen 'n' in the corner 'm'.
OBDuino switches every second between the description string of the PID and its live value.
A good list of OBD-II PIDs is on Wikipedia, OBDuino will only allow the PID supported by your car. Here is some specials PIDs you can access (either by decreasing below 0 or by going far up):