Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Member Login

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Eng-Tips
*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...Congratulations for your great site. This site helped me more than university..."

Geography

Where in the world do Eng-Tips members come from?

"timing" problem in simulink using LUT and block "from workspace"

baesae (Electrical)
6 Dec 11 10:49
Hello

I'm using Simulink and HDL-Coder to generate code for some hardware algorithm for OCT (doesn't really matter for the problem underneath ;))

Recently I discovered a strange behavior when debugging in simulink: the input data did not change on every clock, even though the input vector changes its value for every sample-time.
I checked the sample time (fixed step size) for the simulation as well as the sample time vector in the matlab code. But they fit to each other.

Therefore I made a small example to see, whether I could reproduce this 'error'. As you can see in the picture I have the simplest possible simulink model containing an 'from workspace' and a 'to workspace' block. using the settings from underneath I keep receiving a strange behavior for the output. the first half of the ramp is constantly increasing whereas the second half looks has some "edges" (a few samples are not loaded on time)

Settings/configs:
--> sample rate of the 'from workspace' block equals 0.1 (equals simulations fixed step size)
--> 'to workspace' block has sample time "inherited" (--> 0.1 as well)
--> matlab code (as in the screenshot) is:

dt = 0.1;
N = 200;
time = -0.01:dt:(N-1)*dt;
sample = linspace(0,N-1,N);
%samples = [time', sample'];
samples.time = time';
samples.signals.values = sample';
sim('test_data_read_in.mdl', N*dt);


You may know this problem from timing problems in hardware when not respecting the set-up-times for components and so on. But Simulink should NOT behave like hardware, I guess.. Despite that I tried to make the input-signals valid shortly before they will be read in (likely respecting set up time in hardware). And it worked! The ramp of the output data was neat!

Code:
dt = 0.1;
N = 200;
time = -0.01:dt:(N-1)*dt;
sample = linspace(0,N-1,N);
%samples = [time', sample'];
samples.time = time';
samples.signals.values = sample';
sim('test_data_read_in.mdl', N*dt);

I experienced the same problems with Lookup-tables.

Anybody encountered this problem before or has an idea how to avoid it?

Thanks a lot for your help!
baesae

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!

Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close