LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Working on LabVIEW project from two PCs simultaneously

Hi all,

 

Just a short query:

 

Me and my colleague want to develop two different parts of the same LabVIEW project.

Is it possible to work on the same LabVIEW project from two different systems simultaneously? (If LabVIEW project is saved on the network shared drive of the company)?

 

P.S: Connection to RT Target is required for only 1 Host PC.

 

Thanks in advance!

 

 

Best Regards,

 

Rahul

0 Kudos
Message 1 of 7
(3,980 Views)

Hi Rahul,

 

possible: yes.

Recommended: NO!

 

My recommendation:

Have the LabVIEW project local on each development computer. Synchronize using a SVN solution (software versioning tool)!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 7
(3,972 Views)

A software code control software will be essential.  But merging the project file can be interesting.  If you are brand new to the whole SCC thing, I recommend Tortoise SVN.  It is a Windows Explorer interface that is simple to use.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 7
(3,938 Views)

I agree with Crossrulz -- use a Version Control System, Tortoise SVN is pretty good (though you need access to a Subversion server), and Project merging "mostly" works.  I must say that working with a team of one (BS at work and BS at home), SVN is a wonderful way to keep synchronized (as long as I remember the rule "Commit before leaving and Update when starting"), but now that I'm doing some "small team" (2-3) work, we do occasionally "stomp on" each other's files (usually because someone "forgets" to Update First, Commit Last.

 

There are two types of Collisions that can arise -- LabVIEW VIs and Controls, and LabVIEW Projects.  The VIs and Controls you can figure out using the LabVIEW "Compare" utility -- rename "My Bad.vi.r001" and "My Bad.vi.r002" to "My Bad.vi.r001.vi" and "My Bad.vi.r002.vi" (just add ".vi" to the end).  Now Compare will work.  Figure out which you want, delete the others, and rename the "good" one by deleting the final ".rxxx.vi" extensions.

 

If the Project is corrupted, and you've been clever enough (or, perhaps, foolish enough) to (a) have your Project all contained within a single top-level file folder (with sub-folders underneath, perhaps), then I usually just delete the Project file(s) and recreate it, doing an "Add Folder (snapshot)" to "get everything" and discard what I don't want (like .aliases and possibly Documentation).

 

Bob Schor

0 Kudos
Message 4 of 7
(3,901 Views)

My advice - split apart your architecture into components and develop each solely within a project library. That way a project can reference the libraries but not their content and avoid any messy merging problems.

Message 5 of 7
(3,880 Views)

The VIs and Controls you can figure out using the LabVIEW "Compare" utility -- rename "My Bad.vi.r001" and "My Bad.vi.r002" to "My Bad.vi.r001.vi" and "My Bad.vi.r002.vi" (just add ".vi" to the end).


 

 

That's usually unnecessary if you set up TortoiseSVN to do it automatically...

 

How to set up TortoiseSVN to use LabVIEW compare utility

 

 

0 Kudos
Message 6 of 7
(3,863 Views)

 

Thanks all for sharing your ideas and all possible solutions.

Really appreciated.

 

Kudos,

Rahul

0 Kudos
Message 7 of 7
(3,678 Views)