2011 Mercedes-benz C300 on 2040-cars

Auto blog

F1 Race recap: 2016 Russian Grand Prix same as it ever was

The three-year-old Sochi Autodrom that hosts the Russian Grand Prix combines beautiful scenery with a hallmark turn 3, a tricky turn 13, and two long DRS zones. So far, however, those haven't added up to exciting races after the first lap. Despite an in-race issue with his car's MGU-K, Mercedes-AMG Petronas driver Nico Rosberg aced the weekend with his first career grand slam: pole position, fastest lap of the race, leading every lap, and victory. Behind him, not much happened on the leaderboard after an incident-filled opening lap. The drama started at turns 2 and 3. Ferrari driver Sebastian Vettel lined up in seventh on the grid because of a five-place gearbox penalty, Red Bull's Daniil Kvyat sat next to him in eighth. Kvyat hit the back of Vettel's Ferrari in the braking zone for Turn 2, shoving Vettel into Daniel Ricciardo – Kvyat's teammate. Kyvat then clobbered the back of Vettel's car at the entry to Turn 3, spinning the German into the wall and out of the race. Kvyat probably regrets saying before the race that he would show Vettel "no mercy" on the first lap. At the back of the grid at Turn 2, Haas F1's Esteban Gutierrez hit Force India's Nico Hulkenberg and Manor's Rio Haryanto. Gutierrez continued, both the Force India and the Manor retired. A brief Virtual Safety Car period ensued, then the actual Safety Car emerged for three laps while marshals cleaned up the track. Mercedes-AMG Petronas driver Nico Rosberg nailed the restart and took off for the rest of the race. Teammate Lewis Hamilton battled his own gremlins all weekend but still finished second, 25 seconds behind Rosberg. During the final qualifying session on Saturday Hamilton's car suffered the same MGU-H failure as in China two weeks ago. The problem relegated him to tenth on the grid. In the race, Hamilton fought his way to second place by Lap 19 out of 53 laps and began closing the 13-second gap to Rosberg. On Lap 37, the gap now under eight seconds, Mercedes told Hamilton his car had a water pressure issue. The malfunction forced the Briton to manage his race and settle for second. Afterward, Hamilton said he was certain he could have won if not for the malfunction. The rest of the top ten barely changed throughout the contest. The first five positions on Lap 21 crossed the finish line in that order 32 laps later. Ferrari's Kimi Raikkonen took the final podium position ahead of the Williams duo of Valtteri Bottas and Felipe Massa.

2015 Mercedes-Benz ML400 Quick Spin

Mercedes-Benz has taken a risk in its quest to downsize its engine range. For 2015, the brand's popular M-Class five-passenger CUV did away with its trusty 4.4-liter, twin-turbocharged V8, and has replaced it with a 3.0-liter, twin-turbocharged V6. It's no surprise that power is down thanks to this move. Outputs of 402 horsepower and 443 pound-feet of torque are replaced by 329 hp and 354 lb-ft, but weight is down significantly as well. The new ML400 is nearly 300 pounds lighter than the 4,982-pound ML550. Will that tradeoff be enough to satisfy a buying public that's embraced falling fuel prices by buying bigger and thirstier vehicles? To find out if the blown V6 is a suitable replacement for the twin-turbo V8, we spent a week at the helm of the all-new ML400. Driving Notes This 3.0-liter, twin-turbocharged V6 is the same engine being offered in the C400 and E400 sedans. Typical of today's turbocharged engines, peak torque is spread lavishly across the rev range, from 1,600 to 4,000 rpm. That's not as generous a spread as the ML550, which offers all its torque between 1,600 and 4,750, but the power on offer is easy to access. Importantly, the new V6 never feels flat-footed or unable to answer our commands. In fact, the ML400 feels even quicker than its six-second sprint to 60 would indicate, although it's not so fast as to challenge the 5.3-second time of the ML550. After a slight and expected bout of turbo lag, the power arrives suddenly and proceeds linearly until just south of the engine's 6,500-rpm redline. The throttle response is soft in Eco mode, as expected, but sharpens up slightly when the fuel-sipping mode is off, where the gas pedal is still easy to modulate. It's a quiet engine, too. Compared to the brawnier exhaust note of the old ML550 or the howling six-cylinder in the BMW X5 xDrive35i, the ML400's note is smooth and refined, befitting of a V6. Its turbocharged nature is instantly noticed, though. Get on the throttle and the 3.0-liter happily hisses its way up the tachometer. But, it's only when you get on the throttle hard that the engine really weighs in. In day-to-day driving and traffic its soundtrack is unobtrusive and relaxed. The EPA rates the ML400's fuel economy at 18-miles-per-gallon city and a 22-mpg on the highway. That's better than the 14 city and 19 highway of the old V8 ML, but it still seems a bit low, especially for the highway figure.

Mercedes F1 to use Qualcomm 5 GHz WiFi for its tire data

In Formula 1 you need more of everything. More speed, more grip, more hospitality, more money. And you need data, reams and reams of data. The Mercedes-AMG Formula 1 team – the guys with the silver cars driven by 2015 F1 champion Lewis Hamilton and his teammate Nico Rosberg – need so much information that they've teamed with Qualcomm to wirelessly upload thermal imaging data of its tires. During a typical race weekend Mercedes's two racecars will generate approximately half a terabyte of data. Live telemetry has been a feature of Formula 1 for 20 years, though there are more restrictions on it than in the past. (In the days leading up to last weekend's United States Grand Prix in Texas, Formula 1 major domo Bernie Ecclestone said that F1 needs to cease being an engineering war and return more responsibility to the drivers.) Nevertheless, F1 teams gather vast amounts of data during a race weekend, particularly in practice sessions during which restrictions on what they can upload from cars – from engine/power unit parameters to aerodynamic loads – are less prohibitive. For example, during a typical race weekend Mercedes's two racecars will generate approximately half a terabyte of data. Mercedes F1 technical director Paddy Lowe points out that the standard telemetry system simply doesn't have the bandwidth to handle the thermal tire imaging data that the onboard thermal cameras generate. Why do you want a thermal video of the tires? Because it tells the engineers and drivers precisely how much temperature there is across the surface of a tire during a lap, in corners and on the straights. It also indicates how quickly the tires come up to temperature and when they potentially overheat. Understanding the temperature variations allows the team to set the cars up optimally for grip and tire life during a stint. Qualcomm's system works with the race cars like this: Each car has forward- and rear-facing cameras in a winglet mounted on the left side of the engine intake behind the driver's head, which continuously record thermal images of the tires. As a Mercedes enters the pit lane, it passes a Qualcomm 802.11ac WiFi receiver to which it uploads the thermal data. As the car nears the garage, another receiver takes over the upload. Several Qualcomm Snapdragon 805 processors crunch the raw data as it uploads. The data is encrypted – there are always prying eyes in Formula 1.