Jump to content

Recommended Posts

Posted


For further clarification they posted a note in their FB tonight. For some reason the 10 speed is not ready (even though I was email it was [emoji2373]) it is being beta tested at the moment. I have to call range tomorrow. I’ll update in the morning


Ryan B.
Posted

Alright here is the update. They have received reports on some trucks (6.2/10 speed) it doesn’t work and some it does. They are beta testing some trucks at the moment. I was told (since mine has shipped) I can try it out if it doesnt work I can send back (refund or update to the module when that is finalized). We will see when it gets here if it works. [emoji1694]




Ryan B.

  • Like 1
Posted

Center console light was useless with the tray on top, so I added a led book light and velcro’d it inside.  Plenty of light now

F73F8373-05B0-408D-81CF-8C820772C2CF.jpeg

  • Like 1
Posted
Center console light was useless with the tray on top, so I added a led book light and velcro’d it inside.  Plenty of light now
F73F8373-05B0-408D-81CF-8C820772C2CF.thumb.jpeg.cc52d7a1998e55c497340be0cc5796e3.jpeg

So I guess you like the console tray? I’ve been debating getting one for small items so I can find them easily.


Sent from my iPhone using Tapatalk
Posted
On 4/28/2020 at 6:59 PM, alexistence said:

Stock tire size is 33''. The offset and width could case a bit of rubbing but I don't think it'll be extreme. 

 

If you need to level, I went with a motofab 2.5'' top spacer on mine. It was painless enough to install and inexpensive (70$). But you could easily get a set struts for about 300$ that should level the truck out a little up front to give you more clearance. 

 

Take pictures and update when it's done. The wheel and tire combo will be nice. 

I finally got my wheels and tires. Got a great deal too! (Fyi I looked up my OEM tires and they are actually 31" but maybe they have different options especially for the trail boss)

So here's what I've done with my truck so far since my purchase back in July '19:

My truck is a 5.3L Crew Cab Standard bed RST.

I worked in custom leather seats and spray in bed liner into my deal with the purchase. Beyond that I've got..

- weathertech side window deflectors
- center console tray insert
- found the bed had some holes already drilled for an optional accessory, so I purchased some light mounts to hold a flag in the bed.
- teaching myself how to wrap interior pieces before I do exterior. I need to add the bronze to the rest of the chrome trim on the interior.
- 5 or 10% ceramic tint and windshield strip. 80% full windshield ceramic tint.
- full matte black American flag decal on back window.
- removed the front air dam
- Matte Black plasti dipped badges
- Ronin .50 cal antenna
- Baja Kits Leveling Kit
-18x9 -12mm Method NV in bronze
-33x12.5r18 Nitto Ridge Grapplers
 

20200504_113552.jpg

20200504_113611.jpg

20200504_114114.jpg

  • Like 3
Posted
Just now, Atelliott89 said:

I finally got my wheels and tires. Got a great deal too! (Fyi I looked up my OEM tires and they are actually 31" but maybe they have different options especially for the trail boss)

So here's what I've done with my truck so far since my purchase back in July '19:

My truck is a 5.3L Crew Cab Standard bed RST.

I worked in custom leather seats and spray in bed liner into my deal with the purchase. Beyond that I've got..

- weathertech side window deflectors
- center console tray insert
- found the bed had some holes already drilled for an optional accessory, so I purchased some light mounts to hold a flag in the bed.
- teaching myself how to wrap interior pieces before I do exterior. I need to add the bronze to the rest of the chrome trim on the interior.
- 5 or 10% ceramic tint and windshield strip. 80% full windshield ceramic tint.
- full matte black American flag decal on back window.
- removed the front air dam
- Matte Black plasti dipped badges
- Ronin .50 cal antenna
- Baja Kits Leveling Kit
-18x9 -12mm Method NV in bronze
-33x12.5r18 Nitto Ridge Grapplers
 

20200504_113552.jpg

20200504_113611.jpg

20200504_114114.jpg

 

20200505_180129.jpg

20200505_180159.jpg

20200505_180221.jpg

Posted
55 minutes ago, curly said:


So I guess you like the console tray? I’ve been debating getting one for small items so I can find them easily.


Sent from my iPhone using Tapatalk

It's a must have, I couldn't find a dam thing in my center console before I added it.  Mine was kind of a loose fit (maybe 1/4"), so I added little pieces of rubber to edges, and now it doesn't rock back and fourth when I'm driving.

  • Like 1
Posted
On 5/4/2020 at 9:53 AM, Julio13 said:

That’s why I bought the ones on eBay it was about 21 dollars and it’s double sided tape that holds it in place

Which link did you use?  Do you mind sharing?  I have a 2020, so I have smart key up front, but none on the rear handles.  So I need to buy both

Posted
Which link did you use?  Do you mind sharing?  I have a 2020, so I have smart key up front, but none on the rear handles.  So I need to buy both

Ok mine is a custom with no smart key but they do sell with the hole let me see if I find one


Sent from my iPhone using Tapatalk
Posted
20200505_180430.thumb.jpg.0927b7b6d417878397612bf1a508d460.jpg
20200505_180447.thumb.jpg.529cb387f2f0aa037bc64ad279ee471f.jpg
20200505_180529.thumb.jpg.dda08c4ae5773b913fabd9852377266e.jpg
Where'd you order the window flag from? How was the install?

Sent from my Pixel 2 XL using Tapatalk

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