Fisker Ocean Forum banner
41 - 60 of 94 Posts
I don’t know who is right?, who to trust? ….FOA, Fisker or others?

This is what Fisker states about the 2.2 (Sept.9th) to do:
19. When will my Fisker Ocean receive the OS 2.2 update?
- Updates are typically delivered over-the-air (OTA), and the timing may vary. You will receive a notification when the update is available for your vehicle.”
1. Preparation Before Download

Stable Internet Connection

: Ensure your vehicle is connected to a reliable Wi-Fi network or a strong mobile data connection. Interruptions during download can cause issues in the installation process.
Sufficient Battery Charge
: Make sure your vehicle’s battery has a sufficient charge before beginning the download. It’s ideal to perform the update when your vehicle is plugged in or charging.”
2. During the Download Process
Monitor the Progress

: Pay attention to any notifications or progress updates on your vehicle's infotainment screen. Avoid turning off the car or disconnecting it from the internet during the download.
Avoid Interruptions
: Keep the vehicle parked in a stable environment to avoid movement that might cause any connection disruptions.”
3. During the Installation Process
Follow On-Screen Instructions

: The vehicle’s infotainment system will likely prompt you to start the installation. Follow the instructions carefully, ensuring you agree to any terms and conditions if necessary.
Do not Interrupt the Process
: Once the installation starts, do not switch off the vehicle or use any other features unless explicitly allowed by the system. Interrupting the installation could cause software issues.
Allow Time for Completion
: Be patient, as installation times may vary depending on the size of the OS update and your vehicle's hardware.….…………..
5. Troubleshooting
Error Handling

: If the installation fails or you experience issues, refer to the Fisker user manual for troubleshooting tips.
Contact Fisker Support
: If you encounter a significant issue or experience repeated update failures, contact your nearest Fisker authorized service provider for assistance.

So, who do you trust?…. FOA or Fisker instructions? …am I dreaming?🛌 ….aren’t kind of…opposite?
(one is don’t plug it in…the other keep it plugged in????)
I am going to plug 🔌 it in right now….I hope I don’t have to “Contact Fisker Support”!!!
 
I did test V2L and it works with normal household items. Attaching an L1 EVSE and charge my Tesla is on my to-do list - along with disconnecting the front emblem lighting adapters and seeing if there is a difference with the lighting update.
I stopped by New Port Fisker yesterday and talked to the owner who had some FO's updated with 2.2. We did some test trying to charge another FO with 2.2 and a different EV (Nissan Ariya), but it didn't work - The charger light was green indidating it was ready but couldn't switch to charging state.
Image
Image
Image
 
I have yet to drive my Ocean since the 2.2 update. Here's what I'm seeing.

After installation, I noted that the HV charger remained plugged in, but I went to the car in the morning, and SoC was 252 miles. I had lost over 50 miles of range during the update. Ok, I said: we were warned that it consumes alot, so I had maintained the charge (85% setting) at 304 miles.

I noted that it would not enter a charging state after unplugging and reconnecting the HV charger - saying 'fully charged' at 252 miles - so I removed it; locked the car, and plugged it in again the following morning, at which point it accepted the charge connection and began charging, and achieved full charge of 304 miles. I left it that way.

Next morning (today), I looked at Soc: 252 miles again. It depleted 52 miles of range again, just sitting there, in one day. Unplugging/plugging back in: same problem: "fully charged". I unplugged it and am waiting for deep sleep. I also checked Soc on the 12v battery when I unplugged the HV charger: 12.3v.

Something bad is going on. I don't feel comfortable driving this POS yet.

Question:

Does this thing have to be LOCKED in order to avoid a depletion of over 50 miles of range overnight? Why doesn't this sorry software realize a drain is happening, and reactivate HV charging, if the HV charger remains plugged in?? It hasn't before, but it's always managed to 'sleep' with the HV charger plugged in and the car unlocked in the past. Now, on 2.2, it doesn't seem to - and I'm not sure things will change if I lock it regardless.

This is very irritating. These software devs are clearly not sufficiently competent.
 
