Verdin DSI to LVDS adapter Atium Designer PCB project

Hello,
I am working on the hardware implementation of a new LVDS display.
Using the available PCB design in Altium Designer, I noticed a parameter in the Layer Stack Manager. It concerns the internal dielectric layer between the internal copper layers. This parameter is the DK value, which refers to the dielectric constant of the insulator. In the design, its value is set to 0. Altium Designer detects this as an error because the value cannot be lower than 1. The DK parameter is related to the impedance matched for high-speed LVDS signals.

Was the DK value of 0 intentionally set in this design?

Best regards
Sylwester

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello Sylwester,

Thank you for reaching out with your question. The DK (dielectric constant) value is indeed a crucial parameter in PCB design, particularly for high-speed signals like LVDS, as it plays a significant role in impedance matching. A DK value of 0 is not physically meaningful and is likely an error in the design setup. Typically, the DK value should be greater than 1, which reflects the properties of the dielectric material used between the copper layers.

In your Altium Designer project, the DK value set to 0 should be corrected to ensure proper impedance matching and signal integrity for your LVDS display. I recommend checking the design documentation or consulting with the original designer to determine the appropriate DK value for the dielectric material specified in your project.

I hope this helps you move forward with your design. If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/qoriq-grl/9543/2/High_speed_interfaces_layout__layout_design_guide.pdf.

Dear @silvo,

Thank you for bringing this to our attention. I have contacted our Hardware team and they are looking into it. We are unsure of how this has occurred and the public packages will be fixed. In the meantime I would urge you to please use 4.2.

Best regards,
Collin