Subaru Crosstrek and XV Forums banner

Cautionary Obervation: OBDLink LX Bluetooth and Torque App

5 reading
13K views 10 replies 8 participants last post by  kr_xv  
#1 ·
Last week I got the OBDLink LX Bluetooth and the Torque Android app for my Samsung Tab 4 7.

Today, as the snow was coming down in the DC area I plugged it in, paired it with the tablet, and started running Torque. Whenever I parked whilst running errands I checked the readings, worked on the display, and generally got familiar with the setup. (Sitting in the parking lots, hunched over the tablet, and fogging up the windows didn't seem to attract any unwarranted attention...)

One of the first thing that happened was the Skoda Light (Czech Engine) (Sorry) :blink: turning on as well as the Hill Assist Warning Light. I cleared it a couple of time, but it came back. Later, the VDC warning lights came on, and after that, the AT Oil Temp warning light.

This is a 2015 CVT with less than 1500 miles. Air temperature was well below freezing.

Not much I could do other than head home. Once there I checked around online and found discussions indicating that the Torque app may have something to do with the codes appearing -- though there is a lot to sort through on the different forums. Even though it was quite cold, temps were inching up towards freezing and the roads were getting sloppy. But there were a couple of times I wasn't sure the XV was acting as solid as I might expect (11 years driving a 6 cyl, pre-VDC Outback before this).

I pulled the OBDLink LX Bluetooth, plugged in a ScanGaugeII, confirmed one code, cleared it, and after a quick drive around my cul-de-sac there were no more lights.

The first code (and most persistent) was U0073. The second (which preceded the VDC warning) was U0122.

First question: Is there more than a tangential relationship between the codes and the warning lights?

Second question: Were Hill Assist and VDC really not working (properly)?

Third question: Was the AT Oil Temp really high?
 
#8 ·
I picked up the OBDLink LX a month back to clear a code on my wife's Acura. I started off trying to connect with Torque and wasn't able to fully access the ECU to see or clear the code. So I switch to using the app from OBDLink instead and was able to do what I need.

I've since use the setup on the XV without issue. Used it on short drives in town as well as a thousand road trip. Links up easy and reads everything. The OBDLink app looks to have everything Torque does and certainly as much as I can ever use. Point is, if the issue is less with the hardware and more with the app (which I suspect) then should be an easy problem to solve. Doesn't make sense that firmware on the module should be invoking fault codes like you're seeing. Seems more of a software issue.