Data Sheet

Write Your Own Communication Library
You can write your own communication library, if you are working on a target system that neither supports C++ nor C
compiler.
IMPORTANT: If your system does support C/C++ compiler, we would strongly recommend the communication
library provided by SYD Dynamics for easy maintenance and technical support. It also saves plenty time
implementing your own communication library.
Protocol Overview
TransducerM communication protocol is designed with different layers, as illustrated in Figure 39. It is recommended that the
same layered architecture be implemented in Host computers as well.
A host computer refers to the computer that connects to and reads TransducerM data.
Figure 39 is further explained as below.
Application ↔ EasyProtocol (Communicate by Objects)
On the top layer, the Application communicates with EasyProtocol layer using Objects. An Object is a compound memory item
contains multiple values. For example, Roll, Pitch, Yaw and time stamp data put together in a data structure. In C language, an
Object item may look like this:
typedef struct{
uint32 timeStamp; // Time Stamp (uS)
float32 roll; // Roll (degree)
float32 pitch; // Pitch (degree)
float32 yaw; // Yaw heading (degree)
} Ep_RPY;
Easy Protocol ↔ UART or EasyPipeline (Communicate with Raw data stream)
The middle layer, which is called EasyProtocol, is a software implementation which turns the Object into a Data Package. A
Data package is a stream of raw binary data with header, package length and checksum information. An example Raw data
stream (i.e. a binary package) may look like this:
aa551423e04800ac9a1e83839a1c3f6b100341568d29c1170e
The Raw data stream can then be implemented by a layer below it.
If the layer below it is the Serial Port (i.e. UART interface or USB interface running virtual serial port profile), the Raw data
stream can be transferred or acquired through it directly.
The Physical Connection layer
This is where the actual data communication happens. Signal transmits using physical wire connections.
Copyright © 2015-2019 SYD Dynamics ApS | www.syd-dynamics.com Page 25 / 33
Figure 39: Communication Protocol Layers