Send net_fdm Packet to FlightGear

Transmit net_fdm packet to destination IP address and port for FlightGear session

• Library:

• Aerospace Blockset / Animation / Flight Simulator Interfaces

• 

Description

The Send net_fdm Packet to FlightGear block transmits the net_fdm packet to FlightGear on the current computer, or a remote computer on the network. The packet is constructed using the Pack net_fdm Packet for FlightGear block. The destination port should be an unused port that you can use when you launch FlightGear with the FlightGear command line flag:

--fdm=network,localhost,5501,5502,5503

This block does not produce deployable code.

Ports

Input

net_fdm — FlightGear net_fdm data packet

scalar

FlightGear net_fdm data packet, specified as a scalar.

Data Types: uint8

Parameters

Destination IP address — Destination IP address for remote computer

127.0.0.1 (default) | scalar

Destination IP address, specified as a scalar.

You can use one of several techniques to determine the destination IP address, such as:

• Use 127.0.0.1 for the local computer

• Ping another computer from a Windows^® cmd.exe (or UNIX^® 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, type ipconfig and use the returned IP Address:

  H:\>ipconfig
  
  Windows IP Configuration
  
  Ethernet adapter 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: DestinationIpAddress

Type: character vector

Values: scalar

Default: 127.0.0.1

Destination port — Destination port for remote computer

5502 (default) | scalar

Destination port, specified as a scalar

Programmatic Use

Block Parameter: DestinationPort

Type: character vector

Values: scalar

Default: 5502

Sample time — Sample time

1/30 (default) | scalar

Sample time (-1 for inherited), specified as a scalar.

Programmatic Use

Block Parameter: SampleTime

Type: character vector

Values: scalar

Default: 1/30

Model Examples

HL-20 Project with Optional FlightGear Interface

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