• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 117 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TPIC8101: Questions on How to Use

Shinichi Yokota
Genius 9715 points
Part Number: TPIC8101

Hello,

I'd like to ask some questions on how to use the TPIC8101.

  • How long does it take for the internal MUX to switch since its SPI register setting?
  • What's the purpose/background of having two know sensor interfaces in this device?
  • How much frequency tolerance is allowed for the oscillator input?
  • Does the TPIC8101 have a start-up sequence of each pin?
  • Do you have actual waveform of the input and the output captured with real knock sensors?
  • Can the GUI of TPIC8101EVM run on the latest Windows 10?
  • Is a simulation model of the TPIC8101 (SPICE model, for example) available?

Best regards,
Shinichi Yokota

  • 0
    TI__Expert 7599 points

    Hello Yokota-San,

    Here are the response. Let us know if you need more! 

    1) The internal MUX should be instantaneous. The exact details are not provided and the limitation here would be on how fast the SPI is configured. 

    2) Application section information 9.1 indicates that the product was designed to work with one or 2 flat type or resonant tyne knock sense elements. So it's optional to work with 1 or 2 sensors. 

    3) As the XIn is the clock input to the device and its the internal sampling frequency of the A/D Converter. A high precision low tolerance and low jitter would be the recommendation. 

    4) There is no start up power sequence and there is specific timing information mentioned in the section 8.3.2 

    5) No. 

    6) Yes, sometimes the GUIs are specific to OS and also the .net that is installed and can be worked with Windows and NI partnership. 

    7) No. The datasheet does provide guidance on the signal chain.