How JustAnswer Works:
  • Ask an Expert
    Experts are full of valuable knowledge and are ready to help with any question. Credentials confirmed by a Fortune 500 verification firm.
  • Get a Professional Answer
    Via email, text message, or notification as you wait on our site.
    Ask follow up questions if you need to.
  • 100% Satisfaction Guarantee
    Rate the answer you receive.
Ask Paul M ASE Master Your Own Question
Paul M ASE Master
Paul M ASE Master, ASE Master Tech
Category: Dodge
Satisfied Customers: 4684
Experience:  Ase Master Tech 20+ Years
Type Your Dodge Question Here...
Paul M ASE Master is online now
A new question is answered every 9 seconds

2000 dodge dakota: wont shift..P1734,P1732 error codes..speed sensors

Customer Question

2000 dodge dakota won't shift into gear. P0731,PO734,P1734,P1732 error codes. Replaced speed sensors already
Submitted: 7 years ago.
Category: Dodge
Expert:  Paul M ASE Master replied 7 years ago.

Hello and thank you for using Just Answer


Most commonly these codes are caused by the speed sensors


there are also known issues with the connectors to the sensors


did you verify the readings from the input and output sensors with a scan tool?


if the reading of the sensors are showing good with a scan tool the transmission may have failed


click here for more information on testing speed sensors


click here for more information on testing for bad connector

click here for more information on transmission slippage causing codes


if the speed sensors are showing good on a scan tool your transmission is to blame.


let me know what you get for readings





Customer: replied 7 years ago.
I have replaced both the input and output speed sensors already. Didn't help. The gear shift moves freely but the transmission doesn't engage. Could it be the transmission control solenoid? No signs that the transmission failed. Parked the truck and when I came back it threw the MIL and wont engage into gear.
Expert:  Paul M ASE Master replied 7 years ago.

you need to verify the readings of the sensors with a scan tool


you could have a bad connector or a problem in the harness


the nest step is to verify the sensor readings