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

[bbelley]

Odd right?

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?

[rolfk]

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"

[bbelley]

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

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

[rolfk]

---

@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 :-).

[diman27]

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

[rolfk]

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.

[diman27]

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).