Troubleshooting problems with your Saab 9.3 can be a very frustrating and time-consuming process if you do not know what areas to look at first. Auto manufacturers today now equip their cars with an on-board diagnostic computer that allows both drivers and mechanics to scan the diagnostic system for error codes. There are error codes given out for each unique component of your car which has a sensor that is connected to the diagnostic computer. You can scan for these error codes to find out which parts are failing, saving you time in the troubleshooting process.
- Skill level:
- Moderately Easy
Things you need
- OBDII Code Reader
Find the location of your 9.3's on-board diagnostic port. Check the owner's manual if you cannot locate it on your own. Typically, the diagnostic ports are located underneath the steering wheel somewhere in the driver's side foot well. The specific location can vary depending on what year and generation that your 9.3 is.
Put your key into your Saab's ignition and turn it to the "II" or "III" position, which will respectively either turn on the electronics system, or activate the electronics and turn on the engine. When troubleshooting some problems, your engine may not be able to run, so it is sufficient to turn it to the second position only.
Insert the code reader's plug into the diagnostic port while your car's electronics are turned on. Allow the code reader to scan for error codes that are present in the diagnostic system.
Watch the display of the code reader as it scans for error codes. Write down a list of error codes that appear on the display.
Contact your local Saab dealer, auto parts store, or local Saab mechanic and explain that you are having trouble decoding error codes on your Saab. Each of these three resources will be able to provide you with the specific parts that are associated with each error code, allowing you to determine which parts need to be replaced.
- 20 of the funniest online reviews ever
- 14 Biggest lies people tell in online dating sites
- Hilarious things Google thinks you're trying to search for