Maettu - 2018-03-26

Many device feature a text based command set, i.e. a command is defined by a line of text and terminated by an end-of-line sequence, typically <CR><LF> or just <LF>. Other devices feature a binary protocol, i.e. a command is defined by a sequence of bytes.

YAT anticipates this fact by offering the option to configure a 'Text' or 'Binary' terminal. Differences are:

Settings Options

Text terminals provide:

  • Text encoding/decoding.
  • EOL sequence.
  • Line related send settings.
  • Character substitution.
  • Text exclusion.

Binary terminals provide:

  • Count related displaying options.
  • Sequence related displaying options.
  • Timing related displaying options.

All other settings are available for both terminal types.

Default Settings

Text terminals by default display content in 'String' radix whereas binary terminals by default use 'Hex' radix. This is just the default setting, the radix can be changed for both terminals types.

Text terminals by default display control characters in ASCII mnemonics whereas binary terminals do not treat control characters specially by default.

Monitor Behavior

As a consequence of the above differences, text terminals by default display lines of text, broken by EOL, whereas binary terminals displays sequences of bytes, which can optionally be broken into separate display lines depending on byte count, byte sequences or timing.

[Send File]

Text terminals always send files line by line, no matter whether a text, RTF or XML file is selected. For RTF and XML files, only the content lines are sent, not the whole file. For all formats, YAT-style escapes like \h(0D) or <CR> can optionally be enabled.

Binary terminals allow to send binary files (whole file is sent, YAT-stylish escapes like \h(0D) or <CR> are not taken into account). In addition, text and XML files containing same content as [Send Text] can also be sent. For XML files, only the content lines are sent, not the whole file.

 

Last edit: Maettu 2018-04-13