Skip to content
  • There are no suggestions because the search field is empty.

Using {0xFF} as a delimiter generates an error

We need to get a variable length string, delimited by FF hex. We have defined the response as:

{receive_baud_rate}{0xff}

Clicking on OK gives error message "Variable width sequence cannot be followed by another sequence".

If we use:

{receive_baud_rate}{0x0D}

we get the same error. But if we use:

{receive_baud_rate}{$CR}

it accepts it.

We've tried the usual stuff, using {0xff:1B} etc. and we still get the error. If we put any ordinary character e.g. 0 before the delimiter, e.g. {receive_baud_rate}0{0x0D} it accepts that. How can we use 0xFF as a delimiter?

What you are seeing is by design. Any sequence, defined as something between the curly-cue brackets, cannot follow a variable length sequence. The only exception to this is any sequence that begins with a dollar sign ($). This is interpreted by OmniServer as a hard-coded one-character sequence.

The way to program an "FF" as a delimiter is as follows:

{receive_baud_rate}\xff

Any hex character can be used as a delimiter as long as the "\x" precedes the number.