Jump to content

code ferret

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0

About code ferret

  • Rank
    Active

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2010
  • Since
    2001
  1. One nice side effect of handling the "Instance close" event is that it provides a nice way to close certain types of aplications which are otherwise awkward. For instance, if you are working with a VI that has no title bar (for an embedded or kiosk UI application, for instance), but it also has no exit button or other UI control for exiting, how can you gracefully shut it down while working with it in development? There are any number of ways, but handling the "instance close" event provides a convenient way. Assuming you are using a project, you can close your VI by clicking on the LV proje
  2. This is working for me with LV 2010, in the VI description field only, and only after I perform a check-in, as Chris mentioned. The values between "::" and "$" were inserted by SVN. I'm using tortoise, FYI.
  3. Vattic, Off the top of my head, I would approach this problem using hardware flow control. You can watch the DTR/DCD lines, and use an event structure for control. If you do not have a 5-wire serial port, you could try watching your input buffer over time and change program state when the data isn't arriving. Just a thought.
  4. Mikael, I can't speak to your specific problem but no, you are not the only person to experience labview slowness. I am using 2009 SP1 and not only is it slow, but it is a little unstable. I frequently encounter strange problems that require not merely a labview restart, but a reboot - particularly regarding RT tools.
  5. True, it is complex! You may be right that using queues may be desirable when running software on only one machine or VI. But, I'm not ready to lower the shared variable battle standard :-) . The advantage of shared variables is that you can use them across PCS on a network.
  6. This is correct, but i think that creating this behavior is simple. You could use events to create this situation - for instance, use an event-driven loop to wait upon a variable change event and not allow any other code execution until the event takes place (say, by using a notifier to notify local VIs!).
  7. I think that network shared variables do everything that you've requested. You can create a shared variable on machine 1, have machines 2 and 3 subscribe to it, and machines 2 and 3 will both get the same data. The queue manager that you have hypothesized about is the shared variable engine, which knows about all of the publishers and subscribers and buffers the data to make sure that all of the subscribers get the same data. You can set buffer lengths to arbitrary lengths. In a consumer VI you can watch for a change event for the shared variable in question, and your consumer VI wil
  8. Getting excited about NI week.

  9. All, I'm having an issue with the LabVIEW IDE crashing hard when I perform a certain sequence of operations using a DLL. I'mfairly certain that my DLL is faulty, but am wondering if there is some kind of debugging info I can get out of the IDE regarding the crash; when I restart the IDE after the crash, it does not know it crashed and doesn't ask me to investigate.
×
×
  • Create New...

Important Information

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