A Translation is a flexible special OmniServer element that gives you the ability to replace a specified byte or sequence of bytes with something else in your sent or received (or both) protocol messages. This is typically needed in situations where a device protocol sends preamble characters or maybe a "Double DLE" sequence that requires special handling. Or even to simply convert something like a text or numeric value to something else, like a boolean value.
In this video blog, I show you how to get the most from your OmniServer by using translations with your protocol to convert necesssary sequences to process data to and from your devices in the most effective way possible.
Watch this video to learn what OmniServer translations are and how to start implementing them for your OmniServer protocol. Miss our video tutorial on using OmniServer Registers? Click Here to get caught up!
Just to summarize, in this video, I've shown you:
- How to configure a translation in your OmniServer protocol.
- What the different translation modes are and how they determine whether a translation is applied to sent messages only, received messages only or both.
- An example translation converting Hex values for 0 or 1 to boolean "False" and "True".
- What other settings are available and how they should be used to affect whether or not a translation is applied and when.
- How to define the translation in the actual request/response portion of your command/response message in your OmniServer protocol.
Don't forget to subscribe to our blog to learn about other useful OmniServer how-to videos, use cases or features for integrating all of your non-standard devices - including our previous how-to blog post on using translations.
Ready to work with your own OmniServer protocol using translations?