Jump to content

2009 F150 Pic's And Info Has Been Released


cc1999

Recommended Posts

Posted

09f150_xl_3-4frtdrvr_as10925.jpg

 

The site I posted the link to must have pulled the info but here are a few extra pics.

Posted

I am partial to the new 09' Ram, myself, I am not really seeing much change at all in the Ford, and the high belt line and bedsides, are some what erarratating when actaually using the truck or getting stuff out of the bed.

ram3.jpg

dodge-ram.jpg

Posted

I think it would be kind of hard changing the sides of the truck, I mean what can you possibly do? and 06 07 ram looks nicer than the one above.

Posted

I diagree with the 08 ram vs the 09, I think that 09 is the best looking truck by far. I have an 08 Ram and this 09 is just awsome IMO.

 

As for what can be done with a bed side. This is picture of a new option on the 09 Ram.

2009-ram.jpg

 

Its similar to what the Avalanch has but bigger and more functional.

Posted
I diagree with the 08 ram vs the 09, I think that 09 is the best looking truck by far. I have an 08 Ram and this 09 is just awsome IMO.

 

As for what can be done with a bed side. This is picture of a new option on the 09 Ram.

2009-ram.jpg

 

Its similar to what the Avalanch has but bigger and more functional.

I really hope thats an option only because that would suck to lose out on that much bed space on the sides.

Posted

Its just an option, i think its also only available on the crew cab models. You can see in the pics of the blue sport model Ram that it does not have that option.

Posted

ok, we see Ford and Dodge, now where is the GM's?

The curent Fords still look better.

Dodge's feshening up the lights improves the exterior a bit, but still doesn't impress me too much. Is the grille angled forward for a more aggressive look, or is it just the pic angle?

Posted

Never been a Dodge fan, and I have been saying for the past year that the new F150 was going to leapfrog everyone. I am now thinking that the new Ram will be lead frog in 09. I like Ford's, but I do not like this new F150, I am disappointed to say the least. The 09 Ram is a sweet truck. It looks good and should perform good. That interior rivals the GMT900 LT/SLT interior. It looks like Dodge hit a home run with this truck, time will tell. But this much is for sure, with the 09 Ram and F150 coming out and the GMT900's out, the Tundra's stay in the spotlight is sure to be shortlived, heck, it's already being forgotten. Poor Toyota, all that effort and it still will be at the bottom of the pack.

Posted

f-150-1.jpg

 

King Ranch, looks awesome.

 

"The current 5.4-liter Triton V8 is getting replaced by Ford's new "Boss" engines that are expected to displace around 6.2 liters at the top end and around 5.4 to 5.6 liters on the low end. Expect horsepower numbers approaching 400 and similar levels of torque, as Ford wants to stay on top of Toyota's 5.7-liter V8. It delivers 381 hp and 401 pound-feet of torque through a six-speed automatic, so expect six gears in the Ford's automatic transmission as well."

Posted

gm's 6.2 replacing the 6.0 and the 6 speeds cant get here fast enough. or the baby duramax for that matter. competition, gotta love it. im interested to see how the coil sprung rear works for the dodge. and i actually like the front end on the new f-150. and those bedside ram bins are pretty cool.

Archived

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

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...