Jump to content

Recommended Posts

Posted (edited)

 

We're talking extended and crew cab midsize pickup trucks here (Colorado won't have a regular cab option)

 

Starting price on a REGULAR CAB Tacoma is $18, 125. Starting price on EXTENDED CAB Tacoma is $22,505.

 

Starting on the EXTENDED CAB Tacoma is $21,500 after delivery fee vs $20,995 for the Colorado after delivery is hardly competitive.

 

The reason why these trucks failed before was because you could by a comparatively trimmed full size for the same price or below, and the quality of the last gen colorado and canyons was a joke. They barely make good fleet vehicles.

 

I want these trucks to succeed just like everyone else, but why buy $30,000 top of the line colorado, when you can get a $30,000 mid to high level trimmed silverado for the same. Its the same crap that ran GM into the ground before.

Edited by DaveH71
  • Like 2
Posted

 

Starting on the EXTENDED CAB Tacoma is $21,500 after delivery fee vs $20,995 for the Colorado after delivery is hardly competitive.

 

The reason why these trucks failed before was because you could by a comparatively trimmed full size for the same price or below, and the quality of the last gen colorado and canyons was a joke. They barely make good fleet vehicles.

 

I want these trucks to succeed just like everyone else, but why buy $30,000 top of the line colorado, when you can get a $30,000 mid to high level trimmed silverado for the same. Its the same crap that ran GM into the ground before.

Exactly. GM never gets it. It's like they live under a pile of rocks or something.

  • Like 1
Posted

 

Starting on the EXTENDED CAB Tacoma is $21,500 ...

 

Toyota should use your starting prices. I'm looking at thier web page right now, and it still says $22,505 including delivery charge on a base stripped Access cab.

Posted

 

Toyota should use your starting prices. I'm looking at thier web page right now, and it still says $22,505 including delivery charge on a base stripped Access cab.

 

Its dependent on the region you select, the farther west you go the more expensive it gets. Try an east coast state, i used PA because that's where i live.

Posted

Considering the new GM full-size trucks (with options) will probably be in the high $40k to $50k+ range, this sounds like a bargain.

 

the Escalade is approaching $80K in the Platnium trim!

Posted

Wow I guess you get raped all the way around it doesn't matter if you go big or small, I'm leaning toward Ram for my next one.

Posted

Looks like the days of a reasonably priced vehicle from GM are long gone. :(

The days of a reliable one are too, so I'm not too broken up about the price. I WON'T be buying one. EVER.

Posted

As stated, the MSRP isn't the deciding factor. Incentives will make all the difference. I really like the looks of the new Colorado, but a Silverado for the same money (or just a couple grand more) is a no-brainer. The MSRP is inflated on all GM trucks (in my opinion) so a good incentive/rebate program might make these trucks worth looking at. Otherwise, I'll buy a HD gasser and have a whole lot more truck for the money.

Posted

Wow I guess you get raped all the way around it doesn't matter if you go big or small, I'm leaning toward Ram for my next one.

Ram has a good thing going price wise with the Express.

Posted

We're talking about midsize trucks here. Not the tundra.

 

Starting price on the Tacoma is $18,125.

 

Starting on the Tundra is $26,200.

FIND those trucks... they barely exist..... When I sold we couldn't get the basic ones.... in 2006 for example only 2.5% of Tacoma was RC 4x2 stick roll windows, etc.....

Posted

Here's what gets me.... people whine for small trucks... gm gives a small truck yet wants to be paid for it (and with inflation is in line with S10 pricing, and these trucks are way bigger and nicer with more safety ) and people say "I can buy a fullsize for that" Uh, yeah that's probably why they all quit selling small trucks...........

Posted (edited)

Ram has a good thing going price wise with the Express.

I see way too many rams with rusted out fender wells here in MI, no thank you!

Edited by Kenbow

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

    • 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. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...