Tested Motorcycle Models (Work with OBD2)

[jlsch]

Hi John

BMW F800GS ADV 2013 is working well with cable adapter from BMW pins to OBD and OBDLink LX Dongle, only Oiltemp. is missing. I mention it will also work with never modelyears.

[jipppo13]

The OBD2 (OBD Link LX) sensor works with DBD2 on my Triumph Tiger 1200 2023 Model using a Samsung Galaxy Active Tab 3. I have also paired it with a Silver Fox Controller with the DMD2 Firmware.

[Kresimir Petrovic]

João Pereira wrote:

omadon wrote:

CRF300L Rally 2021 everything works except battery voltage (and the fuel indicator but this is probably not exposed over obd2). I’m using ELM327 V1.5 (Single Board PIC18F25K80). When using Torque on the same tablet it can normally read battery voltage and other sensor info. If someone can help me troubleshoot this it would be great.

There are two ways to read the Battery voltage, from ECU or from dongle, in the new DMD2 Beta in OBDView Settings there is an option called “Get Voltage from Dongle”. Can you tell me which other sensors work in Torque that do not in DMD2?

Finally found some time to troubleshoot missing voltage value using ELM327 adapter on my Honda CRF 300 Rally. I seams that for “Get voltage from the dongle” you are using STVR command which is part of the extended ST command set available only on the new Obdlink adapters. There is original ATRV command which is compatible on both Obdlink and ELM327 adapters. Is there a way that you can add both options in the OBD configuration window?

Omadon

[Kresimir Petrovic]

I created a small python scripts that will check all available PIDS  on the motorcycle. This way you can see what will be available to you in DMD2 for your motocycle. On my motorcycle (Honda CRF 300L Rally) majority is not supported. I will try some custom and extended PIDS maybe I can find gear indicator which would be a nice feature. I’m hoping that developers will fix Voltage issue and add ATRV command for the ELM327 dongle owners.

You can download the script at: https://github.com/omadon/Moto_OBD2_Discovery

Below is the example from my bike:

 

C:\OBD2>python OBD_supported_features.py
Available serial ports:
1. \.\COM3
2. \.\COM4
3. \.\COM5

Enter desired serial: 2

———– Honda ———– CRF 300L Rally EU ———– VIN: MLHND16A6M50XXXXX ———-

Mode PID Active Description Value
—— —– ——– ———————————- —————————————-
00 ATI Yes ELM327 version string OBDII v1.5
00 ATRV Yes Voltage detected by OBD-II adapter 14.6 volt
01 00 Yes Supported PIDs [01-20] 01111100001111101100000000010001
01 20 Yes Supported PIDs [21-40] 10000000000000000000000000000001
01 40 Yes Supported PIDs [41-60] 10000000000000000000000000000000
09 00 Yes Supported PIDs [01-20] 0101010101000000000000000000000000000000
09 02 Yes Vehicle Identification Number bytearray(b’MLHND16A6M50XXXXX’)
03 Yes Get DTCs []

