Communications
Quanser provides external interfaces to establish communication channels between C/C++ applications and the real-time code running on a target machine. These APIs include the Communications API, Stream API and Persistent Stream API. The Communications API defines a generic unbuffered communication API. It is the lowest-level API and only supports the reception and transmission of bytes. However, it is the foundation of all the other communications APIs. The Stream API is a generic buffered communication protocol API based upon the Communications API. It is the most commonly used API because it supports buffered I/O, the common C/C++ binary data types, formatted textual I/O and endian conversions. The Persistent Stream API includes high-level C functions to create server/client applications which support persistent connectivity. It is based upon the Stream API and is the basis for QUARC's Basic Communications blocks in Simulink.
All the communications APIs support a range of communications protocols through a common interface. For a list of protocols supported by QUARC, please refer to the Quanser Communications Protocols section of the QUARC documentation. New protocols may also be added to the communications APIs by writing a protocol driver. For information on developing protocol drivers, please contact Quanser directly.
Use the following list to refer to each communications API:
Copyright ©2024 Quanser Inc. This page was generated 2024-10-17. Submit feedback to Quanser about this page.
Link to this page.