Executable and Register event callbacks

Hi,
I have been running into an issue regarding the building of an executable that has register event callbacks (specifically Test Stand Callbacks). The VI that is responsible for setting up the event registration is an asynchronous VI. During development everything works but during deployment of an executable the Callback is either not running or capturing the event from the Test Stand engine (I am looking for the end of execution event). The setup is not reporting an error, and the pathing to the callback VIs is correct. Any Ideas on this?
Does the Teststand engine not post a endexecution callback when running from a executable labview environment?
Thanks,
Andrew

akonecki wrote:
Hi,
I have been running into an issue regarding the building of an executable that has register event callbacks (specifically Test Stand Callbacks). The VI that is responsible for setting up the event registration is an asynchronous VI. During development everything works but during deployment of an executable the Callback is either not running or capturing the event from the Test Stand engine (I am looking for the end of execution event). The setup is not reporting an error, and the pathing to the callback VIs is correct. Any Ideas on this?
Does the Teststand engine not post a endexecution callback when running from a executable labview environment?
Thanks,
Andrew
The TestStand engine is singular regardless of what is hosting the components so it will post the appropriate callbacks. Try some tracing and see what flags up in your callback VI.

Similar Messages

Problem with register event callback in use of instrument control

now, i use the register event callback to register a value change of a boolean control on the front panel, and wire the cluster's ref of the instrument control parameters to the user parameter input, then create the callback vi. In the callback vi, i select the pump-control subvi, and pass the user parameter to the subvi. The problem is that, when i press the boolean control, the instrument (here is pump) can act, but immediately, the code crashes.
I use labview 8.6
Attachments:
callback vi.png ‏8 KB
register event callback.png ‏8 KB

You would wire the event registration wire that comes out of the Register for Events node into an event structure. You will need to right click on the event structure and check off "Show Dynamic Event Terminals" and it into that. Then you can create a new Event Case that uses the dynamic event. You can place your subVI in that event in whatever way you want. (Just drop the subVI in or do a Call by Reference there, or whatever.) Look in the Example Finder for "Dynamically Register for Events.vi".

Recursive ActiveX register event callback VI

Hi!
I am trying to control a motor in LV2013 using the ActiveX concept. When I use a "register event callback VI" function, can I call the same VI that calls a VI (with the "stop rule" controlled be the user data terminal, of course, inside)? By default, callback Vis that one can create for this are all reentrant (preallocated clone) and synchronious (according to help). However, both when I use the "server VI reference" ("This VI") and when I create a reference and browse for the same file - "register event callback" shows me a broken wire.

_Basil_ wrote:
As far as I understood, putting a movement method in the loop will not give any result, so I tought in the direction of the recursive callback. However, I found this post. Would you in general agree that the callback VI cannot be recursive? I attach my code in LV13 (if you need me to convert, I will)
Sorry, I'm still on LabVIEW 2012 here, so can't look at your VIs. I don't understand your comments in these sentences though. What do you mean by putting a movement method in a loop will not give any result? And why would you ever want a recursive callback? The callback is called each time the event occurs. There's no sense in making it recursive, nor would you want to re-register for a callback on an event inside a callback VI. Normally a callback should contain very little logic; it should primarily pass some piece of information (through a queue, user event, etc) back to the main thread and let the main logic handle it.

Register Event Callback issue

I have registered an event called MoveComplete, where the VI lets the user know that the motor's move has been completed, obviously. My issue is that the event is inside a for loop. The motor moves incrementally, and I need the event called after each move so that something can be done before it moves again. I am having timing issues because the MoveRelative method returns after the motor starts moving, instead of after it finishes moving. I tried changing bWait to false but that simply messes up the motor's movement. I tried unregistering for the event, so that in each loop it re-registers and unregisters, but that doesn't work. Is there a way I can call the event multiple times in a for loop?

It's hard to understand what you're trying to do from your written description. Can you attach your code? What motor driver are you using? What library generates the events?

Event Callback Problems during compilation

Hi
I try to register a callback vi with the "Register Event Callback"-node. I
pass a reference of an array as user parameter into to the "Register Event
Callback"-node. Everything works well in the development environment. But
when I try to build an executable I get the Error "1003 . The vi is not
executable".
What is wrong?
Mareike

Hello Mareike,
you can surch in the http://www.ni.com/support/ for "error" and "1003". There you will find a lot of links where this error is discussed. With a little luck, there will be an answer.
Regards ThomasD

