James N

I'm new to the Subversion world too. About a month ago I setup a server in our lab for our department's SCC needs. I was advised to do the one-big-repository method with all my LabVIEW code (or in general, any mass of files that are related). That way it would be easier to reorganize the directory structure in the repository if necessary. A lot of advice I'm taking of faith.. figuring I'll understand the benefit down the road. I going to create another repo for each dept. member just for misc. files not related to any LabVIEW projects. Yeah, migrating existing code into the repository is another challenge. I'm almost wanting to dictate that anything which goes into the repository must be cleaned up and rewritten to be more "reuseable". I really want to use this as a catalyst for new and better coding. I'm reluctant to populate the repository with the mess we've been working with before. Another tip, in LabVIEW edit the Options and check the "Tread read-only VIs as locked" and "Do not save automatic changes". Then before each commit and after each update, make all of your files READ-ONLY. As you know, often LabVIEW will indicate a file has changed when you really didn't change anything. Say some path to a DAQ VI has changed. You may not want to increment the revision number just because of this. Then change the write status of only those VIs you are working on. Or you can do it when you save and the "Cannot save VI..." message appears. Ctrl-M will "unlock" any read-only VIs allowing you to modify it. But the file on the disk is still read-only and thus protected. Good luck, James

Forrest, Personally I like the ease and reliablity of the serial port. Even though the physical 9-pin connectors are going away, you can always purchase a $20 Belkin USB to RS232 adaptor that shows up in Max like any other Com port. We've been faced with the option to upgrade the communication method on a test box we use. Going USB requires more development on both ends. How does the guy developing the box write USB drivers and how to I interface to them in LV? Like I say, RS232 is simple and for us, already done. Speed is also not an issue for us. Using a TTL interface means you'll need a DAQ card to acquire the signal (or some combersome parallel port DIO scheme. I'd be interested in learning a simple way to acquire a TTL signal using standard PC hardware, if anyone knows...). If you will always have a DAQ card in the system with your third party box, then maybe it's no problem. I didn't want our box to require a DAQ card in every application. We didn't investigate a TCP/IP approach but again that adds some level of complexity over the RS232 solution. Just my two-cents... -James

We have over 100 full and professional licenses on our SSP but haven't received any CDs yet. Although we have received the Developer Suite CDs for which we have 5 licenses. Only a few have upgraded to 8.20. So we've just downloaded the installation from ni.com. Now I'm anxious to get the cool carrying case. -James

Cool.. After 8 years I have never heard of annotations before. Goes to show... you learn something new everyday. See if my modification makes sense to you. -James Download File:post-5791-1157029287.vi

Once the XY graph is on the front panel, right click on the Y-axis and select "duplicate scale". Then you can right click again and swap the scale to the other side of the graph. You'll also need to identify which plot associates with which scale. You can do this through the properties dialog of the graph. Go to the "Plots" tab and select the plot to modify, then choose the appropriate Y-scale to use. I think this will get you started. There are still many cosmetic aspects you can adjust. For the pointer, you could use a cursor. Right click the graph and make visible the "Cursor Legend". You can move the cursor around during run-time or programmatically control the cursor through a property node of the graph. Using the cursors can be a challenge but it can create some decent user interfaces. Hope this points you in a good direction, James

Here's how I handled it.. Open file Explorer and right click on the root diretory that you want to mass compile, then search for "*.svn.". Zip up all of those .svn directories. Winzip has a function to "Save full path info". Be sure this is checked. Now delete all of the .svn directories in the Search Results window. Do the mass compile. Last, unzip the all of the .svn directories back to their respective paths. -James

Keith, See how this VI works for you. I'm a fan of disposing of references manually. I like to see it being done vs. thinking it's being handled for me. The draw back is that the VI probably stays loaded into memory. -James Download File:post-5791-1156210685.vi

I had the same problem. Here's a portion of NI support's response: _____ This appears to be a constant folding bug. I apologize if this is review, but constant folding is the process by which the compiler takes the code and wraps the constants into the compiled machine code itself rather than allocating storage in memory for them like variables. LabVIEW appears to be tricked into thinking that it doesn't need to recheck the color control array input again, since all the inputs it receives in the loop are constants. We have seen similar issues on rare occasions with loops and constants in LabVIEW 8.0, though not this particular instance. I am quite confident you would see the same behavior with a For Loop in your code. I will add your information to those existing reports for further investigation by R&D. This will be a high priority for us to say the least. In the meantime, I would recommend one of the following workarounds. First, as you mentioned, you could place the Index control inside the loop, which will short circuit the constant folding that causes this bug. Alternatively, you could leave the Index control outside the loop and turn its wire tunnel on the loop frame into a shift register. Then just wire the data through from the left shift register node to the right one. That will force LabVIEW to reread the control value every time. ____________ -James

Hey All. Long time reader, first time writer. There's a lot of cool stuff here. The NI Week blogs have been a highlight recently. I work at Lexmark and we rotate people who attend NI Week. This was my year to go but I was schedule to be in Asia for four weeks.. which got postponed last Saturday. Sad story sadder (except the part where I would have been in southern Asia in August).. looks like everyong had a lot of fun and I missed it. -James