Mode PID Active Description Value
—— —– ——– ————————————— ——————————————————–
01 00 Yes Supported PIDs [01-20] 01111100001111101100000000010001
01 01 No Status since DTCs cleared not supported
01 02 Yes DTC that triggered the freeze frame (‘P0000’, ”)
01 03 Yes Fuel System Status (‘Open loop due to insufficient engine temperature’, ”)
01 04 Yes Calculated Engine Load 26.274509803921568 percent
01 05 Yes Engine Coolant Temperature 24 degree_Celsius
01 06 Yes Short Term Fuel Trim – Bank 1 0.0 percent
01 07 No Long Term Fuel Trim – Bank 1 not supported
01 08 No Short Term Fuel Trim – Bank 2 not supported
01 09 No Long Term Fuel Trim – Bank 2 not supported
01 0A No Fuel Pressure not supported
01 0B Yes Intake Manifold Pressure 47 kilopascal
01 0C Yes Engine RPM 2106.0 revolutions_per_minute
01 0D Yes Vehicle Speed 0.0 kilometer_per_hour
01 0E Yes Timing Advance 23.5 degree
01 0F Yes Intake Air Temp 22 degree_Celsius
01 10 No Air Flow Rate (MAF) not supported
01 11 Yes Throttle Position 10.196078431372548 percent
01 12 Yes Secondary Air Status Upstream
01 13 No O2 Sensors Present not supported
01 14 No O2: Bank 1 – Sensor 1 Voltage not supported
01 15 No O2: Bank 1 – Sensor 2 Voltage not supported
01 16 No O2: Bank 1 – Sensor 3 Voltage not supported
01 17 No O2: Bank 1 – Sensor 4 Voltage not supported
01 18 No O2: Bank 2 – Sensor 1 Voltage not supported
01 19 No O2: Bank 2 – Sensor 2 Voltage not supported
01 1A No O2: Bank 2 – Sensor 3 Voltage not supported
01 1B No O2: Bank 2 – Sensor 4 Voltage not supported
01 1C Yes OBD Standards Compliance not supported
01 1D No O2 Sensors Present (alternate) not supported
01 1E No Auxiliary input status (power take off) not supported
01 1F No Engine Run Time not supported
01 20 Yes Supported PIDs [21-40] 10000000000000000000000000000001
01 21 Yes Distance Traveled with MIL on 0.0 kilometer
01 22 No Fuel Rail Pressure (relative to vacuum) not supported
01 23 No Fuel Rail Pressure (direct inject) not supported
01 24 No 02 Sensor 1 WR Lambda Voltage not supported
01 25 No 02 Sensor 2 WR Lambda Voltage not supported
01 26 No 02 Sensor 3 WR Lambda Voltage not supported
01 27 No 02 Sensor 4 WR Lambda Voltage not supported
01 28 No 02 Sensor 5 WR Lambda Voltage not supported
01 29 No 02 Sensor 6 WR Lambda Voltage not supported
01 2A No 02 Sensor 7 WR Lambda Voltage not supported
01 2B No 02 Sensor 8 WR Lambda Voltage not supported
01 2C No Commanded EGR not supported
01 2D No EGR Error not supported
01 2E No Commanded Evaporative Purge not supported
01 2F No Fuel Level Input not supported
01 30 No Number of warm-ups since codes cleared not supported
01 31 No Distance traveled since codes cleared not supported
01 32 No Evaporative system vapor pressure not supported
01 33 No Barometric Pressure not supported
01 34 No 02 Sensor 1 WR Lambda Current not supported
01 35 No 02 Sensor 2 WR Lambda Current not supported
01 36 No 02 Sensor 3 WR Lambda Current not supported
01 37 No 02 Sensor 4 WR Lambda Current not supported
01 38 No 02 Sensor 5 WR Lambda Current not supported
01 39 No 02 Sensor 6 WR Lambda Current not supported
01 3A No 02 Sensor 7 WR Lambda Current not supported
01 3B No 02 Sensor 8 WR Lambda Current not supported
01 3C No Catalyst Temperature: Bank 1 – Sensor 1 not supported
01 3D No Catalyst Temperature: Bank 2 – Sensor 1 not supported
01 3E No Catalyst Temperature: Bank 1 – Sensor 2 not supported
01 3F No Catalyst Temperature: Bank 2 – Sensor 2 not supported
01 40 Yes Supported PIDs [41-60] 10000000000000000000000000000000
01 41 Yes Monitor status this drive cycle False, 0, spark
01 42 No Control module voltage not supported
01 43 No Absolute load value not supported
01 44 No Commanded equivalence ratio not supported
01 45 No Relative throttle position not supported
01 46 No Ambient air temperature not supported
01 47 No Absolute throttle position B not supported
01 48 No Absolute throttle position C not supported
01 49 No Accelerator pedal position D not supported
01 4A No Accelerator pedal position E not supported
01 4B No Accelerator pedal position F not supported
01 4C No Commanded throttle actuator not supported
01 4D No Time run with MIL on not supported
01 4E No Time since trouble codes cleared not supported
01 4F No Various Max values not supported
01 50 No Maximum value for mass air flow sensor not supported
01 51 No Fuel Type not supported
01 52 No Ethanol Fuel Percent not supported
01 53 No Absolute Evap system Vapor Pressure not supported
01 54 No Evap system vapor pressure not supported
01 55 No Short term secondary O2 trim – Bank 1 not supported
01 56 No Long term secondary O2 trim – Bank 1 not supported
01 57 No Short term secondary O2 trim – Bank 2 not supported
01 58 No Long term secondary O2 trim – Bank 2 not supported
01 59 No Fuel rail pressure (absolute) not supported
01 5A No Relative accelerator pedal position not supported
01 5B No Hybrid battery pack remaining life not supported
01 5C No Engine oil temperature not supported
01 5D No Fuel injection timing not supported
01 5E No Engine fuel rate not supported
01 5F No Designed emission requirements not supported

