The E6DOF waypoint trajectory generator, developed by Network Sensing Technologies (NST), is a generic point mass 6-Degee-of-Freedom flight path trajectory generator. It generates a trajectory that passes through a sequence of user defined waypoints referenced to the World Geodetic System 1984 (WGS-84) ellipsoid
E6DOF is a 64-bit C#/C++ software application that executes on Windows 10 platforms. E6DOF GUI creates scenarios which are saved in XML format. E6DOF parses the XML input file that contains airframe maneuverability parameters, initial conditions, and a sequence of waypoints. E6DOF’s output is a time history ASCII output file containing the trajectory data. It can be invoked via command line with corresponding .XML input file. NST has various fidelities of 6DOF models based on the E6DOF that includes GPS/INS error models which are used for different purposes and applications. This version's outputs are uncorrupted by GPS/INS error modeling.
E6DOF implements a six degree-of-freedom simulation of an airborne platform. Originally developed as a medium fidelity model for GPS/INS guidance / transfer alignment studies, it was extended to provide a software component in real-time closed loop operations with GPS RF simulators and GPS UE. Later the E6DOF received modification for hardware in the loop stimulus to GPS and other RF stimulators as well as Embedded GPS Inertial navigators for open loop deterministic testing. The E6DOF Capabilities are simplified to support streamlined testing without the extra burden of GPS/INS error models, Kalman filters etc. E6DOFs simulated platform is generic, without an aerodynamic model. Maneuver parameters limiting accelerations and angles-of-attack are specified by input parameters. Initial conditions and a sequence of waypoints describe the desired trajectory. Two autopilot types are supported: Bank-to-Turn (BTT) and Skid-to-Turn (STT). BTT autopilots are typically used on aircraft. This autopilot will cause the platform to roll and pull Gs until the desired vertical acceleration vector is aligned with the next waypoint. Almost all accelerations sensed by the “pilot” are upward”. Downward accelerations are limited to 1 G and lateral accelerations are minimized. Skid-to-turn autopilots are typically used on projectiles and other high dynamic unmanned aerial vehicles. The STT autopilot will minimize the roll angle and pull significant accelerations in both the vertical and lateral directions. E6DOF implements two waypoint-based guidance laws (Time-at-Waypoint Guidance or Velocity-at-Waypoint Guidance) defined by latitude, longitude, altitude, and the type (Time or Velocity) parameter. The Time-at-Waypoint Guidance law uses an optimal controller to command a thrust that is designed to place the platform at the waypoint at the specified time. The Velocity-at-Waypoint Guidance law will try to maintain the commanded velocity between waypoints. E6DOF cannot generate trajectories for every conceivable sequence of waypoints as the guidance law in use vs waypoints spacing that may violate physics.
Methodology for waypoint based 6DOF trajectory generation is rather simple; specify the maneuverability parameters, initial conditions, waypoint laydown via mouse map entry or manual inputs, a pre-validation phase, modification if necessary and finally trajectory generation. The default step size interval is 5 msec. The same E6DOF model is used for Waypoint, Satellite and Ship based trajectories.
The Maneuverability Parameters section defines several fields that allow you to constrain the motion of the platform. The parameters are:
The Parameter Type allows guidance law selection for platform velocity control Two options are:
Waypoints may be entered either as Latitude, Longitude, Altitude or by clicking on the World Map
It is possible to laydown waypoint trajectories with limited initial and maneuverability settings such that the waypoints cannot be reached causing an endless loop as the E6DOF attempts to fly through the waypoint, circling back over and over. The E6DOF Editor will not create a trajectory without first validating convergence with the constraints and waypoints selected.
|4||Altitude||Meters Relative to WGS84|
|5..7||ECEF Vel X,Y,Z||Meters/Seconds|
|8..10||ECEF Accel X,Y,Z||Meters/Second2|
|11.13||Roll, Pitch, Yaw (hdg)||Degrees|
|14..16||Body Rate X,Y,Z||Radians/Second|
|17..18||Angular Accel X,Y,Z||Radians/Second2|
|5..7||North, East, Up Velocity||meters/second|
|8..10||North, East, Acceleration||meters/second2|
|11..13||Roll, Pitch, Yaw||Degrees|
|14..16||Body Rates X,Y,Z||degrees/second|
|17..19||Angular Acceleration X,Y,Z||degrees/second2|
|22..23||Pitch & Yaw AOA||degrees|
|24..25||Pitch & Yaw AOA dot||degrees/second|
|26..28||Accel Body X,Y,Z||meters/second2|
|31||Commanded Pitch AOA||degrees|
|32||Commanded Yaw AOA||degrees|
|36||Commanded Vertical Acceleration||meters/second2|
|40||Roll from Accel||degrees|
|46||Vertical||1 = almost +/-90deg|
|47||Roll Rate Cmd||Deg/sec|
Note: Things Change Rapidly! Specifications, Capabilities, Features and Availability Subject to Change Without Notice and May Be Restricted to Certain Users.