Topic Sponsor
2015 - 2020 Ford F150 General discussion on the 13th generation Ford F150 truck.
Sponsored by:
Sponsored by: Worksport

Adding Front Camera to XLT

Thread Tools
 
Search this Thread
 
Old May 18, 2017 | 10:53 AM
  #681  
Lurch96's Avatar
5 Year Member
5 Year Member
Liked
Loved
 
Joined: Sep 2016
Posts: 130
Likes: 18
Default

Zxlr88,

What exactly were the problems you were having after the 4-1-17 software update? I've noticed that since doing that update, my 8" screen will sometimes be blank.

About 40% of the time when I start my truck, the screen is black. No Ford logo, nothing. It is completely dark and unresponsive for the rest of the trip. If I turn the truck off for 5-10 minutes, the screen usually works normally. This didn't happen prior to the Rostra software update.

The good news is that if the screen does turn on, the cameras seem to work without issue. I'll contact Rostra today about the push-to-start update but I just wanted to see if this is an issue that others are having. Thanks!
Reply
Old May 19, 2017 | 09:50 AM
  #682  
Zxlr88's Avatar
Senior Member
 
Joined: Apr 2011
Posts: 218
Likes: 39
Default

Originally Posted by Lurch96
Zxlr88,

What exactly were the problems you were having after the 4-1-17 software update? I've noticed that since doing that update, my 8" screen will sometimes be blank.

About 40% of the time when I start my truck, the screen is black. No Ford logo, nothing. It is completely dark and unresponsive for the rest of the trip. If I turn the truck off for 5-10 minutes, the screen usually works normally. This didn't happen prior to the Rostra software update.

The good news is that if the screen does turn on, the cameras seem to work without issue. I'll contact Rostra today about the push-to-start update but I just wanted to see if this is an issue that others are having. Thanks!

Those are definitely the same problems I was having.
Reply
Old May 19, 2017 | 09:59 AM
  #683  
Zxlr88's Avatar
Senior Member
 
Joined: Apr 2011
Posts: 218
Likes: 39
Thumbs down

Update:

SO after running the push to start update for a couple of days, it is better, but it is definitely not fixed. I had two instances of a black screen while moving my camper across town and running a couple errands.

I hate to say this, but I am wondering if we would not be better off relying on a programmer in our midst instead of Rostra. I am not sure how they continue to get it wrong. I wonder if there are voltage differences that happen when the truck turns off and it causes the OS(Windows CE) within the module to blackscreen. Since it has to be on to transmit the screen, the screen quits working altogether. One workaround would be some type of switch that would bypass the module in those circumstances. It would not even be a big deal if the included button rebooted the module after holding it for like 10 seconds. I don't have the button hooked up, but I wonder if that wouldn't make sense.

I am starting to wonder what they are going to do to help us since they plan on shipping new modules to the 2.2 sync owners. I would hope they give us the option to upgrade for free since that means our Sync would never be able to upgrade past 2.1. Finally, if this is a hardware failure and we are just throwing software updates at something that can't be addressed with updates, why are we doing this?
Reply
Old May 19, 2017 | 10:20 AM
  #684  
Husker's Avatar
Just The Basic Facts
5 Year Member
Photogenic
Liked
Loved
iTrader: (4)
 
Joined: Aug 2016
Posts: 2,831
Likes: 1,027
From: Nebraska
Default

Originally Posted by Zxlr88
Update:

SO after running the push to start update for a couple of days, it is better, but it is definitely not fixed. I had two instances of a black screen while moving my camper across town and running a couple errands.

I hate to say this, but I am wondering if we would not be better off relying on a programmer in our midst instead of Rostra. I am not sure how they continue to get it wrong. I wonder if there are voltage differences that happen when the truck turns off and it causes the OS(Windows CE) within the module to blackscreen. Since it has to be on to transmit the screen, the screen quits working altogether. One workaround would be some type of switch that would bypass the module in those circumstances. It would not even be a big deal if the included button rebooted the module after holding it for like 10 seconds. I don't have the button hooked up, but I wonder if that wouldn't make sense.