Mode PID Active Description Value
—— —– ——– ————————————— —————————————-
09 00 Yes Supported PIDs [01-20] 0101010101000000000000000000000000000000
09 01 No VIN Message Count not supported
09 02 Yes Vehicle Identification Number bytearray(b’MLHND16A6M50XXXXX’)
09 03 No Calibration ID message count for PID 04 not supported
09 04 Yes Calibration ID bytearray(b’407′)
09 05 No CVN Message Count for PID 06 not supported
09 06 Yes Calibration Verification Numbers

 

 

• This reply was modified 1 year, 1 month ago by Kresimir Petrovic.

Omadon

[rmirage]

vlinker FS tested on a Yamaha tracer 9GT 2022 with DMD2 everything works 100% except the fuel level may be a limitation of the ecu

[jcesilva]

Olá a todos, testei na minha Honda XRE 300 ano 2011, e não tive sucesso com a versão 2.74 DMD2 usando ELM 327 nem mesmo com outros softwares. Não sei o que acontece, conforme manual técnico da motocicleta usa o protocolo K-LINE (ISO 9141 -2 / ISO 14230-4) Conector (Diagnóstico) DLC 4 pinos, uma pena.

Hello everyone, I tested it on my 2011 Honda XRE 300, and I had no success with version 2.74 DMD2 using ELM 327 or even with other software. I don’t know what happens, according to the motorcycle’s technical manual it uses the K-LINE protocol (ISO 9141 -2 / ISO 14230-4) Connector (Diagnostics) DLC 4 pins, a shame.

 

• This reply was modified 11 months, 2 weeks ago by jcesilva.

[geoffmurray5955]

R1250GS with T665 and UniCarScan UCSI-2100 OBDII adaptor (recommended for Motoscan) gives readings for Coolant temperature, Intake temperature, Voltage, RPM, Throttle position and Spark Advance 🙂

• This reply was modified 11 months ago by geoffmurray5955.

[hansolo1975]

Works with OBD Link LX on BMW F800GS 2008

BMW F80000GS Model 2008
Living in the south of Germany near Lake of Constance

[olarf]

Just tested my Super Tenere XT1200z DP07 and it works fine. The Yamaha 4 to 16 Pin cables don’t fit in the 4pin Plug under the Seat but it fits to the free 4pin port under the right sidecover. Fuel Level don’t work but I think it is just no odb2 data.

Dmd2 offer a calculatef way fit that as well, so Im fine with that.

I use the vLinker MC+ to connect, fits perfect under the side cover.

• This reply was modified 6 months, 2 weeks ago by olarf.

[navnerd]

I have tested a BMW R1200 GS ADV model year 2007 (so the old air/oil cooled model). The used OBD2-dongle is OBDLink LX (the green one). The  following data is provided over the BMW’s OBD2 interface of that model year (I have tested that with their own software called “OBDlink”- note other BMW models or model years may not provide any data via the OBD2 interface!):

Vehicle speed, engine speed (RPM), coolant (=oil) temperature, intake air temperature, throttle position, ignition timing advance, battery voltage (just read out from the OBD dongle!). No fuel level is provided by the BMW OBD2 interface, even though the motorcycle’s cockpit itself provides this value.

In DMD2, I have configured and tested the OBD dashboard with the following quantities:

motorcycle speed, coolant temperature, intake air temperature, engine RPM, voltage or throttle position (both works), and fuel level – but this just with the DMD2 functionality of entering an estimated average range and counting that down by the GPS milage you drive. Note the motorcycle’s OBD2 interface does not support a direct read out from the fuel sensor in the fuel tank.

When connecting the OBD dongle via bluetooth to DMD2 at the start of te trip, all works fine and stable. The problem comes if you stop the engine by switching off the ignition. Then, the communication between DMD2 (3.00032, but similar in much older versions, e.g. 2.xy) and the dongle breaks down and cannot be reliably reestablished after restarting the engine. The only thing that helps is pulling the dongle off the plug and reconnect it :-(. I’ll file a bug report for this, since this problem only appears in combination with the OBDlink LX dongle connected to DMD2. If connected with the native OBDlink Android App, the connection is immediately reestablished when the ignition is on and the engine starts again.

• This reply was modified 9 months ago by navnerd.
• This reply was modified 9 months ago by navnerd.

[Author]

Posts