RJV15
Well-Known Member
- Joined
- Apr 17, 2023
- Threads
- 5
- Messages
- 502
- Reaction score
- 559
- Location
- Los Angeles
- Vehicle(s)
- 2022 Honda Civic Si
Same.Got 6.1 yesterday and 6.2 just finished installing...
First, thanks for sharing the VIN. Seems you like you've gotten 4 total updates, so there are more than 3 in total out there. The ABS update is 24-PU0201-NCNS-FX followed by 6.1.0, 6.2.0 and 6.3.2. I can see a lot. I have dealer access to PTS and FDRS.@rugedraw not sure whats going onand how much you can check online , but kind of weird that since taking my car to the dealership I've had two updates, a "steering fault" error, and somehow my speedo is now calibrated to my new wheels.
VIN: 1FA6P8CF1R5404130
Oh man, you're deep in the mainframe.First, thanks for sharing the VIN. Seems you like you've gotten 4 total updates, so there are more than 3 in total out there. The ABS update is 24-PU0201-NCNS-FX followed by 6.1.0, 6.2.0 and 6.3.2. I can see a lot. I have dealer access to PTS and FDRS.
![]()
The updates had nothing to do with your dealer visit. They didn't even connect the car to FDRS. The notes from your visit haven't been posted to PTS yet, so not sure why it was there or what they did, but for sure they didn't calibrate your speedo. Not sure FDRS is even capable of doing that. The updates you got were for the TCU and APIM which have nothing to do with the speedo, either. I see someone pulled your VIN the same way I did on 4/5 and again on 4/15, so I assume that was the dealer.
I'm even more confused about the steering fault error, because it didn't report any codes about that to the cloud. It reported a few soft codes (all cars do), but not that. The only time your car seems to have been turned on today was at 11am. No steering fault code reported. Since 4/5, your car started reporting a new soft code in the PSCM for improper shutdown performance. That is the only thing I can tie in to a steering fault. However, it is a soft code and there is no SSM, GSM or TSB referencing the code, so not sure why it starting reporting that or what is causing it. Is the steering fault error consistent, or was it an isolated incident? When did you take it to the dealer and why did you take it to them?
![]()
When I did the wheels/tires on my truck, I used FORScan to calibrate the speedo, and dealers don't use FORScan. Idk what to say about that, but the dealer didn't do it. The steering fault I would forget about. Unless it happens again, attribute it to a glitch in the matrix.Oh man, you're deep in the mainframe.
I took the car into the dealership for my first oil change on 4/5. The steering fault code was a one-time code that popped up 3 days after and has yet to pop up again. The car drove fine the whole time. As for the speedo, I guess it might have calibrated? The car was around 3 MPH off going 70mph when I installed my wheels and tires about 2 months ago but yesterday it was accurate.
I did have to reset the infotainment twice in the last week. Last couple of days the music keeps playing for around 5 seconds after I shutdown the car and open the door. I started the car up today around noon pst and the infotainment screen was blank so I reset it.
You got the same updates RJV got minus the ABS update, and you code is reporting a code for the ABS that his car used to have until he got the OTA, so I assume the reason for the OTA is to fix that code, but just an assumption. You do have an ABS update pending on the server, so you'll probably get that soon.@rugedraw can you run mine and see what’s all on there? 1FA6P8TH1R5122023
Had an error message not long ago on the screen but wasn’t able to catch what it was saying. Haven’t seen it since. Also screens are having issues since the update I got like a week ago per pass app
I have a few little things that I have found that bother me on the car but I’m sure they’re part of the car “learning” my driving. But the screen issues really bug me the most lolYou got the same updates RJV got minus the ABS update, and you code is reporting a code for the ABS that his car used to have until he got the OTA, so I assume the reason for the OTA is to fix that code, but just an assumption. You do have an ABS update pending on the server, so you'll probably get that soon.
Nothing obvious that I can see causing issues. To anyone here who is just getting a connected Ford vehicle capable of OTA's; welcome to the terror-dome. Brace yourselves. Growing pains are part of the process.![]()
Can you please check mine, Am not in the United States, mine is a Middle East version (Dubai).First, thanks for sharing the VIN. Seems you like you've gotten 4 total updates, so there are more than 3 in total out there. The ABS update is 24-PU0201-NCNS-FX followed by 6.1.0, 6.2.0 and 6.3.2. I can see a lot. I have dealer access to PTS and FDRS.
![]()
The updates had nothing to do with your dealer visit. They didn't even connect the car to FDRS. The notes from your visit haven't been posted to PTS yet, so not sure why it was there or what they did, but for sure they didn't calibrate your speedo. Not sure FDRS is even capable of doing that. The updates you got were for the TCU and APIM which have nothing to do with the speedo, either. I see someone pulled your VIN the same way I did on 4/5 and again on 4/15, so I assume that was the dealer.
I'm even more confused about the steering fault error, because it didn't report any codes about that to the cloud. It reported a few soft codes (all cars do), but not that. The only time your car seems to have been turned on today was at 11am. No steering fault code reported. Since 4/5, your car started reporting a new soft code in the PSCM for improper shutdown performance. That is the only thing I can tie in to a steering fault. However, it is a soft code and there is no SSM, GSM or TSB referencing the code, so not sure why it starting reporting that or what is causing it. Is the steering fault error consistent, or was it an isolated incident? When did you take it to the dealer and why did you take it to them?
![]()
Station break: Its because in your screen cap the cloud is disconnected and co-pilot (ai) is trying to take over. - we will now return to our regular program …First, thanks for sharing the VIN. Seems you like you've gotten 4 total updates, so there are more than 3 in total out there. The ABS update is 24-PU0201-NCNS-FX followed by 6.1.0, 6.2.0 and 6.3.2. I can see a lot. I have dealer access to PTS and FDRS.
![]()
The updates had nothing to do with your dealer visit. They didn't even connect the car to FDRS. The notes from your visit haven't been posted to PTS yet, so not sure why it was there or what they did, but for sure they didn't calibrate your speedo. Not sure FDRS is even capable of doing that. The updates you got were for the TCU and APIM which have nothing to do with the speedo, either. I see someone pulled your VIN the same way I did on 4/5 and again on 4/15, so I assume that was the dealer.
I'm even more confused about the steering fault error, because it didn't report any codes about that to the cloud. It reported a few soft codes (all cars do), but not that. The only time your car seems to have been turned on today was at 11am. No steering fault code reported. Since 4/5, your car started reporting a new soft code in the PSCM for improper shutdown performance. That is the only thing I can tie in to a steering fault. However, it is a soft code and there is no SSM, GSM or TSB referencing the code, so not sure why it starting reporting that or what is causing it. Is the steering fault error consistent, or was it an isolated incident? When did you take it to the dealer and why did you take it to them?
![]()
Based on previous experiences helping other people out in the UAE, I don't think you you guys are set up to receive updates there. Even with FDRS, it is a problem to get updates onto vehicles. Your modem appears as "not authorized", so for sure you're not getting any updates by OTA. I would recommend you call Ford Customer Care there and ask if you guys are able to receive OTA updates or not. I don't think so, though.Can you please check mine, Am not in the United States, mine is a Middle East version (Dubai).
Am so curious what it would give you, cause so far whenever i check for updates it says, none is available.
1FA6P8CF4R5413159
Thank you for taking the time to check.Based on previous experiences helping other people out in the UAE, I don't think you you guys are set up to receive updates there. Even with FDRS, it is a problem to get updates onto vehicles. Your modem appears as "not authorized", so for you sure you're not getting any updates by OTA. I would recommend you call Ford Customer Care there and ask if you guys are able to receive OTA updates or not. I don't think so, though.
![]()
Yea, you got all four known OTA's at the same time frames the few others I have seen got them. Like the others, you show a BCM and PCM update pending on the server. I'm sure the next OTA that gets pushed out will be for one of those two modules.Well, here’s my VIN but I’ve had 3 (or 4) updates that I can remember so far. Last one was 6.3.2 that included the 60th Anniversary Gauge cluster.
1FA6P8CF1R5411028