User:John Burt - Revision history

Esden at 20:34, 10 March 2011

2011-03-10T20:34:49Z

← Older revision		Revision as of 14:34, 10 March 2011
Line 125:		Line 125:

	Flight 3: Cularis w/ standard RC receiver (no AP on board). Cularis flight was first since a crash in Seattle last year. The Seattle crash was luckily at low altitude, but caused some damage, including cracking wing mount and compressing nose. The original crash was caused by glitching in the RX where plane became unresponsive. Today's flight was to test the semi-repaired plane (a few things still broken, including wing lock mechanisms). In this flight, I just wanted to test the plane and repairs. The result: initial launch, plane climbed strongly (quite windy at this time BTW), but lots of up-thrust (maybe due to nose compression from first crash, but also possibly balance?). After trimming flight and flying around a bit I attempted to land. The plane was a bit downwind and on final leg to land when it began glitching again at low alt (about 10m). I managed to straighten it out and flew it w/ only occasional control until it landed far out in the field. When we reached downed plane, it was unresponsive to TX commands and motor was trying to run (maybe 25% throttle). I disconnected battery and reconnected and RX behaved properly. I don't know what's wrong but there seems to be a glitching problem unrelated to any other onboard electronics. Maybe the speed controller is causing interference. This may be resolved when I use an AP w/ plane.		Flight 3: Cularis w/ standard RC receiver (no AP on board). Cularis flight was first since a crash in Seattle last year. The Seattle crash was luckily at low altitude, but caused some damage, including cracking wing mount and compressing nose. The original crash was caused by glitching in the RX where plane became unresponsive. Today's flight was to test the semi-repaired plane (a few things still broken, including wing lock mechanisms). In this flight, I just wanted to test the plane and repairs. The result: initial launch, plane climbed strongly (quite windy at this time BTW), but lots of up-thrust (maybe due to nose compression from first crash, but also possibly balance?). After trimming flight and flying around a bit I attempted to land. The plane was a bit downwind and on final leg to land when it began glitching again at low alt (about 10m). I managed to straighten it out and flew it w/ only occasional control until it landed far out in the field. When we reached downed plane, it was unresponsive to TX commands and motor was trying to run (maybe 25% throttle). I disconnected battery and reconnected and RX behaved properly. I don't know what's wrong but there seems to be a glitching problem unrelated to any other onboard electronics. Maybe the speed controller is causing interference. This may be resolved when I use an AP w/ plane.

			[[Category:User_Notes]]

Quill65: /* Flight logs */

2009-04-06T04:22:56Z

Flight logs

← Older revision		Revision as of 22:22, 5 April 2009
Line 95:		Line 95:

	==== Flights on 2009/03/06 ====		==== Flights on 2009/03/06 ====
	Easystar flight test. At a small field in Vancouver.		Easystar flight test. Paul Cox assisting. At a small field in Vancouver.

	Flight 1: Takeoff on manual w/ no modem link worked fine (aileron still has very little effect, due to overly stable design). When I switch to AUTO1, the plane is still controllable and (apparently) AP stabilizes. However, motor shut off. (this was because we didn't click the Launch button before starting the flight). When I switched to AUTO2, the plane did a circle near the switch point, and then seems to start wandering away. The GCS says the plane is in “hold mode”. It may be that the plane would have circled back around, but it’s hard to tell. In any case, it didn’t show any tendency to head “home”, even after I re-defined home as approx at launch point.		Flight 1: Takeoff on manual w/ no modem link worked fine (aileron still has very little effect, due to overly stable design). When I switch to AUTO1, the plane is still controllable and (apparently) AP stabilizes. However, motor shut off. (this was because we didn't click the Launch button before starting the flight). When I switched to AUTO2, the plane did a circle near the switch point, and then seems to start wandering away. The GCS says the plane is in “hold mode”. It may be that the plane would have circled back around, but it’s hard to tell. In any case, it didn’t show any tendency to head “home”, even after I re-defined home as approx at launch point.
