Jump to content

Recommended Posts

Posted

Hey there.... I have been reading about the few ways to add steering wheel controls to the 07 up Silverado and have found what might be one of the easier ways to do it. (Besides buying a wheel... ) I was reading in some of the other threads that you can't buy the steering wheel wiring harness by itself. Well, I have done some digging and have found it. It is a little different but works great. Here are a couple of photos of the 2 wiring harnesses... This being the original. IMG_0026.jpg and this being the new one. IMG_0025.jpg And the 2 plugs side by side. The old one on the left and the new one on the right. I know some of the colors are different in the wires but they go to the same places. IMG_0024.jpg And here is the control pod that I ordered. IMG_0029.jpg I must say the hardest part of this project was cutting the steering wheel shroud for the switch pod. (I also did not disconnect the airbag or remove the steering wheel.... ) After removing the airbag from the wheel you have this... IMG_0020.jpg Remove the 4 Torx (T-30) screws from the horn basket and remove the basket. IMG_0022.jpg And now remove the wiring harness. Next you will want to mount the new switches to the wheel cover. (Also separate the 2 halves. It will make the next step easier) The next step will be to trim the steering when shroud. go slow and take small chunks out till the switch fits nice. before adding the new wiring harness you need to change one connector. the brown wire has the wrong sex connector on it. It has a male and needs to be female. change it and extend it 2 or 3 inches. Now you can add the new harness to the steering wheel. install the horn basket and re-install the rest.... Bah Bam!!!! You now have steering wheel Audio controls!!! IMG_0034.jpg And here are the part numbers that you need.... 25889498 is the wiring harness and 25851951 is for the controls..... Have fun!! (Next I will be adding the controller for my aftermarket radio to use the steering wheel controls.... )

  • Like 2
Posted

Thanks... :) I never thought I would enjoy having them as much. But I do. (I added the PAC Adaptor for my pioneer head unit and it works like a champ!)

  • 2 weeks later...
Posted

This is great. Im going to order today. Where did you get the replacement connector?

Posted (edited)

Got everything from autoway chevrolet. (I work in a bodyshop and thats who we get our GM aprts from. ) Seeing that you have a 2010 you might want to pull your airbag and see if it is pre-wired...

Edited by 08lt
  • 8 months later...
Posted

Great write up. I recently completed this mod and it works great. Please note, I used a different harness that required NO modifications. I have a 08 LT silverado and found a harness that was a direct plug-in. The part number used was 25776048.

  • 10 months later...
Posted

Did you do this without removing the steering wheel? Do you have any pics of where and how you did the trimming? Thank you for providing great info. I was hesitant about taking things apart without any chance of making things work. You did disconnect the battery first and let the air bag system bleed off power for 10 mins. didn't you?

  • 1 month later...
Posted

 

 

 

Received my new Original Equipment Steering wheel today. Ordered it from Ebay/JJ Original Equipment in Dallas, Texas. Opened the box and everything looked great. It is equipped with cruise control and radio controls. Went out and disconnected the battery for 20 min. Removed the Air Bag. popped off the old steering wheel. Installed the new steering wheel. replaced the Air Bag. hooked up the battery. Turned on the radio, and just like everyone I have asked or responded to my cries for help, the controls work just like they are suppose to. Thank you all for your help. Install time, 40 minutes including the 20 minute wait for the Air Bag system to discharge. Steering wheel cost, $119.00. After I recover for this cost I will be ordering a Costar Blue Star unit to replace my Over Priced on board GM cell phone.

  • 10 months later...
Posted

Hey guys quick question. If I buy a new steering wheel do I still need to order the wiring harness? Thinking of going this route instead of cutting the shroud. I tend to rush things and hack!

Posted

Received my new Original Equipment Steering wheel today. Ordered it from Ebay/JJ Original Equipment in Dallas, Texas. Opened the box and everything looked great. It is equipped with cruise control and radio controls. Went out and disconnected the battery for 20 min. Removed the Air Bag. popped off the old steering wheel. Installed the new steering wheel. replaced the Air Bag. hooked up the battery. Turned on the radio, and just like everyone I have asked or responded to my cries for help, the controls work just like they are suppose to. Thank you all for your help. Install time, 40 minutes including the 20 minute wait for the Air Bag system to discharge. Steering wheel cost, $119.00. After I recover for this cost I will be ordering a Costar Blue Star unit to replace my Over Priced on board GM cell phone.

If I buy a new steering wheel do I still need to order the wiring harness? Thinking of going this route instead of cutting the shroud.

Posted

I did not need any additional wiring harness. The steering wheel came equipped with all wiring needed as long as you order the one equipped with the radio controls. The harness is only needed when you are converting your existing steering wheel and adding the radio controls to it.

  • 5 years later...
Posted
On 8/25/2015 at 9:34 PM, Arejaye said:

Hey guys quick question. If I buy a new steering wheel do I still need to order the wiring harness? Thinking of going this route instead of cutting the shroud. I tend to rush things and hack!

i think if the wheel you buy has the radio control harness it will be plug and play

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...