Jump to content

Color change parking sensors?

MattMo27
 Share

Recommended Posts

MattMo27 Enthusiast

MattMo27

Posted
Posted

Does anyone know if there’s a way to color match parking sensors on the front and rear bumpers? Have a 2021 SLT that I’ve replaced the chrome bumpers to color match but am having trouble finding black parking sensors. The parts guy at my local dealership wasn’t much help just saying they come color matched to the original bumpers on new vehicles so all he could think to do was order original chrome sensors and try painting them myself. Those things get crazy when there’s too much water on them from rain so painting them scares me. Any ideas?

CF7CB90E-82D4-48EC-9B9F-2D9679F2F162.jpeg

10AA8D2A-97D7-4C53-8C6F-E350724B2A39.jpeg

mafd2 Senior Enthusiast

mafd2

Posted
Posted
1 hour ago, MattMo27 said:

Does anyone know if there’s a way to color match parking sensors on the front and rear bumpers? Have a 2021 SLT that I’ve replaced the chrome bumpers to color match but am having trouble finding black parking sensors. The parts guy at my local dealership wasn’t much help just saying they come color matched to the original bumpers on new vehicles so all he could think to do was order original chrome sensors and try painting them myself. Those things get crazy when there’s too much water on them from rain so painting them scares me. Any ideas?

CF7CB90E-82D4-48EC-9B9F-2D9679F2F162.jpeg

10AA8D2A-97D7-4C53-8C6F-E350724B2A39.jpeg

They are painted from the factory. I had a damaged one and were paint to match from GM. Paint won't hurt them. No issues

  • 8 months later...
mafd2 Senior Enthusiast

mafd2

Posted
Posted
2 hours ago, porksmush said:

Did you ever figure this out? I just had my chrome bumpers wrapped to match the white paint and my sensors were left chrome and it looks horrible.

There's nothing to figure out just paint them.  They're painted from the factory and come unpainted from GM with paint to match.

MattMo27 Enthusiast

MattMo27

Posted
  • Author
Posted
2 hours ago, porksmush said:

Did you ever figure this out? I just had my chrome bumpers wrapped to match the white paint and my sensors were left chrome and it looks horrible.

spacer.pngI actually used this and it works great

porksmush Enthusiast

porksmush

Posted
Posted
1 hour ago, MattMo27 said:

spacer.pngI actually used this and it works great

Awesome! Thank you! So did you just clean the sensors off and add a layer? How many layers did it take? Or how many passes did it take? I assume the chrome shine doesn't come through the paint at all? 

MattMo27 Enthusiast

MattMo27

Posted
  • Author
Posted
1 hour ago, porksmush said:

Awesome! Thank you! So did you just clean the sensors off and add a layer? How many layers did it take? Or how many passes did it take? I assume the chrome shine doesn't come through the paint at all? 

I probably did 3 layers but it probably would’ve been fine with two as the first coat did well. I only used rubbing alcohol to prep and that was it. I also had a GMC parts guy say all they do to theirs is paint them. That Krylon Fusion All-in-One was recommended on another video I watched before doing my flood light chrome outing and the chrome piece by the side of the hood behind the side mirror. Both of those have held great for over 8 months. I only did the sensors about a week ago when I finally replaced the black plastic caps over chrome with a full black bumper but have had no issues with the sensors since then.

porksmush Enthusiast

porksmush

Posted
Posted

Awesome, I ordered the gloss white just now on Amazon for like $6, gonna try it tomorrow! So what are the black plastic caps over chrome that you're talking about? Like caps for the sensors?

MattMo27 Enthusiast

MattMo27

Posted
  • Author
Posted
1 minute ago, porksmush said:

Awesome, I ordered the gloss white just now on Amazon for like $6, gonna try it tomorrow! So what are the black plastic caps over chrome that you're talking about? Like caps for the sensors?

Oops, no. I meant the plastic BumperShellz that were 3 pieces that just double sided taped over the entire bumper.

Mora84 Enthusiast

Mora84

Posted
Posted

You can actually sand them down and paint them. No problems. I did mine 4 years ago 

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