Character strings, Character, Strings – Banner PresencePLUS P4 COLOR Series User Manual
Page 327
•
• , for comma
• ; for semi-colon
• : for colon
•
• \t for tab
In addition to the above field delimiters, you can enter other delimiter types keeping in mind the following:
• ASCII hex format can be used as a delimiter
• a NULL character can be used as a delimiter (specified in ASCII hex format)
• Field delimiters can be multi-character sequences up to 10 characters long
Character Strings
Communications Tool configured for Barcode or String Tool output may produce strings that contain non-printable
ASCII characters, such as carriage returns, line feeds, and characters in the upper ASCII range.
To output these strings, the following encoding rules are used:
• Tool output strings will be enclosed in double quote characters, “.
• Any non-printable ASCII character, including NULL, will be converted to its ASCII Hex equivalent. The ASCII Hex
string will be preceded by character sequence “\x” (backslash-lower-case-x). The ASCII Hex string will always be
two characters long. For example, NULL will be converted to “\x00”, and carriage return will be converted to “\x0D”.
To represent ASCII Hex digits, only upper case letters, A-F, will be used.
• Any backslash encountered in the Barcode or String Tool data will be converted to its ASCII Hex equivalent, “\x5C”.
• Any double quote encountered in the Barcode or String Tool will be converted to its ASCII Hex equivalent, “\x22”.
For RCC input strings, the formatting rules are expanded to accommodate readability as follows:
• Carriage return can be specified as character sequence "\r" (backslash-r).
• Line feed can be specified as character sequence "\n" (backslash-n).
• Double quote can be specified as character sequence "\"" (backslash-doublequote).
• Backslah can be specified as character sequence "\\" (backslash-backslash).
• tab can be specified as character sequence "\t" (backslash-t).
• Embedded NULLL characters are not allowed.
327
Minneapolis, MN USA
Banner Engineering Corp.
Communication Tool Setup
2/2010