Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by JustinThomas

  1. If NI can get the CLA summit scheduled close to NI Week, maybe the week before or after it would be just great. For guys like me its not possible to convince my boss a trip to the US two times a year.
  2. I have seen a few posts suggesting bigger and bigger monitors. I do admit that having great screen size does reduce scrolling, but i feel 1280X1024 is ideal. I do all my coding on a laptop with this resolution. I feel anything which does not fit on this screen size should be inside a subVI. Another important point to remember is where your applications will be deployed. I have burnt my hands a few times by developing GUI's on large screen but then deploying them on smaller resolution screens. Lets admit LabVIEW does not scale GUI objects very gracefully and its usually a pain when screen resolution changes. Although I have to admit the introduction Splitters and Panes have helped to address issues with GUI scaling. As with processing power and RAM capacity, i believe its best to develop and test on a system similar to what you would deploy your applications. Again developing on a Rockstar (Highend) PC can give you fall impressions on performance of your application. Justin Thomas
  3. you should have a look at subpanels to embed a child vi into a parent vi. Also tabs are a good option for your problem. Just place the booleans as required on different tab pages and set the tab page based on your control boolean.
  4. It is not possible to create pages on the fly during runtime for a Tab Control. I generally do this kind of thing using a 'subpanel'. If you could post what you are trying to achieve people on the forum can give alternate suggestions
  5. Thanks to the LAVA community for all your help. Thanks to the moderators and Admins for keeping this site alive and rocking all the time. Hope to keep reading great articles and discussions in the coming years too. A very Happy New Year to all fellow wireworkers
  6. Looks like LabVIEW Web Server is enabled on your machine. Open LabVIEW go to Tools>>Options menu. You will find WebServer:Configuration in the Listbox on the left. Click this option to find a Checkbox for Enable Web Server. Remove the check mark and save. Now the right click option should be gone. The WebServer Configuration panel may be in a slightly different place based on the version of LabVIEW you have. The above mentioned location is with respect to LabVIEW 8.6.1
  7. Make the Splash VI your top level VI and call the Main VI dynamically then use the Notifier trick mentioned above to close the Splash VI. You can also send custom messages to the Splash VI through the Main VI, similar to the Splash screen when LabVIEW loads thus informing the user as to what the application is doing. This gives a feeling to the user that the application is doing something in the background rather than just a splash screen.
  8. There are lot of PCI extender options available. Checkout the attached link for details on PCI/PCIe extender options from a popular brand http://www.adlinktech.com/solution/tech_forum.php?file=measure/20071219.htm&gclid=CLTRsaXl8pwCFUUwpAodBF-ciw
  9. In a nutshell WinXP Embedded is a subset of the WinXP which you can create using the Embedded Tools available on the microsoft site. I have tried it and though it gets a little getting used to create the image it does give you a customized image of Windows XP. I agree Support is a problem if you have various version of the XP image installed. We use it on Fanless PC's with our applications. The level of customization can be such that it is difficult to guess the OS used on the platform is Windows XP and gives a product like feel to the system. LabVIEW does run on WinXPe SP2 and even DAQmx (I've tried it for M Series and DSA boards). Here's a link to a tutorial on the NI site on how to install LabVIEW on WinXPe. http://zone.ni.com/devzone/cda/tut/p/id/4011
  10. this may remain for quite some time considering NI is planning to release a new version of LabVIEW every year
  11. I absolutely love LV 7.1 for this very reason. It was so good. But now I can't live without the LV Project, Quick Drop and all the new goodies so have to work with LV 8.6 Speed wise LV 8.6 is pretty good compared to LV 8.5 and LV 8.2. Haven't started working with LV 2009 though.
  12. try wiring a numeric constant to the case struture selector (the question mark on the case structure frame). Now you should not see the quotes in the case names
  13. As far as I can remember in DAQmx the rate specified helps the DAQmx driver to set the buffer size for your task. As such it should not matter if the rate specified is not exactly the rate of the external clock. Just my two cents
  14. LabVIEW 8.6.1 runs just fine on Windows 7 RC. I have been using it for the last couple of months.
  15. You could use the 'Blinking' property too.
  16. Add a Value change event for your string control. In this event compare the control value with the stored constant using the equal to operator. You would also be required to right click on the string control and select 'Update while typing'. This ensures that the value change event would fire every time you make a change in the string control
  17. PXI based hardware is available from a large number of vendors. The official PXI system alliance website www.pxisa.org
  18. i like the new behaviour too. As i keep reading posts in order its nice that whenever i click the 'view new content' link it directly shows the list from the first unread. The earlier behaviour was a bit annoying as i would have to manually scroll to the first unread post each time i come to the new posts page.
  19. Filtering works for me. Its the easiest solution
  20. Can you post the vi you already have? We can give you some suggestions on it
  21. HI LabViewnoob, Can you be a little more specific on what you want to achieve? Do you want the indicator B to have the same value as indicator A?
  22. I think you need to be a premium member to be able to edit your posts. Get in touch with the moderator for this.
  23. QUOTE (Scooter_X @ Apr 14 2009, 07:43 AM) Hi Scooter_X I do not want to give you the answer as its your school project but I can give you some direction When you execute or run your program the string elements are built and the array of string is formed. Now this does not remain in memory as you do not store it anywhere. So the next time your run your program it does not retain any values from the previous run. Look for and read about uninitialized shift registers and functional globals in the forums and LabVIEW help this should give you some direction
  24. Hi Scooter X, You can use a cluster with one string and one numeric for each racer build an array of this for your data. Clusters allow you to keep different data type elements together. As far as the sorting goes I am not aware of any ready made functions for sorting a cluster. You may have to write custom code for sorting your cluster, but should not be very challenging. Justin Thomas
  25. QUOTE (Thang Nguyen @ Apr 3 2009, 12:11 AM) I was just about to recommend shared variables. Thats an easy way out. Justin
  • Create New...

Important Information

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