How to Retrieve Trouble Codes for a 1986 300ZX

Written by katebo
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Retrieve Trouble Codes for a 1986 300ZX
Read your Nissan's codes using an OBD scanner. (Jupiterimages/Polka Dot/Getty Images)

You can retrieve the trouble codes from your '86 Nissan 300ZX right from your home garage, saving time and money. To read the codes you must obtain an OBD I code scanner. These small computerised devices can be purchased online or from your local auto parts store. The OBD I code scanner reads the trouble codes which are stored in the Nissan's On-Board Diagnostics (OBD) computer. Each code tells you information about the vehicle's mechanical and electrical systems to help you find the problem with your 300ZX.

Skill level:
Moderately Easy

Things you need

  • OBD I code scanner
  • Ignition key
  • Pen and paper
  • OBD I code scanner manual

Show MoreHide


  1. 1

    Locate a port on the driver's side of the car next to the steering column. This port is the same size and shape as the connective end on the OBD I code scanner. Plug the scanner into this port.

  2. 2

    Put the key into the ignition and turn it to the "On" position, but don't start the engine. This will power on your scanner.

  3. 3

    Find the "Retrieve Codes" command on the scanner and select it. Wait for the scanner to display the trouble codes. Write the alphanumeric codes down on a piece of paper. Look up these codes in the scanner's manual.

  4. 4

    Unplug the OBD I code scanner from the port. Take the car and the codes to be fixed or serviced by a qualified mechanic, or do the repairs yourself if you have the knowledge.

Tips and warnings

  • Most auto parts stores will loan their scan tools for free to help you diagnose the trouble codes.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.