running LV when source control is not available

[instrumento]

My laptop has a LV "home license" so I can run it disconnected from my work's network. My source control, perforce, can run disconnected from my work's network, and I can sync back whatever I did when I reconnect.

Now, if I configure LV to use P4, and I'm disconnected, I have to wait a loooooooooooooooooong time for LV to tell me that it can't connect to source control, and then it disables the source control configuration. Trying to exit LV takes a looooooooooooooooooong time, then it shows a "Resetting VI" dialog, on NI_SCC_ConnSrv.lib:SCC_ConnectionServer.vi, and never exits!

Not very useful, actually outright annoying.  I'm on 2012, is this better handled in newer versions? Or is there something that I didn't configure right?

[j_bou]

Hello instrumento,

The first troubleshooting step to take is to make sure you configured LabVIEW correctly. Refer to the two links below for guidelines.

Configuring LabVIEW to Use Source Control

https://www.ni.com/docs/en-US/bundle/labview/page/configuring-labview-to-use-source-control.html

Using Perforce with LabVIEW

https://decibel.ni.com/content/docs/DOC-3203 

If this does not help you resolve the issue, provide us with more information about the error which LabVIEW in throwing when it does not successfully connect to the source control.

Thank you,

Jonathan

[instrumento]

Guess I should have made clear that everything works fine when I'm  at work, and can reach the perforce server, so I think I configured it properly.  I can check things in and out, no problem.

It's when I'm not at work and thus the perforce server is unreachable that it doesn't work.

• Off the network I can still run perforce in disconnected mode, no problem.
• Off the network, if LabVIEW is not configured to use Perforce, I can run LabVIEW as the laptop has a "home" license, no problem.
• Off the network, if LabVIEW is configured to use Perforce,  it takes for ever to start, then pops up a warning that it will disable source control.  After I acknowledge that dialog, and manage to open a VI, LV is unusable taking for ever to acknowledge any input, be it keyboard or mouse, like it is either competing with a looping thread or just timing out still trying to connect to perforce.  Exiting LabVIEW doesn't work, just brings a popup with "Resetting VI I_SCC_ConnSrv.lib:SCC_ConnectionServer.vi" and I have to kill LV.  The only way to make it work was to remove the SCC entries from LabVEW.ini, but I'd like to avoid  editing the file back and forth when I'm at work or not.

I'm calling this in at lunch time....

[j_bou]

Hello Instrumento,

Take a look at the following link:

Working Disconnected From The Perforce Server:

http://answers.perforce.com/articles/KB_Article/Working-Disconnected-From-The-Perforce-Server

It turns out that Perforce keeps all unopened files in the workspace as “Read Only”. Therefore, to work offline, you will need to make the files writeable to be able to work with them. The article explains the details. Hopefully this helps.

Thank you,

Jonathan  

[instrumento]

I believe I figured out what is wrong in the interaction between LabVIEW and P4.

One reason is that a lot of times, the popup to enter the password for p4 is actually a popdown buried underneath a lot of windows.  This leads to confusion, LV freezing, popping up the dialog that the SCC is not available, etc.

Another reason is that if LV dies (when I'm playing with half debugged DLLs under Visual Studio), the next time I start LV it complains it can't connect to P4, and then I have to exit and restart LV for it to connect.

After a while one gets used to these idiosyncrasies, but until then one wonders what's going on.

[levitt2me]

Hello Instrumento,

I am happy to hear that you found some sort of work around for the issue that you are experiencing.  I am not sure why that keeps happening or what the previous error you were seeing was.  However, I have found an article from Perforce that talks about how to Avoid Source Control Errors in LabVIEW.  I hope this helps!

Casey L.

Applications Engineer