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.

LM22674, LM22671 - distribution of switching frequency

Other Parts Discussed in Thread: LM22671, LM22674

Hi all

Would you mind if we ask LM22674 and LM22671?
The switching frequency of LM22671 and LM22674 are MAX600kHz, MIN400kHz.
Do you have distribution of switching frequency?
Because, our customer would like to know switching frequency exactly.
(We recognize that it is not possible to measure switching frequency exactly at SW node.)
Is it possible to know switching frequency with Serial No?

Kind regards,

Hirotaka Matsumoto

  • Hello,
    I am not sure that I understand the questions. What do you mean by "it is not possible to measure switching frequency exactly at SW node."? In fact you should be able to measure the frequency at the SW node. Also what do you mean by "Serial No."?

    Regards,
    Akshay
  • Akshay san

    Thank you for your reply.

    And we are sorry that our explanation makes you confuse.

    As the question, do you have the distribution map of switching frequency?
    If the device is checked switching frequency on shipping test, we guess that we can know the device which has switching frequency by using Serial No of device. 
    (Of course, it is no matter that there is no check switching frequency on shipping test.)

    Kind regards,

    Hirotaka Matsumoto

  • Hi,

    First of all, as Akshay mentioned, swithcing frequency is measured at the switch node by definition.

    The switching frequency is one of the parameters we measure at the IC's production test. But there's no serial number on each IC. They only have data code. There are a big group of ICs having the same date code. We do keep sample data log, but there's no way to match it to an individual part. I'd suggest measuring the switching frequency on the board.

    Regards,

    Yang
  • Yang san

    Thank you for your reply always!
    OK, we got it.

    Kind regards,

    Hirotaka Matsumoto