98-04 2001 Mercedes-benz Slk230 Kompressor Hardtop Convertible Low Miles Cheap! on 2040-cars

Auto blog

Smart brand will be built in China as a Daimler-Geely joint

FRANKFURT/BEIJING — Daimler will build its next generation of Smart electric cars in China through a joint venture with Geely, as a way to increase economies of scale in a market segment that is struggling to turn a profit. China's Geely built a stake of almost 10 percent in Daimler last year, saying it wanted to forge an alliance to develop electric and self-driving cars to better compete against new challengers such as Uber and Google. Daimler said on Thursday it would build the next generation of Smart-branded city cars at a purpose-built factory in China, and planned to share its expertise in manufacturing, engineering and design with Geely. The high cost of electric car batteries has made it hard for automakers to build affordable zero-emissions vehicles, leading several of them to strike alliances with Chinese partners. Daimler's German rival BMW recently unveiled plans to build electric Minis in China, where production costs are low and demand for small electric cars is rising. Daimler and Geely did not disclose financial terms of their deal. The details of the joint venture will be finalized by the end of 2019, they said in a joint press release. Daimler currently develops and builds Smart cars with Renault at factories in France and Slovenia. The Daimler factory in Hambach, France, will be retooled to build Mercedes-Benz cars. Geely has been expanding rapidly through mergers and acquisitions since 2010, when it acquired Swedish carmaker Volvo from Ford. Last year, Daimler and Geely set up a ride-hailing joint venture in China. Daimler's Chief Executive Dieter Zetsche said last month the German carmaker was in talks to deepen its alliance with Geely after the Chinese's group's chairman Li Shufu bought a 9.69 percent stake in Daimler in 2018.

Mercedes Concept GLA45 AMG is ready to run

This is the Mercedes-Benz Concept GLA45 AMG, and what we mean by that is, "This is the Mercedes-Benz GLA45 AMG." Mercedes has just unveiled the liveried 'concept' at the 2013 Los Angeles Auto Show, giving potential customers a very good look at the newest lunatic in the AMG asylum - a 355-horsepower, 332-pound-foot crossover that uses the same 2.0-liter, turbocharged four-cylinder engine found in the CLA45 AMG and Europe's A45 AMG.
Joined with a seven-speed, AMG Speedshift dual-clutch transmission and an AMG Performance 4Matic all-wheel-drive system, Mercedes promises a sub-five-second run to 60 miles per hour. That's not just quick for a crossover, that's quick full stop.
That sleek, lifted body has also been tweaked by the minds at AMG's Affalterbach facility. A new rear spoiler, side sills and front clip are the primary aerodynamic tweaks. Aesthetically, AMG has fitted the requisite "Turbo" badges, gloss-black accents (including exhaust tips and roof rails) and a set of 21-inch, AMG-spec alloy wheels to round out the overall package. Based on the spy shots we've seen, expect slightly toned down aerodynamics when the GLA45 AMG arrives in showrooms.

2014 Mercedes SL and SLK add small expansion to Takata airbag recall

Mercedes-Benz is the latest automaker to be affected by Takata's massive airbag recall. The company has announced a voluntary recall campaign on a small number of model-year 2014 SLK- and SL-Class roadsters.
In Mercedes' case, 300 vehicles are affected, 200 of which are in the hands of customers. According to spokesperson Donna Boland, the affected roadsters were built between March and April of this year.
The issue, which is apparently the fault of one of Takata's subcontractors, rests with some improperly installed fasteners, which could keep the airbag from performing the way it's supposed to. According to Boland, Mercedes isn't sure what, if any, injuries the recalled airbags could cause, but simply claims there's an increased risk in these particular vehicles. There's been no reported instances of the faulty airbags deploying on a customer and the original issue was found in a production test.