FAQ
For questions not answered in this FAQ or if you require additional support using SimWB, please contact us at support@ccur.com.
Contents
General Questions
What are the system requirements for a SimWB real-time host?
What are the system requirements for a SimWB client?
Is there a 64 bit version of SimWB?
Yes, there is a 64 bit version of SimWB which can be installed on the 64 bit RedHawk Operating System.
Does SimWB support 32 and 64 bit MATLAB on Windows and Linux?
Yes, SimWB supports both 32 and 64 bit MATLAB on Windows as well as Linux. SimWB has a small MATLAB/Simulink footprint so SimWB is easily made compatible with the latest version of MATLAB/Simulink offered by the MathWorks.
Using SimWB
SimWB MATLAB/Simulink interface
How does SimWB fit into Model Based Design
What is the SIMulation Workbench Toolkit?
The SIMulation Workbench Toolkit when installed on the MATLAB path provides an interface between MATLAB and the SimWB real-time host. Under Simulink, this toolkit will provide a Configuration Tool GUI which is used to create an RTDB automatically from the model and generate SimWB compliant code from the Simulink model. The Toolkit also provides a MATLAB command line API to communicate with the SimWB real-time host.
SimWB user interface
How can I build custom HMI's in SimWB?
How do I create test in SimWB?
How do I create a test session in SimWB?
How do I record a test in SimWB?
How do I playback a test in SimWB?
SimWB I/O
Is there a list of I/O supported by SimWB?
Troubleshooting
How do I debug my source code in SimWB?
Debugging source code under SimWB
SimWB provides the ability to debug models using KDbg. The following steps are needed to start the debugger from SimWB.
- First re-make the code with the –g flag. This is done by modifying the make file in the source code folder on the real-time host. For example:
- Go to "/usr/local/ccursim/projects/RTW.Sources/modelname_ccurt" folder where "modelname" is the name of the model.
- Edit the "modelname.mk" file
- In the General User Options add the –g flag. Approximately line 153 in the MAKE file should now read OPTS = -g
- Use the commands "make –f modelname.mk clean" and "make –f modelname.mk" to remake the model.
- In the SimWB Control Panel start the Run/Playback test GUI
- In the Test Control GUI select the test with the model that was compiled with the –g flag.
- Press the CTRL key on the keyboard and left click the mouse on the Start button. This will open a menu with the NightTrace and the Debug option
- Hover the mouse over the Debug option and this will display a list of User Tasks and System Tasks which one can debug.
- Select the model that you want to debug from the User Tasks list. Upon selection of the model the KDbg GUI will open and stop in the ccurrt_mainC.c file for this model. If the debugger stops in the schedutils.c task it is an indicator that you need to remake the source with the –g file.
- Now you can place debug points in the source code to debug the model. The model is called by the rt_OneStep() function.