1971 Ford F250 Highboy 4x4 Nice A Must See. 60+ Pictures on 2040-cars

Auto blog

Shelby GT500 laps N"urburgring in under 7:40?

A couple of weeks ago we brought you footage and official times of the new Chevy Camaro Z/28 lapping the Nürburgring. With a 7:37.47 lap time, the Z/28 emerged as the fastest muscle car ever to lap the circuit. But what was missing from that picture was how fast the king of all Mustangs, the Shelby GT500, could manage to lap the Nordschleife.
Ford never released any information or footage of the GT500 on the Nürburgring that we were aware of - that is, until the guys at SVTPerformance.com put in a request for Mustang videos. Among the clips they received was never-seen, in-car footage of the Shelby GT500 lapping the circuit. And boy did it hustle.
Although not quite official, the video seems to show the GT500 lapped the venerated German track in a touch under 7:40. That would make it a tick or two faster than the Camaro ZL1 - but what of the Z/28? By Chevy's quoted time, the Z/28 is still faster than the GT500, but SVTPerformance suggests GM may have fudged the numbers a bit and scrubbed half a second or so off their lap time.

Major Alexa deal will bring Amazon services into more cars

Amazon and its personal assistance service Alexa are partnering with HERE Technologies to create a new connected mobility service powerhouse. Alexa will integrate with HERE's navigation and location services to offer what the two companies are calling a "true voice-first-navigation experience." Alexa will come pre-integrated with HERE navigation on-demand, which the automakers can then enable, which should help cut down on development time. One of the biggest features from this partnership is how directions could be offered and delivered using HERE's Open Location Platform (OLP). Currently, the OLP uses data from several car manufacturers to provide insights into real-time location and traffic. But on Alexa, this could be used to provide directional context. For example, Alexa could say, "Turn right after [such-and-such a building]" rather than just, "Turn right." Amazon has been testing the automotive waters throughout the past decade. Its home-based Alexa-enabled devices are already offered with connections to several manufacturers. To various degrees of integration, it can already pair with Ford, Genesis, Toyota, Lexus, Hyundai and BMW vehicles. At the end of 2018, Amazon took things a step further when it introduced the Echo Auto, a Bluetooth-connected Alexa assistant device that can be physically kept in a car. Currently only available by invitation (its production and distribution have been delayed), the $25 device is essentially a voice service that works together with smartphones and connects to a car's speakers. Users can command it to do a variety of things, including playing music, setting navigation, opening the garage door, finding local stores, making calls, setting reminders, and thousands of other "skills." According to The Verge, nearly 1 million people have already ordered the device. Some (well, probably few) may know HERE Technologies from its maps on Windows Phones. We all know how that turned out, though. Today, HERE has expanded into a multi-function suite that is available in multiple mediums, including many automotive applications. HERE Automotive's connected vehicle services include real-time traffic, parking, weather, fuel prices, hazard warnings, traffic sign integration, and even EV charging stations. These all incorporate and extend the use of HERE's location and tracking programming. HERE is already partnered with BMW, Audi, Daimler, Intel, Mobileye, NVIDIA, and has investments from Bosch, Continental and Pioneer.

Ford made three big mistakes in calculating MPG for 2013 C-Max Hybrid

It's been a rough time for the official fuel economy figures for the Ford C-Max Hybrid. When the car was released in 2012, Ford made a huge deal about how it would beat the Toyota Prius V, which was rated at 42 combined miles per gallon, 44 city and 40 highway. The Ford? 47 mpg across the board. How did Ford come to this place, where its Prius-beater turned into an also-ran? Well, after hearing customer complaints and issuing a software update in mid-2013, then discovering a real problem with the numbers last fall and then making a big announcement last week that the fuel economy ratings of six different 2013 and 2014 model year vehicles would need to be lowered, the C-Max Hybrid has ended up at 40 combined, 42 city and 37 highway. In other words, the Prius trumps it, as daily drivers of those two vehicles have known for a long time. The changes will not only affect the window sticker, but also the effect that the C-Max Hybrid (and the five other Ford vehicles that had their fuel economy figures lowered last week) have on Ford's compliance with greenhouse gas and CAFE rules for model year 2013 and 2014. How did Ford come to this place, where its Prius-beater turned into an also-ran? There are two technical answers to that question, which we've got below, as well as some context for how Ford's mistakes will play out in the bigger world of green vehicles. Let's start with Ford's second error, which is easy to do since we documented it in detail last year (the first, needing to do a software update, was also covered). The basic gist is that Ford used the general label rule (completely legally) to test the Fusion Hybrid and use those numbers to figure out how efficient the C-Max Hybrid is. That turned out to be a mistake, since the two vehicles are different enough that their numbers were not comparable, despite having the same engine, transmission and test weight, as the rules require. You can read more details here. Ford's Said Deep admitted that the TRLHP issue is completely separate from the general label error from last year. Now let's move on to last week's announcement. What's interesting is that the new recalculation of the MPG numbers – downward, of course – was caused by a completely separate issue, something called the Total Road Load Horsepower (TRLHP). Ford's Said Deep admitted to AutoblogGreen that the TRLHP issue had nothing to do with the general label error from last year.