Probing an Event Callback vi

Hi All.
Please could someone tell me why when I probe or enable tracing on the block diagram of an event callback vi nothing is indicated even after I know the vi was called because I can the the results of it being called. I am running Labview 2009.
Thanks in advance
Ian
Solved!
Go to Solution.

Hi and thanks for answering. Unfortunately I cannot post any code for security reasons. However the code I am degugging (not my code) is not using the usual event structure but uses a 'Register Event Callback' function to call a particular vi when a certain event (top level front panel control) is initiated. When I initiate the event I get the correct response on the top level vi (a user prompt pops up) so I know the vi is being called correctly. However if I pre-open the sub vi and set tracing or probes then initiate the event again I do not see anything register on tracing or in the probes (shown as not executed) even though the vi obviously ran again. The reason I want to probe the called sub vi is that a similar event is not working correctly and I was trying to see what happens with a functioning bit of code to draw comparisons. Hope I'm explaining this OK.
Thanks again
IanR

Event Callback from a Reentrant VI Recursion Error

Greetings,
I am using Register Event Callback with an ActiveX object to respond to user mouse events. The problem is that when I run the VI (the main, calling vi) as reentrant, Labview gives an error that the "Callback.vi" is attempting to recursively call "Main.vi".
Is there a way around this problem? I intend to run two copies of "Main.vi", so reentrant execution seems necessary.
- Colin Holbrook

Hi Colin,
Are you placing the Register Event Callback inside of the Main VI and then wiring the same Main VI to the VI Reference terminal? If so, then that explains why you are getting an error. You cannot use the Register Event Callback to call a VI within itself. If this is not the case, then please post a simple VI that demonstrates the problem.

Configure Event Callbacks in test stand using labview

Hi,
I was going through Full OI - Configure Event Callbacks.vi in the test stand example. Can you please explain me how the vi works and what is techniwue behind it?
When i open the individual VI's in the reference, I could see more that 1 control in the front panel. But Only the user parameter is wired in the vi? Why is it so?
Regards
Gopal

Hi Gopal,
When the TestStand Engine fires events, this VI specifies how your Operator Interface will respond. For example, let's examine the first event callback registered in Full OI - Configure Event Callbacks.vi , Exit Application. When the TestStand Engine receives the message to shutdown, and then finishes its neccessary shutdown procedures, it will send a message to the Operator Interface. For the Operator Interface to receive this message, it must "listen" for it. In LabVIEW, this is done by Registering an Event Callback. See the links below for details on how to implement this.
The answer to your specific question is in step 7 of the first link below. When TestStand sends the message to LabVIEW, there is information that is always passed. The other input controls contain this information. To create a VI that always includes these controls, right-click on the VI Ref input to the Reg Event Callback Property Node, and then select Create Callback VI.
Here are two references that talk about handling ActiveX callbacks in LabVIEW in general:
Registering and Handling .NET and ActiveX Events
Register Event Callback (Not in Base Package)
Cheers,
David Goldberg
National Instruments
Software R&D

Event Callback VI with LVOOP / overhead, caveats, future

OK another exploratory post from me. To anyone who has put up with this kind of thing from yours truly many times in the past, apologies. Completely impervious to any objections, here goes:
I have discovered a new toy : Registering event callback VIs. OK, I have used them before but a previous post by James McNally about his MVC framework revealed to me a usage which I had not previously thought of. Thanks for that James.
I like LVOOP. One pattern which is quite easy to understand is the command pattern in conjunction with state machines where we essentially replace the individual states of a state machine with external VIs. This makes it far easier to customise behaviour and allows for re-use of the core state machine for differing functionalities. Cool.
We can leverage this with LVOOP by passing different "commands" to the state machine depending on the real object being utilised and thus we have a nice extensible architecture. Again, cool. If we need to change one common action, we simply update that VI and instantaneously all ancestors share the new code in that command object. Double cool.
Problem is that I love User Events. The idea of having an extensible object model gets awkward to handle when you start using Events to handle communications in and out of the object. Create a Parent, Implement the 15 Events required. Create a child, Implement the 15 Parent events and the 12 new events. Create a Grandchild, Implement the 15 Grandparent, the 12 Parent and then the 25 new Events. Armageddon occurs when you want to change the common functionality for the sixth Event of the Parent. Now you need to go to each and every ancestor which uses them and update them. Wait a second, isn't LVOOP supposed to save me from this kind of crud? Frustration ensures. Can you ever be sure you got all instances? What about those obejcts not listed in the project, maybe you forgot one of them...... Nasty testing and debugging ensues.
I think I may have (partially) found the answer. What we need to do is basically do the same thing we have done with the command pattern and extract the individual frames of the event structure and place them into external VIs so that we can 1) re-use the VIs in each level of hierarchy and 2) maintain all the other niceties of Events.
Turns out that using Callback VIs for each level of the object hierarchy can help to solve this problem. You need to have a method with a different name for each level of the hierarchy which exposes the events int his way because each method will most likely have different input values.
Has anyone else done things like this? Are there limitations as to what can and can't be done with this arrangement? Any nasty bugbears waiting for me around the corner? How to deal with events which should give some kind of return value? Do I encorporate the return value into an implementation-agnostic return channel (again Events of course) with the object in question providing one return user event for each callback function which requires a return value?
Say hello to my little friend.
RFC 2323 FHE-Compliant

