Jump to content

Recommended Posts

Posted

Yes. All the vertical slats had to be cut. If you zoom in on the picture above you can see what I cut. I used 1/2 inch spacers to clear the active shutters but still had to cut 2 of them where the light bar dips back on the outer edges

  • 4 weeks later...
  • 1 month later...
Posted

Hi...ive got the light bar sitting at home... if I removed 1 or 2 of the active shutters do you believe I could get the light bar mounted behind the grill without cutting the vertical slats ?

Also I didn't get the mounting brackets. Do you happen to have the center distance of the 3 bolts on either side of the rad... I work in a fab shop so making my own isn't a problem

Posted
1 hour ago, flyingfool said:

why would you want an active shutter?

Why would you block the air flow to the transmission cooler, A/C condenser and radiator with light bars?

Posted

I have see HD trucks with light bars covering up the transmission cooler in the  bumper..  This is  foolish.. But this is my opinion, It might be Ok if you  never tow.

I look at it this way,  It's a hot summer day,  A/C on,  towing a  trailer. 

 

  • 2 months later...
Posted

just curious why you decided to trim the shutter rather than the aluminum heat fin on the light bar? It doesn't look like it needed much trimming and would have left the active shutters untouched. Awesome build though, I'm definitely starting that project this weekend!

  • 2 weeks later...
Posted

Also did this install on my 17 Silverado LT. Only removed the lower 2 rows of shutter fins and then all my other trimming was don on the grille itself. Very happy with the finished product but wouldn't have even thought of the install option without the forum topic.36c3d68b2017f6068af60f9e039ef3a3.jpgb875341624f0819b8267648c63d5534d.jpgc7d354648587f668bfa8bd36c4abac69.jpg

Sent from my SM-G955U using Tapatalk

  • 1 month later...
Posted

I also was hesitant to put this on.  I used spacers and minor cutting of grille, no trimming of the the active shutters at all.  I think it looks good.  I was gonna leave it behind my billet grille but decided to cut it out and it looks really good. Thanks for the support on getting me to do this.

20190707_172357.jpg

20190707_172254.jpg

20190707_210617.jpg

  • Like 1
Posted
On 12/11/2018 at 10:07 PM, Ryan2017Z71 said:

I installed the RC light bar behind the grill of my 17 Sierra with Active Shutters.  Slight modification to the grill and used nylon spacers to allow the light bar to stand off from the shutters. No issues and no CEL. 

 

IMG_1537.jpg

What bar and bracket are you using? I love the look of it and want to do pretty much the same.

Posted (edited)

I used the Rough Country 30” curved light bar and the brackets that came with it. I used nylon spacers to get the right stand off from the active shutters. 

 

Here is where I have more detail on what I did  

 

Edited by Ryan2017Z71
  • 5 months later...
Posted

They make a 8d flat light bar and curved flat light bar that might be alot easyier to install . I read this thread because i have to work on a 2017 tomarrow. The shutter has thrown a code and i got to figure it out . I didnt know it had them till i read the code tonight and i had got a light bar for him for chrismas . But since i have seen the shutter ill get the 8d  quad row 20 inch. Will post pick once it comes in. But for now i have a 12 inch ill post pick of.

Posted (edited)

12l x1w x3h

 

15773425923837523968573553907902.jpg

Edited by Will ride
To show some of face of light and add measurement

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

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...