i2c bitbanging

[JimmyD]

Hello,

I'd like to create a LabVIEW program that communicates to a stand alone component using I2C.

I'm guessing that I will need to use bitbanging to get this accomplished.

Does anyone have any examples of this?

Is this even possible to do using LabVIEW? (You'd somehow have to quickly switch your data line from input to output)

Help on this subject would be greatly appreciated!

[PackersFan]

Check out this thread: i2c interface in LabVIEW

[Dennis_Knutson]

Your question is incorrect. LabVIEW is software. In order to do I2C programming, you need hardware. You can buy the USB-8451. Some NI DAQ boards can do I2C. NI's FPGA boards can do I2C. Numerous third party I2C devices.

[JimmyD]

Of course I need hardware!

What I'm asking is if I can use any ol' DAQ to do this.

Let's say I have the USB-6009, is it possible to make a LabVIEW program that communicates to a device (through this DAQ) using I2C?

Or do I need a special DAQ?

p.s. I've already looked at that other i2c thread and didn't find it helpful.

[Dennis_Knutson]

No, you cannot use the 6009. The other thread does list some of the DAQ hardware that you can use ("like the NI 6547, 6548, 6551, 6552, and 6556 devices") and lists the requirements so you can review NI DAQ boards to see if they meet the specs ("any device that supports per-cycle tri-stating"). What other help do you need? The 8451 is the cheapest option from NI if all you need is I2C.

[JimmyD]

Ah okay, this helps!

I also have a myDAQ, but it doesn't say anything about supporting per-cycle tri-stating.. I'm guessing this means it doesn't support it?

Thanks

[Dennis_Knutson · Accepted solution]

I have never used myDAQ. If the digital I/O is software timed like the 6009, then no.

[JoeySpinella]

The myDAQ does not support per-cycle tri-stating, but does have hardware timing, unlike the USB 6009.

I would recommend getting a USB-8451.