I have a Simulink model file, and I am attempting to run the model on a Mac or linux/UNIX machine. The main model has many blocks, and does not fit into the window when viewed at 100% size. When I select "Simulation -> Start", the model appears to redraw repeatedly and the model takes an extremely long time to start running.
MATLAB: Does the model redraw repeatedly when I run it in Simulink 6.2 (R14SP2) on a Mac or Linux/UNIX machine
drawsflashlineslinuxmacososxredrawrefreshscreensimulinkslowunix
Related Solutions
MATLAB: How to configure the mdce service to start automatically at boot on Linux/Unix cluster nodes
To configure the mdce service to start at system boot, follow the appropriate instructions below depending on your OS distribution type:
=====
Debian Platform
=====
On each cluster node, register the mdce service as a known service and
configure it to start automatically at system boot time by following these steps:
1. Create the following link, if it does not already exist:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce2. Create the following link to the boot script file:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce3. Set the boot script file permissions:
chmod 555 /etc/init.d/mdce4. Look in /etc/inittab for the default run level. Create a link in the rc
directory associated with that run level. For example, if the run level is 5,
execute these commands:
cd /etc/rc5.d;ln -s ../init.d/mdce S99MDCE=====
SUSE Platform
=====
On each cluster node, register the mdce service as a known service and
configure it to start automatically at system boot time by following these steps:
1. Create the following link, if it does not already exist:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce2. Create the following link to the boot script file:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce3. Set the boot script file permissions:
chmod 555 /etc/init.d/mdce4. Look in /etc/inittab for the default run level. Create a link in the rc
directory associated with that run level. For example, if the run level is 5,
execute these commands:
cd /etc/init.d/rc5.d;ln -s ../mdce S99MDCE=====
Red Hat, Fedora Platform
=====
On each cluster node, register the mdce service as a known service and
configure it to start automatically at system boot time by following these steps:
1. Create the following link, if it does not already exist:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce2. Create the following link to the boot script file:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce3. Set boot script file permissions:
chmod 555 /etc/init.d/mdce4. Look in /etc/inittab for the default run level. Create a link in the rc
directory associated with that run level. For example, if the run level is 5,
execute these commands:
cd /etc/rc.d/rc5.d;ln -s ../../init.d/mdce S99MDCE=====
Solaris Platform
=====
On each cluster node, register the mdce service as a known service and
configure it to start automatically at system boot time by following these steps:
1. Create the following link, if it does not already exist:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/mdce2. Create the following link to the boot script file:
ln -s matlabroot/toolbox/distcomp/bin/mdce /etc/init.d/mdce3. Set boot script file permissions:
chmod 555 /etc/init.d/mdce4. Look in /etc/inittab for the default run level. Create a link in the rc
directory associated with that run level. For example, if the run level is 3,
execute these commands:
cd /etc/rc3.d;ln -s ../init.d/mdce S99MDCEInstructions for configuring the mdce service to start at boot are included in the Cluster Setup Instructions found at the link below:The code that is generated by Real-Time Workshop is ANSI-C and thus platform independent. You can use PackNGo utility introduced in Real-Time Workshop 6.5 (R2006b) for packaging generated code, see the following page for details:
Best Answer