Skip to main content

title: "Serial" url: doc/communication/serial.html page_css_file: /4diac/css/4diac_doc.css sidebar: - sb-doc --- = Serial

Serial communication can be used with Client, Server, PUB and SUB function blocks. Best practise is to use a Client block.

Configuration

To enable serial communication, 4diac FORTE must be compiled from source.

Make sure that the CMake option FORTE_COM_SER is enabled.

After compiling FORTE with this option, serial communication support will be available.

Function Blocks

  • To send and receive data over serial, use a CLIENT_1 function block. SD_1 is the output data and RD_1 the input data.

  • For unidirectional data transfer only, PUB and SUB function blocks can also be used:

    • Use a PUBLISH_1 function block to send data.

    • Use a SUBSCRIBE_1 function block to receive data.

ID Parameter​

The ID parameter has the following format:

  • Device Path

  • Baudrate

  • Data Bits (5, 6, 7, 8)

  • Stop Bits (1, 1.5, 2)

  • Parity (NONE, ODD, EVEN, MARK, SPACE)

  • Termination Symbol ($$r$$n, $$r, $$n)

Example:

fbdk[].ser[/dev/serial0,115200,8,1,NONE,$$r$$n]

Data Transmission

To send plain text over a serial connection, use the raw[] layer.

To transmit IEC 61499 data types, use the fbdk[] layer.

The fbdk[] layer prepends additional bytes to the payload, according to its datatype. When communicating with external devices (e.g., microcontrollers), a good way is to use a hex viewer to identify these additional bytes.

Where to go from here?

Or Go to top