Problems with OBDLink MX BT

Discussion related to external OBD and other sensors
Post Reply
OliverG
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 8
Joined: Fri Mar 13, 2015 3:17 pm

Problems with OBDLink MX BT

Post by OliverG »

Hi.
Running Laptimer on Samsung Galaxy Note 4 in a Renault Megane III RS 265. I had noname OBD sensor ELM327 experiencing the problem that the OBD Speed stayed red. I then ordered the recommended OBDLink MX BT but still having the same troubles.
On Torque and the OBDLink app everything works fine. I can actually see the difference when running those programs the leds of the sensor blink at a very fast rate.
When I try it in Laptimer the blink rate is very slow.
Idea anyone ?

thx

Oliver
User avatar
Harry
Site Admin
Site Admin
Posts: 10520
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Problems with OBDLink MX BT

Post by Harry »

Please make sure you do not run two apps accessing the OBDLink in parallel. While LapTimer disconnects when sent to background, other probably do not.

Harry
Image Image Image Image
OliverG
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 8
Joined: Fri Mar 13, 2015 3:17 pm

Re: Problems with OBDLink MX BT

Post by OliverG »

This is not the case here. I actually rebooted my phone twice so there was no other app using it
User avatar
Harry
Site Admin
Site Admin
Posts: 10520
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Problems with OBDLink MX BT

Post by Harry »

You may create a log on the communication between adapter and LapTimer. For me, it sounds like a connection issue - but we will see... Please check viewtopic.php?f=20&t=1500 for a how-to.

- Harry
Image Image Image Image
User avatar
Harry
Site Admin
Site Admin
Posts: 10520
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Problems with OBDLink MX BT

Post by Harry »

Thanks for sending the log. The thread should probably be renamed to "Problems with Renault Megane III RS 265" (not kidding, may help others):

During initialization, LapTimer asks for PID 0106 (Short term fuel % trim) once. According to the OBD docs, it should be answered with a single byte. Instead, the reply is coming in with 2 bytes (41067E56 should be 41067E):

Code: Select all

09006610580          ---------  mode: 1 pid: 0x06 [STFT1] (index: 23)
09006610580          Tx: "30 31 30 36 0D '0106\r'"
09006610640 +   60ms Rx: "34 31 30 36 37 45 35 36 0D '41067E56\r'" (9)
09006611680 + 1040ms Rx: "0D 3E '\r>'" (2)
LapTimer considers this a communication error and resets communication.

To work around the Megane's OBD implementation, please exclude 0106 from the PIDs requested. To do this, enter the four digits into the exclude pid field in LapTimer's Expert settings.

- Harry
Image Image Image Image
OliverG
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 8
Joined: Fri Mar 13, 2015 3:17 pm

Re: Problems with OBDLink MX BT

Post by OliverG »

Just tested it and it's working now. Made my first timed run in the 30 kmh Limit neighborhood track i set up. Gas RPM and gear were displayer correctly.
stupid french!! They never can follow any standards......
I bet
OliverG
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 8
Joined: Fri Mar 13, 2015 3:17 pm

Re: Problems with OBDLink MX BT

Post by OliverG »

I bet my old adapter works as well now but I will keep the new one as it should be much faster.
Post Reply