Connect with us

News

Tesla Model S and X owners face discrimination at dealer-run auto show

(Photo: James Ransom/The Drive)

Published

on

A number of Tesla owners are calling foul on the organizers of the 2019 Kansas City Auto Show after the event’s organizers, the Automobile Dealers Association of Greater Kansas City (ADAKC), showed discrimination against a Model S and Model X by forcing the electric cars out of the event.

The annual exhibition is being held at the Bartle Hall convention center, and since the auto show itself did not fill the entire venue, the ADAKC allocated the south end of the exhibit hall to the Kansas City Auto Museum. The museum reached out to the local auto enthusiast community to look for volunteers who wish to display their vehicles as part of the event. Numerous locals answered the call, bringing their cars over to be part of the show. Among these vehicles were a Tesla Model S and Model X.

Tesla enthusiast James Ransom prepared the two electric cars for the auto show, dropping them off at the exhibition’s location. The next day, he received a call from the event’s organizers informing him that the Teslas are not welcome in the event. Ransom explained the circumstances in a statement to The Drive.

“I was called on Wednesday evening and asked to remove the Teslas. I was told that the cars were not allowed to stay because they were not part of the Dealers Association. Something about a higher-up in the association who said that the Teslas could not be at the show due to the manufacturer not using dealerships for their sales,” Ransom said.

(Photo: James Ransom/The Drive)

Fellow Tesla owner and prominent Kansas-based auto enthusiast Ken Smiley, whose 1956 Jaguar XK140 and 2016 Porsche GT4 are on display at the show, noted in an email to Teslarati that the ADAKC’s excuse for the removal of the two electric cars was questionable at best. Smiley mentioned in an email that there were several other vehicles on display from manufacturers who were not part of the ADAKC, such as Noble, Pontiac, Ariel, and Lamborghini. All these vehicles were welcomed and allowed to remain.

To address the situation, Ken sent an email to the organizers, calling them out on the discriminatory practice. Below is the Tesla owner’s email in full.

Dear Larry and Natalie,

It has come to my attention that a particular make of automobile is being singled out for unfair discrimination at the KC Auto Show this year and that the owners of these cars were asked to remove them from Bartle Hall. The vehicles in question were two used Tesla automobiles owned by private individuals and put on display as part of the KC Auto Museum’s variety of cars display at the KC Auto Show. As an officer/member in multiple car clubs in Kansas City (Porsche, Jaguar, All British, Tesla) I find this action reprehensible and urge you to immediately reconsider your actions before something like this goes viral and brings negative publicity to the car show.

Advertisement
-
-

I understand that with regard to NEW cars that Tesla does not have a dealer network and does not participate in the Automobile Dealer Association of Greater Kansas City. I would understand if your association told Tesla that they could not bring new cars down and could not be represented at the show unless they joined the organization. However, this is NOT what is happening in this instance. These two cars are privately owned used cars brought by their enthusiastic owners to help support the KC Auto Museum display at the auto show. There were owners who brought Pontiacs, a Noble, a couple of Ariel Atoms and Lamborghinis ALL of which are NOT members of the ADAKC. So if you are going to discriminate against non-members, then you need to do it equally and ask that ALL non-member cars leave the show, not simply single out Tesla.

Please let me know whether or not the Teslas are welcome to come back or if the unfair discrimination against these owners and their vehicles is going to continue. Speaking of the owners, the people you are hurting are automotive enthusiasts, not the audience you want to hurt. These individuals took their time to clean up their cars and transport them down to Bartle Hall only to be told a few hours later that they had to take them back out. While I currently have two cars on display at the show (1956 Jaguar XK140 and 2016 Porsche GT4) I am not sure that I will be willing to support a show in the future that unfairly discriminates against a certain model car. I hesitate to think how Marion Battaglia would react if I told him that either my Jag or Porsche was being discriminated against and being asked to leave the show. As I mentioned, this unfair discrimination isn’t hurting Tesla the car company, which the association may have an issue with, but rather hurting individual automotive enthusiasts.

Sincerely,

Ken

The auto enthusiast notes that the ADAKC has not responded to his email yet. Due to the incident and the blatant act of discrimination, Ken notes that numerous car fans and Tesla owners are boycotting the event to show their frustration at the organizers. An ADAKC spokesperson did issue a statement to The Drive, but based on the organization’s stance, it appears that they are putting the blame on the offended Tesla enthusiasts.

“This is a non-story. Ken Smiley is simply bringing this up because he seems to be angry and wants to stir the pot,” the spokesperson said, adding that the two Teslas do not fit the “Classic Car” theme of the exhibition. When pressed by the publication why other modern vehicles from non-ADAKC members, such as Ariel Atoms and Lamborghini Huracans, were allowed to remain, the spokesperson was less certain, stating that they “had to talk to the show’s producer.”

The 2019 Kansas City Auto Show was held from March 6-10, 2019.

Advertisement
-
-

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

on

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Continue Reading

Elon Musk

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading

News

Elon Musk reveals SpaceX performed secret Starship test on Flight 13

Published

on

Credit: SpaceX

SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.

Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.

All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.

However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.

Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:

SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.

Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.

The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.

Continue Reading