Main Content

Receive net_ctrl Packet from FlightGear

Receivenet_ctrlpacket from FlightGear

expand all in page
  • Library:

  • Aerospace Blockset / Animation / Flight Simulator Interfaces

  • Receive net_ctrl Packet from FlightGear block

Description

TheReceive net_ctrl Packet from FlightGearblock receives a network control and environment data packet,net_ctrl, from the simulation of a Simulink®model in the FlightGear simulator, or from a FlightGear session. This data packet is compatible with a particular version of FlightGear flight simulator. This block supports all signals supported by the FlightGearnet_ctrldata packet. The block arranges the signals into multiple groups. The block inserts zeros for packet values that are part of inactive signal groups.

The Aerospace Blockset™ product supports FlightGear versions starting from v2.6. If you are using a FlightGear version older than 2.6, the model displays a notification from the Simulink Upgrade Advisor. Consider using the Upgrade Advisor to upgrade your FlightGear version. For more information, seeSupported FlightGear Versions.

If you run a model that contains this block in Rapid Accelerator mode, the block produces zeros (0s) and it does not produce deployable code. In Accelerator mode, the block works as expected.

For details on signals and signal groups, seeOutput.

Ports

Output

expand all

Controls information from FlightGear, returned as a 744-by-1 vector.

Data Types:uint8

Received FlightGear packet size, specified as a scalar.

  • 0, if no data is received

  • Size of the packet (744) in bytes.

Dependencies

This port is enabled by theEnable received flag portcheck box.

Data Types:double

Parameters

expand all

Enter a valid IP address as a dot-decimal string. This IP address must be the address of the computer from which FlightGear is run, for example,10.10.10.3.

You can also use a MATLAB expression that returns a valid IP address as a character vector. If FlightGear is run on the local computer, leave the default value of127.0.0.1(localhost).

To determine the source IP address, you can use one of several techniques, such as:

  • Use 127.0.0.1 for the local computer (localhost).

  • Ping another computer from a Windows®cmd.exe(or Linux®shell) prompt:

    C:\> ping andyspc Pinging andyspc [144.213.175.92] with 32 bytes of data: Reply from 144.213.175.92: bytes=32 time=30ms TTL=253 Reply from 144.213.175.92: bytes=32 time=20ms TTL=253 Reply from 144.213.175.92: bytes=32 time=20ms TTL=253 Reply from 144.213.175.92: bytes=32 time=20ms TTL=253 Ping statistics for 144.213.175.92: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 30ms, Average = 22ms

  • On a Windows machine, typeipconfigand use the returned IP address:

    H: \ > ipconfig Windows IP配置以太网艾达pter Local Area Connection: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.42.178 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.42.254

Programmatic Use

Block Parameter:ReceiveAddress
Type: character vector
Values: scalar
Default:'127.0.0.1'

UDP port that the block accepts data from. The sender sends data to the port specified in this parameter. This value must match theOrigin portparameter of theGenerate Run Scriptblock. It must be a unique port number that no other application on the computer uses. The site,https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers, lists commonly known UDP port numbers. To identify UDP port numbers already in use on your computer, type:

netstat -a -p UDP

Programmatic Use

Block Parameter:ReceivePort
Type: character vector
Values: scalar
Default:'5505'

Specify the sample time (-1 for inherited).

Programmatic Use

Block Parameter:SampleTime
Type: character vector
Values: scalar
Default:'1/30'

Enable a received flag output port. Use this check box to determine if a FlightGear network packet has been received.

Dependencies

Selecting this check box enables theRx bytesport.

Programmatic Use

Block Parameter:packetFlag
Type: character vector
Values:'off' | 'on'
Default:'off'

Model Examples

HL-20项目可选FlightGear接口

HL-20项目可选FlightGear接口

This project shows how to model NASA's HL-20 lifting body with Simulink®, Stateflow® and Aerospace Blockset™ software. The vehicle model includes the aerodynamics, control logic, fault management systems (FDIR), and engine controls (FADEC). It also includes effects of the environment, such as wind profiles for the landing phase. The entire model simulates approach and landing flight phases using an auto-landing controller. To analyze the effects of actuator failures and wind gust variation on the stability of the vehicle, use the "Run Failure Analysis in Parallel" project shortcut. If Parallel Computing Toolbox™ is installed, the analysis is run in parallel. If Parallel Computing Toolbox™ is not installed, the analysis is run in serial. Visualization for this model is done via an interface to FlightGear, an open source flight simulator package. If the FlightGear interface is unavailable, you can simulate the model by closing the loop using the alternative data sources provided in the Variant block. In this block, you can choose a previously saved data file, a Signal Editor block, or a set of constant values. This example requires Control System Toolbox™.
Open Example

Version History

Introduced in R2012a

See Also

||||

Topics

External Websites