Jump to content

Wire Warrior

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Wire Warrior

  1. I have a compiled program created with LabVIEW 2009 that on the first run after the computer is re-booted will work fine but after shutting down the program it will not run properly. The program uses a compiled launcher to dynamically activate a set of VI's containing Queue Driven State Machines (QDSM). On subsequent program starts the launcher module comes up fine and its progress bar shows that it is launching each of the VI's. Once the launcher is complete it removes itself from memory leaving the dynamically launched VI's running. The subsequent launches which fail the main user interface VI pops up barely long enough for the observer to see (if at all) then shuts down. The program is then gone from memory as far as I can tell. There are no processes in memory or anything. Additionally, the when I try to run the installed version of the exe on a computer that has the 2009 development environment installed I get this behavior consistently with a successful run even once. In both cases my program does not throw any errors (which are logged) nor does the runtime engine generate any that I can see. Also, when I run my program in the development environment the program does not behave this way. It has no problems at all. I have used this style of architecture before in LV8.6 with out any problems. Can anyone suggest some possible solutions or even some debugging tips? I have never had a problem that I could not duplicate in the development environment so I am unsure how begin attacking my issue. Thanks for any help. Jason
  2. Okay, so what's RTB for us acronym poor folks? Jason
  3. Don't ruin my dream man! Writing games is what got me started programming....okay so I was like twelve and didn't know what I was doing on my Commodore64. Still, I have considered writing a game now and then in LabVIEW to prove I can. Jason
  4. Hooovaah, Are you suggesting that multiple UI's be created as unique VI's and then launched at "run time" with a dynamic launcing scheme? If not I don't think I under stand how to do this. Interesting way to solve the problem though. Thanks Jason
  5. Great, another LabVIEW thing that keeps me from doing productive work. "No really boss, this isn't a game it's a learning tool." Jason
  6. That's cool. I would love to have one of those. Jason
  7. I am hoping that one of you out there can help me find a paper that I found on NI.com the other day. It was one the topic of more efficient ways of coding string selection routines. I read through it on a saturday and now of course I would like use one of the recommended techniques but I can't find it or clearly remember the information. Is there any chance any one here knows the paper I am speaking of? If so a name or link would be great. It's beginning to bug me now. Thanks Jason
  8. Thanks for the info! Now I need to post more. And one more to up the count.....Bwah-ha-ha-ha!
  9. I'll also chime in and say Nancy's classes rock! Matter of fact the Advanced class she taught is how I found LAVA and much other LabVIEW goodness on the internet.
  10. Okay, here's my issue. We have an in house piece of test software which we are working on a new release for. Some of the new features require the use of the PortMon program (serial port monitor) for use during the verification/validation process of the software. These are not needed during the normal operation. We would like to have the NI LabVIEW application builder automatically include the installer for PortMon on the distribution CD but not run it during the install, preferrably to not even install it on the target machine (Windows XP OS FYI). We are concerned with later releases not having the required support software installed if we simply trust it to human action. Has anyone done this with the NI App Builder? Know of an article? Anything? I have tried searching the NI site and LAVA but I have not been able to find the right information. I would appreciate any help any one could give. Thanks Jason
  11. QUOTE (crelf @ Mar 3 2009, 02:14 PM) It took that long to get to the 'crelf on LAVAG said' part of the description. :laugh:
  12. So if we chant Darren 3 times will he come answer this? Let's see.....Darren, Darren, Darren...
  13. Just remember guys....all those really bad software QA folks have to come from somewhere. You know the ones...they have a computer science degree or some such but some how managed to miss the concept of how a computer works? I would think its the ones like this who get us to "help" with there problem. Do I need to mention that we are dealing with out of house QA folks this week? Jason
  14. Changing the connection type to required on the connector pane isn't enough? Jason
  15. One just hit me....and while its not LabVIEW specific, it is closely couple. Kring Kong Jason
  16. QUOTE (Sonic_Soul @ Nov 12 2008, 04:35 AM) It's hard to tell without seeing the code or having more information about how the don't work. Can you post a copy of your code with the sub VI's inserted or atleast a screenshot of the block diagram? That would assist in answering your question. Thanks Jason
  17. QUOTE (Neville D @ Nov 5 2008, 11:00 AM) Oh. I did not realize that. Too many years since I worked with the base version. Thanks for clarifying. Jason
  18. You could have your friend save the VI for version 8.2 and not have to re-write it. Otherwise just duplicating the VI's block diagram and front panel in 8.2 would work based on a cursory examination of the section of block diagram you presented. Didn't appear to be anything unusual there. Jason
  19. QUOTE (BrokenArrow @ Oct 28 2008, 07:04 PM) Could it be that you have an long timeout, like never, on a visa component that is waiting for a response from the closed port? Just a thought, Jason
  20. At last a question I can help with! With Windows XP the way that we handled this at my company was to have the installer place a shortcut to the executable in the startup directory under the programs menu. The thing to watch out for with this is to be sure that you place the shortcut appropriately based on the user-related behavior you desire. By this I mean if you have logins to a machine at the Windows level then you need to be sure and place the shortcut in the all users folder so that it initates the program in all cases. If you are just booting straight to Windows without any user variances then its less of an issue. The installer creation function of the LabVIEW really makes it easy to produce the desired result. This link has some useful information on creating installers http://zone.ni.com/devzone/cda/tut/p/id/3303. Jason
  21. But of course a good signal to noise ratio is related to how soon some brings up nipple tassels Jason
  22. QUOTE (crelf @ Jun 19 2008, 11:09 AM) Now I won't get to go to the LAVA-BQ. I'll keep an eye out for when they are available again. Jason
  23. QUOTE (crelf @ Jun 16 2008, 12:37 PM) :thumbup: EXCELLENT! This will be my first NI week and I am really looking forward to it. Jason
  • Create New...

Important Information

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