The car needs to be locked whenever it is parked or it never shuts off…. That’s been discussed somewhere on these forums.
I have yet to drive my Ocean since the 2.2 update. Here's what I'm seeing.

After installation, I noted that the HV charger remained plugged in, but I went to the car in the morning, and SoC was 252 miles. I had lost over 50 miles of range during the update. Ok, I said: we were warned that it consumes alot, so I had maintained the charge (85% setting) at 304 miles.

I noted that it would not enter a charging state after unplugging and reconnecting the HV charger - saying 'fully charged' at 252 miles - so I removed it; locked the car, and plugged it in again the following morning, at which point it accepted the charge connection and began charging, and achieved full charge of 304 miles. I left it that way.

Next morning (today), I looked at Soc: 252 miles again. It depleted 52 miles of range again, just sitting there, in one day. Unplugging/plugging back in: same problem: "fully charged". I unplugged it and am waiting for deep sleep. I also checked Soc on the 12v battery when I unplugged the HV charger: 12.3v.

Something bad is going on. I don't feel comfortable driving this POS yet.

Question:

Does this thing have to be LOCKED in order to avoid a depletion of over 50 miles of range overnight? Why doesn't this sorry software realize a drain is happening, and reactivate HV charging, if the HV charger remains plugged in?? It hasn't before, but it's always managed to 'sleep' with the HV charger plugged in and the car unlocked in the past. Now, on 2.2, it doesn't seem to - and I'm not sure things will change if I lock it regardless.

This is very irritating. These software devs are clearly not sufficiently competent.
 
Next morning (today), I looked at Soc: 252 miles again. It depleted 52 miles of range again, just sitting there, in one day. Unplugging/plugging back in: same problem: "fully charged". I unplugged it and am waiting for deep sleep. I also checked Soc on the 12v battery when I unplugged the HV charger: 12.3v.
The adjustment to the miles remaining is part of the update. You're not experiencing battery drain. They changed the calculation from the original based on EPA numbers to one based on actual driving. So you will see the miles remaining increase or decrease depending on real usage. For example, with my recent driving, a 100% SOC is not around 345 for me vs the original 360 miles.

And yes, it's always been a good idea to keep the car locked. Unnecessary battery drain too.
 
The adjustment to the miles remaining is part of the update. You're not experiencing battery drain. They changed the calculation from the original based on EPA numbers to one based on actual driving. So you will see the miles remaining increase or decrease depending on real usage. For example, with my recent driving, a 100% SOC is not around 345 for me vs the original 360 miles.

And yes, it's always been a good idea to keep the car locked. Unnecessary battery drain too.
Ok, I locked it. 3 hours ago. The HV charger is not plugged in, but the blue LED remains on.

It is not going into deep sleep.

When it read 252 after the update, I put it on the HV charger after letting it alone overnight, and it DID get to 304 miles of range on the 85% setting. Why did it do that if what you're saying is correct?

The range is now 246, and it still will not accept a charge, because the blue led means that whatever needs to be reset in deep sleep to allow charging has not happened - same as I experienced immediately after the 2.2 update.
 
When you see 252 miles, what was the battery percentage (SOC)? I don't think you stated that in the original post.
So I just went out there and looked: 244 range; 84% SoC. So, because it wasn't 85%, I plugged it in - and it accepted charging.

So, in fact, you're totally correct: the 2.2 update monkeys with the SoC/etc, so I didn't in fact lose 50 miles of range; I lost the previously inaccurate calculation of what 85% SoC looks like (previously 304, which never actually happened in practical application).

Thanks for that.

That leaves two questions:

1. Why did it accept charge the very first time I attempted to charge it when I realized it was at 252 range, and got up to 304 again, only to do the same thing? I presume some glitch.

2. Why is my blue LED not extinguishing fairly shortly after I lock the car and walk away, to enable deep sleep?

I'm going to drive this thing around the circle of my block for quite a while before I feel comfortable taking it out on a drive. I do NOT want to have to tow it again.
 
41 - 60 of 94 Posts