Jump to content

Ford introduces all new F-150

Zane

By Zane
in Future GM News & Rumors

Recommended Posts

Jsdirt Senior Enthusiast

Jsdirt

Posted
Posted

None of the shops that I know of locally are equipped to work on aluminum. Also, chatted with a guy from PA who said the same - he runs an autobody shop out there and explained the issues to me. You need an entirely different set of tools ($$$ - guess who will pay for that?), you cannot work on traditional panels near an aluminum vehicle and vice-versa ($$$ - for another bay/extra space), and you need self etching primer, which of course ... costs more.

 

I'm not the expert in that arena - he is.

 

Most guys that have been in the business will just stick with what they know, and refuse to work with aluminum .... which will drive the cost up even more as it becomes a niche market ... that is, until automakers force it upon us by building EVERY panel out of aluminum. I know the routine. The hell with stuff that worked for 100 years - gotta hurry up and make it "better".

  • Replies 57
  • Created
  • Last Reply
'01LS1 Senior Enthusiast

'01LS1

Posted
Posted

And they will go out of business. With so many aluminum hoods on current production cars/trucks they might as well offer 8-track player & sewing machine repair services to make up the lost cash flow.

 

Curiously wondering how many even know what an 8 track or sewing machine even looks like. :cool:

 

Not so worried about the aluminum panels in terms of collision repair, guess that will depend upon insurance rates. Hopefully Ford ran that past insurance companies as if premiums double, F150 sales will fall.

But lets say it is a wash, my concern would be more so the odd dent or a hail storm. Not sure what the paintless dent repair guys can do with it.

 

Edit: added video.

 

http://www.youtube.com/watch?v=GeMrvLb3QKA

Jsdirt Senior Enthusiast

Jsdirt

Posted
Posted

And they will go out of business. With so many aluminum hoods on current production cars/trucks they might as well offer 8-track player & sewing machine repair services to make up the lost cash flow.

Well he's working 80+ hours a week and can't find enough help .... so I don't see that happening anytime soon.

Jsdirt Senior Enthusiast

Jsdirt

Posted
Posted

Is everyone 15 years old on here or what? :nonod:

mawint Enthusiast

mawint

Posted
Posted

This world has proven time and time again... Adapt or die.

 

I have a feeling though that with the way the world is going, vehicles are more of a consumable item then a repairable item. As soon as it is broken, get rid of it. Sell it for scraps and move on.

Daryl LBZ Senior Enthusiast

Daryl LBZ

Posted
Posted
This world has proven time and time again... Adapt or die.

I have a feeling though that with the way the world is going, vehicles are more of a consumable item then a repairable item. As soon as it is broken, get rid of it. Sell it for scraps and move on.

 

Which is going suck. Hello to a lifetime of car payments.

  • 1 month later...
Aaron1085 Senior Enthusiast

Aaron1085

Posted
Posted

Same here...would love to drive one and they look BAD with some aggressive wheels on there. But very pricey and its a Ford...hmmmm

 

Sent from my DROID RAZR HD

Daryl LBZ Senior Enthusiast

Daryl LBZ

Posted
Posted

Same here...would love to drive one and they look BAD with some aggressive wheels on there. But very pricey and its a Ford...hmmmm

 

Sent from my DROID RAZR HD

 

 

Meh, I like your Sierra better.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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