Line 102:		Line 102:

	==== Flights on 2009/03/23 ====		==== Flights on 2009/03/23 ====
	Easystar flight test. At a small field in Vancouver. It was overcast and cold. Occasional rain / showers / hail. Wind		Easystar flight test. Paul Cox assisting. At a small field in Vancouver. It was overcast and cold. Occasional rain / showers / hail. Wind
	sometimes calm, other times 5-10mph or so.		sometimes calm, other times 5-10mph or so.

Line 110:		Line 110:

	==== Flights on 2009/03/30 ====		==== Flights on 2009/03/30 ====
	Easystar flight test. New flying site at big field near Vancouver Lake, WA.		Easystar flight test. Paul Cox assisting. New flying site at big field near Vancouver Lake, WA.

Quill65: /* Flights on 2009/04/05 */

2009-04-06T04:22:03Z

Flights on 2009/04/05

← Older revision		Revision as of 22:22, 5 April 2009
Line 118:		Line 118:

	==== Flights on 2009/04/05 ====		==== Flights on 2009/04/05 ====
	Easystar, Cularis flight test. New flying site at big field near Vancouver Lake, WA.		Easystar, Cularis flight test. Paul Cox assisting. New flying site at big field near Vancouver Lake, WA.

	Flight 1: Easystar, using new flight plan w/ triangle mission (fly between 3 wps in loop). Launched in auto1 mode. There was a problem w/ pitch, likely from canopy tilted forward from last crash (whole nose section was compressed a bit). Adjusted pitch in flight in auto1 to correct for level flight. I switched the mode to auto2 and we let the plane stay in standby mode (flying around standby wp) so that we could tweak settings: 1) set nav circle to 75m, 2) varied nav gain, and it seems to work best at 0.8, 3) alt gain: turned out to be just right as is. At end of flight, the plane began losing alt, but GCS reported high throttle value. This was because the motor battery was running down (seperate motor and AP batteries). I switched to auto1 mode and landed.		Flight 1: Easystar, using new flight plan w/ triangle mission (fly between 3 wps in loop). Launched in auto1 mode. There was a problem w/ pitch, likely from canopy tilted forward from last crash (whole nose section was compressed a bit). Adjusted pitch in flight in auto1 to correct for level flight. I switched the mode to auto2 and we let the plane stay in standby mode (flying around standby wp) so that we could tweak settings: 1) set nav circle to 75m, 2) varied nav gain, and it seems to work best at 0.8, 3) alt gain: turned out to be just right as is. At end of flight, the plane began losing alt, but GCS reported high throttle value. This was because the motor battery was running down (seperate motor and AP batteries). I switched to auto1 mode and landed.
Line 124:		Line 124:
	Flight 2: Easystar w/ same flight plan. Nav circle reduced to 50m (original). The wind was a problem in both flights: varied from 12mph or so to near 0. When wind was high, the plane had trouble with courses requiring cross-wind flight (over or under corrected), BUT the AP did a good job of recovering from mistakes. In triangle mission, the plane did exactly as I wanted: flew to within nav circle radius, then flew a line to next wp. Landed in auto1 mode before battery level declined.		Flight 2: Easystar w/ same flight plan. Nav circle reduced to 50m (original). The wind was a problem in both flights: varied from 12mph or so to near 0. When wind was high, the plane had trouble with courses requiring cross-wind flight (over or under corrected), BUT the AP did a good job of recovering from mistakes. In triangle mission, the plane did exactly as I wanted: flew to within nav circle radius, then flew a line to next wp. Landed in auto1 mode before battery level declined.

	Flight 3: Cularis w/ standard RC receiver (no AP on board). Cularis flight was first since a crash in Seattle last year. The Seattle crash was luckily at low altitude, but caused some damage, including cracking wing mount and compressing nose. The original crash was caused by glitching in the RX where plane became unresponsive. Today's flight was to test the semi-repaired plane (a few things still broken, including wing lock mechanisms). In this flight, I just wanted to test the plane and repairs. The result: initial launch, plane climbed strongly (quite windy at this time BTW), but lots of up-thrust (maybe due to nose compression from first crash, but also possibly balance?). After trimming flight and flying around a bit I attempted to land. The plane was a bit downwind and on final leg to land when it began glitching again at low alt (about 10m). I managed to straighten it out and flew it until it landed far out in the field. ~~On approach to~~ downed plane, it was unresponsive to TX commands and motor was trying to run (maybe 25% throttle). I disconnected battery and reconnected and RX behaved properly. I don't know what's wrong but there seems to be a glitching problem unrelated to any other onboard electronics. Maybe the speed controller is causing interference. This may be resolved when I use an AP w/ plane.		Flight 3: Cularis w/ standard RC receiver (no AP on board). Cularis flight was first since a crash in Seattle last year. The Seattle crash was luckily at low altitude, but caused some damage, including cracking wing mount and compressing nose. The original crash was caused by glitching in the RX where plane became unresponsive. Today's flight was to test the semi-repaired plane (a few things still broken, including wing lock mechanisms). In this flight, I just wanted to test the plane and repairs. The result: initial launch, plane climbed strongly (quite windy at this time BTW), but lots of up-thrust (maybe due to nose compression from first crash, but also possibly balance?). After trimming flight and flying around a bit I attempted to land. The plane was a bit downwind and on final leg to land when it began glitching again at low alt (about 10m). I managed to straighten it out and flew it w/ only occasional control until it landed far out in the field. When we reached downed plane, it was unresponsive to TX commands and motor was trying to run (maybe 25% throttle). I disconnected battery and reconnected and RX behaved properly. I don't know what's wrong but there seems to be a glitching problem unrelated to any other onboard electronics. Maybe the speed controller is causing interference. This may be resolved when I use an AP w/ plane.

