Jump to content

crossrulz

Members
  • Posts

    530
  • Joined

  • Last visited

  • Days Won

    21

Everything posted by crossrulz

  1. If you put in an indicator to see the array before your interpolating, you will see that it has two elements (36, 15370). What you need to do is split the signals and take the second signal (frequency) and then interpolate.
  2. I think this will accomplish what you are after...
  3. They could at least learn to spell LabVIEW correctly (capitalization is wrong multiple times, two words once)
  4. where is this error list you speak of?
  5. It looks like Default Value is a scripting property (at least as of 8.6). So in the development environment, the answer would be yes. No so in an application. A work around may be to save your current value, invoke the Reinitialize to Default (use an invoke node), grab the new value (the default), and then set the value back to your original saved value. Hopefully somebody smarter than I has a better idea than that.
  6. Your problem is in where you are trying to figure out when button was pressed. The state tunnel out of the for loop will only output the result from the last button check (Button 3). If you want to keep what you have, change the tunnel to a shift register and feed the previous value through in the false cases. However, polling controls are BAD. You will be much better off with an Event Structure. NI's example is from right when the event structure was coming out and I have a feeling it was simply upgraded from a previous version long ago. Polling uses up lots of CPU unless you have waits in your loops. An event structure will sleep until one of its registered events have occurred.
  7. I'll take stability over fancy new toys any day!
  8. The most simple way would probably make another consumer loop for showing your non-modal dialog boxes. Have another queue (or notifier) running around to tell the loop to run a certain window. You would be limited to one dialog box opening in the new consumer, but it is a quick and easy way to handle your issue.
  9. Shaun hit the big one. You need to properly shut down your system: turn power supplies, function generators, DIO, etc. off, reset other equipment, close out references and handles. The abort button will not do that. I have troubleshot a program where someone hit the abort button and ran again and wondered why the DIO port was not available (because it wasn't released from the previous run!). My experience, however, is mostly with non-LabVIEW people as my user and 99.9% of the time they do not see my giant Stop button (even though it is in the top right corner) and go straight for the Windows "X". If you don't handle this properly, the VI is still actually running even though you don't have a front panel. This will lead to a similar problem as just aborting. So I don't use Stop buttons anymore and just use an event structure and the "<This VI> Panel Close?" filter event. I discard the event, close up everything properly, and then shut down (if needed).
  10. You can use a property node to set the Minimum and Maximum values of the control inside the array. All items in the array will have the same properties (not sure if you care about that).
  11. I've was playing around with VIPM 2010 yesterday and found that I can now build all the packages I want with the free community version. There used to be limitations, but it looks like JKI decided to open it. Here are my major reasons to use VIPM: 1. It manages your user library for each version of LabVIEW you have installed, 2. You can define your palettes a lot more easily than using LabVIEW's palette editor, 3. You can install only which packets you need, 4. It handles packet dependencies (ex. my GPIB packet need my Wait packet in order to work). These are things a normal SCC just cannot do, or at least not cleanly.
  12. So was I. Luckily Christina set me straight in her blog post.
  13. I have been looking into this for the last few months and VIPM is the only thing that I have found that will do this. And it does it well.
  14. NI will release a service pack in the spring. That's how their new software cycle is going to be starting with 2009.
  15. Darren explains them fairly well in one of his weekly nuggets.
  16. What exactly do you mean by "merge"? Are you looking for a 3D array or a concatenation? It really depends on what the data is and what you are doing with it (post processing algorithms, save to disk, etc.).
  17. Have you looked at the Array Subset Function?
  18. I feel your pain. What I ended up doing was copying the distribution DVDs onto my hard drive and then install from my hard drive. The installer builder looks at the location of the installer at the place the function was installed from. So since I installed from my hard drive, the installer builder found the location and didn't give me a pop up. Only do this if you have plenty of hard drive space (for obvious reasons). Another option might be to copy the DVDs onto a server and install from there. Haven't really tried that yet.
  19. Multiple property nodes will execute in parallel. What the authors are talking about is when a single property node is used to set/get multiple properties (the property node can be expanded just like the build array or bundle/unbundle cluster). Hopefully this picture will help clear things up.
  20. I have had good luck with SuperLogics. Finding motherboards with six PCI slots might be a challenge for any vendor though. Also make sure you get a computer that is at least 4U or else many of your PCI cards might not fit inside the case.
  21. Look in Numeric>>Data Manipulation to find Join Numbers and Split Number. Join Numbers will take two U8s and turn them into a U16. Split Number will do the opposite. If you are dealing with arrays of your 16bit data, you may want to also look at the Decimate 1D Array and Interleave 1D Arrays.
  22. I would have thought that you wanted Termination Character Enable to be set to FALSE. But I don't have the stuff in front of me. As long as the thing works. I honestly have not used the VISA Clear function. According to the help it just clears out the transfer buffers. It might be a good practice to use it after opening your VISA session, but definitely not necessary.
  23. There is equipment out there that uses termination characters. I think by default VISA has termination characters on. The o-scope may be using what VISA thinks is a termination character as a separator for some reason. You can use a property node to change the VISA settings. You should check with Hameg, but it is likely you either need to disable termination characters or change the termination character.
  24. From the LabVIEW Help, it appears that the two modes only matter when comparing arrays or clusters. Do a search for "Using Comparison functions" or "Setting Comparison Functions to Compare Elements or Aggregates" for the official wording.
  25. Here's a good example: The results are the same.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.