NI USB-8452 I2C Slave -
Using an USB-8452 in listener mode to test the ability of a device to communicate before next level assembly. Device sends write command, high address byte, low address byte, number of bytes to read (this is how it's used in the system), then it sends a repeated start and a read command. The 8452 will acknowledge the write, the 3 bytes but will not acknowledge the read command. The VI I created (I can zip and share if it helps) uses a state machine using the API event handler and never reaches the DataRequested event because it never acknowledges the read command. I receive no errors and the fact that the device acknowledges the write command and data would seem to indicate there's no issue with timing nor levels (pull up, etc).
Anyone seen this? Is there an issue with the device and repeated starts?
Thanks in advance.
