I was using the Scan String for Tokens VI in my application to parse a comma-delimited input string. This string sometimes has consecutive commas, indicating null values. In Windows, my usage worked fine, outputting "a", "b", "", and "c" for the input "a,b,,c".
When I loaded the same VI on the PDA, it returned "a", "b", "c", even though "allow empty tokens?" was set to true.
I worked around the problem using the Search/Split String VI instead, but I thought I'd let people know.