Jump to content

mzu

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

1

About mzu

  • Rank
    Very Active
  • Birthday 09/17/1979

Profile Information

  • Gender
    Male
  • Location
    USA

LabVIEW Information

  • Version
    LabVIEW 2014
  • Since
    1997
  1. AQ, Thank you for the reply, enabling the highlighting tool is not a problem, and if nothing else works I will resort to that. If we talk probe scripting then I can script some code inside (and outside) of each of B.vi which will pass the unique ID to each of the B.vis. But those solutions look like hacks and workarounds to me. What I am actually looking at is the kind of functionality that the breakpoint provides. I mean, let us modify the code for B.vi as follows: Now it will stop when B.vi is called the second time. I go to the "stack trace" menu on the top: and the LabVIEW highlights the exact node out of 3 B.vi nodes where the breakpoint occured: the second one: How is it done inside of the LabVIEW, and is there any easy scripting way to get an access to this functionality?
  2. Thanks, Todd, no solution there. Voted up Jim's suggestion, though. May be I can do without determining the state of the node, if I can somehow get a reference to the exact node, that called my subVI.
  3. I am working on a tiny debugging tool. Say, we have a 2 vis, A.vi and B.vi. A.vi calls B.vi in multiple places on the BD. B.vi is being executed now. I would like to get the reference to the node on the block diagram of A.vi of a particular B.vi being executed right now (It may be paused, or just running). Same way as we get clickable "stack trace" drop-down list on a breakpoint. How can I accomplish it? A.vi BD: 1. If B.vi is reentrant, I could have used clone #. But if B.vi is not reentrant? 2. I can easily get an array of nodes of type "subVI" on A.vi BD. But the node does not have any property to show it's state (reserved, running, idle, bad etc). 3. Each VIRef of each subVI node has different numerical value. However, I was not able to find a VI property that would give me the distinction between a running VI and a reserved one. 4. I enabled supersecretprivate key in the ini file, but still no methods/properties I can use.
  4. That is what I am talking about. The trick with property node -> Selected sort of works works but I there might be some hidden problems. At least none of the XControls that ship with LabVIEW do that.
  5. When (in edit mode) you click on the border of a regular control it becomes selected.Not so for all XControls I've seen or created so far. The only way I found to mimic the behavior is to use Control refnum from the container state cluster and set "selected" (Scripting enabled) property to true. Questions: 1. Is it safe to do so, as I recollect there some synchronization related limitations on what you can do with this refnum. 2. Do I really have to enable scripting; am I missing some much easier way to do it?
  6. do you do it through localhost? This is really strange and may point out to issues with OS installation as well as with issues inside the P2. (If it's not a mistype)
  7. Could it be something like a global variable?
  8. You did not follow the advice given here: http://labviewportal.eu/viewtopic.php?f=21&t=3523 So let me repeat it. First of all - disconnect "Service name" (as shown). It does not specify the interface to listen on. Second: check that you get the length (the first 4 bytes you are reading in correct byte order). This could be the cause of the memory error.
  9. Thank you for an answer... Will look for the next release. Back to designing workarounds ... I understand that it is impossble to make it work properly now for 2011 release, but is it posible to make it so that LabVIEW 2011 spits out a meaningful error, instead of "VI failed to comiple"? And does not crash afterwards?
  10. This is the way simulation subsystems work - they are "macroed" inside the top simulation diagram, say this one: would be executed same way as top level simulation diagram and as a subsystem. So, ading this feature to LabVIEW would not be a big problem (but totally pointless). and yes, I would agree with you that a warning may be justified when the subVI is created out of 2 totally independent things - and this might be a good topic for idea xchange.
  11. AQ, what version of beta do you refer to as to the second one. The latest beta 11.0b79 contains same bug (I go through the sequence of actions above verbatim and get the same result).
  12. This is exciting news!! Thank you for your efforts! I got so tired designing the workarounds, when single wrong step crashes LabVIEW. The resolution of this CAR It is a reason enough for me to participate in 2011 beta. I filled out the application, got no answer yet.
  13. From time to time I am not able to access LAVA, whether it from home, work or cell. The browser says: "unable to find host". It all started approximately when the server was upgraded/moved. Does anybody else experience the same?
  14. My regular development platform is 2010SP1, but this time I am forced to use 8.2.1. due to client license. jgcode, were your problems stability related, performance related or ... ? Did you refer to 8.2 or 8.2.1 when you spoke about the problems?
×
×
  • Create New...

Important Information

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