Grr, I was trying to attach a file (whose contents apparently didn't match the file name?!!) when I ran out of time to edit and now I lost my text.
Here's an example.
Base class swaps out a control Caption for Label upon "Mouse Enter"
Child class swaps out a control Label for Caption on "Mouse Leave"
Grandchild increments a counter (stored in Description) for every "Mouse Enter"
Trivial but get's at what I mean.
I know I can do this in other ways but
1) I don't need a parallel process
2) I'm just having fun
Darn, I can't attach a zip. Rename this file to .zip and unpack. Sorry guys.
Say hello to my little friend.
RFC 2323 FHE-Compliant
Attachments:
LVOOP with Event callbacks.txt ‏78 KB

Event callback timing

When I am using dynamic events and transmit a counter as event data each time I fire the event, I can have multiple consumers that receive the identical count. Thus, only a single event is generated each time and signaled to all consumers. Ok, so far.
Now, I am using the Register Event Callback function in LV8.2. to fire events from an ActiveX component (pressing buttons on a joystick device) and use a dynamic event to signal this to multiple consumers. Again, I add a counter to the dynamic event data. What happens now is that the consumers receive different counts, even if I only click the joystick button once. As if there are multiple events generated. For 2 consumers, 2 events are being generated, for 3 consumer 3 events and so on. But how would the callback VI know that there are multiple consumers?
I tried reentrant and non-reentrant callback VIs and see no difference ("reentrant" is specified in Help, but I do not fully understand why that should be needed).
Could anyone explain this behaviour to me? Thank you!
Dirk

Hi Daniel,
thank you for your reply. Although I managed to include the ActiveX components supplied with my special input device, I am not in general familiar with ActiveX. Therefore, I have no idea how to find something as general as "keyboard hit". However, triggered by your reply I now tried it with a modified version of LV's example file using Excel worksheets. There, I do not see the described behaviour.
Well, I will check again on that special device driver now. At the moment, it is not working at all, which looks fishy...
Dirk

Is there any event callback for "pre/post-register/unregister" object?

Dear all,
We noticed that there are rich set of event callback provided by TopLink, including "pre/post-Refresh/Build/Clone/Merge". However, we cannot found any callback method for "pre/post-register/unregister" events. They will be very useful, if we to manage the internal status of register/unregister to indicate whether it is still under the control of TopLink.
Thanks and regards,
William

William,
Those specific events do not exist. The postClone event is called after an object is registered. This is frequently used to copy non-persistent values from the cached original into the working copy.
There is also the ability to customize the clone/copy policy used by TopLink in creating the working copies in the UnitOfWork.
http://download-west.oracle.com/otn_hosted_doc/toplink/1013/DP4/_html/descfg028.htm#sthref3950
Doug

Why can´t I see contacts and calendar events from my iPhone in my mac pro if I already registered it in the cloud?

Why can´t I see contacts and calendar events already registered in my iPhone, in my Mac Pro ? I already actualize LION OSX and selected these items in the adjustments menu of the icloud. I could do it just once, after I installed Lion OSX, but up to the moment it does not updates.

Assuming you activated iCloud, try going to Settings>iCloud and make sure Calendars and Contacts are set to ON.

How to place event callback components and "main-VI" components in the same Front Panel?

