LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Load bluehill 3 API into LabVIEW

Ok, I have worked with the Null key and have gotten it so that the key is no longer null from the APIObject, which I changed to a control. I added a second node that I can hover over and see that it does have a key. However, the SetAPIReference still throws a null reference error. At this point, I am pursuing a different method of solving the problem, since all I need the API to do it send a TestStart event. I believe I can make a transducer that will read an LED of the Instron's control panel and just use that to trigger. I am still open to suggestions to get this to work via .NET.

 

Thanks for the help though.

 

Luke J

0 Kudos
Message 11 of 19
(2,271 Views)

Give us new screenshot?

 

George Zou
0 Kudos
Message 12 of 19
(2,263 Views)

Capture2.PNGHere you go. As far as I can tell, both have the same key, which I am not sure matters. Anyways, when I run it, it still throws the "Key cannot be null" error.

 

Luke J

0 Kudos
Message 13 of 19
(2,246 Views)

You might have to use a constructor.

 

George Zou
0 Kudos
Message 14 of 19
(2,241 Views)

Ok, I added the constructor for BluehillAPI, which needs a System.Object Argument, so, I constructed that too. It still throws an error, but I haven't seen this one before, which is exciting.Capture3.PNGCapture3.PNG

0 Kudos
Message 15 of 19
(2,231 Views)

Hello, 

 

I am linking an NI Forum post that discusses this in a bit more detail. Are you encountering this error in development mode or in an executable?

 

https://forums.ni.com/t5/LabVIEW/NET-Control-Error-1172-Only-in-executable/td-p/2497534

 

Regards, 

 

Shezaan Noorani

0 Kudos
Message 16 of 19
(2,215 Views)

Untitled.png

Is there any other constructor available?

Is there any examples available in other programming language?

 

George Zou
0 Kudos
Message 17 of 19
(2,207 Views)

That is the only constructor available for the BluehillAPI.

There are some examples in C#, which I can open, but I am hesitant to post them online due to this heading:

//-----------------------------------------------------------------------------

// Property of Instron Corporation

// Source Code is Confidential

// Copyright (c) Instron Corporation 2010

//-----------------------------------------------------------------------------

In theory, I can change the BluehillSkin.dll to be strong named, but I haven't tired it yet.

Thanks

Luke J

0 Kudos
Message 18 of 19
(2,199 Views)

There are many constructors available in the assembly:

Untitled.png

George Zou
0 Kudos
Message 19 of 19
(2,187 Views)