UPdate.
http://bit.ly/1w1cj2f picture of the ecu s.
my answers to your paragraph 10 in a row, pasted from Elm327 OBD Terminal android app to your interpreter and then pasted here.
> ATI
ELM327 v1.5
>> ATZ
ELM327 v1.5
>> ATL1
ATL1
OK
>> ATE1
ATE1
OK
>> ATI
ATI
ELM327 v1.5
>> ATPPS
ATPPS
00:FF F 01:FF F 02:FF F 03:32 F
04:01 F 05:FF F 06:F1 F 07:09 F
08:FF F 09:00 F 0A:0A F 0B:FF F
0C:68 F 0D:0D F 0E:9A F 0F:FF F
10:0D F 11:00 F 12:FF F 13:32 F
14:FF F 15:0A F 16:FF F 17:92 F
18:00 F 19:28 F 1A:FF F 1B:FF F
1C:FF F 1D:FF F 1E:FF F 1F:FF F
20:FF F 21:FF F 22:FF F 23:FF F
24:00 F 25:00 F 26:00 F 27:FF F
28:FF F 29:FF F 2A:38 F 2B:02 F
2C:E0 F 2D:04 F 2E:80 F 2F:0A F
>> ATRV
ATRV
13.3V
>
---------------------------------------------------------------------------------------------
> ATZ
ATZ
ELM327 v1.5
>> ATL1
ATL1
OK
>> ATE 1
ATE 1
OK
>> ATDP
ATDP
ISO 9141-2
>> ATSP 3
ATSP 3
OK
>> ATDP
ATDP
ISO 9141-2
>> 0100
0100
BUS INIT: BUS ERROR
>> 0101
0101
BUS INIT: BUS ERROR
>> 03
03
BUS INIT: BUS ERROR
>> 07
07
BUS INIT: BUS ERROR
>> ATH1
ATH1
OK
>> 0100
0100
BUS INIT: BUS ERROR
>> 0101
0101
BUS INIT: BUS ERROR
>> 0105
0105
BUS INIT: BUS ERROR
>> 010C
010C
BUS INIT: BUS ERROR
>> 03
03
BUS INIT: BUS ERROR
>> 07
07
BUS INIT: BUS ERROR
>> ATRV
ATRV
13.0V
>
-------------------------------------------------------------------------------------------
> ATZ
ATZ
ELM327 v1.5
>> ATL1
ATL1
OK
>> ATE1
ATE1
OK
>> ATSP 3
ATSP 3
OK
>> ATH1
ATH1
OK
>> ATAL
ATAL
OK
>> ATKW0
ATKW0
OK
>> ATTA 13
ATTA 13
OK
>> ATAT 0
ATAT 0
OK
>> ATTIA 51
ATTIA 51
?
>> ATIIA 51
ATIIA 51
OK
>> ATWM 82 51 13 A1
ATWM 82 51 13 A1
OK
>> ATSH 83 51 13
ATSH 83 51 13
OK
>> B903
B903
BUS INIT: BUS ERROR
>> B9F0
B9F0
BUS INIT: BUS ERROR
>> AE01
AE01
BUS INIT: BUS ERROR
>> ATSH 84 52 13
ATSH 84 52 13
OK
>> ATSH 84 51 13
ATSH 84 51 13
OK
>> A50701
A50701
BUS INIT: BUS ERROR
>> ATPC
ATPC
OK
>> ATIIA 58
ATIIA 58
OK
>> ATIIA 7A
ATIIA 7A
OK
>> ATWM 82 7A 13 A1
ATWM 82 7A 13 A1
OK
>> ATSH 83 7A 13
ATSH 83 7A 13
OK
>> B9F0
B9F0
BUS INIT: BUS ERROR
>> AE01
AE01
BUS INIT: BUS ERROR
>> ATPC
ATPC
OK
>> ATIIA 58
ATIIA 58
OK
>> ATWM 82 01 13 A1
ATWM 82 01 13 A1
OK
>> ATSH 82 01 13
ATSH 82 01 13
OK
>> B9F0
B9F0
BUS INIT: BUS ERROR
>> AE01
AE01
BUS INIT: BUS ERROR
>> ATRV
ATRV
13.0V
>
------------------------------------------------------------------------------
I did it on my phone, so I can try again having my laptop along to plug in the commands straight away.
many bus init errors though. any explanation to those?
1997 850 Bluetooth obd2 doesnt connect to the ECU
By the way, after all it was the first time I figured out how to send commands to the obd2. Do you think that without it connecting properly again, is it possible that the B90300 command would turn any results?
The results are fresh, meaning I went to the car after 10pm, due to severe weather, freezing rain and snow all day, and heavy schedule. I will try again tomorrow to see if I can get the mileage, which would be great.
The results are fresh, meaning I went to the car after 10pm, due to severe weather, freezing rain and snow all day, and heavy schedule. I will try again tomorrow to see if I can get the mileage, which would be great.
-
esl_97_850_T5
- Posts: 271
- Joined: 19 June 2012
- Year and Model: 1998 S70 GLT
- Location: Knoxville, TN
- Has thanked: 18 times
- Been thanked: 27 times
tzanis,
1. I suggest you avoid testing with B90300, and, in general, totally stay away from the 00-padded KWPD3B0 requests that only work with the 850. Those were discovered in my initial ignorant fumbling around with KWPD3B0 and were the only way that I initially discovered to get responses from certain ECUs displayed immediately. A year later, I finally discovered that ATRA 13 (in conjunction with all the other ELM327 commands to establish KWPD3B0 setup) unlocks the capability of immediately seeing the responses.
It's much better to learn the same request that works for both the '96-'97 850 and the '98 S70/V70/XC70. Both ATSH 83 51 13 / B903 and ATSH 84 51 13 / B90300 are equally reliable for the 850, but only the first one works with the '98 S70/V70/XC70. So make it easy on yourself and stick with the more generally useful B903 case.
2. Concerning the picture, I get a Dropbox - 403 error (and I don't plan on establishing a Dropbox account, so I can view others' photos). Since you have the pictures, you can do some online research with the provided numbers and determine if you have a Motronic 4.3 or Motronic 4.4. That's all that I was trying to determine.
3. In the future, when you issue the commands with whatever terminal emulator you used, issue ATE0 instead of ATE1, in order to eliminate the duplicate ">" prompt and the duplicate ELM327 commands being displayed.
4. By the way, what terminal emulator did you use?
5. From ATRV response of 13.3V and knowing that you have a ELM327 clone (the ELM327 v1.5 listed by ATI and ATZ implies a clone) and knowing that my ELM327 v1.5 USB shows similar voltage while the engine is running, I'm assuming your engine was running during that test.
So another obvious thing you can do is perform the test again, but with ignition at pos II. I would then expect the only difference would be that the ATRV responses show voltages roughly 1.0-1.5 volt lower than the engine on responses.
6. The ATPPS values are exactly the same as those that MVS user gmh used https://www.matthewsvolvosite.com/forums ... 76#p318074 with his ELM327 Bluetooth clone, and which (almost) all other users of ELM327 v1.5 clones of some sort (most likely Bluetooth) have submitted to kwpd3b0_interpreter in the past year or so. So I don't think your ATPP values are inhibiting any connection.
7. If you get "BUS INIT: ...ERROR", then I'd say:
- you don't have ELM327 USB cable plugged in to car's OBDII port, but do have it plugged in to USB port, *OR*
- you don't have either ignition at pos II or engine running.
But that's not what you had. Your error was "BUS INIT: BUS ERROR". The ELM327 data sheet says BUS ERROR is a generic problem meaning basically an invalid signal has been detected on the bus, and is usually due to a wiring error. In my 200+ logs of over 2.7 years, I've only had that happen 7 times (that I've kept records of). Delving into those logs, I discovered "BUS INIT: BUS ERROR" was caused by a) having fuse 15 removed, or b) not having my ELM327 USB cable plugged into the car's OBDII port.
Case a) does not apply to you. Since in your case, you have previously verified your fuse 15 controls the OBD port and that your fuse 15 is good, we can rule out that case a) for you. In fact, just because your ELM327 sees 13.3V from ATRV, we can rule out case a) for you, since the ELM327 will be reading that voltage from the OBDII pin 16. That 13.3V is far different than the 0.0V that I would expect to see from a blown or missing fuse 15.
Case b) obviously does not apply to you, since your ELM327 receives its power from the OBDII pin 16, the ELM327 has a very substantial, engine-is-running voltage of 13.3V, so I just presume that you have it plugged in to the car's OBDII port.
8. It seems you are forging your own new territory in this case.
If I were you, I would keep in mind the words "invalid bus signal" and "wiring error". You have not yet ruled out that the problem is the ISO 9141-2 transmitter and/or receiver of the Bluetooth ELM327, since you haven't seen proper signals being sent/received. You also have not yet ruled out that the problem is the car's wiring.
9. You could do the tests also from the laptop, but I'm not sure you would get any different results.
10. Seems to me you should still suspect the ISO 9141-2 transmitter/receiver circuitry or logic of the Bluetooth ELM327, thru the car's OBDII port, at least thru the first leg of the wiring from the OBDII pin 7 to each of the ECUs seen in:
1997 850 Wiring Diagrams
and thru the wiring from the OBDII pin 5 (or pin 4 depending on if your Bluetooth ELM327 uses pin 4 for its grounding) to the grounding point.
Since absolutely *none* of the ECUs connected, I'm inclined to think there's some common point of failure. I wouldn't worry about the legs of the wiring diagram from 24/421 out to the respective ECUs. I have a hard time believing ALL of them are bad. It seems that:
- a) the problem is from 24/421 back to somewhere in the ELM327 internals, or
- b) the problem is from the grounding point back through pin 5 or pin 4, depending on the tool, continuing up to pin 5 or pin 4 in the ELM327.
What do you think? Make sense?
11. There's other things I could suggest, but they require more OBDII equipment on your part, so I'm inclined to let you do your own debugging for the time being. In the meantime...
I've already bought 2 different Bluetooth ELM327 devices and a Bluetooth USB dongle for the laptop. In the coming weeks, I'll test them, document the testing with pictures and/or videos, and post the results online. Then I might be able to give you some better pointers, if you haven't already solved your car's particular connectivity problem.
esl_97_850_T5
1. I suggest you avoid testing with B90300, and, in general, totally stay away from the 00-padded KWPD3B0 requests that only work with the 850. Those were discovered in my initial ignorant fumbling around with KWPD3B0 and were the only way that I initially discovered to get responses from certain ECUs displayed immediately. A year later, I finally discovered that ATRA 13 (in conjunction with all the other ELM327 commands to establish KWPD3B0 setup) unlocks the capability of immediately seeing the responses.
It's much better to learn the same request that works for both the '96-'97 850 and the '98 S70/V70/XC70. Both ATSH 83 51 13 / B903 and ATSH 84 51 13 / B90300 are equally reliable for the 850, but only the first one works with the '98 S70/V70/XC70. So make it easy on yourself and stick with the more generally useful B903 case.
2. Concerning the picture, I get a Dropbox - 403 error (and I don't plan on establishing a Dropbox account, so I can view others' photos). Since you have the pictures, you can do some online research with the provided numbers and determine if you have a Motronic 4.3 or Motronic 4.4. That's all that I was trying to determine.
3. In the future, when you issue the commands with whatever terminal emulator you used, issue ATE0 instead of ATE1, in order to eliminate the duplicate ">" prompt and the duplicate ELM327 commands being displayed.
4. By the way, what terminal emulator did you use?
5. From ATRV response of 13.3V and knowing that you have a ELM327 clone (the ELM327 v1.5 listed by ATI and ATZ implies a clone) and knowing that my ELM327 v1.5 USB shows similar voltage while the engine is running, I'm assuming your engine was running during that test.
So another obvious thing you can do is perform the test again, but with ignition at pos II. I would then expect the only difference would be that the ATRV responses show voltages roughly 1.0-1.5 volt lower than the engine on responses.
6. The ATPPS values are exactly the same as those that MVS user gmh used https://www.matthewsvolvosite.com/forums ... 76#p318074 with his ELM327 Bluetooth clone, and which (almost) all other users of ELM327 v1.5 clones of some sort (most likely Bluetooth) have submitted to kwpd3b0_interpreter in the past year or so. So I don't think your ATPP values are inhibiting any connection.
7. If you get "BUS INIT: ...ERROR", then I'd say:
- you don't have ELM327 USB cable plugged in to car's OBDII port, but do have it plugged in to USB port, *OR*
- you don't have either ignition at pos II or engine running.
But that's not what you had. Your error was "BUS INIT: BUS ERROR". The ELM327 data sheet says BUS ERROR is a generic problem meaning basically an invalid signal has been detected on the bus, and is usually due to a wiring error. In my 200+ logs of over 2.7 years, I've only had that happen 7 times (that I've kept records of). Delving into those logs, I discovered "BUS INIT: BUS ERROR" was caused by a) having fuse 15 removed, or b) not having my ELM327 USB cable plugged into the car's OBDII port.
Case a) does not apply to you. Since in your case, you have previously verified your fuse 15 controls the OBD port and that your fuse 15 is good, we can rule out that case a) for you. In fact, just because your ELM327 sees 13.3V from ATRV, we can rule out case a) for you, since the ELM327 will be reading that voltage from the OBDII pin 16. That 13.3V is far different than the 0.0V that I would expect to see from a blown or missing fuse 15.
Case b) obviously does not apply to you, since your ELM327 receives its power from the OBDII pin 16, the ELM327 has a very substantial, engine-is-running voltage of 13.3V, so I just presume that you have it plugged in to the car's OBDII port.
8. It seems you are forging your own new territory in this case.
If I were you, I would keep in mind the words "invalid bus signal" and "wiring error". You have not yet ruled out that the problem is the ISO 9141-2 transmitter and/or receiver of the Bluetooth ELM327, since you haven't seen proper signals being sent/received. You also have not yet ruled out that the problem is the car's wiring.
9. You could do the tests also from the laptop, but I'm not sure you would get any different results.
10. Seems to me you should still suspect the ISO 9141-2 transmitter/receiver circuitry or logic of the Bluetooth ELM327, thru the car's OBDII port, at least thru the first leg of the wiring from the OBDII pin 7 to each of the ECUs seen in:
1997 850 Wiring Diagrams
and thru the wiring from the OBDII pin 5 (or pin 4 depending on if your Bluetooth ELM327 uses pin 4 for its grounding) to the grounding point.
Since absolutely *none* of the ECUs connected, I'm inclined to think there's some common point of failure. I wouldn't worry about the legs of the wiring diagram from 24/421 out to the respective ECUs. I have a hard time believing ALL of them are bad. It seems that:
- a) the problem is from 24/421 back to somewhere in the ELM327 internals, or
- b) the problem is from the grounding point back through pin 5 or pin 4, depending on the tool, continuing up to pin 5 or pin 4 in the ELM327.
What do you think? Make sense?
11. There's other things I could suggest, but they require more OBDII equipment on your part, so I'm inclined to let you do your own debugging for the time being. In the meantime...
I've already bought 2 different Bluetooth ELM327 devices and a Bluetooth USB dongle for the laptop. In the coming weeks, I'll test them, document the testing with pictures and/or videos, and post the results online. Then I might be able to give you some better pointers, if you haven't already solved your car's particular connectivity problem.
esl_97_850_T5
1998 Volvo S70 GLT - 205.5K miles - S70 & M44 testbed in 2016-2019; traded 2019-07-15 (for spare time)
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
Thanks for the detailed answers.
1) I was looking in your website and I figured out what you mean about ATRA.
2) http://puu.sh/gmXAb.jpg This link works for sure. (261 203 936 1996-98 Volvo 850 / 70 series GLT (LPT) Usually marked G4.2 in lg letters to right of barcodes) so Motronic 4.4
3) I will.
4) The link to the app -> https://play.google.com/store/apps/deta ... inal&hl=en
5) engine was running because I did not want to be found in the form of ice cream the next day
I am joking, I will try again.
So, your suggestions are
- there is a fault at the clone's tranceiver internal wiring on the Iso part? ( I am not sure if this is what you meant) If that, torque gets connected to my dad's 99 corolla and my friend 02 s40 in seconds.
- or pin 4 or 5 on my car not having proper ground.
I will look it up in the next days, and work more on learning the how to.
I came up with far shot thought, which I will test, and if positive I will reveal it.
thanks again esl.
1) I was looking in your website and I figured out what you mean about ATRA.
2) http://puu.sh/gmXAb.jpg This link works for sure. (261 203 936 1996-98 Volvo 850 / 70 series GLT (LPT) Usually marked G4.2 in lg letters to right of barcodes) so Motronic 4.4
3) I will.
4) The link to the app -> https://play.google.com/store/apps/deta ... inal&hl=en
5) engine was running because I did not want to be found in the form of ice cream the next day
I am joking, I will try again. So, your suggestions are
- there is a fault at the clone's tranceiver internal wiring on the Iso part? ( I am not sure if this is what you meant) If that, torque gets connected to my dad's 99 corolla and my friend 02 s40 in seconds.
- or pin 4 or 5 on my car not having proper ground.
I will look it up in the next days, and work more on learning the how to.
I came up with far shot thought, which I will test, and if positive I will reveal it.
thanks again esl.
-
esl_97_850_T5
- Posts: 271
- Joined: 19 June 2012
- Year and Model: 1998 S70 GLT
- Location: Knoxville, TN
- Has thanked: 18 times
- Been thanked: 27 times
tzanis,
1. I can see the picture now. I'll assume you have accurately determined you have a Motronic 4.4.
Now we know that you do not need a flashing LED for use on OBDII port's pin 3 (since it's for Motronic 4.3, Fenix 5.2, etc). Instead, you'll eventually be able to communicate with the Motronic 4.4 via: a) the standard OBDII emission diagnostic protocol using functional address 33, and b) the Volvo special KWPD3B0 protocol using physical address 7A -- both of which will be using the OBDII port's pin 7.
But you could use a flashing LED tool for pin 6 (ECC) and pin 13 (Cruise Control), if you needed/wanted to.
2. Nice to hear about yet another ELM327 terminal emulator for Android. Do you like it so far? Have you tried any others?
3. Does your dad's 99 corolla and friend's 02 s40 use ISO 9141-2? My understanding is that ELM327 devices have different hardware components to speak the different protocols.
I'm wondering if your ELM327 can speak anymore to any vehicle with ISO 9141-2?
4. You got some points, but let's restate them, adding some new ideas. I think the problem might be one of these (where the first two are the most likely):
a) tool is not seated in car's OBDII socket firmly, or
b) recessed male pin(s) or female pin receptable(s) such that contact is not being made for pin 7 (and maybe the pin 5 or pin 4 grounding pin, whichever ground pin applies to your ELM327), or
c) possible open or short between 24/421 distribution point back to where car's OBDII port connects with ELM327, or
d) pin 4 or 5 on your car not having proper ground, or
e) some problem in ELM327 internals -- maybe its ISO 9141-2 oriented transceiver, or maybe something else internal to ELM327, or
f) something awry with Bluetooth profile that's then inhibiting sending/receiving via software, or
g) Low Power circuitry inadvertently causing ELM327 to fail to connect.
May insight surround you.
esl_97_850_T5
1. I can see the picture now. I'll assume you have accurately determined you have a Motronic 4.4.
Now we know that you do not need a flashing LED for use on OBDII port's pin 3 (since it's for Motronic 4.3, Fenix 5.2, etc). Instead, you'll eventually be able to communicate with the Motronic 4.4 via: a) the standard OBDII emission diagnostic protocol using functional address 33, and b) the Volvo special KWPD3B0 protocol using physical address 7A -- both of which will be using the OBDII port's pin 7.
But you could use a flashing LED tool for pin 6 (ECC) and pin 13 (Cruise Control), if you needed/wanted to.
2. Nice to hear about yet another ELM327 terminal emulator for Android. Do you like it so far? Have you tried any others?
3. Does your dad's 99 corolla and friend's 02 s40 use ISO 9141-2? My understanding is that ELM327 devices have different hardware components to speak the different protocols.
I'm wondering if your ELM327 can speak anymore to any vehicle with ISO 9141-2?
4. You got some points, but let's restate them, adding some new ideas. I think the problem might be one of these (where the first two are the most likely):
a) tool is not seated in car's OBDII socket firmly, or
b) recessed male pin(s) or female pin receptable(s) such that contact is not being made for pin 7 (and maybe the pin 5 or pin 4 grounding pin, whichever ground pin applies to your ELM327), or
c) possible open or short between 24/421 distribution point back to where car's OBDII port connects with ELM327, or
d) pin 4 or 5 on your car not having proper ground, or
e) some problem in ELM327 internals -- maybe its ISO 9141-2 oriented transceiver, or maybe something else internal to ELM327, or
f) something awry with Bluetooth profile that's then inhibiting sending/receiving via software, or
g) Low Power circuitry inadvertently causing ELM327 to fail to connect.
May insight surround you.
esl_97_850_T5
1998 Volvo S70 GLT - 205.5K miles - S70 & M44 testbed in 2016-2019; traded 2019-07-15 (for spare time)
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
Update.
1) motronic 4.4 and the details as you say.
2) It is the first terminal I manage to make it work, the previous apps or windows xp software like realterm, I never managed to make them work, plus the appearance of this app is nice and user friendly, so I will say I like it a lot.
3) Not being sure this cars use Iso9141-2, and I can 100% say that ISO9141-2 works on this adapter, and you will see why, next.
4) I believe your point g) is the cause of the problem.
So, the long shot thought I mentioned yesterday in the end of my post, actually worked and torque got connected successfully !!
screenshots
So, I put my thoughts in a row, and knowing that I read and cleared codes about this time last year that I purchased the 850, something after that must have went wrong. After reading a lot of stuff in here, I came to the thought that maybe, the really bad abs module fix/resoldering that I did, and I know it didn't work, only worked for a little, then I redid again and practically destroyed it, may have caused a problem in the whole thing (first experience in my life soldering). I have not done other electrical jobs in the car other than connecting a few cables, putting an aftermarket deck and replacing bulbs and fuses. So, today I took out the abs module completely from the car, put everything back on, and tried to connect. As you can see in those pictures it successfully connected with torque and the dials for most sensors work.
As you already know, without the abs module on the speedometer does not work. It works when "My destroyed" abs module is on the car. As far as I read, the distance being driven without it on is not "stored" on the cluster? I am asking because I will either need to put it on, to make it continue storing since I am driving, and while I get this matter solved, and the other odometer gear comes along. Also I did not try any of the commands to see what my mileage is, I will have though by the weekend.
Furthermore, this must be another matter that came along, but since this is a topic I started. My incentive to get working on this matter has been a cel that I have had for like two weeks now. When I am scanning the codes on torque it goes up to 90-92% and the doesn't turn any results, like I dont have a cel. I tried clearing the codes but the cel is still there. My readiness is incomplete on many areas like catalytic and evap, which I believe justify the gas smell I have in the cabin when the car is cold.
I think, my best shot is to find another abs module.
I also feel bad and grateful at the same time about the time you spent, and thanks for that.
Next up comes the mileage (hopefully)
1) motronic 4.4 and the details as you say.
2) It is the first terminal I manage to make it work, the previous apps or windows xp software like realterm, I never managed to make them work, plus the appearance of this app is nice and user friendly, so I will say I like it a lot.
3) Not being sure this cars use Iso9141-2, and I can 100% say that ISO9141-2 works on this adapter, and you will see why, next.
4) I believe your point g) is the cause of the problem.
So, the long shot thought I mentioned yesterday in the end of my post, actually worked and torque got connected successfully !!
screenshots
So, I put my thoughts in a row, and knowing that I read and cleared codes about this time last year that I purchased the 850, something after that must have went wrong. After reading a lot of stuff in here, I came to the thought that maybe, the really bad abs module fix/resoldering that I did, and I know it didn't work, only worked for a little, then I redid again and practically destroyed it, may have caused a problem in the whole thing (first experience in my life soldering). I have not done other electrical jobs in the car other than connecting a few cables, putting an aftermarket deck and replacing bulbs and fuses. So, today I took out the abs module completely from the car, put everything back on, and tried to connect. As you can see in those pictures it successfully connected with torque and the dials for most sensors work.
As you already know, without the abs module on the speedometer does not work. It works when "My destroyed" abs module is on the car. As far as I read, the distance being driven without it on is not "stored" on the cluster? I am asking because I will either need to put it on, to make it continue storing since I am driving, and while I get this matter solved, and the other odometer gear comes along. Also I did not try any of the commands to see what my mileage is, I will have though by the weekend.
Furthermore, this must be another matter that came along, but since this is a topic I started. My incentive to get working on this matter has been a cel that I have had for like two weeks now. When I am scanning the codes on torque it goes up to 90-92% and the doesn't turn any results, like I dont have a cel. I tried clearing the codes but the cel is still there. My readiness is incomplete on many areas like catalytic and evap, which I believe justify the gas smell I have in the cabin when the car is cold.
I think, my best shot is to find another abs module.
I also feel bad and grateful at the same time about the time you spent, and thanks for that.
Next up comes the mileage (hopefully)
-
esl_97_850_T5
- Posts: 271
- Joined: 19 June 2012
- Year and Model: 1998 S70 GLT
- Location: Knoxville, TN
- Has thanked: 18 times
- Been thanked: 27 times
tzanis,
Glad you got Torque going with your Bluetooth ELM327.
I like how you isolated the problem to possibly being your ABS module, since that's one of the things that you had changed (and possibly butchered) after you had previously read/cleared codes successfully.
Your soldering skills sound similar to mine.
To verify that your ABS module is definitely the true culprit, you might want to put the ABS module back in, check if Torque is unable to connect again, then remove the ABS, and see if Torque can once again connect and display successfully.
Also, the recheck will help determine if your ABS fix was as bad (functionally) as you think it is, rather than just being bad cosmetically.
You understand correctly about the "lost" mileage. If the ABS is not sending the speed signal to your 97 850 COMBI, then the COMBI will not be accumulating mileage in ECU 51 B903. If you want to keep track of lost mileage, it would be best to do it via # gallons multiplied by typical Avg MPG (of course, using your metric equivalents), accumulation via a GPS system (if that's possible), estimating the mileage of your regular routes and multiplying by # of those trips, etc. Do not waste your time trying to derive the lost mileage from the "Manipulation" value in B90A. Use the common sense, lost mileage recording mechanisms just mentioned. Or just forget about the few hundred kilometers that will expire before you get a working ABS.
If the ABS removal recheck verifies the ABS is the problem, I'm thinking that all your previous conclusions about what doesn't work -- other terminal emulators, Realterm, etc -- are erroneous. Is that correct?
I don't understand what "it goes up to 90-92% and the doesn't turn any results" means when you were talking about your CEL. Please explain.
esl_97_850_T5
Glad you got Torque going with your Bluetooth ELM327.
I like how you isolated the problem to possibly being your ABS module, since that's one of the things that you had changed (and possibly butchered) after you had previously read/cleared codes successfully.
Your soldering skills sound similar to mine.
To verify that your ABS module is definitely the true culprit, you might want to put the ABS module back in, check if Torque is unable to connect again, then remove the ABS, and see if Torque can once again connect and display successfully.
Also, the recheck will help determine if your ABS fix was as bad (functionally) as you think it is, rather than just being bad cosmetically.
You understand correctly about the "lost" mileage. If the ABS is not sending the speed signal to your 97 850 COMBI, then the COMBI will not be accumulating mileage in ECU 51 B903. If you want to keep track of lost mileage, it would be best to do it via # gallons multiplied by typical Avg MPG (of course, using your metric equivalents), accumulation via a GPS system (if that's possible), estimating the mileage of your regular routes and multiplying by # of those trips, etc. Do not waste your time trying to derive the lost mileage from the "Manipulation" value in B90A. Use the common sense, lost mileage recording mechanisms just mentioned. Or just forget about the few hundred kilometers that will expire before you get a working ABS.
If the ABS removal recheck verifies the ABS is the problem, I'm thinking that all your previous conclusions about what doesn't work -- other terminal emulators, Realterm, etc -- are erroneous. Is that correct?
I don't understand what "it goes up to 90-92% and the doesn't turn any results" means when you were talking about your CEL. Please explain.
esl_97_850_T5
1998 Volvo S70 GLT - 205.5K miles - S70 & M44 testbed in 2016-2019; traded 2019-07-15 (for spare time)
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
Next update with more information will come by fast. 
I will recheck the abs module and see what comes up.
There are numerous free apps that give speedometer readings, and actually keep an odometer storage so, I temporarily will use those, to firstly have a track of my actual speed, and not lose any kilometers.
My assumptions are erroneous from the base anyway, and I just commented a personal opinion, since the apps and software actually work, and with more functions than a bluetooth and a smartphone app, it's just my fault that I didn't come to get them to work.
I will explain with a screenshot what I mean about the 90%, and it is while on the process of receiving any fault codes.
I will recheck the abs module and see what comes up.
There are numerous free apps that give speedometer readings, and actually keep an odometer storage so, I temporarily will use those, to firstly have a track of my actual speed, and not lose any kilometers.
My assumptions are erroneous from the base anyway, and I just commented a personal opinion, since the apps and software actually work, and with more functions than a bluetooth and a smartphone app, it's just my fault that I didn't come to get them to work.
I will explain with a screenshot what I mean about the 90%, and it is while on the process of receiving any fault codes.
with the ABS module removed, scan would give me p0500 code, vehicle speed sensor error.
(this time the scan worked and returned codes)
obvious why I believe.
with the abs on again, it doesnt connect at all, like my initial post. so it is known for now, that the result of this thread is:
A badly redone abs module can affect connectivity of your obd2.
I think the thread can be marked as solved now. I left my abs module on, to have the speedo working, and counting the kilometres I am missing. I will need to order the 12 tooth gear, because I had only replaced the 15 tooth small odometer gear, and have another abs module (silly me). Hopefully there are going to be more updates on this thread on miscellaneous stuff about my 850 around that.
Thanks mvs forum, and special thanks to member esl.
(this time the scan worked and returned codes)
obvious why I believe.
with the abs on again, it doesnt connect at all, like my initial post. so it is known for now, that the result of this thread is:
A badly redone abs module can affect connectivity of your obd2.
I think the thread can be marked as solved now. I left my abs module on, to have the speedo working, and counting the kilometres I am missing. I will need to order the 12 tooth gear, because I had only replaced the 15 tooth small odometer gear, and have another abs module (silly me). Hopefully there are going to be more updates on this thread on miscellaneous stuff about my 850 around that.
Thanks mvs forum, and special thanks to member esl.
-
esl_97_850_T5
- Posts: 271
- Joined: 19 June 2012
- Year and Model: 1998 S70 GLT
- Location: Knoxville, TN
- Has thanked: 18 times
- Been thanked: 27 times
Thanks for the feedback, especially the part about a badly redone ABS module can inhibit connectivity of the entire OBDII bus connected to OBDII port's pin 7.
1998 Volvo S70 GLT - 205.5K miles - S70 & M44 testbed in 2016-2019; traded 2019-07-15 (for spare time)
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
1997 Volvo 854 T5 - 147K miles - 850 testbed in 2012-2017; junked 2017-09
-
- Similar Topics
- Replies
- Views
- Last post