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.

LM73: Figure 9. Typical Pointer Set Followed by Immediate Read of a 2-Byte Register

Guru 29720 points
Part Number: LM73

Hi Team,

Is it possible to issue STOP and START condition between Frame 2 and Frame 3?



I believe it is no ploblem as long as timing requirement (page. 7) is satisfied but would like to confirm just in case.
http://www.tij.co.jp/jp/lit/ds/symlink/lm73.pdf

Best Regards,
Yaita / Japan disty

  • Hi Yaita-san,

    Yes you can insert a STOP then a START condition in between frame 2 and 3. There shouldn't be a problem.

    Aaron
  • Hi Aaron-san,

    Thank you for your reply. I understood.

    I heard abnormal temperature data is read if tBUF (SMBus Free Time Between Stop and Start Conditions) is 2.5us in this case from my customer. I also heard the error probability is about 1/50000.
    If he set tBUF=5us, the abnormal temperature data wasn't read over 630000 of trials.
    So he wondered if 2.5us is sufficient value or not.

    I believe tBUF=2.5us isn't problem because of the following specification.


    May I have your comments about the issue?


    Best Regards,
    Yaita / Japan disty

  • May I have your comments?

    Best Regards,
    Yaita

  • Hi Yaita-san,

    I'm sorry for the delayed response. The tBUF is basically the time from the last detected STOP condition to the START condition where a new transaction can be inserted again. The wait time could be day, but can't go below 1.2µs. So, 2.5µs shouldn't be a problem.

    Hope this helps!
    Aaron
  • Hi Aaron-san,

    Thank you for your reply.
    >The wait time could be day, but can't go below 1.2µs. So, 2.5µs shouldn't be a problem.
    What is "day" mean? Is it typo?

    Best Regards,
    Yaita

  • Hi Yaita-san,

    I'm sorry for the confusion. I meant you can wait as long as you want until you want to insert the next transaction.

    Aaron