-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scripting Support #27
Comments
@skthelimit Unfortunately, when this custom device was created, there was no scripting API created for it. Also, there are portions of the system definition for this custom device that contain information about the UI. However, if you were able to script the system definition without using the UI, I still think your system would deploy, you just wouldn't be able to open it in System Explorer and keep all the scripted properties. That said, there are some VIs that are called by the UI that you might be able to use for scripting something. The primary VIs you would use would be For examples of how you might use these VIs, look at the Bank0 Select Vsup case in Additionally, VeriStand does not provide a way to script SLSC modules into your SLSC chassis in the system definition. I needed that functionality for another SLSC custom device, so I made a library that will allow you to do this (with just a little more work). It's currently located in the Routing and Faulting Custom Device source, but I would like to make it a separate repo so it could be consumed by other projects. The library is generic, but in order to use it, you'll need to provide the path to the custom device XML and call the Initialization VI. To see how I did this, look at Add SLSC Switch Custom Device.vi. Screenshot below. Additionally, the Routing and Faulting Custom Device has an example of using this library to add the module to a system definition. |
My goal is to create a script that add SLSC 12201 custom device under SLSC and configure each channel/port etc. Does this custom device support scripting in any way?
The text was updated successfully, but these errors were encountered: