Jump to content

Recommended Posts

Posted

So we are seeing some 21's showing up here in Alberta but no Chevy's with the new tailgate yet. Actually lots of High Country trucks that you would expect to see them on. Has anyone else seen any?

Posted

GM's website says the multi-function tailgate is "late availability" on the 1500 Silverado.

 

The order guide still show the power up/down tailgate as standard on the higher trim Silverados.

Posted
On 10/23/2020 at 4:50 PM, Likarok said:

So we are seeing some 21's showing up here in Alberta but no Chevy's with the new tailgate yet. Actually lots of High Country trucks that you would expect to see them on. Has anyone else seen any?

I’m in IL I just picked up a 21’ Sierra 3.0 Dmax a week ago. They only had two 21’s in stock but six on order. I do believe GM will be pushing the 3.0 sales hard over the next 12 months.

  • Like 1
Posted
On 10/24/2020 at 4:33 PM, Crazypontiac03 said:

I’m in IL I just picked up a 21’ Sierra 3.0 Dmax a week ago. They only had two 21’s in stock but six on order. I do believe GM will be pushing the 3.0 sales hard over the next 12 months.

I agree. Dealer here has about 6 1500 Denali's and 5 High Countries, all diesels. SOL for a gas. 

 

So what do you think of your 3.0L so far?

 

Posted
36 minutes ago, Likarok said:

I agree. Dealer here has about 6 1500 Denali's and 5 High Countries, all diesels. SOL for a gas. 

 

So what do you think of your 3.0L so far?

 

Thus far I love it! I’m averaging about 25 mpg my  commute is a mix between rual and City driving. Average speed is the 45-60mph range. I haven’t had it out on the expressway just yet, but you  definitely feel like torque. 10 speed trans seems to shift with ease, Only time I really feel it is between 2nd and 3rd gear, otherwise I could tell you want gear it’s in. Steering seems nice and tight and still turns with ease. 
 

Going from a 5.3 gasser to a diesel and knowing how quiet they’ve made the diesels over the years I thought I would miss the exhaust note. However upon start up you can tell your driving a diesel as well as in the cabin you definitely know your driving a diesel with a nice exhaust tone. Not annoying as with the older trucks. 
 

I’m curious what maintenance costs will run in the future.I live in a highly agricultural area so diesel is only 10-20 cents higher, sometimes lower believe than 89 believe it or not. 
 

I’m sure I’ll find some displeasures as time goes on but right now I would buy out my lease if it expired tomorrow. 

  • Like 1
Posted (edited)

I just took delivery of a 21 AT4 6.2L Friday. There was only 1 within 200 miles of me. Hard to find around here. One local dealer said they didn't expect any until April 2021.

Edited by GMC207
Posted
9 minutes ago, GMC207 said:

I just took delivery of a 21 AT4 6.2L Friday. There was only 1 within 200 miles of me. Hard to find around here. One local dealer said they didn't expect any until April 2021.

Damn! April is along time away, that’s a lot of potential business lost. 

Posted
14 minutes ago, Crazypontiac03 said:

Damn! April is along time away, that’s a lot of potential business lost. 

I was kinda confused by that too...I asked if they had any in transit and he said no not til Spring....Maybe he was confused, sucks for him, just lost the sale of a 66,000 truck.

 

Posted
1 hour ago, GMC207 said:

I was kinda confused by that too...I asked if they had any in transit and he said no not til Spring....Maybe he was confused, sucks for him, just lost the sale of a 66,000 truck.

 

At least he didn't lose the sale of a 75k truck, he is probably selling plenty of bottom feeding 30k cuv's...

 

Tyler

Posted
10 minutes ago, amxguy1970 said:

At least he didn't lose the sale of a 75k truck, he is probably selling plenty of bottom feeding 30k cuv's...

 

Tyler

Not his fault though, if they don't have them they can't sell them...Is what it is.

Posted
On 10/27/2020 at 7:48 AM, GMC207 said:

I just took delivery of a 21 AT4 6.2L Friday. There was only 1 within 200 miles of me. Hard to find around here. One local dealer said they didn't expect any until April 2021.

Actually there are quit a few around Alberta. Mostly high end trucks, Denali's/High Country. At least a dozen at one of our Calgary dealers.  

Posted
23 minutes ago, Likarok said:

Actually there are quit a few around Alberta. Mostly high end trucks, Denali's/High Country. At least a dozen at one of our Calgary dealers.  

I don’t live near there, I was talking about near me.

Posted
1 hour ago, GMC207 said:

I don’t live near there, I was talking about near me.

Ordered one in late Sept, they built it about 4 weeks later.  

 

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