Welcome to the North American Subaru Impreza Owners Club Monday March 25, 2019
Home Forums WikiNASIOC Products Store Modifications Upgrade Garage
NASIOC
Go Back   NASIOC > NASIOC Technical > Transmission (AT/MT) & Driveline

Welcome to NASIOC - The world's largest online community for Subaru enthusiasts!
Welcome to the NASIOC.com Subaru forum.

You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, free of charge, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, so please join our community today!

If you have any problems with the registration process or your account login, please contact us.
* Registered users of the site do not see these ads. 
Reply
 
Thread Tools Display Modes
Old 10-10-2014, 11:05 PM   #1
mrsaturn7085
Scooby Specialist
 
Member#: 375462
Join Date: Dec 2013
Chapter/Region: NWIC
Location: Portland, OR
Vehicle:
2006 Impreza WRX STI
WR Blue

Default 2006 STI DCCD issues

As long as I've owned my STI, I've had issues at low speeds with the center diff. not going full open unless I manually forced it into that mode. Also, pulling the codes using the e-brake/diff. select dial has always shown a few codes such as 26, 31, and 37. AUTO mode still works, but just has issues with low speed parking lot driving (diff. binding).

I finally bit the bullet and had a dealership clear the DCCD codes today. Oddly enough, the SSM didn't show any codes in the DCCD module. Issuing a command to clear the codes, then pulling codes with the e-brake/diff. select dial showed the same exact codes afterwards. SSM still showed no stored or current codes.

Is the module bad? The codes it's giving would cause a loss of AUTO mode functionality and I certainly don't seem to be experiencing any issues with that.

EDIT: I just realized this should be in Transmission/Drivetrain - please move this thread
* Registered users of the site do not see these ads.

Last edited by mrsaturn7085; 10-10-2014 at 11:27 PM. Reason: wrong forum
mrsaturn7085 is offline   Reply With Quote
Sponsored Links
* Registered users of the site do not see these ads.
Old 10-10-2014, 11:52 PM   #2
Back Road Runner
Scooby Guru
 
Member#: 60082
Join Date: Apr 2004
Chapter/Region: MWSOC
Location: Minnesota
Vehicle:
2004 Forester STI
Silver

Default

It's worth trying out a new module. I mean what could hurt? Did the dealer tell you anything? They should have discussed options in more detail. It seems odd they'd just clear the codes and send you on your way.

26 DCCD engine rpm signal system Open or shorted engine speed
signal circuit

31 Manual mode switch
Open or short in the manual mode switch circuit

37 Neutral position switch
Open or short in the neutral position switch circuit


I would start searching for other threads with those codes. You will likely find other people complaining about DCCD functionality, codes, what might have originated the issue, and solutions. I'm not going to dig through a pile of threads for you, but you are free to spend a little time digging around. Otherwise yeah, get and toss in a new DCCD to see if things go away. It's a simple check. You might even look into DCCD Pro or MapDCCD and check out the neat upgrades...if you're already going to spend a little cash to replace a stock one.
Back Road Runner is offline   Reply With Quote
Old 10-11-2014, 01:56 PM   #3
mrsaturn7085
Scooby Specialist
 
Member#: 375462
Join Date: Dec 2013
Chapter/Region: NWIC
Location: Portland, OR
Vehicle:
2006 Impreza WRX STI
WR Blue

Default

My original and very specific request was the following:
1. Clear codes from DCCD (I had replaced an ABS sensor and stored codes remained) - the '06 requires the SSM to do this, the '05 didn't
2. Diagnose noise in driver's front CV joint - suspected CV wear, boot intact
3. Diagnose rotational noise from rear - suspected wheel bearing
4. Disable impact sensor from OEM alarm system

What I got when I picked the car up was a recommendation that the center diff. needed replacement due to low-speed binding, a recommendation to replace the passenger's rear wheel bearing, an impact sensor ADJUSTMENT (not a full system disable), and being told the DCCD had no codes so they didn't clear anything.

