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.


Comments

Popular posts from this blog

UTM (qemu on OSX) only boots into uefi shell after installing Ubuntu 22.10 (solved!)

I've been meaning to try out running Linux and Windows virtual machines on my x86 MacBook Pro using qemu . I've been using Parallels for several years. Parallels is a nice application and works well but I'm always getting bugged to purchase upgrades. Parallels provides free updates on minor version upgrades only, say 13.0 to 13.1. With so many prompts to purchase upgrades it feels like Parallels could release a bit more minor versions and a bit fewer major versions. Rather than just purchase an upgrade to Parallels I figured I'd try out qemu via the UTM application . UTM wraps qemu with a helpful gui and comes as a packages Mac application. And UTM supports both x86 and M1 systems (as qemu also supports these systems). Creating an Ubuntu VM with UTM didn't go as smoothly as with VirtualBox or Parallels but it was the settings I chose that messed me up. Here are two things I ran into when installing Ubuntu on UTM. #1. Configure the qemu instance to use a 'Display...

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...

Graco Swing By Me - Battery to AC wall adapter modification

If you have one of these Graco battery powered swings you are probably familiar with the cost of C batteries! The swing takes four of them and they only last a handful of days. I'm not sure if the newer models support being plugged into the wall but ours didn't. If you are a little familiar with electronics and soldering, here is a rough guide on how you can modify yours to plug in! I wasn't sure how exactly to disassemble the swing side where the batteries were. I was able to open up the clamshell a bit but throughout this mod I was unable to determine how to fully separate the pieces. I suspect that there is some kind of a slip plate on the moving arm portion. The two parts of the plastic are assembled and the moving arm portion with the slip plate is slid onto the shaft. Because of the tension in that slip plate it doesn't want to back away, and because of the mechanicals that portion of the assembly doesn't appear accessible in order to free it. I was...