Search results

BC updates are done across many OTAs, most of which were the 6.x series. Most 22's should be up around 6.8 plus a few priority updates by now, but to my knowledge, no Lightning has gotten whatever the "final" BC 1.4 update will be yet (aka the one that actually turns on 1.4 features)...

I don't think it's the same cause as the Mach-E, but the symptoms are similar enough that those threads might be useful for diagnosis ideas. My suspicion is temperature throttling, either due to a real issue or a bad temp sensor. I would check the charge port for debris in case something is...

Original Mach-E thread on similar behavior: https://www.macheforum.com/site/threads/l2-charging-speed-recently-dropped-33.28779/ I believe this is the applicable TSB: https://www.macheforum.com/site/threads/tsb-24-2010-slow-level-1-or-level-2-charging-or-does-not-charge.33059/ Regardless...

That almost looks like power is reduced due to duty cycle, meaning the truck is throttling the power. Mach-E's had an issue last year where something similar happened, I believe due to a software update exposing a faulty temperature sensor near the charge port. I'll try and dig up that thread.

This queued up on my way to work today after getting 24-PU0105-CMR-FX yesterday. I'll install it when I get home. Keep 'em coming... Edit: installed after work with no issue.

Got this today also, successfully installed without issue. I got 6.8 in December but never got 6.13, for what it's worth.

It does show Tesla in Plug and Charge for the Lightning this morning, so it just took a while like you said. Strange delay but at least it's there now.

Got this update today also, and like others, Tesla does not show up under Plug & Charge for the Lightning in Fordpass. Oddly enough, my wife did not start her Mach-E today so it has not gotten the update, but Tesla does show up under Plug & Charge for the Mach-E. I'm not sure what to make of that.

Gotcha, so known issue with that app template being adapted from the MME. In that case, I would just ignore whatever input current it is reporting and instead calculate output current based on output kW divided by V. 11kW charger output being about 44.5A output current most likely indicates...

I'm not sure I would trust the data shown in those screenshots. ~11kW should be about 44.5A at 247V and 17.36kW should be about 71A at 244V, so either the kW displayed is wrong or the current displayed is wrong, or maybe it is only showing current draw from one of the two onboard chargers...

Yes, the truck is involved in limiting the current through communication with the EVSE on the pilot signal. I was just asking because it sounded like you were suggesting that Fordpass is communicating a limit to the truck directly and that should not be the case. It sounds like the current limit...

Again forgive my ignorance about how the FCSP works, but why would Fordpass tell the truck's charge controller anything? Shouldn't it communicate the max amp setting to the FCSP only?

Forgive me if this has been covered in other threads on this topic, but have you tried another L2 charger to see if the truck will request a higher rate? And do you know anyone with an EV that can try charging on your FCSP to see what happens? Those could help narrow down if the issue is with...

The EV version will be marked with "EV".

Those are the non-EV Open Country AT3's. The EV version is not out yet. Also the thread title should probably be "announced" rather than "released" as the first size will not be released until February (assuming no delays).

That info has been removed from their web site, but the original version of the site had a graphic that said the first size being released in February is LT275/60R20, aka a higher load range version of the stock Lariat size.

What a mess. Glad you got it working!

The Sync menu PAAK reset is the right way to do it. I think if the Sync menu's PAAK reset fails, it's because there aren't any existing keys. If you try the PAAK setup again and it fails, you should be able to do the Sync menu PAAK reset. Also make sure you remove any truck related Bluetooth...

Was the watch turned off or in airplane mode? If it was still turned on and close enough to be connected to your phone, you could still have the same problem I did. Also check for other bluetooth devices being on/connected to your phone like headphones, etc and disable them as well. Basically...

Not a bad theory but I believe Bluetooth does not assign fixed channels like wifi does, but rather dynamically hops between channels as RF conditions change over time. Similar to wifi, it's also a packet based protocol, so multiple devices sharing the same channel is not necessarily a problem as...