The datasheet describes 2 modes of operation: hold master / no hold master, which is a funny way of saying enable / disable clock stretching. If you don't have other devices on the same I2C bus that cannot tolerate the bus being busy for a few 10's of milliseconds, it will be easiest to you to work in the "hold master" mode, where you don't need to worry about delaying. Otherwise, you can work in the other mode, issue the command, Thread.sleep() for however long you need to according to the table on page 8 and then attempt to read. Remember to check the boolean return value of writeRead(), which will be false if the device is not ready yet (NACKing). In such case, you may want to retry a few times before giving up.
On Sun, Jan 19, 2014 at 10:49 PM, Matanel <[email protected]> wrote: > See page 7, right side. > > -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/groups/opt_out.
