These probes are for use with the Simscape multi-domain physical modeling tools (Simscape, Sim Driveline, SimHydraulics and SimElectronics). The ssc_Probes.m file calls the library file containing probes for viewing the through and across variable for each domain. The ssc_dc_motor.slx model file is an example of how to use. See Help block for additional usage notes.
To learn more about MathWorks Physical Modeling products go to: https://www.mathworks.com/solutions/physical-modeling.html
This toolbox was developed by Tom Egel from the [Consulting Services](http://www.mathworks.com/services/consulting/) group at MathWorks
Tom Egel (2021). Simscape Probes (https://www.mathworks.com/matlabcentral/fileexchange/17969-simscape-probes), MATLAB Central File Exchange. Retrieved .
Can you please update this very useful probes for version R2017b ?
Updated for R2014a. Created ssc_Probes.m to open the library based on version of MATLAB being used. Older versions placed in the Archive folder.
Provided one more update for R2013b that includes Probes for SimPowerSystems 3G domain in the Electrical library
The Probes have been updated to use Simulink Signal logging instead of the To Workspace blocks. This seems to be much more robust. Comments/suggestiotn welcome.
The switch to "To Workspace" was done to accomadate users who want to be able to have the Probes used in a library block (this is not possible with Scopes). As for the naming limitation, until I can figure out a better way, it is up to the user to provide unique names (I tried using genvarname, but there is a 64 char limit). The names are updated during model update. As for simlog, currently the only options are All or None. Once additional functionality is added here, I will be able to add a logging option.
Thanks for your feedback.
Tom, was there a reason you shifted to ToWorkspace blocks instead of scopes? It seems that the ToWorkspace block variable name does not change when the name of the block changes - also creates a problem if I use them within different subsystems with the same name.
I think a potential addition would be a right click menu configure option to switch between logging and no logging (using something like a variant subsystem). It could improve simulation performance if there are a large number of probes (I tend to use more probes and save it to the workspace because the simlog files become too large).
The lastest update for 12b fixes the callback issue.
However, can you release an update for 2012b? In 2012b when evaluating the OpenFcn callback it tries to do close_system(gcs) which generates an error if the probe is at the top level of a model. If it is not at the top level of the model then it does not produce an error but it goes to the top-level of the model. You then have to use the back button to get back to your original spot.
The SimPowerSystems library contains voltage and current measurement blocks that output a Simulink signal. You could easily recreate what I have done by putting these blocks under the mask. You’ll also have to remove the PS->S block since it is not needed for SimPower.
I was wondering if this approach could also be applied to electrical systems built with Simpowersystems blockset?
Very good idea this lib ! Was thinking about creating something like this but the work is already done and Well done !
Save a lot of room when we need to put scope in model.
Very useful blocks. Saves a lot of time
I always use them, I modified the blocks a little bit to include them as a library in the Simulink browser.
Let me know if you are interested to get the modified version I created.
Find the treasures in MATLAB Central and discover how the community can help you!Start Hunting!