SPI and I2C Driver API missing files

[simbex]

Hi, I have Labview 2017 and installed the SPI and I2C Driver. When I try to use the I2C VIs there are files not found. The files missing are, nirviReadWriteControl.xnode, niLvFpgaAdjustHostInterfaceError.vi, niFpgaNodeNameForErrorReporting.ctl, and niLvFpgaWhatHappensToTopLevelVi.ctl. I tried reinstalling and turned off mass compiler off as suggested by a National Instruments post but no luck. I am really not sure what to do. Below is a pic of one of the broken VIs and I highlighted the part of the vi that is broken. Anyone know what I should do to fix this?

[Bob_Schor]

The most likely explanation for the "Missing Driver files" is that ... they are missing, meaning that you never installed them.

Setting up LabVIEW for moderately complex situations (i.e. other than a simple installation that use largely NI hardware with Projects involving only a single Host) can be quite tricky, even after a decade's experience.  It also gets "interesting" when dealing with older (meaning > 4 years) versions of LabVIEW.

To help us to help you, please provide the following:

• What version of LabVIEW (you said "2017", but failed to specify 32-bit or 64-bit) are you running?  Are other versions of LabVIEW installed on the same machine?
• What other Toolkits and Modules have you installed?  In particular, are you using the LabVIEW Real-Time Module (2017)?
• What specific NI hardware are you trying to use?

Also, please attach the LabVIEW code that we can run ourselves to verify (and try to correct!) the missing files problem you encountered.

Bob Schor

[simbex]

I don't have a program written. The provided VIs are broken. If you look at the first post the pic shows the part of the provided VI program that is broken. When you go to place them from the connectivity menu LabVIEW attempts to find the files but fails to find them. After canceling all the unfound files listed above, the VIs load broken. I don't have specific hardware that I am using. I just need to interface with a device using I2C. My company is developing a product for another company so I can't say too much about what I am doing. The excel file shows everything else besides the SPI and I2C Driver API that is loaded onto my computer. 

[Bob_Schor]

NI makes the NI-845x I²C/SPI "box" that has a USB connector at one end and screw-terminal connectors for I²C and SPI signals (MISO, MOSI, SS, SCLK, etc.) along the sides.  They also have a driver that gives you an SPI to get LabVIEW to "talk" i²C or SPI out those lines and read data back from whatever you have hooked up to use this form of communication.

As you probably know, I²C and SPI are "few-wire" serial protocols that run at fairly fast clock speeds, certainly higher than simple DAQmx multi-function devices.  Now, if you had an NI device with an FPGA, and some expertise in FPGA code generation, you could "synthesize" (write code to create) your own I²C or SPI controller ... or maybe you can find another Chip that you talk Serial (RS-232) at high baud rates and doi it that way.

Bob Schor

[simbex]

I am aware of that and that is why I need to fix the issue I am having. I downloaded the driver and it is missing files that I mentioned above. I don't know how to fix that. That is my question. I want to make those Vi's work. Is there a way I can directly talk to a LabVIEW  engineer? 

[rolfk]

You still totally omitted on what hardware and hardware modules you want to run this. It would seem that you try to run in on your host computer aka, Windows, but that has no FPGA hardware that those FPGA driver functions could access. So your problem is likely that you try to access the wrong examples for the wrong system.

[Bob_Schor]

Conspicuously missing from your Installed Software list is "LabVIEW Real-Time Module".  Without that, I doubt you'll be able to access the FPGA chips that the cRIOs use for SPI and I²C.

Bob Schor