This was a clear case of me being more knowledgeable about the DCCD system than the dealer. I re-scanned the codes after paying my bill and picking the car up and then went back in to stand over the techs shoulder while showing him where in the manual to find the SSM instructions for the DCCD computer. The initial recommendation I received was that the center diff. needed replacement due to low-speed binding (while in AUTO).

I asked the tech if he had opened the diff. for low-speed driving (part of the request to diagnose a CV joint). His response was "did I open the transmission case?". I explained that to do a sharp parking lot turn, he had to manually open the diff. to hear the noise.

I am pretty well educated with the issues people have had, and the advantages to aftermarket systems. Unfortunately, anything short of Pectel (and to a lesser extent, MoTeC) removes a TON of the input data that the 06/07 offered. I got a little long-winded here but my main question here was if anyone had seen the issue where the SSM wouldn't show codes, while the manual read-out would.

Last edited by mrsaturn7085; 10-11-2014 at 02:44 PM.
mrsaturn7085 is offline   Reply With Quote
Old 03-13-2015, 09:15 PM   #4
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Wanna bump this as I have the exact same codes. My car came out of the garage for the first time in 8 months (it was down for a roll cage installation) and on the second drive out (not the first) my DCCD open light (green "O") was blinking/flashing. At the end of the first drive, when doing a turn around in a cove, I got that binding noise as well, aka, "the clunk". Not sure if this was the diff or something else.

I did the checks for DTC 26, 33, and 37 and the only one that showed results was 37. This isn't unusual from my experience. One problem can often trigger other codes.

Anyways, I measure the resistance at (T9) #2 - #5 while in neutral as the FSM suggested in step 4 of the diagnostics (6MT(diag)-70)...

Quote:
CHECK NEUTRAL POSITION SWITCH.
1) Move the shift lever to “N”.
2) Measure the resistance between transmission harness connector terminals.
Connector & terminal (T9) No. 2 — No. 5:

Is the resistance less than 1Ω?

(Yes): Go to step 5.
(No): Replace the neutral position switch.
I got somewhere around 7kΩ. I will R&R the NPS and let you guys know.

Unfortunately I had track plans this weekend. While I acknowledge this issue is probably benign and won't hurt the drivetrain, I don't have $3,500+ to buy a new tranny if it does go catastrophic. I know this mentality is paranoid, but just the same, to each his own. Money for one man is different than money to another man.

I hope this helps!

Just thought I would add some data out there.

Now I'm stuck trying to find one of these freakin' things... A neutral position sensor (Subaru part number 32008AA160) does not appear to be something I can get locally on a weekend at short notice...

EDIT: Changed "DCCD open light" to "DCCD closed light". Apparently in the 2006 STI when the DCCD goes into limp/safe mode, it goes full lock according to the FSM.

EDIT2: I think I was wrong. Someone else whose probably smarter with Subaru than I told me the diff goes open, hence the open blinking light.

Last edited by skep18; 03-19-2015 at 09:46 AM.
skep18 is offline   Reply With Quote
Old 03-14-2015, 04:19 PM   #5
k3ogh_sti
Scooby Newbie
 
Member#: 415968
Join Date: Mar 2015
Location: England
Vehicle:
2005 widetrack sti
48w

Default

very handy to know thanks, im having the same sort of issue at the minute

https://www.youtube.com/watch?v=sDo-Q1IhON8
k3ogh_sti is offline   Reply With Quote
Old 03-14-2015, 06:45 PM   #6
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Quote:
Originally Posted by k3ogh_sti View Post
very handy to know thanks, im having the same sort of issue at the minute

https://www.youtube.com/watch?v=sDo-Q1IhON8
Yea, I had tons of codes during my swap. Turned out two of my sheel speed sensors were bad. This was confirmed by resistance checks at the component terminals. They measured out of limits. Fixing those two issues fixed all the lights. Many of the lights had nothing to do with those components.

GL with fixing your issue.

