Adding Front Camera to XLT
I understand what you are saying and it make pretty good sense... (That is what is scaring me... :-))
It's just that they are some conflicting info out there. I guess the only way to find out will be to test it.
Another quick look at fordparts.com comparing the 2015 and 2016, the part number of the camera are the same. The 2015 is not on the Sync3 system. So is it safe to conclude that the 2015 would be analog ?
(I know, I may still only be hanging on a futile idea... I just want a front camera... :-))
It's just that they are some conflicting info out there. I guess the only way to find out will be to test it.
Another quick look at fordparts.com comparing the 2015 and 2016, the part number of the camera are the same. The 2015 is not on the Sync3 system. So is it safe to conclude that the 2015 would be analog ?
(I know, I may still only be hanging on a futile idea... I just want a front camera... :-))
I am by no means insisting I am right, I think we all would like to just know the facts. I wonder how much they share with the techs in the factory training?
Lockpick developers et al must have figured out much of it.
The system may also be backwards compatible supporting both NTSC and FP-link?
Lockpick developers et al must have figured out much of it.
The system may also be backwards compatible supporting both NTSC and FP-link?
Perhaps somone with such a cable could confirm that the wires pass directly from the RCA to a connector or do they enter a module where it could be converted to LVDS first.
The physical wiring shielding etc is consistant with LVDS, the diagrams use twisted pair symbols, plus labels such as D+ D-.
I also offer this snippet from a semiconductor press release:
At the CES, Ford also showed for the first time its new SYNC3 infotainment system,
developed in close cooperation Texas Instruments and containing several contributions
out of TI's development department. The system is built around TI's OMAP5 processor.
For wireless communications it contains TI's WiLink 8Q single-chip solution for WiFi,
Bluetooth 4.0 which also takes the part of navigation reception for all GNSS systems
(GPS, GLONASS, Beidou and Galileo).
Camera connection is established through FPD Link III SerDes chips.
All together, these building blocks enable the SYNC 3 to offer handsfree Bluetooth connectivity,
enhanced driver interactivity and improved voice recognition capabilities, claims TI.
The physical wiring shielding etc is consistant with LVDS, the diagrams use twisted pair symbols, plus labels such as D+ D-.
I also offer this snippet from a semiconductor press release:
At the CES, Ford also showed for the first time its new SYNC3 infotainment system,
developed in close cooperation Texas Instruments and containing several contributions
out of TI's development department. The system is built around TI's OMAP5 processor.
For wireless communications it contains TI's WiLink 8Q single-chip solution for WiFi,
Bluetooth 4.0 which also takes the part of navigation reception for all GNSS systems
(GPS, GLONASS, Beidou and Galileo).
Camera connection is established through FPD Link III SerDes chips.
All together, these building blocks enable the SYNC 3 to offer handsfree Bluetooth connectivity,
enhanced driver interactivity and improved voice recognition capabilities, claims TI.
True, the camera does have (+), (-), video+ and video- outs for the LN Bus, which is as you all pointed out, low voltage regulated.
However, the camera and everything downstream from it has a video out, which I believe it is plain ol' analog video, which is what I am banking my theory on. Another guy in my old thread mentioned that its a regular video source, which should work with any processor that is capable of converting the analog signal to something that is understood by HS-CAN3.
The LIN bus is only affecting the rear park assist camera, which is not tied to the front camera in this scenario.
In shot, I'm getting the lockpick from a vendor that will have a generous return policy should it need to be executed and my total investment in this project will be 100 dlls, which is not as bad as it could have been.
I am by no means insisting I am right, I think we all would like to just know the facts. I wonder how much they share with the techs in the factory training?
Lockpick developers et al must have figured out much of it.
The system may also be backwards compatible supporting both NTSC and FP-link?
Lockpick developers et al must have figured out much of it.
The system may also be backwards compatible supporting both NTSC and FP-link?
Functionally they are the same, I have had access to mine (purchased new using a VIN from a Limited) and someone's 602A (KR), both 2015 models.
Not bad.





