LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LVCompare is causing errors. "Open.VI Reference in LVCompare.VI" Does anyone know what could be causing this?

Could anyone kindly help me with this? I'm really stuck and I've been trying to figure this one for a while but I really don't know what to do here.

 

I'm trying to configure LabVIEW Compare with the versioning tool that I use. (I'm using Git Fork, the latest version)

 

I'm also using LabVIEW 2017, professional (I've confirmed in the about section). I can use LVCompare if I call it from the tools menu (So long as the VIs have different names), but it fails whenever I attempt to do an external diff with the tool I'm using.

 

I read the guide from Delacor and here's the config I ended up using:

 

HorseBattery_Stapleguy_2-1645463758999.png

 

The error I get is this:

 

HorseBattery_Stapleguy_1-1645463508776.png

 

Does anyone know what could be causing this issue? I've actually tried googling for the issue but I haven't found similar posts. The only thing I found is an NI error / knowledge post about an error with the Invoke method. But that's not my issue as the error is different, and I do have LabVIEW professional.

 

What I do specifically, Is that I make a local change in the repository. Once it appears in "Local Changes" in Git Fork, I attempt to do an external diff in that SubVI but it fails with that error. It doesn't seem to make a difference if I have LabVIEW open or not / project open or not.

 

If there's anymore info I have to include please let me know, this is a little bit outside of what I know so I genuinely don't know what else I should include. 

 

Any help is appreciated,

 

0 Kudos
Message 1 of 4
(1,594 Views)

Hi HorseBattery_Stapleguy !

 

Did you solved the problem? I have the same issue and I do not know what the problem is. 

I know LVCompare works, because if I use CMD to launch it with differents VI-s it works properly.

I think is something about the path of the VI in the "REMOTE" branch

0 Kudos
Message 2 of 4
(1,424 Views)

LVCompare will try to open the LVCompare code on the last active target in your system.

If you happen to have RT or FPGA targets, make sure you select a host target in your project before calling LVCompare.

Why LVCompare does not initiate a new host context before executing is beyond me.

0 Kudos
Message 3 of 4
(1,419 Views)

I actually did, I had to use some bash scripts I found and modified them a bit.

 

The reason they failed was because of some issue with paths in windows as far as I remember.

 

I'll upload them if I get the chance.

0 Kudos
Message 4 of 4
(1,336 Views)