hobbs

Sorry, I should have been more specific. To my knowledge, if an FPGA file is not opened through a LV project (as in lvproj file) it is not edited as an FPGA file. As a result, the project file must be check out and then updated every time you want to edit an FPGA file. Additionally, should two members need to edit FPGA files at the same time, the lvproj file will develop a conflict.

I'm working on a team of 5 to develop a relatively large software project spread across a PC, FPGA (R-Series card), cRIO, and an ARM board. Our last attempt this problem lead to a source control nightmare. We managed an svn repository using tortoisesvn. This became problematic because we couldn't edit any of the FPGA files without checking out the entire project. This lead to parallel projects being worked on and the eventual merging problems. I know that LV has a source control manager, but to my knowledge it requires you to have a relatively expensive source control manager. Does anyone have good ideas about how to manage a large, multi-fabric project without buying perforce?

I'm on a college robotics team competing in the Intelligent Ground Vehicles Competition in Detroit, MI. We recently had an 9642 sbRIO have a component fail. Is there anyone in the area that would be willing to lone us a board for the next three days? I know our recent failure would not inspire confidence in getting it back in one piece, however, if it does fail, we would happily buy you a new board. We simply can't get one in time. Thanks! Nick