VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1124 After modifying a workspace object

Solved!
Go to solution

I'm hoping someone can help me with an issue I am experiencing modifying workspace objects in Veristand please?

 

I don't believe I am trying to do anything overly complicated and in fact it is covered by option 2 of this link http://www.ni.com/tutorial/9989/en/ -  "2.Changing the Appearance of a Workspace Object". 

 

One of the problems I am having is that I am using LabVIEW 2015 and Veristand 2014. If I simply modify an existing workspace item and save with a new name, Veristand gives me an error stating that the object isn't compatible when I try to drop it on the workspace. 

 

So I used the option to save as an earlier version, but now I am getting the following error message when I try to drop it on the workspace:

Error 1124.JPG

I have tried a few things but to no avail, so any help would be greatly appreciated.

 

Thanks Si. 

0 Kudos
Message 1 of 7
(2,719 Views)

Hi, I belive your software combination is wrong.

If you are using LabVIEW 2015, you should use VeriStand 2015.

Also using LabVIEW 2014, use VeriStand 2014.

 

 

See this compatibility table.

http://www.ni.com/product-documentation/54028/en/

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
Message 2 of 7
(2,695 Views)
Solution
Accepted by topic author SRML1124

This is because VeriStand 2015 uses VIs which is compiled in LabVIEW 2015.

If you edit VIs with LabVIEW 2014, the compatibility is lost, VeriStand cannot call those VIs.

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
Message 3 of 7
(2,693 Views)

Ah okay, I was worried that would be the root cause. 

 

So saving my VI (LabVIEW 2015) as an earlier version (LabVIEW 2014) isn't a viable solution? 

 

I suppose I will stick with the standard workspace objects.

 

Thanks Si?

0 Kudos
Message 4 of 7
(2,686 Views)

Saving earier version may be a solution but i have no confidence. I haven't tried it : (

 

Why don't you use a compatible software?

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
0 Kudos
Message 5 of 7
(2,682 Views)

Hey, did saving VI as an earlier version solve the problem?

 

If you could have solved, plz make this thread resolved by setting "mark as solution".

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
0 Kudos
Message 6 of 7
(2,663 Views)

Unfortunately saving as an older version did not work, but I now have a access to LabVIEW 2014, so I have got around the problem. 

 

Thank you for your help.

Si

0 Kudos
Message 7 of 7
(2,655 Views)