Bug Report on Simulink "Unbuffer Block" in R2017a

2 views (last 30 days)
Lloyd Landon
Lloyd Landon on 6 Oct 2017
Commented: Suze Zhang on 9 Oct 2017
I found when using the Unbuffer Block in Simulink that a third clock domain was being created in the tool. There should be one domain on the input and one on the ouput, but a third clock domain was being created.
  1 Comment
Suze Zhang
Suze Zhang on 9 Oct 2017
Hi Lloyd,
By a third clock domain, do you mean the types of sample time that can be viewed from the Sample Time Legend window? And about the third one that you observe with the Unbuffer Block, does it happen to be Hybrid?

Sign in to comment.

Sign in to answer this question.

Answers (0)

Categories

Find more on Sources in Help Center and File Exchange

Tags

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!