LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to create an application that utilizes Source Control?

All,

Is it possible to create an application that utilizes Source Control?  I have created a VI that checks out a file editis it then checks it back in.  (LabView 8.6.1  with SVN via PushOk)  When I build the appliacation I get:

"Warning -2970 occurred at an unidentified location

Possible reason(s):

LabVIEW:  You cannot perform source control operations until you configure source control in LabVIEW. Select Tools>>Source Control>>Configure Source Control to configure source control."

Is there a step i am missing?

 

Thanks in advance!

Rich

0 Kudos
Message 1 of 8
(3,975 Views)

Hi there

 

I assume you're dealing with the SCC VIs from NI. Are there any problems when you run your application from LV? Is the SCC properly configured (Tools->Options->Source Control)?

 

Just a wild guess: Try to copy the SCC related keys from LabVIEW.ini to <Your App>.ini.

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
Message 2 of 8
(3,957 Views)

I think NI DOES NOT officially support SVN (even with PushOK) as an SCC tool. This might be a reason for your getting an error in the application & not in the IDE.

Message Edited by parthabe on 06-30-2009 01:36 AM
- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 3 of 8
(3,952 Views)

NI does support the SVN (via PushOK), well support, they have tested it. There are special cases for almost every SCC possible inside the SCC VIs (including PushOK).

 

However most functions work with a proxy, the actual VI is loaded dynamically based on the actual SCC implementation, the dynamically called VIs are not standard present inside the runtime.

 

Ton

 

2k post

 

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 4 of 8
(3,944 Views)

Rich,

 

as far as i understand it, you have an executable which should checkout VIs automatically. So running this exe creates that error.

My guess is that you haven't configured SCC for the Run Time Environment (RTE). I am not sure if this is possible at all, but you can give it a try:

Just copy the entries of your LabVIEW.ini (the developement environment ini) which contain "SCC" to the ini-file of your exe. I don't know if this will work and if those keys are all which are needed, but you can give it a try....

 

hope this helps,

Norbert 

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Message 5 of 8
(3,941 Views)

Thanks to all your help!  I am getting closer.  Adding the SCC to the ini file was one issue. 

 

SCCOpWarnPrompt="9"
SCCConfigData="rwelch;Main;C:\SProjects\Labview\Library\Main;file:///C:/SVN/LABVIEW/Library|user:rwelch|rev:HEAD"
SCCProviderName="PushOk SVNSCC"
SCCProviderLocation="WinCI"

Now I am gettting "

Open VI Reference in NI_SCC.lvlib:SCC Add.vi->SCC_Open.vi->PromoteToGolden.vi<APPEND>
VI Path: <b>C:\BUILDS\Labview\XID\promote\PromoteXID.exe\WinCI Add.vi</b>

Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared library." 

Does anyone know which files should I force to dynamicly load?

 

Thanks Again!

Rich 

0 Kudos
Message 6 of 8
(3,914 Views)

Add all VIs in

..\National Instruments\LabVIEW 8.6\vi.lib\SourceControl\Providers\<your provider>

 

<edit>

actually there are .lvlibs for each provider you can add to your project

</edit>

Message Edited by chrisger on 06-30-2009 08:59 AM
Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
0 Kudos
Message 7 of 8
(3,908 Views)

Rich,

 

the new error message indicates missing components which are called dynamically. In order to solve the issue, you have to include all dependencies on your target machine.

It seems, that some VIs are missing, so you have to manually insert the VIs as "Always included" to your exe (or distribution kit aka installer).

 

hope this helps,

Norbert 

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 8 of 8
(3,907 Views)