.Modelica_DeviceDrivers.Blocks.Examples.TestSerialPackager_SerialPort

Information

Example for serial port support

Hardware setup

In order to execute the example an appropriate physical connection between the sending and the receiving serial port needs to be established, (e.g., by using a null modem cable between the two serial port interfaces http://en.wikipedia.org/wiki/Null_modem). In fact a minimal mull modem with lines (TxD, Rxd and GND) is sufficient. Next, the SerialPortReceive and SerialPortSend blocks parameters must be updated with the device filenames corresponding to the connected physical serial ports. Now, the example can be executed.

Alternative: Using virtual serial port devices for test purposes

To run the example without serial port hardware, it is possible to resort to virtual serial ports. Possible ways of doing this are described in the following.

On Linux, make sure that socat is installed, e.g., on an Ubuntu machine do

sudo aptitude install socat

Now open a console and create two virtual serial port interfaces using socat:

socat -d -d pty,raw,echo=0 pty,raw,echo=0

The socat program will print the device file names that it created. The output will resemble the following:

2013/11/24 15:20:21 socat[3262] N PTY is /dev/pts/1
2013/11/24 15:20:21 socat[3262] N PTY is /dev/pts/3
2013/11/24 15:20:21 socat[3262] N starting data transfer loop with FDs [3,3] and [5,5]

Use them in the Send and Receive block. E.g., for the output above you would use "/dev/pts/1" in SerialPortReceive and "/dev/pts/3" in SerialPortSend.

You may have also have a look at the discussion about virtual serial port devices on stackoverflowhttp://stackoverflow.com/questions/52187/virtual-serial-port-for-linux.

On Windows, make sure that the null modem emulator com0com is installed.

Start the Setup for com0com and check the device names of the created virtual port pair. E.g. you could type "COM6" in SerialPortReceive and "COM7" in SerialPortSend.


Generated at 2024-03-28T19:15:55Z by OpenModelicaOpenModelica 1.22.3 using GenerateDoc.mos