Jump to content

Recommended Posts

Posted

Hi all...
I successfully installed Truxedo Lo Pro QT this past weekend...
No modification of the bar. However... It looks like the kit comes with foam insulation for the rear bracket mounts that are too small for the Sierra/Silverado. I guess they are for the Canyon/Colorado. I cut foam to size of brackets and such and everything looks tight. Happy Truckin!

  • 2 weeks later...
Posted

I really like the sports bar, but I have a Truxedo Deuce and would lose the versatility of the covers split functions. The more I see the bar though, I may just have to get it!

  • 4 weeks later...
Posted

MORE PICS

 

I was looking at doing the same thing but didn't want to spend $1800 only to have to cut the cover and mess it up.

 

Did you only have to cut the brackets closest to the tailgate and not the ones near the back window?

Posted

 

I was looking at doing the same thing but didn't want to spend $1800 only to have to cut the cover and mess it up.

 

Did you only have to cut the brackets closest to the tailgate and not the ones near the back window?

Exactly, the front ones lay down right on top, the back mounts are the ones that wrap around the edge of the bed to attatch. I hate what a pain it is to post pictures on here so if you want more pictures just pm me your email or phone number and I will send them to you

Posted

I'm the proud owner of a Silverado Realtree edition. After reading through the thread I am leaning towards getting a BAK Revolver X2 and modifying it. Does anyone know if the toolbox (BAKBOX) they sell will work as well?

  • Like 1
Posted

I read a review saying at highway speeds it bounced and flexes like a soft cover. Anyone here experience that or does it stay flat?

 

 

Sent from my iPhone using Tapatalk

  • 3 weeks later...
Posted
Followed Schimbo's post and did the RetraxPro MX as well... works perfect!


2017 GMC Sierra SLT All Terrain X - Retrax Cover


2017 GMC Sierra SLT All Terrain X - Retrax Cover


2017 GMC Sierra SLT All Terrain X


2017 GMC Sierra SLT All Terrain X

  • 2 weeks later...
Posted

Hey all just a heads up. The revolver X2 will not fit with the reg. 6'6" box. Made this mistake. :( Got everything cut and the bars installed but the tonneau scrapes the sport bar and has to be jammed in while rolling. This is because the 6'6" box tonneau has a thicker roll when passing the sport bar. Will try some more tricks tomorrow, hopefully will be able to grind the track of the tonneau cover down to make it fit. Only need about 1/4". If anyone has any ideas please share!

  • 2 weeks later...
Posted

Khaotic and Schimbo: How did you guys cut the back brackets? Also, did you consider bolting down the back brackets again from the top? It looks like neither of you have re-secured the back bracket. Did you consider shimming the sport bar at all which now looks elevated on the outside given you have slid the cover under it? Finally, is everything functioning normally - the weight of the sport bar doesn't impact the sliding cover does it? Thanks!!! I have been waiting and waiting to make a decision for my GMC Sierra All-Terrain X.

Posted

011780ff15f1c5284d9974799514c093.jpg38309d2670f4ddef92aca5f194327291.jpgf04fafae23b7401e8dc6dee780329d4a.jpg

I cut the back bracket with the saw in the picture then grinded it down smooth. I put double sided tape to prevent rattle. The elevated edge is due to the inner part touching the cover rails which is higher. I'm eventually going to run some black caulk to make it look finished. The bar is pretty light (it's hollow) so no problem with use of the bed cover. The sport bar is on there strong. I'm 280 lbs and I can use it to lift myself into the truck and it still doesn't budge. Even with the back not being bolted down.

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Posted

That's very helpful thanks. Was the bar easy to disconnect from the truck - specifically, the wiring for the break light? I assume just a plug somewhere? What did you grind the edge with? Could be my project for tomorrow!

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