06-30-2021 04:24 AM
Hello,
I made a Custom Device which adds custom devices to the same System Definition File. Which Custom Devices are added comes from a external file.
This works well, but when I add the custom devices the System Definition File will not be updated, I have to manually close the System Explorer and open it to see the changes.
Any ideas how can I update the system explorer with the changes I made? Or at least how to close the System Explorer and open it again?
Thanks!
-A
08-10-2021 05:52 AM
Which VeriStand version are you using?
08-10-2021 06:03 AM - edited 08-10-2021 06:05 AM
I came accross this when trying to update alarms in run time
Once a system definition file has been deployed then any changes you make to the same system definition file will only take effect once you redeploy the system definition. Reason being VeriStand takes your system definition file, compiles it and then deploys it, so any changes made to the system definition will require a new compilation and this new compliation needs to be deployed to take effect.
My work around was to use a labview vi to edit the system definition and then once the edit is done the vi undeploys the system definition and then deploys the newly updated version of the system definition automatically
Any reason why you are using a custom device to do this?
How are you interfacing and controlling/monitoring your real time system?
08-10-2021 06:11 AM
Hello,
I am using 2019 and probably changing to 2021 (If it is ever out)
08-10-2021 06:20 AM
Hi,
I did not ment it like that, I wanna see the changes live in the System Definition Explorer while the SDF is undeployed.
Well, you know, clients. We have a configurable Custom Device but they do not wanna add every instance by themselfs, they want to be able to read a xml and with that automatically add the nedded intances of the custom device and they also wanna be able to do that from the VeriStand GUI. I do not know another way to program a GUI VeriStand, only the pages of a Custom Device.
I did explained this was not the best solution ever but they want it like that and would not hear otherwise.
08-10-2021 08:53 AM
Hi ypi,
Typically, dynamically updating the system definition does not act on the current instance opened in the System Definition explorer. Closing and re-opening the system definition is what I would expect to see the latest changes. This is characteristic is what I expect from dynamic changes using the System Definition API as well.
08-11-2021 06:49 AM
Hello,
Thanks for the reply. I kinda "solve it" like that, closing an opening the SDF with python. It kinda works I just feel is not very elgant.
-A
08-11-2021 07:08 AM
Good to hear you figured out a work around
In terms of making VeriStand GUI elements its quite simple, if you can code custom devices then you can make workspace controls for sure, just follow this tutorial
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x4QfCAI&l=en-IE
you can run regular LabView code in these controls so you could use the LabView Python code to call your script from your custom workspace control
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019WHGSA2&l=en-IE