Jump to content

Recommended Posts

Posted

Just wondering what the result was when you attempted to setup the mirrors without tying into the remote open close circuit s.

  • Like 1
Posted

My truck is the 2023 Elevation with 360 cameras and front perimeter lighting.    I cannot get any aftermarket mirrors that are set up for the 360 degree cameras.   No auto wreckers around have mirrors or anything on the new trucks.  May have to look at getting factory GM mirrors...

  • 2 months later...
Posted
On 7/15/2021 at 6:49 PM, Aaaaaaaayush said:

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 wanted to give this a try and so far I would call it a success!

 

This is what I ordered:

  • P/N: 1AMRP03092 The Mirrors (from 1AAUTO.COM)
  • P/N: 84532268 The OEM Power Fold Switch (from any GM Parts store)
  • 22-20 Ga. Female GT 150 Series, Sealed #12191818 The Terminals (from amazon)

  • 22 AWG 6 conductor wire The Cable (from amazon)

  • And The heart of the project: a generic, Chinese, Cheap Power fold mirror controller (from amazon)

 

I WILL MOSLTY BE FOCUSING ON EXPLAINING THE DRIVERS SIDE FOR THIS POST, IT IS ALMOST THE SAME ON THE PASSANGER SIDE EXCEPT THAT SIDE HAS THE AMBIENT TEMP SENSOR. WHEN YOU DISCONNECT THIS SENSOR AND RECONNECT IT THE TRUCK WILL SHOW -40 DEGREES, TO RECALIBRATE THE AMBIENT TEMP SENSOR YOU MUST DRIVE GREATER THAN 65MPH FOR MORE THAN 1 MINUTE.

 

Now my goal for this project was just to be able to power fold my mirrors when I leave my truck and lock the doors, but also unfold when I unlock. I haven't received the interior switch just yet but I am planning on figuring out how to make it work!

 

I started with checking my door harnesses for any existing wire that would make this easier, my truck came from the factory with the wiring for power adjustable mirrors, heated mirrors, and the puddle/task lamps (which is odd because my OEM mirrors did not have the puddle nor task lamps. The new aftermarket mirrors did include the two lights and I was able to get both of them working.

 

Next I played with the generic power fold mirror controller to see how it worked. It has the inputs for lock and unlock as well as inputs for an interior switch. The power inputs are +12V,GND, and ACC. There is just one two-wire output to fold and unfold the mirrors by switching the polarity of the motors. The ACC Wire (Accessory) is required because the controller folds and unfolds the mirrors based on the lock status. When ACC is applied the lock and unlock folding feature is disabled.

 

Next I looked at the GM Upfitter Electrical pinout section to see what pins I was looking for on the Mirror. There are only two pins for the Power Fold Motor, 

  1.  Pin 3 Circuit 3412 Driver Mirror Motor Fold IN Control
  2.  Pin 15 Circuit 3411 Driver Mirror Motor Fold Out Control

 

I first ran the new wires from the drivers side fuse panel to each mirror going under the dash and through the door harness holes and boots. I then terminated two leads on each side right at the mirror, the cable I used had 6 wires but I just wanted extra for any future projects. The mirrors went on without a hitch, and I pulled the locking pin off the mirror connector and put in my new two terminated leads in there correct positions (polarity really doesn't matter because reversing the polarity will just make the motor turn the wrong way). 

 

Now we have two new power folding mirrors with our own DIY harnesses installed and ready to go.

 

Next is finding your power sources and Lock and Unlock signals. For the +12V I used literally any fuse on the drivers side (they are all always powered) and for the ACC I had to run a wire to the heated steering wheel fuse on the passenger side (The passenger side fuse box has both always on power and accessory power). For the lock and unlock signals I used Pins 2 and 4 of the K9 Body Control Module pink X6 connector. These are for the drivers door lock actuator.

 

Finally with the ignition off so that ACC is not powered connect the Fold control wires from the controller to the mirrors and press the lock and unlock button to get the polarity correct. If its wrong just flip the two wires for that corresponding mirror.

 

If you have any questions just reply!

 

IMG_6519.thumb.jpg.c742a88c9f1f296aeb0c14cc94265143.jpg

 

IMG_6520.thumb.jpg.d53f73f5ceac785aa24cffbf32fefdb3.jpg

 

IMG_6521.thumb.jpg.ee566b4bf8dd598824b2b620ad9acf75.jpg

 

IMG_6522.thumb.jpg.f1a3dabb137a0b0bf54868122f29fc0e.jpg

 

IMG_6523.thumb.jpg.884515fa1791d43c00aaaa85d0a67581.jpg

 

IMG_6547.thumb.jpg.7ec4eb9eb67e24f67ce7693dc6772185.jpg

 

You can see the Generic controller tucked away inside the drivers side fuse panel.

 

 

Sent you a message

Posted

I now have the factory mirrors with camera, puddle lights, perimeter lights, blind spot indicator.  Controller, switch, and wiring are almost done now.

 

I want to connect the puddle lights so they work.  Does anyone know how to connect them?

2023 GMC Sierra Elevation

Posted

i bought the terminals listed and they are too big for the mirror and door connectors????

On 5/10/2024 at 4:29 PM, LowUfo said:

I now have the factory mirrors with camera, puddle lights, perimeter lights, blind spot indicator.  Controller, switch, and wiring are almost done now.

 

I want to connect the puddle lights so they work.  Does anyone know how to connect them?

2023 GMC Sierra Elevation

 They use a common ground with the mirror and then are feed power from the BCM..

Posted

You are correct the original author did purchase the wrong size. He told me he feed the conductor through the connector and folded it over little bit. I did the same and it is a lot easier than using a connector.

Posted
7 minutes ago, Tlee6 said:

You are correct the original author did purchase the wrong size. He told me he feed the conductor through the connector and folded it over little bit. I did the same and it is a lot easier than using a connector.

lol that would have been nice to know. I emailed notation but I’m sure they won’t tell me the correct terminal either. 

Posted

So boost auto knows what terminal is used but won’t give the information up. I get it but it’s frustrating. I have a few different terminals I’m going to look into 

Posted

So. OP said he got the puddle lights to work as he had the wires already.  I do as well. Also have them at the BCM. Did he have to get it programmed or did they just work??

 

I have power fold,puddle,front flood light and camera on my mirrors going on. How do all these lights turn on?? Obviously the camera won’t work but I would like the puddle lights to work. 

Posted
4 hours ago, Lowrado20 said:

So. OP said he got the puddle lights to work as he had the wires already.  I do as well. Also have them at the BCM. Did he have to get it programmed or did they just work??

 

I have power fold,puddle,front flood light and camera on my mirrors going on. How do all these lights turn on?? Obviously the camera won’t work but I would like the puddle lights to work. 

I wired the puddle lights(bottom facing) and the task lights(opposite side of the mirror) together in the door, then at the BCM I got power from the dome light wire, the dome light signal(+12v) is a PWM brightness control that can dim and bright a 12v LED directly. If you try to use a relay it will chatter as the lights fade in and out. Be aware there is a current limit on this output, if overloaded the BCM will attempt 3 restarts(lights flash 3 times) until it works or it’s too much. I was able to get the following led lights all to function just from the dome light wire: dome light, task light(L+R), puddle light(L+R), footwell led stripes (4), and led strips as welcome lights under the truck(6ft L +6ftR).

Posted

Excellent. Which BCM MODULE and pin is the dome light. Did you find out which pin style to use on the mirror connector?

Posted

Only ones that know are boostauto.  I found a harness out of a 3.0 LM2 at work and used the terminals to make it work. I also had a harness from the body of a vehicle that had the correct male terminals for door pass through.  All wired up like factory just have to finish moding the mirror caps because I’m not going to use the front flood lights.  Then wire the module for power fold. For as 2020 the back dome lamp is x1 terminal 23

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