Character translations allow the D3 data structure to handle binary or non-ANSI data.
The values, OxFF, OxFE, OxFD, and OxFC are reserved and cannot be used in fields passed into FlashConnect. In order to handle these values (non-ANSI data), character translation may be performed on inbound and outbound data.
1 to 1 Translation
This table describes the translation pairs.
| Translation Pair | Description |
|---|---|
| FF>0F | Translates FF to 0F for inbound messages. |
| FF<0F | Translates 0F to FF for outbound messages. |
| FF=0F | Translates FF to 0F for inbound messages and 0F to FF for outbound messages. This translation pair is the same as using both FF>0F and FF<0F pairs together. |
| 00>30 | Not allowed, cannot translate an incoming binary zero. |
| 22&33 | Illegal direction code (&). The line is ignored. |
1 to 2 and 2 to 1 Translation
This table describes the translation pairs.
| Escape Character | Description |
|---|---|
| +1B | First line of a 1 to 2 and 2 to 1 translation map file is
a '+' followed by an escape character value in hexadecimal. Note: 1B is used here as an example. You may specify any hex value other
than Null (0x00) as the escape value. This implies that the escape
character is automatically translated on inbound and outbound messages
(1B<->1B1B). It is also implied that any sequence of the escape
character followed by an unmapped byte will be translated coming out
to just the byte (1Bxx to xx when xx is unmapped.)
|
| FF>0F | Translates FF to 1B0F for inbound messages. |
| FF<0F | Translates 1B0F to FF for outbound messages. |
| FF=0F | Translates FF to 1B0F for inbound messages and 1B0F to FF for outbound messages. This translation pair is the same as using both FF>0F and FF<0F pairs together. |
| 00>30 | Not allowed. You cannot translate a binary zero. |