Quill65: /* Flights on 2009/04/05 */

2009-04-06T04:18:41Z

Flights on 2009/04/05

← Older revision		Revision as of 22:18, 5 April 2009
Line 120:		Line 120:
	Easystar, Cularis flight test. New flying site at big field near Vancouver Lake, WA.		Easystar, Cularis flight test. New flying site at big field near Vancouver Lake, WA.

	Flight 1: Easystar, using new flight plan w/ triangle mission (fly between 3 wps in loop). Launched in auto1 mode. There was a problem w/ pitch, likely from canopy tilted forward from last crash (whole nose section was compressed a bit). Adjusted pitch in flight in auto1 to correct for level flight. I switched the mode to auto2 and we let the plane stay in standby mode (flying around standby wp) so that we could tweak settings: 1) set nav circle to 75m, 2) varied nav gain, and it seems to work best at 0.8, 3) alt gain: turned out to be just right as is. At end of flight, the plane began losing alt, but GCS reported high throttle value. This was because the motor battery was running down. I switched to auto1 mode and landed.		Flight 1: Easystar, using new flight plan w/ triangle mission (fly between 3 wps in loop). Launched in auto1 mode. There was a problem w/ pitch, likely from canopy tilted forward from last crash (whole nose section was compressed a bit). Adjusted pitch in flight in auto1 to correct for level flight. I switched the mode to auto2 and we let the plane stay in standby mode (flying around standby wp) so that we could tweak settings: 1) set nav circle to 75m, 2) varied nav gain, and it seems to work best at 0.8, 3) alt gain: turned out to be just right as is. At end of flight, the plane began losing alt, but GCS reported high throttle value. This was because the motor battery was running down (seperate motor and AP batteries). I switched to auto1 mode and landed.

	Flight 2: Easystar w/ same flight plan. Nav circle reduced to 50m (original). The wind was a problem in both flights: varied from 12mph or so to near 0. When wind was high, the plane had trouble with courses requiring cross-wind flight (over or under corrected), BUT the AP did a good job of recovering from mistakes. In triangle mission, the plane did exactly as I wanted: flew to within nav circle radius, then flew a line to next wp. Landed in auto1 mode before battery level declined.		Flight 2: Easystar w/ same flight plan. Nav circle reduced to 50m (original). The wind was a problem in both flights: varied from 12mph or so to near 0. When wind was high, the plane had trouble with courses requiring cross-wind flight (over or under corrected), BUT the AP did a good job of recovering from mistakes. In triangle mission, the plane did exactly as I wanted: flew to within nav circle radius, then flew a line to next wp. Landed in auto1 mode before battery level declined.

	Flight 3: Cularis w/ standard RC receiver (no AP on board). Cularis flight was first since a crash in Seattle last year. The Seattle crash was luckily at low altitude, but caused some damage, including cracking wing mount and compressing nose. The original crash was caused by glitching in the RX where plane became unresponsive. Today's flight was to test the semi-repaired plane (a few things still broken, including wing lock mechanisms). In this flight, I just wanted to test the plane and repairs. The result: initial launch, plane climbed strongly (quite windy at this time BTW), but lots of up-thrust (maybe due to nose compression from first crash, but also possibly balance?). After trimming flight and flying around a bit I attempted to land. The plane was a bit downwind and on final leg to land when it began glitching again at low alt (about 10m). I managed to straighten it out and flew it until it landed far out in the field. On approach to downed plane, it was unresponsive to TX commands and motor was trying to run (maybe 25% throttle). I disconnected battery and reconnected and RX behaved properly. I don't know what's wrong but there seems to be a glitching problem unrelated to any other onboard electronics. Maybe the speed controller is causing interference. This may be resolved when I use an AP w/ plane.		Flight 3: Cularis w/ standard RC receiver (no AP on board). Cularis flight was first since a crash in Seattle last year. The Seattle crash was luckily at low altitude, but caused some damage, including cracking wing mount and compressing nose. The original crash was caused by glitching in the RX where plane became unresponsive. Today's flight was to test the semi-repaired plane (a few things still broken, including wing lock mechanisms). In this flight, I just wanted to test the plane and repairs. The result: initial launch, plane climbed strongly (quite windy at this time BTW), but lots of up-thrust (maybe due to nose compression from first crash, but also possibly balance?). After trimming flight and flying around a bit I attempted to land. The plane was a bit downwind and on final leg to land when it began glitching again at low alt (about 10m). I managed to straighten it out and flew it until it landed far out in the field. On approach to downed plane, it was unresponsive to TX commands and motor was trying to run (maybe 25% throttle). I disconnected battery and reconnected and RX behaved properly. I don't know what's wrong but there seems to be a glitching problem unrelated to any other onboard electronics. Maybe the speed controller is causing interference. This may be resolved when I use an AP w/ plane.

