Add to ORKGThor flight 66 consisted of tracking four waypoints in a square configuration spaced 150m apart. Each waypoint has a tolerance radius of 20m around it. There were a few instances where the GPS data was amiss - always in the southern end of the airfield - causing a jagged navigation solution. Besides this, the airplane performed very well. Software modules used were heading_tracker_BP, EKF_15state,waypoint_guidance Thor Flight 66 Rx Data: A010, L999, F000, H00
Thor flight 58 was conducted in the same manner as 57, but the airplane was flown randomly, away fro...
Flight 52 was conducted to test a guidance algorithm where the pilot commands a heading rate which i...
Thor flight 68 consisted of visual range test, and a parametrized sinusoidal waypoint tracking patte...
Thor flight 67 was conducted in the same manner as flight 66, but with the waypoints spaced 100m apa...
Thor flight 65 consisted of tracking four waypoints in a square patter. There were three programmed ...
Adhika, Andrei, Arion, Brian, and Will arrived at ACRC around 9:00am to test the revised waypoint gu...
Adhika, Andrei, Arion, Brian, and Will arrived at ACRC around 9:00am to test the revised waypoint gu...
Adhika, Andrei, Arion, Brian, and Will arrived at ACRC around 9:00am to test the revised waypoint gu...
GPS FASER flight 4 was conducted to test the waypoint tracking capability of the Ultrastick 125 airf...
GPS FASER flight 5 consisted of a 600x250 rectangular waypoint pattern. The maximum bank angle was l...
Thor flight 57 consisted of basic manual control of the aircraft, flying in a landing pattern config...
Andrei, Arion, and Will arrived at ACRC around 3:00pm to obtain fault detection data from Thor. Thre...
Adhika, Andrei, Arion, and Brian arrived at ACRC around 2:00pm to test a quaternion navigation filte...
Thor Flight 19: Waypoint tracker; Engaged multiple times, but the tracker appeared to have difficult...
Adhika, Andrei, Arion, and Brian arrived at ACRC around 2:00pm to test a quaternion navigation filte...
Thor flight 58 was conducted in the same manner as 57, but the airplane was flown randomly, away fro...
Flight 52 was conducted to test a guidance algorithm where the pilot commands a heading rate which i...
Thor flight 68 consisted of visual range test, and a parametrized sinusoidal waypoint tracking patte...
Thor flight 67 was conducted in the same manner as flight 66, but with the waypoints spaced 100m apa...
Thor flight 65 consisted of tracking four waypoints in a square patter. There were three programmed ...
Adhika, Andrei, Arion, Brian, and Will arrived at ACRC around 9:00am to test the revised waypoint gu...
Adhika, Andrei, Arion, Brian, and Will arrived at ACRC around 9:00am to test the revised waypoint gu...
Adhika, Andrei, Arion, Brian, and Will arrived at ACRC around 9:00am to test the revised waypoint gu...
GPS FASER flight 4 was conducted to test the waypoint tracking capability of the Ultrastick 125 airf...
GPS FASER flight 5 consisted of a 600x250 rectangular waypoint pattern. The maximum bank angle was l...
Thor flight 57 consisted of basic manual control of the aircraft, flying in a landing pattern config...
Andrei, Arion, and Will arrived at ACRC around 3:00pm to obtain fault detection data from Thor. Thre...
Adhika, Andrei, Arion, and Brian arrived at ACRC around 2:00pm to test a quaternion navigation filte...
Thor Flight 19: Waypoint tracker; Engaged multiple times, but the tracker appeared to have difficult...
Adhika, Andrei, Arion, and Brian arrived at ACRC around 2:00pm to test a quaternion navigation filte...
Thor flight 58 was conducted in the same manner as 57, but the airplane was flown randomly, away fro...
Flight 52 was conducted to test a guidance algorithm where the pilot commands a heading rate which i...
Thor flight 68 consisted of visual range test, and a parametrized sinusoidal waypoint tracking patte...