ACBR Usage question

JÞB — Thu, 22 Sep 2011 00:21:34 GMT

OK, I admit I've been fighting this all day and

So, I have a VI I want to "fire and forget" Via Asynchronous Call by Referance. This VI is owned by project "Gateway Resouces" and getting a ref to the VI works within the Project.

Today I called the VI containing the ACBR to the VI I need to fire and forget. Got error 1445 complaining about the name of the vi being no longer relevant since the owning project changed (...on Displays.project vice on Resources...)

OK, so I dropped a P-node to get the "Qualified name" I got no "on.... " since it is a project not a library.

I eventually abandoned the ACBR for two invoke nodes (to assign control values and run.vi) but ther is going to be a price to pay after I build the application.

Any wisdom?

Re: ACBR Usage question

tst — Thu, 22 Sep 2011 06:12:14 GMT

I don't use 2011, so this is just a guess.

You say that the error refers to being in the wrong project. Each project functions as a separate application instance, so if you want to connect to a different project, you need to provide the correct application reference to the OVR primitive, as if the project is on a completely separate machine. To get that, you need to use the Open App Reference primitive with the correct port, which should be configurable in the project properties.

topic ACBR Usage question in LabVIEW

ACBR Usage question

Re: ACBR Usage question