Volvo Owners Club Forum - View Single Post

Semnoz · Jul 5th, 2017, 22:15

.

Thanks - I'd not thought of that at this stage as I assumed more specialist ECU reading equipment was necessary (e.g. VIDA).

However, I do have a similar ODBC bluetooth connector that I've used on my Focus (although the Focus ECU didn't like Torque and only seemed to give full info with FORScan).

I've just tried this on the V70 and it really struggled to connect with the ECU. The Torque app constantly cycles through different connection protocols, so it could be that my ODBC connector isn't fully compatible with the D5. It did connect once, and I did a scan of error codes and it said none were stored in the ECU (possible I guess). I tried cranking the engine, but it seemed to get stuck turning over (still not firing) and bizarrely didn't stop trying until, I think, the ECU rebooted (which I think happens if the battery voltage suddenly gets really low). Torque did at least record some info, such as battery voltage getting to about 12.2V, but fuel rail pressure didn't go up, although as per your video, that might be expected if other parts of the engine don't get moving quick enough. I've put the ODBC to one side for now.

My main voltmeter is also saying 12.2V. When I cranked the engine it dropped right down to about 6V for a split second, and gradually back up to about 11.7V after a couple of seconds, and then it hovered around 12.15V. The battery is old, but I can't tell how old. I've got the CTEK MX5 doing a deep charge at the moment, but maybe the battery is getting a bit tired, despite voltage resting at 12.2V.....

thanks again

Jul 5th, 2017, 22:15	#6
Semnoz Senior Member Last Online: Nov 12th, 2023 19:03 Join Date: Jan 2011 Location: NW	. Thanks - I'd not thought of that at this stage as I assumed more specialist ECU reading equipment was necessary (e.g. VIDA). However, I do have a similar ODBC bluetooth connector that I've used on my Focus (although the Focus ECU didn't like Torque and only seemed to give full info with FORScan). I've just tried this on the V70 and it really struggled to connect with the ECU. The Torque app constantly cycles through different connection protocols, so it could be that my ODBC connector isn't fully compatible with the D5. It did connect once, and I did a scan of error codes and it said none were stored in the ECU (possible I guess). I tried cranking the engine, but it seemed to get stuck turning over (still not firing) and bizarrely didn't stop trying until, I think, the ECU rebooted (which I think happens if the battery voltage suddenly gets really low). Torque did at least record some info, such as battery voltage getting to about 12.2V, but fuel rail pressure didn't go up, although as per your video, that might be expected if other parts of the engine don't get moving quick enough. I've put the ODBC to one side for now. My main voltmeter is also saying 12.2V. When I cranked the engine it dropped right down to about 6V for a split second, and gradually back up to about 11.7V after a couple of seconds, and then it hovered around 12.15V. The battery is old, but I can't tell how old. I've got the CTEK MX5 doing a deep charge at the moment, but maybe the battery is getting a bit tired, despite voltage resting at 12.2V..... thanks again __________________ V70 D5 185 SE Lux P3 (with rear integrated booster seats, which the kids love !!) Last edited by CTCNetwork; Jul 6th, 2017 at 20:13. Reason: Quote removed.