I am starting to wonder what they are going to do to help us since they plan on shipping new modules to the 2.2 sync owners. I would hope they give us the option to upgrade for free since that means our Sync would never be able to upgrade past 2.1. Finally, if this is a hardware failure and we are just throwing software updates at something that can't be addressed with updates, why are we doing this?
Disturbing
Reply
Old May 19, 2017 | 04:57 PM
  #685  
Lurch96's Avatar
5 Year Member
5 Year Member
Liked
Loved
 
Joined: Sep 2016
Posts: 130
Likes: 18
Default

Zxlr88,

Seems like you always have the latest gouge. I can't even get ahold of Tech Support to try the push button update. So you heard that Sync 2.2 will require a whole new piece of hardware? That seems weird since I didn't think that much changed from 2.0 to 2.2.

Yeah, I think it'd be a pretty big problem if they didn't let 2.0 owners swap for a new box since chances are at some point like HuskerHarley you're going to drop your truck off at the dealer and it'll come back with 2.2 whether you like it or not.
Reply
Old May 19, 2017 | 07:09 PM
  #686  
TexasFording's Avatar
Senior Member
iTrader: (14)
 
Joined: Nov 2012
Posts: 3,240
Likes: 603
From: Omicron Persei 8
Default

Originally Posted by Zxlr88
I am not sure how they continue to get it wrong. I wonder if there are voltage differences that happen when the truck turns off and it causes the OS(Windows CE) within the module to blackscreen.
Humm, sync 3 is QNX, has nothing to do with CE. And, Sync 2 was Windows Embedded, not CE. Actually, Windows Embedded Automotive since it was a fork of the actual Windows E.

My best guess is that QNX is not playing with whatever OS Rostra uses.
Reply
Old May 20, 2017 | 09:51 PM
  #687  
camera-source.com's Avatar
F150 Vendor
10 Year Member
Liked
 
Joined: Jun 2012
Posts: 308
Likes: 87
Default

I'm sorry to hear that this is still an ongoing problem. As always we'll support you the best we can so let us know if there is something we can do. At this point it seems your direct communication with Rostra is best if they are working directly with you. If you bought your system from us and are having difficulty reaching someone at Rostra let me know and I'll have our rep contact you.

BTW... just curious if you guys have read anything about issues Ford has had with Sync updates? I read where people were having issues with the Ford Sync 3 2.2 update bombing all on its own without anything to do with interfaces and mods so maybe this is why Rostra is having a hard time figuring this out? If the base Ford firmware/hardware is not stable it will be impossible for them to nail this down.

Might be unrelated but maybe TexasFording or another Ford Tech can shed some light on this.

Appreciate your successes and failures posted here so we can keep an eye on the progress. Rostra just sends us links and tells us it's fixed but we have no way of confirming until you guys give it a try.

Thanks and hope this gets resolved soon!

Chris
camera-source.com
888-844-9763
Reply
Old May 20, 2017 | 10:37 PM
  #688  
TexasFording's Avatar
Senior Member
iTrader: (14)
 
Joined: Nov 2012
Posts: 3,240
Likes: 603
From: Omicron Persei 8
Default

Originally Posted by camera-source.com
BTW... just curious if you guys have read anything about issues Ford has had with Sync updates? I read where people were having issues with the Ford Sync 3 2.2 update bombing all on its own without anything to do with interfaces and mods so maybe this is why Rostra is having a hard time figuring this out? If the base Ford firmware/hardware is not stable it will be impossible for them to nail this down.
Chris,

Someone else here posted the SSM texts regarding Sync 3 issues. The list includes:

- SSM 46570 - 2016-2017 Various Ford And Lincoln - SYNC 3 - Intermittent Blank Screen. The fix is to re-download the software from OASIS and reflash the APIM with IDS and VCM2.

- SSM 45918 - 2016-2017 Ford/Lincoln - SYNC 3 - Navigation Fault Message Or System Lock Up. The fix is to have the customer update the OS on the phone and the apps (they blamed it on apps like MLB and Spotify) and again said to wipe the APIM and reload the software from OASIS with IDS and VCM2.

