01-04-2008 04:40 AM
01-07-2008 08:22 AM
01-08-2008 09:44 AM
01-08-2008
10:16 AM
- last edited on
02-28-2025
06:44 PM
by
Content Cleaner
Steffi,
what you gonna try to implement isn't that easy with your approach.
Simulink and LabVIEW are running independent from each other. Furthermore, Simulink is generally a simulation environment, to combine it with other targets (HW or SW) you need to use the Real-Time Workshop (RTW) from Matlab to create a DLL of your Simulink model. Afterwards you can implement this DLL in LabVIEW by using the SIT. In case of using the Simulink DLL, the structure of two independent running frameworks changes in the following way: Just imagine that LabVIEW is the only framework and in this framework you call the Simulink model again and again and again... (the model is compiled with a fixed steped solver, therefore, the calling framework (LabVIEW in our case) is the time base for the model)
If you don't have the RTW, I recommend to go one of the following ways:
Use either the LabVIEW Simulation module to translate the Simulink model into LabVIEW code or use LabVIEW for controlling (Kp,Ki, etc.) and/or monitoring (specific signals) only.
Another possible - but really hard way - would be to synchronize Simulink by using a timer obj in combination with a triggered subsystem.
I hardly recommend to use the RTW.
Thanks,
Thomas
01-10-2008 06:12 AM
01-10-2008 06:36 AM
01-15-2008 10:30 AM
01-15-2008 01:17 PM