View Single Post
Old 12-23-2015, 12:13 PM   #9
steve99
Banned
 
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,996
Thanks: 1,035
Thanked 4,994 Times in 2,984 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
Quote:
Originally Posted by Toyarzee View Post
Hopefully this is an appropriate subsection... I bought an elm327 that other members have recommended in some other threads. However, I can't leave this one plugged in to use with torque or Harry's lap timer for longer than 5 to 10 minutes before I lose communication and the whole dash shuts down. I throw a cel, U0155, every time without fail and the car goes into limp mode and won't drive.

Since there seems to be quite the variety of Bluetooth obd2 sensors out there, and some have issues with some and not others, I'm hoping someone can point me in the direction of an obd2 Bluetooth module that doesn't instantly fail. I understand this may be a somewhat common issue and is easily fixed on the fly, but my car going into limp mode in the middle of a hot lap on race track is no bueno.

Edit: extra note, using with android, not ios

Many thanks,

Mike
That sounds like the connection to the obd socket is intermittent. You often get code U0155 Can Buss errors if obd devices plugged/unplugged while engine running

some brz/86 have suspect obd sockets. They can cause intermittent connections to obd devices. Especially those with thin pins like elm327's

Try

1. a short obd extension cable

or

2. Bend the pins on your elm327 inwards slightly, both rows. use something like a full size SD memory card or similar. you only need to bend them inwards very slightly maybe 1mm (don't know what that is in inches) alternatively measurements 1 bee's d1ck, 2 gnats pubes or a fly $hit
steve99 is offline   Reply With Quote