I logged in to PTS and read the tech notes. They state that the issues mentioned above were resolved with the latest update, which would be 2.2 16288 for Lincoln and later on 17011 for both Ford and Lincoln.


WSM 415-00 states that the tech should enter bezel diagnostics (press and hold the EJECT button, and within 1 second, press and hold the SEEK UP button) and perform APIM diagnostics (APIM Diagnostics, touch screen activation test).

Unfortunately, there is no further information other than to replace the APIM if both diagnostics and reloading the software fails.

Now, because guys here have been updating the OS via USB, it accomplishes the same as the ford tech loading the OS via IDS/VCM. And we can also (obviously) enter bezel diagnostics and test.

People have been having problems and bricking their APIMs because installations/upgrades failed due to bad USB sticks (or improperly formatted USB sticks). As mentioned earlier, v2.2 16288 was rolled into 17011 to include Ford vehicles. The notes do not list any major fixes between these two versions. These two are identical and Rostra should have no problems programming for both. I can understand them having an issue programming their units for 1.0 and 2.0 (major dot upgrade to include many fixes and AA/CP).

Even programming between 2.0 and 2.2 should not be an issue. The difference in versions include fixes that mainly dealt with lag in AA/CP and Gracenote music management.

I would suggest to divide and conquer. If guys can pull the Rostra unit and Sync 3 works fine, (run successful diagnostics, try hard to replicate the black screen/freeze) then the issue is with Rostra. If, on the other hand, Sync 3 still freezes/locks/black screens WITHOUT the Rostra, then the issue could be the SSM posted above.

Now, to further D&C, plug in the Rostra without any accessories (HDMI/USB/Cameras) and see if you can replicate the problem. Could it be that the HDMI/USB interface is what causes the screen/APIM to lock? As anyone tested the Rostra unit without those connections? Does this happen with iphone and android phones plugged in?

Does Rostra have any compatibility notes regarding phone OS versions? Do they have a list of approved HDMI cables? HDMI itself is finicky, so a particular cable could also be interfering.

Sorry for the long-winded post, but I hope it shed a little bit of information that hopefully can help Rostra.

Last edited by TexasFording; May 20, 2017 at 10:47 PM.
Reply
Old May 21, 2017 | 08:36 AM
  #689  
Husker's Avatar
Just The Basic Facts
5 Year Member
Photogenic
Liked
Loved
iTrader: (4)
 
Joined: Aug 2016
Posts: 2,831
Likes: 1,027
From: Nebraska
Default

Thanks texasfording for continuing to help Rostra with yer information, thoughts & suggestions.

This won't help resolve the problem but FYI: Before entering my truck after opening the door, I look at the screen to see if the FORD logo is showing up or not. If it does when I climb in and start the truck I have a screen. If no logo appeared, then black screen when I start up.
Reply
Old May 21, 2017 | 06:07 PM
  #690  
camera-source.com's Avatar
F150 Vendor
10 Year Member
Liked
 
Joined: Jun 2012
Posts: 308
Likes: 87
Default

Originally Posted by HuskerHarley
Thanks texasfording for continuing to help Rostra with yer information, thoughts & suggestions.

This won't help resolve the problem but FYI: Before entering my truck after opening the door, I look at the screen to see if the FORD logo is showing up or not. If it does when I climb in and start the truck I have a screen. If no logo appeared, then black screen when I start up.
FYI I had a customer tell me that if he unlocked his door with the keyfob twice he had no issues. This doesn't sound like it could be related in any way but he swore by his method. He mentioned the logo not showing up being directly correlated to the interface not functioning. Seems that when he unlocks a couple times using the key fob the logo always appears.

Don't forget to stand on one foot and hop while doing this... Sorry had to interject some humor. However, I'm serious about the key fob thing but have not tested this myself just relaying the info.

Last edited by camera-source.com; May 21, 2017 at 06:11 PM.
Reply



All times are GMT -4. The time now is 02:17 AM.