Jump to content

Recommended Posts

Posted
Ok gotcha.  I find that because the rear camera is so bright, I put my hand in front of it so I can see out of the side and rear mirrors.  It is so bad.  
 
If you haven't already, file a complaint with the NHTSA on their website.  Takes 3 minutes, just have your VIN ready.  To me and others, this is a safety issue because it renders the rear camera useless at night.


I completely agree it’s a safety issue and I already have!
Posted

Ok I’m impressed 6.2 10 speed in a snowstorm running 65-75 in auto 4wd the entire time my old 6.2
Wouldn’t go above 14 in the same conditions

cc24bf684cdb67f2581405d68540b3e1.jpg


Sent from my iPhone using Tapatalk Pro

  • Like 1
Posted
16 hours ago, 2020SilveradoCC said:

Yep. Tires only had 700 miles on them.

That sucks. Happened to me also. Had new about 1000 miles on Ridge Grapplers and got a piece of metal in the side wall. No plugging, No patching.

Posted
On 2/25/2020 at 9:59 PM, Kintnerboyredoubt said:

@FWaT4 so far so good, driven a few hundred miles on the highway and it hasn’t moved much, it’s got Velcro running down the side of the rails and 2 reinforcements running across. It also has a tension adjustment system that is very easy to adjust for temp changes etc. for the price it seems pretty tough to beat. I’ll report back if my initial impression changes. For $200 it’s less than half the cost of a big brand name cover, and quality wise I’m impressed. I wanted something that would still allow use of the bed without totally removing it and this meets the criteria. I’ve had Undercover hard tonneau covers in the past and while they are great it’s a pain to take them off when you need to use the bed.

@Kintnerboyredoubt thanks for the info. so does it roll up or fold up or just completely pull off in a single piece?

Posted
14 hours ago, RyanbabZ71 said:

Ok I’m impressed 6.2 10 speed in a snowstorm running 65-75 in auto 4wd the entire time my old 6.2
Wouldn’t go above 14 in the same conditions

cc24bf684cdb67f2581405d68540b3e1.jpg


Sent from my iPhone using Tapatalk Pro

@RyanbabZ71 that's great mpg! how was it when you first bought the truck? got almost 17mpg straight highway at 80mph the other day. that's after I put on 35's and the truck had roughly 500 miles. hoping it gets better- honestly the city driving is what's killing it right now. 

Posted


I do have blind spot detection, the sensor for that is in the mirror I believe. Its working as it normally did before I installed the lights. There are no sensors in the footwell.
Behind the the foot well there are sensors, i believe they are opposite of where you put the lights. Looks like you have the back up sensors and blind spot so you should have them. Luckily it doesnt seem like they are affected by the lights which is good.

Nice mod, do they hinder your foot getting enough room in the step?

Sent from my ONEPLUS A6013 using Tapatalk

Posted

QTP cutout going on this weekend. Stoked to try out an electric exhaust cutout. With our 7 month old it makes the most sense when leaving for work early to keep it quiet. 

Posted
12 hours ago, FWaT4 said:

@RyanbabZ71 that's great mpg! how was it when you first bought the truck? got almost 17mpg straight highway at 80mph the other day. that's after I put on 35's and the truck had roughly 500 miles. hoping it gets better- honestly the city driving is what's killing it right now. 

I drive mostly highway every day and average 80-90 @ 17.4 to 18 mpg. with 33.27 dia. A/T tires . I currently have 15,000 miles on my truck.

Posted
[mention=56]RyanbabZ71[/mention] that's great mpg! how was it when you first bought the truck? got almost 17mpg straight highway at 80mph the other day. that's after I put on 35's and the truck had roughly 500 miles. hoping it gets better- honestly the city driving is what's killing it right now. 


I used to get better but since breaking it in my foot has become heavier [emoji16]


Ryan B.
  • Like 1
  • Haha 1
Posted
Wireless charging for the center console completed.  I hate cables all over the cab, always getting crunched in the console lid etc.  I use the built in wireless pad, but it’s nice for passengers not to have to plug in a cable.  This is a simple DIY project.
 
first I picked up a wireless charger on Amazon, get the 3 coil kind so you get wider coverage.  Took it apart and removed the guts, used packing tape to keep it all together.  Minimizing plastic between the coils and your phone is key.  I tried using a small single coil one, but it just didn’t have the juice to power the phone thru all the plastic.   
 
take the bottom cover off the console lid, just use a plastic tool, it pops off very easy.  Squeeze the lid release to the top.    Inside you’ll see the grid structure that strengthens the plastic.  I used a paid of nippers (side cutters) to clip off the plastic to make a flatter area for the coils.  I trimmed more than I needed to as I thought I was going to use a larger round charging pad, so just trim as needed.   Then I used packing tape to hold the coils and it’s little circuit board together and stuck it in place.   Tested it to make it charges my phone before closing it up.  Ran the usb cable along the bottom and out the hinge and into the center console.  Works great!
><a href=https://www.gm-trucks.com/forums/uploads/monthly_2020_02/85213AF3-056D-4184-800E-124C4089959C.jpeg.b2f9d4ee507d16dbeceacaa47dd1986d.jpeg' alt='85213AF3-056D-4184-800E-124C4089959C.jpeg.b2f9d4ee507d16dbeceacaa47dd1986d.jpeg'>
A5C38A5F-27B4-47B2-A5E5-8A7CEE8DC39D.jpeg.cc7678313feed7868cf2d8157e61bec8.jpeg
62F76B93-4D51-49A2-BAE9-95B7E35F4ADD.thumb.jpeg.4d38b0edc0f750345b96e73525ce1e1c.jpeg
5F009BDA-F9F6-4551-B133-29C4CFBD20F1.thumb.jpeg.f52bd3de4796072d712d147e3f0bac9d.jpeg
E1D34A0D-54E2-430F-8A33-76964F350E5C.thumb.jpeg.248f7b4d8be1f3d857698e252e729899.jpeg
1F5DAB78-ED7C-4596-8AAF-49ADBB4F1E89.jpeg.c9e43405fb577df55a575e5ae3e44175.jpeg
I did the same today but use hot glue to hold my charger.

Sent from my SM-G960U using Tapatalk

  • Like 2
  • Thanks 2
Posted

Added the Sealight LED headlights. High and low beams. Looks much better, can’t wait to try them out tonight. Hope they don’t bother other drivers. Super bright. Took about 20 minutes start to finish. Lows went in from the top. Highs went in through the wheel wells. Not a scratch on my arms.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   5 Members, 1 Anonymous, 1,741 Guests (See full list)


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