Difference between I2C Scripting Functions and I2C Basic functions and which type i have to choose to implement while communicating with third party hardware

[kiranteja93]

Hi there,

i want to implement I2C communication between NI-845X and other third party hardware as a slave, but i did not get what is the difference between I2C Script and I2C basic functional palettes in Labview, and which functions i have to use to implement communication between NI-845X to third party hardware. so please help me to go through this thing.

[crossrulz · Accepted solution]

---

@kiranteja93 wrote:

i want to implement I2C communication between NI-845X and other third party hardware as a slave...

---

Who is being the slave here?  If you (the 845X) are the slave, then you need to use the I2C Slave palette.

But if you are actually the master, then it depends on the timing you need.  The I2C Scripting is when you need to write/read a lot is a fairly short and/or deterministic time.  But if you are just sending commands and/or reading data intermittently, then stick with the I2C Basic.

[kiranteja93]

Thank you so much for your explanation.

while i was going through "General I2C write.vi" and "General I2C Read.vi" examples i understood that those examples implemented on "EEPROM", so that's why those examples have parameters like "Address width", "Dat Adress Endianess" and "EEPROM Data Address". I want to communicate some sensors like Light Sensor, Differential Pressure Sensor and  Altimeter through USB-8452 module. i am thinking in order to communicate the sensors i need  the device address only. please clarify me about this which parameters needed to set while communicating the above sensors(underlined).

[crossrulz]

It completely depends on the device you are trying to communicate with.  All of the information you need should be in their respective user manuals.