What I'm trying to accomplish:
Place a .NET component, which generates events, and other standard LabVIEW components in the same Front Panel. The standard LabVIEW components should be updated when events are being generated in the .NET component.
How I tried to solve it:
Problem:
The event callback code must reside in a separate event callback VI. In order to "pass the event up" to the main VI I tried to use a global variable. The interrupt does occur:
but I was hoping that the string indicator would be updated when the event occurred, but it wasn't.
Questions:
What's the best way to solve what I try to accomplish? If I want to solve the problem on the picture above, how would I do it (it may not be the best solution, but I'm still curious what's wrong)? Please feel free to be over-explicit when replying as I am novice LabVIEW programmer. Thanks in advance for any help.

There are two bundle functions for creating clusters. The function simply called Bundle operates almost exactly like the Build Array function I showed. The type of the output cluster depends on whatever you wire in as inputs. You don't have to supply a specific type parameter.
The function called Bundle by Name takes in a specific type of cluster in the top input and allows you to fill in the values of that specific type of cluster. To create the specific type of cluster you want, you need to create a cluster of string references. Here's how to do that:
Go to the Front panel and drop down an empty cluster shell.
Go to the Refnum palette and drop down a Generic Control Refnum. Now here's a cool trick to turn that generic refnum into a string-specific refnum (a so-called strictly-typed refnum). Grab a string from the controls palette and drag it into the Generic Control Refnum. Once you drop it, you'll see the refnum change its icon to display a string picture.
Make copies of this string refnum (as many as you need) and add it to the cluster shell.
Now, if you're making specific types of clusters to work with, now is the absolute best time to learn about typedefs if you haven't already. It will save you hours and hours (if not days) of development time in the future. Trust me!
Jarrod S.
National Instruments

Button executing CloseWindow Java Script and raising event on server

Hi All.
Somebody can help me with this:
<b>What i'm needing:</b> an 'END' button on a BSP, when the user click on this button just show an aswer box asking if the user wants to close the windows, in case to click yes close the current window and execute a business logic in the controller.
<b>What i have:</b> a button with the event onClientClick invoking a Java Script function which is showing the answer box and the event onClick which raise the event on the server side. The thing is if the user click on yes then i'm closing the current window and the server event never is triggered. This is not working !!!
Any ideas ? some sample code ?
Thanks in advance.
Armando.

Hi Armando,
The 'Yes' on the <i>Confirm dialog box</i> (Client Side Scripting) has to tell the application (Server side scripting) to call your METHOD XXX. This is done by passing querystring <i>exit=X</i> to the URL.
1. Comment onClick event of the button.
2. Modify the code the JS function of your End button as follows
   func_end()
//if no
// your original code
// if yes
document.location.href = document.location.href + '?exit=X';
3. Add following code to DO_REQUEST
IF REQUEST->GET_FORM_FIELD( NAME = 'exit' ) ne space.
*your method will be called only when there is an exit=x in the url
       call method XXX.
*set a page attrib as follows
       l_exit = 'X'.
ENDIF.
4. Add following code to your layout
<%if l_exit = 'X'.%>
<script>
window.close();
</script>
<%endif.%>
Regards,
Alwyn

Active x and event callback in Labview

I have an active x written by Aanderaa Instruments (makes
weather and hydrology sensors), it contain various methods and events to get
the next line of records from a sensory scanning unit. The connection is
through the COM1, so far i have wired it up only using the methods to get next
record level, but then I have found that sometimes it does not get the complete
record from the COM port. So to solve that I have to use an event in the active
x to check for new record available. So what I want to do is send the event
(when complete record available) to VI that uses the get next record method to
pick up the data from the COM1 port and then send the data back to the main VI
for processing, plotting and writing.
My problem is that when I connect the output from the GetNextRecord method to a
indicator that I then wire on the connector pane to be an output from this
VI get an error that there is a wire function conflict. I have tried to
explain a bit better in the attached pdf file with diagrams.
The reason why I want to export the data back in the main VI is because it runs
continuously collecting data every 2 min and I plot them on a graph and write
them to a file so it will no work to have all that done in the event callback
VI that will only run ever 2 min, then it will reset the graph the whole time
and I want continuous data plotting for 10 days of historic data records. I
also have a few other sensors that come in through a connector board that are
written o the same file.
hope somebody can give me some hints
Attachments:
labview question.pdf ‏721 KB

Duplicate post, click here for the original: http://forums.ni.com/ni/board/message?board.id=170&message.id=135639#M135639
LabVIEW Champion . Do more with less code and in less time .

Executable and Register event callbacks

Similar Messages

Maybe you are looking for