Name | Description |
---|---|
![]() | Example for using the SerialPackager |
![]() | Example for using the SerialPackager with the AddString and GetString block |
![]() | Example for combining UDP and SerialPackager blocks |
![]() | Example for the PackUnsignedInteger and UnpackUnsignedInteger blocks from the SerialPackager |
![]() | Example for combining SharedMemory and SerialPackager blocks |
![]() | Example for a 3Dconnexion SpaceMouse |
![]() | Example for a joystick/gamepad |
![]() | Example for keyboard input |
![]() | Example for keyboard input using the KeyboardKeyInput block |
![]() | Example for using the RandomRealSource block |
![]() | Example for comedi daq support using USB-DUX D (http://www.linux-usb-daq.co.uk/) |
The example demonstrates that pack and unpack blocks of the SerialPackager
package can be connected directly.
Using Strings in input or output connectors is not very common in Modelica. There are currently no standard connectors for
Strings available in the MSL. Nevertheless, the SerialPackager
package provides blocks for Strings, too. The use of this blocks
is demonstrated in this example.
The uDPSend
block sends to the local port 10002. The uDPReceive
block starts a background process that listens at port 10002. Consequently, the uDPReceive
block receives what the uDPSend
block sends.
Note: There is no causality between the uDPSend
block and the uDPReceive
block. Therefore the execution order of the blocks is not determined. Additionally, the uDPReceive
block starts an own receiving thread, so that the time the data was received is not equal to the time the external function within the uDPReceive
block was called. This indeterminism may also show up in the plots.
In particular this model demonstrates how integer values can be packed and unpacked at bit level using the PackUnsignedInteger
and UnpackUnsignedInteger
blocks.
The sharedMemoryWrite
block writes to the memory partition with memoryID = "sharedMemory"
. The sharedMemoryRead
block reads from that partition.
Note: There is no causality between the sharedMemoryWrite
block and the sharedMemoryRead
block. Therefore the execution order of the blocks is not determined. This indeterminism may also show up in the plots.
Basic example of using inputs from a 3Dconnexion SpaceMouse.
Important for Linux users: In order to work under Linux it is needed that the linux drivers provided by 3Dconnexion are installed and running.
Extends from Modelica.Icons.Example (Icon for runnable examples).Basic example of using inputs from a joystick/gamepad device.
Extends from Modelica.Icons.Example (Icon for runnable examples).Basic example of using a keyboard as input device.
Extends from Modelica.Icons.Example (Icon for runnable examples).Basic example of using a keyboard as input device. For this example the parameter keyCode
is set to the "space" key. Therefore, pressing space while the simulation is running will turn the output of the block to true, otherwise it is false
Important: Works only under Linux. The reason for this is, that the interfaced Comedi device drivers are only available for Linux.
Example tested with USB-DUX D. Assuming input channels are electrical connected to corresponding output channels we should read what we wrote
Extends from Modelica.Icons.Example (Icon for runnable examples). Automatically generated Tue Oct 1 14:26:58 2013.