Skip to main content

CES 2017 - Faraday Future and the FF91

Faraday Future (FF) unveiled their FF91 electric car at CES 2017 in Las Vegas this past week.



Some of the highlights from their presentation:
  • 2.39s 0 - 60 mph, faster than the Tesla Model S P100D
  • 130 kW battery (Tesla's largest is 100 kWh)
  • Autonomous driving. And they demoed parking in this video:

Here is their booth on the floor of the show:


There were quite a few FF employees attending the show. Normal attendees were kept away from the car but some people were let inside of the area and able to get up close and take a look at it.

My take on Faraday future

I'm an engineer and an owner of a Tesla Model S. I'm also an investor in Tesla. I'm not skeptical of FF because they are competing with Tesla or claim to be building a better car. There is plenty of room in the EV market for well built vehicles. Due to the growth in the EV market FF could sell tens of thousands of vehicles per year without much impact on Tesla's sales. I'm a fan of EVs, especially great ones, but the FF91 is almost entirely vaporware.

Today batteries represent a significant cost of any EV. How are they able to achieve their claimed battery density improvements? Global battery sales are in the tens of billions and huge amounts of money have and continue to be spent on improving battery technologies. FF is working with LG Chem on their batteries but so far the details of their battery density claims have been sparse.

The 0-60 mph numbers of the FF91 seem pretty clear, FF has shown video and in person demonstrations of the FF91 going up against several very fast production cars on a drag strip. Are they changing the motor gearing, sacrificing top speed for better 0-60 numbers? Is the car's weight representative of the production vehicle or are they improving performance by removing parts of the interior or other car systems? Are they pushing the batteries to levels that could impact long term reliability?

Self driving is becoming an almost must-have feature for a car company to be working on. FF showed some self driving capabilities at CES, having their car drive and park itself. There haven't been any on-road demonstrations of their systems. They also had an issue with self driving during their CES presentation. The company ended up dimming the lights on the stage and having a person get into the car to drive it. The FF91 being shown is a prototype, a glitch during the show, while embarrassing, isn't entirely unexpected.

I'd recommend being skeptical of FF's claims at this point, and like the story below, I'd recommend NOT giving FF a $5,000 deposit. We should know a lot more in a years time. Their factory should be under heavy construction, some details of how they are achieving their improvements may start to become public, and they may start to let people drive and review prototypes of their cars.

Another great take on FF

The video as a part of this article is an excellent overview of the recent history of the company and some of its trouble.


Labels:

Comments

Post a Comment

Popular posts from this blog

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr...
5 comments
Read more

Travelling on Spirit airlines out of Boston Logan airport? Here are some tips.

I attended CES 2017 in Las Vegas. Booking the trip late I ended up on Spirit airlines. It was both non-stop, making it six hours to Las Vegas from Boston, and affordable, less than $300 for a one way trip compared to around $700 with JetBlue. Here are some tips that might help you when travelling on Spirit from Boston Logan airport. Eat Spirit is located in the B-terminal, gates B-37 and 38, with its own TSA security checkpoint. While it does have restrooms and places to sit the food selection is limited to a single food stand. I'd recommend eating at the Legal C Bar (number 77 in the image below) prior to going through the terminal security checkpoint. The food and service there were great. Drink The water and other drinks are cheaper if you buy them at the food cart rather than on the flight. Seats The seats on Spirit don't recline. They do this to reduce weight, seat cost, seat maintenance costs, and so seats don't impact the free space of other passengers,...
3 comments
Read more

Yocto recipe SRC_URI for a BitBucket / GitHub ssh git repository

This is a particularly geeky post but because Google searches didn't turn up any information I thought it would be helpful to document the issue and solution for others. I was writing  Yocto recipes that pulled from BitBucket git repositories in ssh form and ran into several issues getting a SRC_URI that worked. GitHub uses the same syntax for their ssh repositories. A BitBucket / GitHub git url, in ssh form, looks like: < username >@bitbucket.org:< account name >/< repository name >.git a more concrete example for a git repository in one of my BitBucket accounts looks like: git@bitbucket.org:cmorgan/somerepository.git Yocto recipes can pull from git repositories by setting the SRC_URI variable appropriately. Unfortunately you can't just do: SRC_URI = "git@bitbucket.org:cmorgan/somerepository.git You'll get errors because the Yocto won't know what kind of url this is. You need to specify the protocol for Yocto to k...
2 comments
Read more