Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by bmoyer

  1. QUOTE (sbev001 @ Jun 1 2009, 10:26 AM) My guess would be a for loop, unless you want to stop at a particular value or something special like that. You need to know the format of the 2d array as well. If you put a 2d array into a for loop it will automatically index on each row. If you have a column for time and a column for value it you may not even need a for loop at all. Look at the Index array function to get all the data from a particular column (assuming you have the data organized like this). There's a palette for doing integration in the Mathematics palette you can look at (but you may not have access to this palette depending on the type of LabVIEW package you have. Spend some time and poke around. Ctrl-H gives a pop-up help and usually more help if you click on the link in the pop-up help. Bruce
  2. QUOTE (ShaunR @ May 29 2009, 02:03 PM) That's because LabVIEW developers are crooks! Unlike other languages where they are all law abiding citizens. NI, what have you done to us?!
  3. QUOTE (PJM_labview @ May 21 2009, 01:18 PM) The minimum size of the project window is actually larger than the default size! When you create a new project window, it actually snaps to a larger size when you resize the window and then doesn't let you put it back to the original size! Seems to be a "feature" in LV8.6 only (LV8.5.1 is still good). Bruce
  4. QUOTE (normandinf @ May 21 2009, 04:54 PM) That's what I suspected. It seems like they get locked when going from 7.1 to 8.x. Thank goodness they're still resizable as controls! Bruce
  5. Not sure about all the class hierarchy stuff, but in 7.1 it could be found in the palette, Numeric-->Additional Numeric Contants-->Color Box Constant. Now it's located in the palette, Graphics & Sound-->Picture Functions-->Color Box Constant.
  6. I know this may seem a little bit whiny, but I just noticed that as of LV8.0 the color box constants on the diagram are not resizable (as far as I know). A program that was developed in LV7.1 had a 2d-array of color boxes on the diagram to represent to the programmer the ratio of the dimensions of the actual object. Now I'm stuck with square color box constants (from the palette). :thumbdown: I'm sure there was a good reason for this. Maybe it was an attempt to make the color box constant more constant. Bruce
  7. I was able to get my code to compile to an exe that is executable by uninstalling IMAQ 4.1 (Vision Acquisition Software 8.6) and installing IMAQ 3.8 (VAS 8.5). I avoid IMAQ 4.0 because the structure of the .iid (for instance img0.iid) files is messed up (see NI forum iid file structure in IMAQ 4.0 changed). This bug is fixed in IMAQ 4.1 but apparently there are other new bugs that were introduced. Days lost, totally frustrating. Not a good LabVIEW/NI experience. And I'm stuck using old software versions to get things to work. Bruce P.S. I've been cross posting to NI as well (Why is Building an exe in LabVIEW 8.6.1 so slow?) about similar issues regarding my upgrading experience. Bruce
  8. I am in the process of upgrading a program from LabVIEW 7.1.1 to LabVIEW 8.5.1 (I've also tried LV8.6.1f1) and am having difficulties getting the built exe to function. When running the exe, Windows gives a crash error dialog "Blah Blah Blah.exe has encountered a problem and needs to close. We are sorry for the inconvenience.". When I click the click here link it refers to the "nivision.dll". AppName: Blah Blah Blah.exe AppVer: ModName: nivision.dll ModVer: Offset: 00014715 I'm not sure why this error is occurring since I was able to build (and run) the exe in LV7.1.1. I also noticed that when building the exe it gets to the end and then takes a long time to complete (almost like a timeout is occurring). Is there a way to search for this dll to temporarily remove it to see if this fixes the problem? (I know that it is from the VISION toolkit). Thanks, Bruce
  9. QUOTE (paramesium @ Apr 14 2009, 09:45 AM) This is probably caused by the Automatic Error Handling which only takes effect when running in the development environment (when running the source code). Either wire up the error cluster to properly handle this error or turn off automatic error handling (from the "Tools" menu, select "Options..." the click "Block Diagram" and then uncheck the "Enable automatic error handling dialogs" checkbox).
  10. QUOTE (nature @ Mar 16 2009, 07:18 AM) Srry, i dn't spk/wrt th sm lngge s u (Sorry, I don't speak/write the same language as you). This is an English forum, so please write in English. Bruce
  11. It took 0.046 seconds to read for me! Seems pretty fast actually. Bruce
  12. I haven't used it, but the Image Toolbox http://www.geocities.com/gzou999/imgtool.htm has a PCX read file VI. Wikipedia also gives a very good description of the file format: http://en.wikipedia.org/wiki/PCX Bruce
  13. After LabVIEW loads select the Help-->Find Examples... menu. See screenshot for the details in the NI Example Finder.
  14. QUOTE (rolfk @ Feb 20 2009, 01:10 AM) I would imagine you can probably get the USB-DAQ devices to work since most virtual environments support USB functionality. Even if the DAQ devices are not USB you can probably still get the simulated devices to work. I agree that the error dialog should be improved. When I had an IMAQ error with my app (because IMAQ wasn't installed) at least it showed a dialog with 100 or so VIs that it couldn't find that were needed for the exe to work. Bruce
  15. QUOTE (george seifert @ Feb 19 2009, 01:26 PM) That was my guess too when you said that you were using DAQmx, that the driver wasn't installed properly. Well its good that the problem has been resolved (although not fully understood). Bruce
  16. QUOTE (george seifert @ Feb 19 2009, 11:07 AM) Sorry, wasn't trying to insult your intelligence. Wasn't sure if you or your user was installing it. Sometimes users think they can install an application by just copying the exe. I don't use VirtualPC much anymore (I've switched to the free Sun VirtualBox because it wasn't free for the Mac and VirtualBox is also available for Ubuntu, RedHat, etc.) because I have both Mac and PCs operating but I have tested Installers on VirtualBox to see if they're any problems when installing to a "clean" PC on Windows. My apps didn't have DAQmx but they did have hardware drivers (such as Vision Acquisition Software (VAS/IMAQ)) and they worked fine, as long I had IMAQ installed on the VirtualBox (of course I got an error when trying to use hardware that didn't virtually exist). If I didn't have VAS installed my executable broke (like you described). Not sure if this helps at all, but these problems are usually easy to fix but difficult to find. Bruce
  17. QUOTE (george seifert @ Feb 19 2009, 08:34 AM) You used an installer to install it on the Virtual PC? Does it post a dialog saying anything is missing? Do you have any specialized calls (such as .NET) that are not installed on the Virtual PC? Bruce
  18. I'd like to create an application with a GUI that is similar to a Airport Flight Info display and the application needs to periodically check for changes to an excel file (for now, we'll talk about adding database support later) and then update the display. The information would smoothly scroll vertically through all of the rows and then repeat continuously. At first I was thinking about using Powerpoint to do this (but I don't know if this is easily possible in PP). I think this could be done in LabVIEW quite nicely. What do you think is the best way to go about this? Using LabVIEW, my idea is to use multiple panes and have a header pane and a table pane and use property nodes to scroll the table pane continuously. Any thoughts? Is there a better way to go about this? Thanks, Bruce
  19. QUOTE (hooovahh @ Feb 9 2009, 09:30 AM) The ~$1500 price tag should slow that down a little. Is it included with the Professional version (my guess would be probably not)? Bruce
  20. QUOTE (Antoine Châlons @ Feb 6 2009, 07:46 AM) I just realized that my application has the same "bug". It's pretty obvious that it didn't work - because I automatically popup a dialog when the ROI change event occurs - but to a new user this could be confusing. Bruce
  21. QUOTE (Vende @ Feb 5 2009, 09:50 AM) If you are using NI-VISION then you can use the IMAQ Cast Image.vi. You probably don't want to modify the existing Image Ref, in that case you need to wire in a new Image Ref to the Image Dst input of this VI. Bruce
  22. QUOTE (Vende @ Feb 5 2009, 07:58 AM) Or you need to down-convert your Image Refs to the proper format before storing to AVI (it can only handle U8 grayscale or 32-bit RGB images). Bruce
  23. You may want to do a test to see if it is acquiring the same image more than 1 time. I thought this is the way that it worked - if a new image is not available since the last time, to just return the same image. But I could be wrong or this functionality could have changed at some point. It's probably worth comparing the Acquired Buffer Number output of the IMAQ Grab Acquire.vi to the previous iteration (using a shift register in a while loop) to make sure this isn't the case (at least in your test code). Bruce
  24. QUOTE (Antoine Châlons @ Jan 27 2009, 11:53 AM) I've investigated this further and I think the label gets misaligned when changing the justification of the axis label text. I was able to perform these steps to recreate the issue: 1. Select the y-axis label text. 2. Click the fonts toolbar button, select "Justify"-->"Right". 3. Type additional characters to make the label a longer length. 4. Change it back to left justify and then delete characters some characters and it becomes misaligned. I guess you could just reverse the process to get back but this is difficult if you don't know the exact steps taken. Bruce
  25. QUOTE (Antoine Châlons @ Jan 27 2009, 12:31 PM) Ditto! I see the same issue in 8.5.1 (it only moves 1 pixel up or down), but it still solved the problem I was having. The first time I clicked the arrow it snapped the label back to the center which was exactly was I was trying to do! Thanks, Bruce
  • Create New...

Important Information

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