Other Parts Discussed in Thread: DS90UB933-Q1, DS90UB935-Q1, DS90UB913A-Q1, DS90UB953-Q1
Hi Team,
Have some questions on compatibility between FPD Link-III Devices:
1) The datasheets for many of the FPDLink-III components provide a list of compatible components (e.g. the DS90UB960 lists the 935, 933, and 913A).
- Does this mean that deserializer won’t work with any other serializers?
- The compatibility lists seem to group around the “deserialized” interfaces – LVCMOS to LVCMOS, LVDS to LVDS, etc. For instance, if someone has designed a camera using 947 to convert a camera’s LVDS to FPDLink-III, then would we have to design a receiver that uses the 948 to convert the FPDLink-III back to LVDS, or could we use some other deserializer to convert it to an LVCMOS RGB format?
2) Coax vs STP. In our market Shielded Twisted Pair is often preferred in the big metal 38999 circular connectors, and coax contacts force larger shell sizes vs discrete pins. However, the power-over-coax is very appealing.
- Are there guidelines for doing power over STP?
Also, attached is a spreadsheet I pieced together from the various datasheets for compatibility between the FPD Link-III devices.
There seem to be some gaps (e.g. The 940 is compatible with 925Q and 925A, yet but the 924 is only compatible with the 925Q), but overall it looks like there are sort of two family lines --
A) 921/923/925/927/929/947/949 line
B) 913/914/933/934/964/953/954/964 line
Some of the datasheets for the 913-964 line make reference to being ADAS parts, but it’s not clear what makes them more appropriate for ADAS applications vs the other parts.
I’d like to understand better is what particular features differentiate them.
We’re currently looking at using a sensor with an LVCMOS interface, but at the receiving end we want to output LVDS. If my current understanding of the chip compatibilities is correct, that limits us to the 921 or 925 at the sending end, and the 924/928/948 for receiving. Please let me know if I’m overlooking any options. There’s a LOT of information in all those datasheets to digest.
