Knowledge Base

Solution 37688: TI-Innovator™ Hub Consecutive READ statements overload return buffer.

Why do consecutive READ statements overload return buffer?

Combining multiple READ statements in a single SEND command separated by “\n” may result in unexpected results.

Example of problem case:

Get "READ COLOR.RED\nREAD COLOR.RED",red1
Get "SET COLOR.RED 20\nREAD COLOR.RED",red2

The 2nd variable “red2” has information corresponding to the second READ, and not the last READ.

To workaround this issue use only one READ command in each SEND command.