This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

FDC2214: Poor Documentation Quality

Part Number: FDC2214
Other Parts Discussed in Thread: FDC2212

Sensor Team,

I noticed some areas where the FDC datasheets could use some improvement.  I've spent several hours spinning my wheels because of this.

Specifically this relates to the INTB pin.  Because there was no indication otherwise, I assumed this pin was active high and setup my interrupts as such.  After much frustration and search of the datasheet, I was able to find a single line hidden away that indicated this pin was active low.

On page 20 of the datasheet:
"Setting register CONFIG.INTB_DIS to b1 disables the INTB function and holds the INTB pin high."

I've searched the entire datasheet and this is the only statement that indicates this pin is active low.  I dunno, maybe you should put something in the pin configuration table that indicates this clearly to the user?  Maybe you could add a bar over the pin name to indicate it's active low? Maybe you could do anything more than just putting a single sentence that is hidden away?  Just a thought from someone who is passionate about user experience ;-)

I also noticed the device ID register (0x7F) lists 16 bit values while the register is only 8 bits wide.  I have a FDC2212 and I read 0x48 for the device ID.  That is certainly not listed in the datasheet.

I'm also a little turned off by the cost of the EVMs for these products.  Because of the excessive cost of the eval boards for these devices, I literally designed my own eval board, fabbed, and assembled it just so I could test out these devices for my application.  I get you don't want hobbyists buying up all your stock, but these eval boards should be in the low $100 range.

Best,

Trey

  • Trey,

    Thank you for the feedback. We are sorry for any confusion caused by our collateral.

    Just so you know, many of our customers have struggled to get to production with devices from the FDC2xxx family due to EMC/EMI issues.

    For that reason, we suggest using the FDC1004. It has active shield drivers to help with EMI management and 16 bits of resolution.
    There is a supporting E2E FDC1004 FAQ page with a comprehensive list of available collateral supporting this device.

    Please let me know if you have any questions.

    Regards,
    John

  • John,

    Thanks for the quick response and tip, that is certainly helpful.  When you say EMC/EMI issues are you referring to EMC/EMI regulatory compliance issues?

    Are the issues mostly due to the lack of active shielding?  I have included some opamps to actively drive the outer conductor of my coax.  Obviously the sensor will act as an antenna, but even with an actively shielded coax wouldn't it still radiate as well?  Forgive me, I'm a microcontroller guy and my EMC/EMI knowledge isn't as strong.

    For context we are trying to use this part to do distance sensing between a fiber laser cutting head and the work piece.

    Trey

  • Trey,

    The EMI/EMC issues have to do with electromagnetics from the surrounding environment interfering with the FDC operation.
    We don't have any background or info regarding radiation from a system containing our part.

    Regards,
    John