Quill65: /* Flight logs */

2009-04-06T04:17:03Z

Flight logs

← Older revision		Revision as of 22:17, 5 April 2009
Line 116:		Line 116:

	Flight 2: launched in Auto2 mode. Plane dove into ground, hit and skidded, then rose into the air. Shallow climb at first (100% throttle), then began steep circles at high speed and low altitude. Eventually crashed. I had tried to switch to manual mode on RC TX, but AP did not respond (only after plane was on ground). Probable issues: CLIMB wp alt=25m was too low, climb pitch too low, CLIMB wp too close to launch point (should be at least 200-300m out I think).		Flight 2: launched in Auto2 mode. Plane dove into ground, hit and skidded, then rose into the air. Shallow climb at first (100% throttle), then began steep circles at high speed and low altitude. Eventually crashed. I had tried to switch to manual mode on RC TX, but AP did not respond (only after plane was on ground). Probable issues: CLIMB wp alt=25m was too low, climb pitch too low, CLIMB wp too close to launch point (should be at least 200-300m out I think).

			==== Flights on 2009/04/05 ====
			Easystar, Cularis flight test. New flying site at big field near Vancouver Lake, WA.

			Flight 1: Easystar, using new flight plan w/ triangle mission (fly between 3 wps in loop). Launched in auto1 mode. There was a problem w/ pitch, likely from canopy tilted forward from last crash (whole nose section was compressed a bit). Adjusted pitch in flight in auto1 to correct for level flight. I switched the mode to auto2 and we let the plane stay in standby mode (flying around standby wp) so that we could tweak settings: 1) set nav circle to 75m, 2) varied nav gain, and it seems to work best at 0.8, 3) alt gain: turned out to be just right as is. At end of flight, the plane began losing alt, but GCS reported high throttle value. This was because the motor battery was running down. I switched to auto1 mode and landed.

			Flight 2: Easystar w/ same flight plan. Nav circle reduced to 50m (original). The wind was a problem in both flights: varied from 12mph or so to near 0. When wind was high, the plane had trouble with courses requiring cross-wind flight (over or under corrected), BUT the AP did a good job of recovering from mistakes. In triangle mission, the plane did exactly as I wanted: flew to within nav circle radius, then flew a line to next wp. Landed in auto1 mode before battery level declined.

			Flight 3: Cularis w/ standard RC receiver (no AP on board). Cularis flight was first since a crash in Seattle last year. The Seattle crash was luckily at low altitude, but caused some damage, including cracking wing mount and compressing nose. The original crash was caused by glitching in the RX where plane became unresponsive. Today's flight was to test the semi-repaired plane (a few things still broken, including wing lock mechanisms). In this flight, I just wanted to test the plane and repairs. The result: initial launch, plane climbed strongly (quite windy at this time BTW), but lots of up-thrust (maybe due to nose compression from first crash, but also possibly balance?). After trimming flight and flying around a bit I attempted to land. The plane was a bit downwind and on final leg to land when it began glitching again at low alt (about 10m). I managed to straighten it out and flew it until it landed far out in the field. On approach to downed plane, it was unresponsive to TX commands and motor was trying to run (maybe 25% throttle). I disconnected battery and reconnected and RX behaved properly. I don't know what's wrong but there seems to be a glitching problem unrelated to any other onboard electronics. Maybe the speed controller is causing interference. This may be resolved when I use an AP w/ plane.

