Jump to content

To strip or not to strip? That is the question.


wilco

Recommended Posts

Posted

Sorry to get your hopes up with the provocative title but my post actually refers to window tint.

 

I am about to get my windows tinted (5%) and I wanted to get opinions on whether or not to get the windshield strip. I am 6' 2" and on previous vehicles I found myself slouching down to look under the tint strip, which can be quite annoying. I would like to hear the opinion of those who have put the window strip on a Silverado. Thanks in advance.

Posted

First off, your title sucks... Its false advertisement and you should get a warning for going that direction...

 

Second, I was hoping you were a hot chick and needed some advise (warning point #2)

 

 

3rd, at a towering 5'6", I laugh at your little problem...

 

 

Back to topic.. With 5% all the way around, its gonna be dark in there as it is.. You may want to go with a 20 or 35% up on the windshield "strip" to lighten the visual up a bit... You dont have to go 6 inchs down either, you could do 4 or even 2 (which is a bit of a waste but...) I have had my share of 5% vehicles. What a PIA it has been typically.. Good luck!

Posted

no more windshield strip or 5% for me anymore... Loved it when I was in my 20's ... but not so much in my late 30's

Posted

Your installer should have a scrap piece of tint, set it on the outside of the windshield and move it up and down to your desired height with you sitting in the seat.

Posted

Sorry to get your hopes up with the provocative title but my post actually refers to window tint.

 

I am about to get my windows tinted (5%) and I wanted to get opinions on whether or not to get the windshield strip. I am 6' 2" and on previous vehicles I found myself slouching down to look under the tint strip, which can be quite annoying. I would like to hear the opinion of those who have put the window strip on a Silverado. Thanks in advance.

 

I have 5% on my front windows and 15% on the backs to make it 5% and I have a 7" or so 5% tint strip and im 6'3. I personally like things dark and where the sides are so dark the front being so big makes it kinda like bam! Im probably gonna remove the strip and do 35% on the whole windshield with possibly a smaller strip on top of that maybe. I do like my windows dark because growing up in the city where I did you didn't mess with people in trucks you couldn't see and if they cant see in they are less likely to break into your truck and come on who doesn't love just staring people down who are pointing, looking, and taking pics of your truck :P But in the end I would say either get a strip you don't mind looking through or a 5-6" strip to where its not at that point where its half way through your line of sight or tint the whole windshield.

Posted

Thanks for the replies. I called the installer and he only charges another $10 for the strip. Guess for that I can get a short one and rip it off if I don't like it.

Posted

I did my vehicles. Really helps glare when driving into the sun. I wear glasses, so sunglasses are not an option.

 

Sent from my LGL86C using Tapatalk

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...