LVMerge.exe not working with LabVIEW 2024 Q3 64-bit

[Lolovall44]

Hello

Same problem for me with LV2024Q3 32 bit and LVMerge.exe apparent version 1.0.

Merge tool accessed from menu Tools/Merge/Merge VIs... works fine but a call from command line just opens the LVMerge.exe window without actually starting the merge process.

Any solution?

Félicien

[Bob_Schor]

My only experience with LabVIEW "Environments" is the myRIO.  Have you tried going to Tools, Choose Environment, and choosing "LabVIEW" (without the Compact RIO)?

Bob Schor

[JJ_dev]

Hi Bob, thanks for responding. sorry but I am not getting your point, in my labview tools menu there is no option to click on or select the "Choose Environment".  😞

I may not have been clear enough with my previous comments. "Labview installation environtment" This error appears in labview after to install CRIO support drivers for labview. The only way that I know to fix this error is uninstalling or removing the driver "NI Compact Rio support for labview" but this is not possible if someone intends to work with CRIOs. For that reason I think this driver is the root cause of the error.

if you want to reproduce this error CRIO hardware is not needed. installing the CRIO driver in labview and calling Merge tool externally from windows console its enough to reproduce it. 

Please let me know if there is quick way to enabling/disabling this driver or other solution to fix it. Thank you in advance.

[Bob_Schor]

Hello, JJ.

     I think I didn't quite understand your question, but now "I see the light", and have what I hope are some useful conceps.

     My early experience with LabVIEW was also my early experience with Version Control Systems.  I learned Subversion, and now maintain my own Subversion server (tiny, so far only one user, though I'm trying to get more takers).  When I've used Subversion with text files and it gives me a report that says it can't commit, and walks me through the "merge" process, I can easily "see" the differences and can decide which of the options I wand to keep.

     For LabVIEW, as you note, you need to use LVCompare to help you out.  Here's my strategy (excellent when there are only a few (<10) Conflicts (I've taken some liberties with the extension names, below, because I haven't hgad to do this recently and I forgot Subversios's convention)::

1. Rename my.vi.mine to my.vi.mine.vi.
2. Rename my.vi.orig to my.vi.orig.vi.
3. Rename my.vi.new to my.vi.new.vi
4. Figure out which one you want.  If you've "been bad" and havent cone a Commit recently, so none of the above is a "clean" (meaning all features you want are there) version, you can print out the VIs and study them to decide which to use.
   • Otherwise, choose one and do an Compare with another.  Choose which to discard.
   • Repeat pair-wise comparisons until you know which one to keep.
5. What you now want to do is to delete the files you don't want and rename the file you do want by taking off any "extra" extensions it might have.  Note that clicking on the file name in Windows Explorer (at least, for me) will highlight the filename, but not the extension, so you can "right-arrow" and start deleting the "bookkeeping" part of the extension until you get to the final .vi or .ctl.

Bob Schor