LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

HELP! vi reference type does not match VI connector pane. THANKS

Solved!
Go to solution
Highlighted

 (1) I got 3rd party vi.

(2) When I run it individual, it is fine.

(3) after build into test sequence.

it stop due to "not match vi connector"

Thanks for help

see attached file.

 

 

0 Kudos
Message 1 of 17
(999 Views)

The connector pane (inputs and outputs of the VI) of FT_Set_Bit_F3.vi are not as expected.

 

Without the VI that actually loads the test, it's impossible for us to tell what is wrong with the connector pane. You could also post another test VI that is working. Then we could point out the difference(s) in the connector panes.

 

If I had to guess, the error out is there but is not wired to the connector pane... But that is just a wild guess.

Message 2 of 17
(953 Views)

Hi:

 (1) I add error out for FT_Set_Bit_F3.vi, it still failure the same.

(2) I attached TC003431.vi, which is load FT_Set_Bit_F3.vi

let me know if these 2 not match.

(3) I also attached other working vi.

 

Thanks for help. 

0 Kudos
Message 3 of 17
(939 Views)

Hi:

 (1) I add error out for FT_Set_Bit_F3.vi, it still failure the same.

(2) I attached TC003431.vi, which is load FT_Set_Bit_F3.vi

let me know if these 2 not match.

(3) I also attached other working vi.

 

Thanks for help. 

0 Kudos
Message 4 of 17
(938 Views)

wiebe@CARYA wrote:

The connector pane (inputs and outputs of the VI) of FT_Set_Bit_F3.vi are not as expected.

 

Without the VI that actually loads the test, it's impossible for us to tell what is wrong with the connector pane. You could also post another test VI that is working. Then we could point out the difference(s) in the connector panes.

 

If I had to guess, the error out is there but is not wired to the connector pane... But that is just a wild guess.



Hi:

 (1) I add error out for FT_Set_Bit_F3.vi, it still failure the same.

(2) I attached TC003431.vi, which is load FT_Set_Bit_F3.vi

let me know if these 2 not match.

(3) I also attached other working vi.

 

Thanks for help. 

0 Kudos
Message 5 of 17
(933 Views)

Unfortunately, none of these VI's actually show how the VI is loaded (assuming all 4 uploads are the same).

 

It seems the error is generated somewhere inside a custom test sequencer. All tests have different connector panes. It's impossible to tell why this one VI fails based on the information you are giving.

 

I assume you can't ask the person who made the framework?

Message 6 of 17
(929 Views)

Look at the error message.  It tells you that the error is occurring in "SeqUUTCmd.vi".  No one can help you resolve the error because you haven't provided the VI that is throwing the error.

"If you weren't supposed to push it, it wouldn't be a button."
Message 7 of 17
(923 Views)

Thanks

 

I add SeqUUTCmd and project zip file. 

 

 let me know. 

Thanks again. 

0 Kudos
Message 8 of 17
(910 Views)
Solution
Accepted by topic author zy6

OK That helps us help you

To "Be a Test" within that framework the connector pane must match THIS pattern

Capture.PNG

All the inputs and outputs must be of the same type as that pattern

they must have the same options set (Required / Recommended / Optional)

And the connector pane cannot be flipped either horizontally or vertically nor rotated at all.

Always maintain an accurate count of deployed mousetraps.
Message 9 of 17
(905 Views)

Thanks Jeff:

 I can not get it right.

can you please edit attached file and email or post it?

Thank you again. 


@JÞB wrote:

OK That helps us help you

To "Be a Test" within that framework the connector pane must match THIS pattern

Capture.PNG

All the inputs and outputs must be of the same type as that pattern

they must have the same options set (Required / Recommended / Optional)

And the connector pane cannot be flipped either horizontally or vertically nor rotated at all.


 

0 Kudos
Message 10 of 17
(886 Views)