Unfortunately no aftermarket parts suppliers make Neutral Position Switches and I've got to wait for someone online to ship one out Monday.
skep18 is offline   Reply With Quote
Old 03-15-2015, 02:45 PM   #7
k3ogh_sti
Scooby Newbie
 
Member#: 415968
Join Date: Mar 2015
Location: England
Vehicle:
2005 widetrack sti
48w

Default

cheers hopefully a cheap fix, 36 for the part and whatever labour, do you think the NPS (37) is causing code 33 to pop up aswell ?

cheers chris
k3ogh_sti is offline   Reply With Quote
Old 03-16-2015, 01:30 PM   #8
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Quote:
Originally Posted by k3ogh_sti View Post
cheers hopefully a cheap fix, 36 for the part and whatever labour, do you think the NPS (37) is causing code 33 to pop up aswell ?

cheers chris
I hope so. IIRC, when my wheel speed sensors were bad, I got more codes than issues.

All in all, the dealership is getting the part in Thursday and we shall find out then.
skep18 is offline   Reply With Quote
Old 03-18-2015, 09:40 AM   #9
k3ogh_sti
Scooby Newbie
 
Member#: 415968
Join Date: Mar 2015
Location: England
Vehicle:
2005 widetrack sti
48w

Default

Keep me updated of you will
k3ogh_sti is offline   Reply With Quote
Old 03-18-2015, 09:55 AM   #10
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Quote:
Originally Posted by k3ogh_sti View Post
Keep me updated of you will
Will do. I am hoping to take the car to the track this Thursday (when the part comes in) and this weekend so hopefully it sorts everything out.
skep18 is offline   Reply With Quote
Old 03-18-2015, 10:33 PM   #11
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Little update, it appears there are memorized codes and temporary codes. Rom Raider goes into some detail on this when discussing one of their products:

Quote:
New SSM diagnostic trouble code reader (i.e. CEL codes). Learning View will read both temporary and memorized codes. Temporary codes are current faults which are cleared when turning the ignition from off to on (although may be set again if the fault still exists). Memorized codes are based on code history and are more "permanent" than temporary codes. This feature is in early testing.
So as I understand it, without a scanner tool, these codes will not go away. In my experience, these will also no keep the system malfunctioning. They appear to remain as noise when troubleshooting future issues. I will hopefully confirm this tomorrow because per the FSM:

Quote:
The codes which are memorized in control module, and the codes which are appeared to inform the trouble to driver in normal driving condition are only nine; “21”, “22”, “23”, “25”, “26”, “27”, “28”, “29” and “33”.
You'll recall that I (as well as the OP) am getting 26, 33, and 37.

Two of the codes, 26 (DCCD engine rpm signal system) and 33 (Brake Switch Circuit Range) I can not confirm faults after executing the FSM troubleshooting procedures. These are memorized codes.

DTC code 37 is a temporary code which will go away when fixed. I have removed my NPS and can again confirm my resistance for the open circuit position (button not pressed) is erratic, but mostly around 3kohm. This is not less than 1ohm. If the above is accurate, replacing this should fix the issue.

Also note, I tried to short out the circuit and it did not work. I was hoping to get a CEL when doing so due to the opposite failure mode (P1591 i think), but again, nothing changed. My guess is the system is sensitive enough to pick up the slight change in resistance between a properly working switch and a true circuit short (resistance built in to the switch when closed).

I will update tomorrow when I find out the results.
skep18 is offline   Reply With Quote
Old 03-19-2015, 04:47 AM   #12
k3ogh_sti
Scooby Newbie
 
Member#: 415968
Join Date: Mar 2015
Location: England
Vehicle:
2005 widetrack sti
48w

Default

Great write up mate, valuable information
k3ogh_sti is offline   Reply With Quote
Old 03-19-2015, 09:41 AM   #13
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Quote:
Originally Posted by k3ogh_sti View Post
Great write up mate, valuable information
Fingers crossed. Hopefully my interpretation leads to a confirmed fix.
skep18 is offline   Reply With Quote
Old 03-19-2015, 02:05 PM   #14
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Picked up the part at lunch.
skep18 is offline   Reply With Quote
Old 03-20-2015, 02:02 AM   #15
mrsaturn7085
Scooby Specialist
 
