From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
06-20-2006 05:49 PM
06-20-2006 09:38 PM
Hi Kathy,
If you could attach a sample VI that demonstrates the problem (along with the VI you are trying to open a reference to), that would help. The only times I've seen this problem are when I've already got the VI that makes the dynamic call, and I later make a change to the dynamically-called VI and forget to update the type specifier...but it doesn't sound like that's the problem you're having.
-D
06-21-2006 08:25 AM
Darren wrote "and forget to update the type specifier..."
which reminds me to ask...
Is there anyway to make that update operation automatic?
Ben
06-21-2006 08:31 AM
06-21-2006 10:45 AM
Hi Kathy,
I am still investigating this problem, but right now I do have a workaround for you. If you open your template VI and drag its icon into the type specifier constant, and also drag it into the refnum indicator on the panel of your calling VI, the problem no longer occurs. For some reason the "Browse" operation is behaving differently than dragging the VI icon. I will continue investigating this and let you know what I find out.
Ben: There is no way to automatically update the type specifiers. I've seen people typedef their specifiers before, so they only have to change them in one place when the subVI connector pane changes. We already have this suggestion on file to consider for a future LabVIEW version.
-D
06-21-2006 01:17 PM
It looks like mass compiling the VIs also fixes the problem. I'm guessing that the type specifier is having trouble with one or more of the CAN typedefs in that VI, and the problem is corrected when the template VI (and its subVIs) are mass compiled.
-D
04-27-2016 07:27 AM
Hi everyone,
I am facing the similar problem 'VI Reference type does not match VI connector pane'. Please find the attached vi.
I have selected 'mlt_gaussian_kernel_vi' as the VI server class. And vi path is given also as 'mlt_gaussian_kernel_vi' . Then it is working fine. But if i select kernel type as polynomial or linear, then this error comes.
What should i give to VI specifier refnum input of OPEN VI REFERENCE so that it can work for all kernel types selected. Where is the issue....please suggest.
Best regards!!!