VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

VeriStand Outports old Folders remain after refresh

When updating Simulink Model, array names have been changed.  In Outports, empty folders with old name remain after the model is refreshed.  Is there any way to get rid of the old folders?  Removing and reselecting the model cleans this up, but that would mean remapping of the signals and parameters.  Currently using VeriStand 2013, but also observed this with VeriStand 2012.

0 Kudos
Message 1 of 7
(7,915 Views)

Hello,

 

Is there any way you could post the new and old model?  So that we may look to reproduce the behavior.

 

Regards,

M. Whitaker
ni.com/support
0 Kudos
Message 2 of 7
(7,891 Views)

I do not have models I can send.  This is easy to recreate.  Create a Simulink model with outport arrays, build  and add to System Explorer.  Change the name of the outport array in Simulink, build and use the "Reload Simulation Model" option.  I've attached a snapshot of systems explorer.  Below the current outport array (stm2cdh_msg_out) you will see 3 previous names showing up as empty folders.

 

0 Kudos
Message 3 of 7
(7,878 Views)

Thank you for this information.  I was able to reproduce the behavior you were experiencing.  I will file a CAR, so it can be handled by the correct team.

Regards,

M. Whitaker
ni.com/support
0 Kudos
Message 4 of 7
(7,854 Views)

What is the status of this? Did this issue get resolved in a newer version of Veristand?

0 Kudos
Message 5 of 7
(4,896 Views)

Jansobj,

 

I wanted to let you know that the CAR number that this is being tracked under is 572529, and so you are able to look for this CAR number in future patches and bug lists releases. At the current time it hasn’t been addressed.

 

However, you should be able to delete the unused folders that the model leaves behind without any ramifications. Please let me know if this is not the case and we can readdress the issue.

Sarina
Applications Engineering
National Instruments
0 Kudos
Message 6 of 7
(4,884 Views)

I would like to make a correction to Sarina's statement. The CAR ID is 636420 and indeed the issue is unresolved.

Nestor
0 Kudos
Message 7 of 7
(4,872 Views)