Member#: 375462
Join Date: Dec 2013
Chapter/Region: NWIC
Location: Portland, OR
Vehicle:
2006 Impreza WRX STI
WR Blue

Default

Okay - I meant to respond to this sooner, but it sounds like you're already on the right track.

2 things:
1. In my testing, I've rarely found the DCCD codes to be accurate on the 2006 STI.
2. FreeSSM is a lifesaver and should be used by a co-driver while you test drive, viewing the live data from the sensors. The error code read-out is more-or-less useless, but the live data will show any abnormal outputs from the wheel-speed sensors.
mrsaturn7085 is offline   Reply With Quote
Old 03-26-2015, 04:20 PM   #16
k3ogh_sti
Scooby Newbie
 
Member#: 415968
Join Date: Mar 2015
Location: England
Vehicle:
2005 widetrack sti
48w

Default

Any updates on this?
k3ogh_sti is offline   Reply With Quote
Old 06-23-2015, 02:04 PM   #17
k3ogh_sti
Scooby Newbie
 
Member#: 415968
Join Date: Mar 2015
Location: England
Vehicle:
2005 widetrack sti
48w

Default

Any more news
k3ogh_sti is offline   Reply With Quote
Old 06-28-2015, 01:40 AM   #18
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Quote:
Originally Posted by k3ogh_sti View Post
Any more news
Had a lot of other life events happening that have pulled me away from this. Unfortunately the NPS did not fix it... Chased some wiring around with a DMM and troubleshot the issue some but had no luck yet...

I will look into that live review mentioned above when I get back into the project. This issue is driving me nuts.
skep18 is offline   Reply With Quote
Old 06-28-2015, 07:32 PM   #19
mrsaturn7085
Scooby Specialist
 
Member#: 375462
Join Date: Dec 2013
Chapter/Region: NWIC
Location: Portland, OR
Vehicle:
2006 Impreza WRX STI
WR Blue

Default

With FreeSSM, you'll probably figure out the issue in about 15 minutes. It's usually obvious which signal is bad.
mrsaturn7085 is offline   Reply With Quote
Old 01-22-2016, 07:59 PM   #20
skep18
Scooby Specialist
 
Member#: 214971
Join Date: Jun 2009
Chapter/Region: South East
Location: TN
Vehicle:
2014 WRX
DGM

Default

Quote:
Originally Posted by mrsaturn7085 View Post
Okay - I meant to respond to this sooner, but it sounds like you're already on the right track.

2 things:
1. In my testing, I've rarely found the DCCD codes to be accurate on the 2006 STI.
2. FreeSSM is a lifesaver and should be used by a co-driver while you test drive, viewing the live data from the sensors. The error code read-out is more-or-less useless, but the live data will show any abnormal outputs from the wheel-speed sensors.
Quote:
Originally Posted by mrsaturn7085 View Post
With FreeSSM, you'll probably figure out the issue in about 15 minutes. It's usually obvious which signal is bad.
OMG, you were 100% correct. Listen to this man!!!

I didn't know what FreeSSM was nor did I think it could do everything it does. A coworker spoke to me about a similar software situation for his BMW and it dawned on me to look for such a thing for SUbaru. Low and behold FreeSSM exists! It can hook up to the TCU and pull PXXXX codes (no flashing green "O" DCCD morse code stuff). This made me so happy and so angry all at once!

I had a broken Steering Angle Sensor. After troubleshooting the code I was able to connect the car to FreeSSM and monitor the SAS output and watched it go intermittent or max out and lose signal altogether in real time. It gave me the the added assurance before buying the $280 MSRP part. The new one is in the mail now.

I realize this is an old post and all but life got in the way and the car has sat on the side lines for about a year now. I just got around to looking into this again this past week.

For anyone who cares or future reference, buy "VIMVIP VAG-COM KKL 409.1 OBD2 USB Cable Auto Scanner Scan Tool Audi VW SEAT Volkswagen" or something similar on Amazon for $10 and download the software drivers as instructed in the comments. Download FreeSSM and be amazed. As MrSaturn mentioned, I will be keeping this thing hooked up at the track. How amazing!
skep18 is offline   Reply With Quote
Old 01-23-2016, 01:03 PM   #21
mrsaturn7085
Scooby Specialist
 
Member#: 375462
Join Date: Dec 2013
Chapter/Region: NWIC
Location: Portland, OR
Vehicle:
2006 Impreza WRX STI
WR Blue

Default

Glad you got it sorted - the real benefit of FreeSSM comes from the live data logging. TCM codes, especially on the GD-series STi, are not always reliable. If you get one valid code, it will often throw 2-3 false positives, as well. I've noticed the '04-'06 also have a tendency to show stored codes that never existed in the first place. You can reset the codes entirely and have random stored codes pop up 2 seconds later.
mrsaturn7085 is offline   Reply With Quote
Old 10-22-2016, 03:30 PM   #22
kbarner09
Scooby Newbie
 
Member#: 456449
Join Date: Oct 2016
Default

I am having problems pulling the tcu codes using freessm on my 05 sti.

this dccd does not function, green blinking light. binding up in low speeds. freessm says no codes to pull. using the dccd controller method I get 27, right rear wheel speed sensor, but have heard that on the 05 it can be the left.... just want to confirm that I change the correct sensor.

checked fuses for tcu and the ground wires, everything seems to be in order.... on freessm I get the red circle with line next to obd2 system... I'm assuming that means it is not communicating with it
kbarner09 is offline   Reply With Quote
Old 10-22-2016, 07:35 PM   #23
mrsaturn7085
Scooby Specialist
 
Member#: 375462
Join Date: Dec 2013
Chapter/Region: NWIC
Location: Portland, OR
Vehicle:
2006 Impreza WRX STI
WR Blue

Default

Read the whole thread, monitor the raw signals, and diagnose. The codes, especially related to wheel speed, are largely unreliable.

Last edited by mrsaturn7085; 02-18-2019 at 02:33 AM.
mrsaturn7085 is offline   Reply With Quote
Old 02-16-2019, 08:46 PM   #24
woolaroo
Scooby Newbie
 
Member#: 491879
Join Date: Sep 2018
Default

I experienced similar issues with my DCCD system in a 2006 sti. Green O blinking. The FreeSSM is good software in my experience, but did not allow me to couple to the DCCD system. I had fault codes 28, 31, 33 & 37 found by using ebrake, DCCD auto/manual switch and dial. Kind of a neat process to pull the codes, and once you are in to pull the codes you can go even further to test your DCCD system and use the dial to control the DCCD coil. I tried to fix my issue for quite some time using the procedures defined in the FSM for the numerous DCCD sensors. I replaced the DCCD controller which did not fix the issue. I took the car to the dealership who identified lateral g sensor to be the issue, but the new part did not fix the issue. Troubleshooting with a scan device reported "Lateral G Sensor Fault". Ultimately, I replaced the yaw sensor and this solved my issue...even though I thought I had correctly troubleshot the yaw sensor reading voltages and tilting sensor according to FSM.
woolaroo is offline   Reply With Quote
Old 02-18-2019, 02:34 AM   #25
mrsaturn7085
Scooby Specialist
 
Member#: 375462
Join Date: Dec 2013
Chapter/Region: NWIC
Location: Portland, OR
Vehicle:
2006 Impreza WRX STI
WR Blue

Default

FYI - woolaroo's method will produce false codes prior to 2007. It is a not a reliable way to pull the codes. You should monitor signals using FreeSSM.
mrsaturn7085 is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

All times are GMT -4. The time now is 03:23 AM.


Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
Powered by Searchlight © 2019 Axivo Inc.
Copyright ©1999 - 2017, North American Subaru Impreza Owners Club, Inc.