Replies to This Discussion

3D RoboticsPermalink Reply by Chris Anderson on March 26, 2011 at 10:26am

Rupert:

 

That's very helpful. A few more questions/requests:

 

--Can you please retry the Mission Planner (latest version)? It's been updated and is working well for me. It's also what we recommend and what almost everyone uses, so it's what the code is expecting. The HK GCS can also do mission planning now (they both use the same MAVLink commands), so you could try that. But basically we're only going to support mission planning via MAVLink from now on, and it's the only thing we test and run ourselves.

 

--I assume you've enabled the airspeed sensor in the code and ensured the tubes are plugged in the right way (active at top, if memory serves)

 

--Do you have to reverse your throttle channel? I'm wondering if there's something about the way your radio or ESC handle throttle commands.

• ▶ Reply

Permalink Reply by Rupert Kent on March 27, 2011 at 7:56am

Hi Chris,

 

OK I'm using the MP from this point in. I made another flight today and the problem I was having with the roll limiter in FBW (mentioned in another thread) is solved. Bizarrely, I have done nothing to the airframe not APM. I can only guess I am getting some bizarre compilation / config issues through Arduino, hence I'll go via the MP from this point.

 

Airspeed is inserted in config.h and is working. In fact it's been installed since day 1. Never had any problems there. The a/c maintains cruise airspeed and airspeed in the loiter quite happily. For reference, throttle reversing is not enabled on my Tx, not has it ever been required.

 

Happy to supply config.h or any other data. I just pulled a log down now and am figuring out how to process it. Not done it before...

• ▶ Reply

Permalink Reply by Jimmy P. on March 26, 2011 at 11:12am

I have experienced this w/ MTK16. The alttude was waaay high according to the GCS immdiaely after the GPS locked in from inside the house (it took a while so I know it was having signal issues which is normal from inside on some days. I don't remember if it fixed itself or if I unplugged the lipo battery and pluged it back in. Either way, 5 minutes later, I was getting an accurate reading without flashing th APM.

• ▶ Reply

Permalink Reply by Jimmy P. on March 26, 2011 at 11:18am

Did you flash your APM to 2.0 w/ the planner and go back to 1.x recently by chance? That seemed to do some really weird stuff to my setup. I had to 'reset' via CLI and flash 1.x via Arduino to get it working right again even though APM thought it was working the whole time.

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on March 26, 2011 at 5:59pm

One more thought: can you try doing mission planning from the HK GCS waypoint tab? It does the same things that the Mission Planner does, and if it works there that will help us narrow down the issue.

• ▶ Reply

Permalink Reply by Erik Hatch on March 27, 2011 at 9:15am

chris

i have loaded 2.0 (through the mission planner) to my APM, reset in CLI, and setup the radio and verified mode switch operation. i had to switch the dip switches for the aileron and elevator. gps is at 1.6 version. stabilization mode seems ok on the ground, and im happy to say my altitude look to be correct now. im going to test fly later in the day and i will report back. one last thing, i assume im to use my original apm_config.h file correct?

Thanks

Erik

• ▶ Reply

Permalink Reply by Erik Hatch on March 27, 2011 at 5:42pm

chris

test flew the plane. i was very happy when i went to RTL mode. the plane held perfect altitude, and began to circle. i actually let it fly hands off for about 10 laps. the pattern was not circular i think due to the winds. 15 to 20 mph winds out here. the apm also made throttle adjustments while loitering. i was amazed! anyway, now to fly a programmed mission. i think 2.0 was the key. no issues to report.

Erik

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on March 27, 2011 at 5:45pm

Sweet! Thanks for the update--please let us know how programmed missions go.

• ▶ Reply

Permalink Reply by Erik Hatch on March 27, 2011 at 9:16am

chris

i have loaded 2.0 (through the mission planner) to my APM, reset in CLI, and setup the radio and verified mode switch operation. i had to switch the dip switches for the aileron and elevator. gps is at 1.6 version. stabilization mode seems ok on the ground, and im happy to say my altitude look to be correct now. im going to test fly later in the day and i will report back. one last thing, i assume im to use my original apm_config.h file correct?

Thanks

Erik

• ▶ Reply

Permalink Reply by Erik Hatch on March 26, 2011 at 10:31am

i retraced some of my steps too. i also noticed that my stabilize mode is not working. i switch to stabilize and the servos throw to max. the only thing i changed was added the battery monitoring code. so i commented out the battery monitoring code and reset and reloaded. now stabilize works. i switch to RTL and the plane throttles up while on the ground. its too windy to fly so i will report back later. maybe my post will have a clue to the problem.
Thanks

Erik

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on March 26, 2011 at 10:37am

Erik, make sure you're using the latest code, reset your board via the CLI and reset your radio calibration.

• ▶ Reply

Permalink Reply by Erik Hatch on March 26, 2011 at 10:54am

You mean you want me to try the 2.0 beta? im using 1.02 rite now. i was going to go to 2.0 after beta. let me know and i will give it a go.

 

However, i have reset via cli and reloaded the board 2 times. still have my gps logs saying im about 1800 meters too high.

 

Erik

• ▶ Reply

• ‹ Previous
• 1
• 2
• 3
• 4
• Next ›
• Page