01-22-2015 02:26 PM - edited 01-22-2015 02:27 PM
Hello,
I was hoping to take advantage of aliases in a project on which I'm working so that I can decouple some of the information channels that I'm using. However, when I went to write to an alias defined in my system definition, it does not do anything (no error either).
So, to test if aliases worked at all via the LabVIEW API for VeriStand, I created an alias to try and read from it. This (reading from an alias) work perfect. Also, I tested to make sure that VeriStand was capable of writing to an alias via the channel fault manager. This also worked just fine.
Does anyone know about this issue? To me, it appears to be a bug.
Software: LabVIEW 2013 SP1 + VeriStand 2013 SP1
Thanks.
01-22-2015 02:47 PM
Thanks for the post! We do test writing to aliases from the LV API extensively (that's the same API our Workspace uses). If you post an example system definition and test VI we might be able to help track down what we're missing here.
01-22-2015 04:36 PM
CLA, CTA
01-23-2015 08:30 AM
Jiri, the alias was set to a model inport (not a parameter).
Jarrod, I was using my full project to do this so I will work on trying to create a test project that will recreate the issue (or not). Obviously if it doesn't recreate the issue, I'll have somewhere to be looking.