orko

From page 83 of the upgrade notes: http://www.ni.com/pdf/manuals/371780a.pdf ***************************** File Size Improvements Saving VIs from earlier versions of LabVIEW in LabVIEW 8.0 significantly decreases their file size. The file size of VIs you save in LabVIEW 8.0 is about 55% less than the file size of the same VIs in LabVIEW 7.1. The file size of LLBs in LabVIEW 8.0 is about 20% less than the file size of the same LLBs in LabVIEW 7.1. ***************************** Pretty cool stuff Joe (orko)

What is the warning message? Thanks for testing it out on LV8! Joe (orko)

Jenny, It would help if we had a little more information. What are the values you are comparing? Are you using the blue Express "Comparison" VI or the little yellow triangle "=" operator? I'm assuming since you are getting a 2D boolean array out of it that you are comparing two 2-D boolean arrays? Thanks for clarifying, Joe (orko)

Here you go, hot off the press Download File:post-3266-1140055304.vi LV 7.0

Not sure what you mean by "flipping" them, but you can play with the fonts in the property browser under "PlotTemplate->X/YAxis->Labels->Font" You can invert the whole axis by making "PlotTemplate->X/YAxis->Inverted"=True. This flips the plot and axis labels 180 degrees. This may be what you were after. Joe (orko)

In english version (7.1.1) I see this: So looks like you may have a typo over there (or is that a typographischer Fehler?) Joe (orko)

New rev to fix the following: 1) Button 1 clicks are now the only ones which enable moving 2) Disable comment added. I was getting some freaky behavior when mousing off of the right-click menu items, so I enabled only Button 1 (left click on most mice) for movement. Also, added in a comment explaining that by disabling a control (such as an array or waveform graph) lets the operator click anywhere on it to move it. ... still trying to find time to make this a subVI Download File:post-3266-1140020604.vi LV 7.0 Joe (orko)

Glad it worked out. I'll file it away to look at when I upgrade to 8.0 (hopefully next month). I assume this would be one of those times where you won't be able to save to a previous version (7.1), since it uses version specific pane properties(?) Joe (orko)

Working on it

Welcome Robst, may you find the help useful and find it rewarding to be helping others here at LAVA. Joe (orko)

Did I not notice this on the intro pages, or is it not displayed? If not, it would be nice if the "house rules" were available to read somewhere.

As am I. What good is a number if you can't learn from your mistakes??? I thought I was doing alright but only received a 32, which is barely squeaking by. Granted, I took it in 25 minutes and wasn't in the "mindset" to take the test, but would still like to know what I need to work on....? I felt real confused when the window just closed on me after question #40 and took me to the LV homepage... No "test completed" page? I was lucky that I caught the email in my inbox with my score. If it was an email account that I checked less frequently, it would have bothered me until I found it. Another thing I noticed is that you can't go back and retake the test once you've passed. Personally, I would think that passing it earns the right to take it again(or at least review your answers), shouldn't it? What is the purpose of limiting it to just one time? How long are you locked out of the test until you can re-take it (if you passed)? I'm assuming you can retake as many times as you like if you fail? Joe (orko)

In LV 7.1.1, you could use the "ViewDistance" property in the property browser (basically "zooming" in on the plot). I don't have my LV 8.0 in front of me to compare though. HTH, Joe (orko)

NI's solution, since LV8.0 introduced multiple "panes" to the FP: http://digital.ni.com/public.nsf/allkb/D54...&node=133080_US Joe (orko)

:worship: LV Merge! :worship: We can only wait and hope that it is in the works behind NI's curtain... Joe (orko)

I wouldn't write off clusters so soon, since it sounds like your alternative is to wire 20+ boolean controls to a subVI? I'm fairly certain that would fall under the category of "overcrowded" I don't believe that bundling would cause very much if any performance hit on your application, and would save tremendously on portability and maintainability of the code in later projects. Can you imagine dropping this subVI into a new VI and wiring each input up individually? Whereas with a cluster it's as easy as "create control" and you get all of the controls you need inside the cluster already labeled and GTG. Now if you were passing along large sets of data, clustering probably wouldn't be the way to go. HTH, Joe (orko)

Just to be clear, what do you mean exactly by "label an indexed array item"? It seems to me that arrays are indexed elements, and clusters are labeled controls. If you label 5 items in an indexed array and add a new element, what do you label the new one? What you may be after is an enum, or a ring? Thanks for clarifying, Joe (orko)

Two things I may suggest when testing WMassey's VI are: 1) make sure you are selecting the proper VISA resource name for your system for COM1 on your system. Unless you have aliases already set up, it will most likely be something like "ASRL1::INSTR". 2) Make sure you wait at least ten seconds after hitting "send" before giving up on the reply. That is what the timeout is set to in the configuration here, and since you said you probably are only getting back ~5 bytes, you'll hit the timeout for sure unless you lower the buffer to something less than 5 (although I would lower the timeout myself). HTH, Joe (orko)

The VISA resource name (taken off of the reference output of an Visa Open primative) can be wired to a Instrument property node that gives you all kinds of information about the devices. One of these properties is the Interface Information:Interface Description property which will spit out things like "ASRL1 (COM1 - Communications Port)" or "ASRL10 (LPT1 - ECP Printer Port)" which can be parsed easily for COM1 or LPT1. If you wire a "VISA Find Resource" with a search query like "ASRL?*INSTR" and wire the output array to a FOR loop, you can iterate through them getting those human read-able names. Of course, that may not be the easiest way, but it seems to be the least dependant on machine specific things such as aliases. YMMV, Joe (orko)

That screenshot seems to have been from a temporary glitch in the NI force protection grid. 8.1's not in the options anymore. From a fairly reliable source: 8.0.1 is scheduled for Q3 2006. That's as good as I have right now. Joe (orko)

Thanks for the example pointer. I knew I had seen it done somewhere before... It's funny, the thought of making a LED indicator (round and rectangle) version of BlackOut came to my mind as I was wiring this up! Hehe... I wonder how Battle Tank or Tempest would look in an XY plot... Probably much better than the originals! Defender of the Pong, Joe (orko)

Reminds me of the binary clock I saw on there: http://www.thinkgeek.com/homeoffice/lights/59e0/ When I had entirely too much time on my hands I made a LV version of it, I just can't seem to find it in my archives

Someone asked if it was possible. Actually it was a request from info-labview where the requirements were for raw display of multiple arrays wth indeterminate sizes, with the ability to compare side by side with large data sets. Evidently screen real estate was limited and they wanted a way to move the data sets around to compare against each other. Other than that I don't know much about the usefulness of this, but I've been fooled in the past thinking that I would never use a tool until that one fateful day... Cheers! Joe (orko)

I whipped this up to enable dragging (selected) controls around on the FP while the VI was running. Of course, comments would be most welcome. I'm working on an optional perimeter check to make sure that the control doesn't get "hidden" off of the FP, and making this a sub-VI with a configurable input array of control refs (if possible). Are there any other useful features I could put in? Download File:post-3266-1139872912.vi Joe (orko)