Lmpacent: /* I2CSendReceive() */

2026-04-09T19:50:44Z

I2CSendReceive()

← Older revision		Revision as of 19:50, 9 April 2026
Line 38:		Line 38:

	''''S'''' represents a start condition, while ''''P'''' represents a stop condition. If your I2C device requires data in a different structure than this, you may need to use {{Code\|I2CComplexTransaction()}}, as explained in the next section.		''''S'''' represents a start condition, while ''''P'''' represents a stop condition. If your I2C device requires data in a different structure than this, you may need to use {{Code\|I2CComplexTransaction()}}, as explained in the next section.








	=== I2CComplexTransaction() ===		=== I2CComplexTransaction() ===

Lmpacent: /* Introduction */

2026-04-09T19:44:04Z

Introduction

← Older revision		Revision as of 19:44, 9 April 2026
Line 8:		Line 8:


	Before starting this guide, visit the Quick Start Guide on your Adapter Phidget's product page for information about wiring.		Before starting this guide, visit the Quick Start Guide on your I2C Adapter Phidget's product page for information about wiring.

	== Address Format ==		== Address Format ==

Lmpacent: /* Introduction */

2026-04-09T19:43:28Z

Introduction

← Older revision		Revision as of 19:43, 9 April 2026
Line 4:		Line 4:
	<div class="toclimit-4">		<div class="toclimit-4">
	== Introduction ==		== Introduction ==
	This guide will provide ~~additional details for~~ the DataAdapter API so you ~~can better understand what~~ your I2C Adapter Phidget ~~is doing when communicating with an I2C device~~.		[[Image:ADP0001_0.jpg\|thumb\|<center>I2C Adapter Phidget (ADP0001_0)</center>]]
			This guide will provide information about the DataAdapter API to get you up and running with your new I2C Adapter Phidget.


			Before starting this guide, visit the Quick Start Guide on your Adapter Phidget's product page for information about wiring.

	== Address Format ==		== Address Format ==

Mparadis: Created page with "{{#seo:|description=Get started with your I2C Adapter Phidget}} Category:IntroGuide

== Introduction == This guide will provide additional details for the DataAdapter API so you can better understand what your I2C Adapter Phidget is doing when communicating with an I2C device. == Address Format == The I2C Adapter Phidget interprets the device address as follows: 550px The read/write bit i..."

2026-04-09T18:16:26Z

Created page with "{{#seo:|description=Get started with your I2C Adapter Phidget}} Category:IntroGuide <div class="nonumtoc"> <div class="toclimit-4"> == Introduction == This guide will provide additional details for the DataAdapter API so you can better understand what your I2C Adapter Phidget is doing when communicating with an I2C device. == Address Format == The I2C Adapter Phidget interprets the device address as follows: link=|550px The read/write bit i..."

New page

{{#seo:|description=Get started with your I2C Adapter Phidget}}
[[Category:IntroGuide]]
<div class="nonumtoc">
<div class="toclimit-4">
== Introduction ==
This guide will provide additional details for the DataAdapter API so you can better understand what your I2C Adapter Phidget is doing when communicating with an I2C device.

== Address Format ==

The I2C Adapter Phidget interprets the device address as follows:

[[Image:I2C_Addr.png|link=|550px]]

The read/write bit is not included in the hexadecimal value for the address, as this bit is handled by the API calls.
You may find that datasheets for some I2C devices include the read/write bit, so a read-only device like a simple temperature sensor might specify the address as '''0xE3''' instead of '''0x71''' in this case. When using such a sensor, be sure to ignore the R/W bit and shift the remaining seven bits down to get the address you need to send to Phidgets API calls.

== Methods ==
=== I2CSendReceive() ===

Parameters:
* int '''address'''
* byte[ ] '''data'''
* int '''receiveLength'''

This is the main function you'll use for simple read and write operations.

* The first parameter is the I2C address of your device, usually specified in the datasheet or printed on the circuit board.
* The second parameter is the data array, which can contain up to 127 bytes. If the data array is empty, the I2C Adapter Phidget will skip sending the write address and bytes.
* The third parameter is the receive length, or the number of bytes you're expecting back from the device for this transaction. Maximum receive length is 127, and if it's zero the I2C Adapter Phidget will skip sending the read address and bytes.

This diagram illustrates the data structure when using {{Code|I2CSendReceive}}:

[[Image:I2C_SendRecv.png|link=|850px]]

''''S'''' represents a start condition, while ''''P'''' represents a stop condition. If your I2C device requires data in a different structure than this, you may need to use {{Code|I2CComplexTransaction()}}, as explained in the next section.

=== I2CComplexTransaction() ===

Parameters:
* int '''address'''
* string '''I2CPacketString'''
* byte[ ] '''data'''

This function gives you more control over the read/write structure for more complex interactions. This is useful for longer commands that make use of repeated start conditions.

* The first parameter is the I2C address of your device, usually specified in the datasheet or printed on the circuit board.
* The second parameter is a string that dictates the read/write sequence to follow.
* The third parameter is the data array, whose length must match the number of writes in the string, up to 127 bytes.

The string is made up of the following characters, case-sensitive with no spaces:
* ''''s'''' for a start condition
* ''''R'''' for a read byte
* ''''T'''' for a write byte
* ''''p'''' for a stop condition

Here's an example:

[[Image:I2C_Complex.png|link=|850px]]

Numerals can also be used after a 'T' or 'R' to make the string compact. In this example, the data array would need to have a length of 3, since a total of three bytes are written in the sequence.

I2C Adapter API Guide - Revision history

Lmpacent: /* I2CSendReceive() */

Lmpacent: /* Introduction */

Lmpacent: /* Introduction */