LINX

cancel
Showing results for 
Search instead for 
Did you mean: 

Possible Error: LINX Appears to open I2C connection in the close I2C connection VI

Highlighted

Odd right?

 

bbelley_0-1600446191776.png

 

I just noticed it.  I am using the Labview community 2020 32 bit LINX that I opened up to find this.  Can anyone else with my version or other confirm this same code layout?

0 Kudos
Message 1 of 7
(233 Views)
Highlighted

Check the actual VI name. In my Linx 2014 version the VI also has the open icon, but it really is the "Local IO\LinxI2cClose.vi"

Rolf Kalbermatter
Averna BV
0 Kudos
Message 2 of 7
(185 Views)
Highlighted

Thanks for the tip, but I opened up the VI and it went to 

 

LMH-LINX.lvlib:Local IO.lvlib:LinxI2cOpen.vi

0 Kudos
Message 3 of 7
(147 Views)
Highlighted

@bbelley wrote:

Thanks for the tip, but I opened up the VI and it went to 

 

LMH-LINX.lvlib:Local IO.lvlib:LinxI2cOpen.vi


Hmmm, Interesting! Someone seems to have "fixed" that error between 2014 and 2020, only in the wrong way :-).

Rolf Kalbermatter
Averna BV
0 Kudos
Message 4 of 7
(141 Views)
Highlighted

No, this is a valid call to the LinxI2cClose function from the shared library. Only the wrong icon on Close Vi.LINX_I2C_Close.png

0 Kudos
Message 5 of 7
(125 Views)
Highlighted

Is this Linx/LabVIEW 2020? Because I see the same as you with Linx for LabVIEW 2014 but the OP claims that it opens the LinxI2COpen VI for him when opening that icon.

Rolf Kalbermatter
Averna BV
0 Kudos
Message 6 of 7
(114 Views)
Highlighted

Yes, Its LINX/LabView2020. And I just noticed that the i2c bus channel selection wire (marked in red) is not connected in I2C Close.vi (Local IO frame).

LINX_I2C_Close2.png

0 Kudos
Message 7 of 7
(110 Views)