Guy on Simulink

Simulink & Model-Based Design

Posts 21 - 30 of 50

다음에 대한 결과: Code Generation

My Introduction to Embedded Coder 7

This week, I want to share the example which helped me, a long time ago, to get started with Embedded Coder. For readers who never used it, I hope this example will be as useful for you as it has... 더 읽어보기 >>

How do you hold the value of a signal? 23

Yesterday, I was giving a training to new hires at MathWorks and one of the attendees asked me how to hold a value in Simulink. Of course, my answer was that there are many ways to hold a value... 더 읽어보기 >>

What can Simulink Code Inspector do for you? 4

Some time ago I was having a discussion with my colleague Sarah Dagen, from our Consulting Services, and she began explaining Simulink Code Inspector™ to me. I immediately stopped her and said:... 더 읽어보기 >>

Stateflow Active State Output

Did you know that with Stateflow, it is possible to monitor which state is currently active, and use that information in the rest of the Simulink model? This feature is named Active State Output. The screenshot below shows how to do this for one of the charts in the example Temporal Logic Using the AT Function.... 더 읽어보기 >>

Debugging Simulink Coder Executable Easily in R2013b

A few days ago I was showing a user how to debug an executable generated by Simulink Coder and I realized that the new Toolchain approach in R2013b makes this process a lot easier.... 더 읽어보기 >>

Tracing Requirements to Models, Tests, and Generated Code 4

When I wrote a post about the R2013b new features, Fraser replied in a comment that one of his favorite new feature is the requirements linking to MATLAB code. This made me realize that I never... 더 읽어보기 >>

A Tweeting S-Function for the Raspberry Pi 10

I recently bought a Raspberry Pi. After trying a few of the demos included with the Simulink support package for Raspberry Pi, I began thinking about what I could do next. Just for fun, I... 더 읽어보기 >>

Creating Driver Blocks for Arduino, Lego, and other targets 12

As you may know, it is easy to run Simulink models on a set of supported target hardware. This has been possible since R2012a. Even if we add more targets and support more features for each target... 더 읽어보기 >>

To Latch or not to Latch?

Yesterday I explained to a colleague the effect of the Inport block option Latch input for feedback signals of function-call subsystem outputs . I thought it would be interesting to share... 더 읽어보기 >>

Data Dependency Violation Errors and Subsystem Semantics 3

Did you ever receive a "data dependency violation" error message from a Simulink model? I will try to explain why this happens and what you need to do to avoid this error by introducing my... 더 읽어보기 >>

Posts 21 - 30 of 50