Using NI-9402 I2C with CRIO-9039

[Amy4082001]

Hi, I'm currently trying to use the NI-9402 I2C with CRIO-9039.  It works fine in Labview  but everytime I make changes to it, I have to go through a 5 minutes of Synthesizing (see attachment). Why does it do this? Can this Synthesis be bypassed?

Also, when I tried to add this VI to Teststand, it gives me an error (see second attachment).  Any idea how to get this VI to work in Teststand as well?

This is the Labview VI I am using: https://www.ni.com/en/support/downloads/tools-network/download.spi-and-i2c-driver-api.html

Thanks.

[TheOtherKid]

I think it would be best to break these questions into two parts.

The TestStand question is probably better posted in the TestStand forums. That said, the error is probably occurring because you are trying to run the VI as an action which will cause TestStand to run the vi locally using the LabVIEW 2017 runtime, rather than on the cRIO using the FPGA. I would post a little more detail about exactly what you're trying to achieve in TestStand over there, and they should be able to help you.

For the 9402 itself and the synthesis process, you really shouldn't skip synthesis. It's an important part of how the final hardware is determined. I don't believe there is a way to get around it in LabVIEW FPGA specifically, but I still wouldn't recommend it. The time synthesis and the rest of the compilation takes depends on the code itself, all the connected hardware, and what compile method you're using. 5 minutes is definitely not unheard of and isn't really that long in the realm of FPGA compilation.

Also, the link you posted doesn't appear to be valid, at least from my browser.

[amyle]

Thank you, Bill.  My goal is to use this NI-9402 to read from a sensor using I2C.  If it keeps synthesizing every time I am debugging, that would make debugging very painful.  I'll rethink how I should move forward. Thanks.