Quill65 at 01:29, 1 April 2009

2009-04-01T01:29:35Z

← Older revision		Revision as of 19:29, 31 March 2009
Line 19:		Line 19:

	----		----
	=== Easystar: ===		=== Easystar ===
	----		----

Line 67:		Line 67:
	----		----

	=== Cularis: ===		=== Cularis ===
	----		----

Line 94:		Line 94:
	----		----

	==== Flight on 2009/03/23: ====		==== Flights on 2009/03/06 ====
			Easystar flight test. At a small field in Vancouver.

			Flight 1: Takeoff on manual w/ no modem link worked fine (aileron still has very little effect, due to overly stable design). When I switch to AUTO1, the plane is still controllable and (apparently) AP stabilizes. However, motor shut off. (this was because we didn't click the Launch button before starting the flight). When I switched to AUTO2, the plane did a circle near the switch point, and then seems to start wandering away. The GCS says the plane is in “hold mode”. It may be that the plane would have circled back around, but it’s hard to tell. In any case, it didn’t show any tendency to head “home”, even after I re-defined home as approx at launch point.

			Flight 2: We installed modem and launched in manual mode. At altitude, I switched to AUTO2, and plane cut motor (postmortem: battery critical trigger) and started wandering around over a house a ways off, not near home, standby wps, etc. When I switched to manual mode, I lost all control of the plane and it nosedived into the ground from a fairly high altitude.

			==== Flights on 2009/03/23 ====
	Easystar flight test. At a small field in Vancouver. It was overcast and cold. Occasional rain / showers / hail. Wind		Easystar flight test. At a small field in Vancouver. It was overcast and cold. Occasional rain / showers / hail. Wind
	sometimes calm, other times 5-10mph or so.		sometimes calm, other times 5-10mph or so.
Line 102:		Line 109:
	Flight 2: started in auto1 mode. Figured out the correct sequence to allow auto2 mode to launch: click Takeoff, then Launch, then launch the plane in Auto1 mode. We also fixed default altitude, which was set too low (ground alt was 60m). In this flight, I was able to get ES to circle over home and auto-maintain altitude by varying throttle. However, flight behavior was affected by the wind: the plane would get downwind and then flounder with nose pitched up. Eventually, I switched to auto1 and dipped the nose down to penetrate into the wind and get the plane home.		Flight 2: started in auto1 mode. Figured out the correct sequence to allow auto2 mode to launch: click Takeoff, then Launch, then launch the plane in Auto1 mode. We also fixed default altitude, which was set too low (ground alt was 60m). In this flight, I was able to get ES to circle over home and auto-maintain altitude by varying throttle. However, flight behavior was affected by the wind: the plane would get downwind and then flounder with nose pitched up. Eventually, I switched to auto1 and dipped the nose down to penetrate into the wind and get the plane home.

	==== ~~Flight~~ on 2009/03/30: ====		==== Flights on 2009/03/30 ====
	Easystar flight test. New flying site at big field near Vancouver Lake, WA.		Easystar flight test. New flying site at big field near Vancouver Lake, WA.

Quill65 at 01:18, 1 April 2009

2009-04-01T01:18:05Z

@@ Line 10: / Line 10: @@
 The goal of this project is to develop and promote a UAV platform for biological research, conservation work, and wildlife management. The UAV system I am building is intended to be extremely rugged, cheap, relatively easy to use and maintain, flexible, and hackable for different missions. The system is ultimately intended to be used in extremely difficult and remote field environments where there is no internet or reliable power source (e.g., African bush, South America, South Pacific, US Pacific Northwest wilderness).
 == Airframes ==
@@ Line 105: / Line 87: @@
 '''Progress:'''
 * Airframe tested and flying.

Quill65 at 01:16, 1 April 2009

2009-04-01T01:16:41Z

← Older revision		Revision as of 19:16, 31 March 2009
Line 10:		Line 10:

	The goal of this project is to develop and promote a UAV platform for biological research, conservation work, and wildlife management. The UAV system I am building is intended to be extremely rugged, cheap, relatively easy to use and maintain, flexible, and hackable for different missions. The system is ultimately intended to be used in extremely difficult and remote field environments where there is no internet or reliable power source (e.g., African bush, South America, South Pacific, US Pacific Northwest wilderness).		The goal of this project is to develop and promote a UAV platform for biological research, conservation work, and wildlife management. The UAV system I am building is intended to be extremely rugged, cheap, relatively easy to use and maintain, flexible, and hackable for different missions. The system is ultimately intended to be used in extremely difficult and remote field environments where there is no internet or reliable power source (e.g., African bush, South America, South Pacific, US Pacific Northwest wilderness).

			== Flight log ==

			==== Flight on 2009/03/23: ====
			Easystar flight test. At a small field in Vancouver. It was overcast and cold. Occasional rain / showers / hail. Wind
			sometimes calm, other times 5-10mph or so.

			Flight 1: Launched in manual mode (mistake), auto1 mode gave good stability. auto2 mode also cut throttle, and plane seemed to wander around too far away.

			Flight 2: started in auto1 mode. Figured out the correct sequence to allow auto2 mode to launch: click Takeoff, then Launch, then launch the plane in Auto1 mode. We also fixed default altitude, which was set too low (ground alt was 60m). In this flight, I was able to get ES to circle over home and auto-maintain altitude by varying throttle. However, flight behavior was affected by the wind: the plane would get downwind and then flounder with nose pitched up. Eventually, I switched to auto1 and dipped the nose down to penetrate into the wind and get the plane home.

			==== Flight on 2009/03/30: ====
			Easystar flight test. New flying site at big field near Vancouver Lake, WA.


			Flight 1: launched in Auto1 mode. Climbed out and switched to Auto2 for route testing. The plane is still over-correcting when making course changes. Tends to "waffle" around and never does neat circles around wp,etc. Tested line 1-2 in basic config. Worked more or less, but waffling caused plane to wander around a lot.

			Flight 2: launched in Auto2 mode. Plane dove into ground, hit and skidded, then rose into the air. Shallow climb at first (100% throttle), then began steep circles at high speed and low altitude. Eventually crashed. I had tried to switch to manual mode on RC TX, but AP did not respond (only after plane was on ground). Probable issues: CLIMB wp alt=25m was too low, climb pitch too low, CLIMB wp too close to launch point (should be at least 200-300m out I think).

	== Airframes ==		== Airframes ==

John Burt: /* Airframes */

2009-03-12T16:44:05Z

Airframes

← Older revision		Revision as of 10:44, 12 March 2009
Line 15:		Line 15:
	I am currently exploring two Multiplex products:		I am currently exploring two Multiplex products:

	~~----~~

John Burt: /* Easystar: */

2009-03-12T16:43:34Z

Easystar:

← Older revision		Revision as of 10:43, 12 March 2009
Line 14:		Line 14:

	I am currently exploring two Multiplex products:		I am currently exploring two Multiplex products:

			----



	----		----
Line 63:		Line 67:

	----		----

	=== Cularis: ===		=== Cularis: ===
	----		----