Jump to content

Adding Power fold Mirrors to your T1 truck without the memory package

Aaaaaaaayush
 Share

Recommended Posts

  • Replies 85
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Aaaaaaaayush
Aaaaaaaayush

I found a cheap pair of T1 Power folding mirrors on 1AAUTO (NON OEM) that are meant just as a replacement to the OEM Memory Package mirrors, obviously I don't have the memory package but I really want

Aaaaaaaayush
Aaaaaaaayush

The pins from the BCM are going straight to the drivers door actuator(solenoid), these are the actual High Low signals for the actuator, no relay needed.   I did this so that I can unlock an

Aaaaaaaayush
Aaaaaaaayush

Seriously! Or at least some likes on my posts 😂

Posted Images

Lowrado20 Enthusiast

Lowrado20

Posted
Posted

To everything installed and for some reason driver side works opposite no matter how I hook it up lol going to try a different way before buying a second module. I had to swap terminal 13 with 5 to get puddle lights to work

Lowrado20 Enthusiast

Lowrado20

Posted
Posted

Got everything working with puddle lights. The module will not unfold mirrors if I remote start the truck. I have to turn it off and infold then start it.  I have tried swapping the dip switch inside but then it folds the mirrors when I turn truck on after a remote start lol

  • Like 1
Tlee6 Enthusiast

Tlee6

Posted
Posted

When you enter the truck after the remote start you have to step on the brake and push the start button. After that you should be able to use your switch to open the mirrors. 

Lowrado20 Enthusiast

Lowrado20

Posted
Posted
2 hours ago, Tlee6 said:

When you enter the truck after the remote start you have to step on the brake and push the start button. After that you should be able to use your switch to open the mirrors. 

Ahhh I don’t have a switch yet. But it says when ignition turns on it should unfold

Lowrado20 Enthusiast

Lowrado20

Posted
Posted
10 hours ago, Tlee6 said:

When you enter the truck after the remote start you have to step on the brake and push the start button. After that you should be able to use your switch to open the mirrors. 

Ahhh I don’t have a switch yet. But it says when ignition turns on it should unfold.  Going to install a relay that gets a signal when shifter out of park and applies ignition to power fold module so they work with the fob and buttons till out of park

LowUfo Enthusiast

LowUfo

Posted
Posted

What are the pin numbers on the mirror for the puddle lights?   Where do they connect on your truck?

  • 4 weeks later...
LowUfo Enthusiast

LowUfo

Posted
Posted

Been super busy at work.  I have a few days now to get everything working.  Trying to find the proper connectors to fit, as the OP has the wrong size.   I really don't want to push the wire through the connector and fold the wire back

Aaaaaaaayush Enthusiast

Aaaaaaaayush

Posted
  • Author
Posted
15 minutes ago, LowUfo said:

Been super busy at work.  I have a few days now to get everything working.  Trying to find the proper connectors to fit, as the OP has the wrong size.   I really don't want to push the wire through the connector and fold the wire back

I never found the correct connectors but it’s worked fine for years, if wired properly it’s fused at 5amps and it’s not mission critical. If the wire comes loose, the mirror will have to be manually folded and unfolded. If the wire comes loose and shorts out, the fuse blows… and it’s a manual folding mirror again.

 

maybe be able to find the connector on eBay or something and salvage the terminals that way

  • Like 1
LowUfo Enthusiast

LowUfo

Posted
Posted

 I confirmed that Pin 5 works to turn the puddle lights on (test bench checked).  When I finally get some time to do the install, would the power source come from K9X6 pin 4  (door unlock)?   If so, do I need to install a time delay (off) relay so the puddle lights stay on for a number of seconds, or does pin 4 keep power on for 10 to 15 seconds?  Where did you power your puddle lights from.

 

Also, has anyone got their driver's side mirror dimming to work?  That should be Pin 17.  Where did you connect the power source to?

On 5/20/2024 at 7:28 PM, Lowrado20 said:

Got everything working with puddle lights. The module will not unfold mirrors if I remote start the truck. I have to turn it off and infold then start it.  I have tried swapping the dip switch inside but then it folds the mirrors when I turn truck on after a remote start lol

 

  • 1 month later...
2020LTTB New Member

2020LTTB

Posted
Posted
On 2/11/2024 at 7:54 AM, Timothy Lee said:

Attached is an updated wiring diagram eliminating the OEM door mirror switch and adding momentary switch.

Silverado Mirror wiring diagram02092024.pdf 209 kB · 52 downloads

Timothy, reviving an older threat here! Thank you for posting your diagram and efforts here. I have a 2020 LT Trail Boss and I was pulled over for towing my boat with the small mirrors as the CHP officer said I didn't have sufficient view behind me. I just purchased two OEM Tow mirrors with Camera and power fold for same year GMC Sierra 1500. I am going to attempt the wiring per your diagram this weekend. One question... I really want to use the mirror/window switch panel... I bought the switch with the power fold button, is there anyway to use that instead of a separate momentary switch?

2020LTTB New Member

2020LTTB

Posted
Posted
41 minutes ago, 2020LTTB said:

Timothy, reviving an older thread here! Thank you for posting your diagram and efforts here. I have a 2020 LT Trail Boss and I was pulled over for towing my boat with the small mirrors as the CHP officer said I didn't have sufficient view behind me. I just purchased two OEM Tow mirrors with Camera and power fold for same year GMC Sierra 1500. I am going to attempt the wiring per your diagram this weekend. One question... I really want to use the mirror/window switch panel... I bought the switch with the power fold button, is there anyway to use that instead of a separate momentary switch?

 

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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...