PHEV Watchdog

You'll need a compatible OBD2 adapter plugged in the OBD2 port.

• Please see all the info about the OBD2 protocol in the website index page here.

• Please see "Which OBD2 adapter should I get and where from?.

• Please see "Where do I find this OBD2 port?.

Not every OBD2 adapter on the market will work with this App.

In order to extract battery data from the interface the adapter must support a specific type of commands.

Cheap generic OBD2 adapters available are known as "chinese clones" are built with low cost electronics and most do not support the required protocol.

They are also usually slow and will normally fail with regular usage. When failing they might return erroneous data, just stop working or generate malfunction in the interface which will trigger errors in the car.

Please stick to the list of adapters listed on the website which are reported to work with the App.

Also get your adapter from a reliable source and one that you can get a replacement or refund from if needed.

For left hand drive cars, remove the plastic cover located below the dashboard on the left side of the steering wheel. There you'll find the fuses and the 16 pin OBD2 port.

For right hand drive cars, remove the plastic cover located below the dashboard on the right side of the steering wheel. There you'll find the fuses and the OBD2 port.

16 pin OBD2 port

For the App the only difference is the way you configure each..

When connected to a Wi-Fi adapter you won't be able to access other data networks (mobile or Wi-Fi) from your device.

With a Bluetooth adapter this will not happen and you shouldn't have any problems using other Bluetooth accessories simultaneously as multiple connections are usually supported for most devices.

Please see "Setting up the Watchdog... Step by Step".

Please see "Downloading the App!".

Yes, no problem. Here's what you should do:

• 1. In the free App from the Settings menu "Backup" your data.

• 2. Install the payed App.

• 3. In the payed App from the Settings menu "Restore" your data (files are named with the date/time of the backup, it should be the most recent in the list).

• 4. Uninstall the free App.

• 5. In order to be able to see the data in the new App, you'll need to connect to your car at least once so the App can learn the VIN number. It will then filter all restored data by the VIN number.

Here's what you should do:

• 1. In the old Android device do a backup from the Settings menu ("Backup" option).

• 2. Install the App in the new Android device.

• 3. Copy the whole folder "PHEVWatchdog" inside the folder "Download" from the old to the new Android device.

• 4. In the new device from the Settings menu "Restore" the backup (files are named with the date/time of the backup, it should be the most recent in the list).

• 5. In order to be able to see the data in the new App, you'll need to connect to your car at least once so the App can learn the VIN number. It will then filter all restored data by the VIN number.

Please see "How to sync data online... Step by Step".

Assuming that your adapter is not a refurbished unit with some cheap chinese electronics clone and that it is not faulty, you might be experiencing compatibility issues.

TThe connection between the adapter and the App is handled by the Android system only, the App only uses the service provided and communicates through it.

With every manufacturer able to build its own version of the Android system the platform is rather unstable and issues between specific hardware devices are not uncommon..

Nevertheless you may want to try another third party App like Torque and see if the same happens. If it persists you could try to replace the adapter with one from another brand.

No, because you will definitely have connection issues.

The Watchdog App uses the OBD2 adapter intensively (over 30 commands/second for a fast adapter).

Splitting the OBD2 port will reduce the performance and originate a lot of timeouts which will make the App to drop the connection.

Please see "App's screens... explained".

Displayed speed on the App comes directly from the OBD2 interface (car) and is usually an estimate of the real vehicle speed. The difference from the car's speedometer is due to an introduced error.

Most speedometers have tolerances of some ±10%, mainly due to variations in tire diameter.

You can read more about this here: "Speedometer (Wikipedia)".

Range estimation of the App does not come directly from the car and has its own calculation.

App's calculation is based on the actual consumption and on the last fifty recorded trips.

Electric/Fuel consumption of the App does not come directly from the car and has its own calculation.

For electric consumption the App's calculation is based on monitoring the battery current.

Fuel consumption is calculated by monitoring the fuel flow rate which is generally obtained throught the Mass Air Flow sensor (MAF) readings.

Both calculations uses readings in intervals of milliseconds which should make them very accurate.

There is always some kind of discharge either to power the heating/cooling system or to overcome inertia.

There are two options to start the recording of a Trip:

"Start Live Data" creates a new session/recording which results in a single Trip card in the Trip List.

"Resume Live Data" creates a new session/recording (reason why the stats are zeroed) which will be merged with the most recent Trip in the Trip List (and consequently it will not produce a new card).

The App produces some files being all stored under the App's folder located inside the Download folder inside the device.

See the structure example bellow and hover a folder or file to see the description.

•  Download

  •  PHEVWatchdog

    •  backups

      •  autobackup_evwd_logs.db

      •  backup_evwd_logs.db

      •  20211015_134653_evwd_logs.db

    •  trips

      •  ChargeLog_2021_10_28_23_47_11.csv

      •  TripLog_2021_10_26_19_49_14.csv

      •  TripLog_2021_11_03_22_26_15.csv

    •  screens

      •  Screenshot_2021_10_29_09_15_12.png

      •  Screenshot_2021_10_30_11_55_02.png

      •  Screenshot_2021_11_05_10_40_25.png

    •  debug

      •  CrashLog_2021_10_28_11_57_25.txt

      •  DebugLog_2021_10_31_21_41_47.txt

      •  UploadLog_2021_10_29_09_36_08.txt

Battery Condition List:

• One Green card for every change in the Battery Capacity value (State of Health or SoH) observed.

• One Red card between Green cards for maximum Battery Charge (State of Charge or SoC) observed above 95% of State of Charge.

• One Blue card between Green cards for minimum Battery Charge (State of Charge or SoC) observed below 30% of State of Charge.

• SoC cards (Red and Blue) can be hidden with the toggle button on the upper right corner.

Battery cards are generated only when a change is observed by the App.

Unless a change is detected no card is generated.

SoH or the State of Health expresses in percentage the actual battery capacity compared to its ideal condition.

Typically, a battery SoH will be 100% at the time of delivery and will decrease over time and use.

However, manufacturers introduced an upper buffer (typically 5%) to avoid full charge to 100% which is known to impact the battery health.

Usually there is also a lower buffer to prevent discharging to 0% which is also known to reduce the battery capacity.

Although sometimes expressed in kiloWatt-hour (kWh) Battery Capacity is generally measured in Ampère-hour (Ah).

Kilo Watt/hour assumes open circuit terminal voltage to remain constant as a battery discharges and its internal resistance to be zero, both of which are not the case.

Hence the specification in Ampère/hour which is based on a discharge test.

But since when normally used the battery is never discharged to empty* (as this is generally accepted to be bad for Lithium based batteries) capacity is rather obtained through a software estimation which may be not that accurate.

* State of Charge for the Mitsubishi Outlander is generally kept above 25%.

SoC or the State of Charge is the actual level of charge of an electric battery relative to its capacity in percent.

BMS or the Battery Management System (also known as BMU or Battery Management Unit) is the electronic system (hardware and software) that manages the battery pack by preventing it from working outside its safe operating specifications and ensures that it is maintained in proper condition.

BMS reports two types of SoC: the Display SoC (or SoC displayed) and the BMS SoC (or Battery Management System SoC).

It is believed that BMS SoC takes into account the existent upper buffer while Display SoC does not.

BMS SoC is displayed in the Battery Screen while Display SoC appears within the Battery icon in the Main Screen.

Upper buffer is around 5% hence the difference between both SoCs.