Error constant ring should be converted to code when saving in previous version

[Mat_P]

Currently if you use the new error constant ring and want to save your VI into a version older than 2012, you get a broken code telling you that this object doesn't exist.

It should be automatically converted to some code as it's already the case for other new functionnalities.

[AristosQueue (NI)]

You are right that it should be... and on my machine, it is. I re-ran the entire save-for-previous test suite for this node just now... if you save backwards, it does indeed replace the node with the generated code (I double checked by hand for LV 2011, 8.6 and 8.0 just to be sure). Do you have something incorrectly installed about your LabVIEW?

I'm going to ask that this be pulled out of the idea exchange and moved to the regular forums for AEs to assist you further.

[Mat_P]

That's strange, it might come from the French localization of LabVIEW. I have tested on two PCs : LV 2012 French x86 on Win XP x86 and LV 2012 SP1 French x86 on Win 8 x64.

Both gave me the same result: Missing Object. The object "Error constant ring" doesn't exit in previous version

About the installation, I don't think it could come from it. I'm a former AE (I left NIF 2 months ago) and those were not my first install

[AristosQueue (NI)]

Turns out Mat found a bug -- the Save for Previous works fine --- as long as the terminals are all wired. If you have the output terminal unwired, save for previous doesn't generate code and instead replaces with a label. That's my mistake. CAR 410500 filed.

[JordanG]

Converted to a CAR

[Jeff-P]

CAR 410500 discussed in this thread was fixed in  LabVIEW 2014.  For a more complete list of bugs fixed in LabVIEW 2014, check the LabVIEW 2014 Bug Fixes. You can download an evaluation copy of LabVIEW 2014 at www.ni.com/trylabview/ or if you have an earlier version of LabVIEW installed and an active SSP subscription, you will be able to download the latest version of LabVIEW through NI Update Service.

Regards,

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect 

[Pie566942.0]

I don't know if this came up during your tests, but when I save LabVIEW 2013 for LabVIEW 2012, the VIs are broken in 2012 because the error ring, "Library version is incompatible with Xnode version".  The ring shows up grayed in 2012.  If I replace it with the "2012 version" and then Undo the replace, the contents of the ring appear to be preserved and the node relinks.  Unfortunately, nothing gets fixed and there are some wierd run-time errors.  I don't know if it matters but I'm using a %s parameter in my ring.

-Steve K

[FabiolaDelaCueva]

This issue is back on LabVIEW 2018. If I save a DQMH project built in LabVIEW 2018 for previous, the error rings are broken.

[confused2000]

same problem using labview 2018 and 2017.

Get Error Ring: Library version is incompatible with XNode version. Replacing the error ring did not work. Please let me know the best solution for this problem.

[AristosQueue (NI)]

Problem will be fixed in LV 2018 SP1. Sorry -- I forgot to update the Save-For-Previous code when I fixed a bug in the Error Ring recently.

[AristosQueue (NI)]

You could save to a version back before the error ring came into existence (LV 2011 or earlier). That will change the ring into regular cluster-building code. You might not want to save your whole project that far back, but the VIs that include error rings might suffice.

An annoying workaround, yes, but maybe it'll get you unstuck. I'm sorry for introducing the problem.