Firmware Update Only Works For Planes, Not Copters.

[stevec5000]

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

[DonLakeFlyer]

Sounds more like a firmware problem than a QGroundControl problem. There isn’t any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 notifications@github.com wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

— Reply to this email directly or view it on GitHub.

[stevec5000]

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne notifications@github.com wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 notifications@github.com wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110 .

[DonLakeFlyer]

I’m a bit confused as to what exactly you are doing. You can’t mix usage of APM Planner/Mission Planner with QGroundControl. APM Planner/Mission Planner use the APM Firmware. QGroundControl uses the PX4FMU firmware. In general if you are using APM Firmware on a Pixhawk you use either APM Planner or Mission Planner. If you are using PX4FMU Firmware on a Pixhawk you use QGroundControl.

On Aug 20, 2014, at 3:04 PM, stevec5000 notifications@github.com wrote:

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne notifications@github.com wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 notifications@github.com wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110 .

— Reply to this email directly or view it on GitHub.

[stevec5000]

I'm just trying to get it to work for the first time to use with a quadcopter and it turns out that I can mix firmware, at least for the plane. So far all I have is the PX4 connected with a USB cable to a Windows laptop. I tried Qground first for the copter because that's what Pixhawk recommends but when that didn't work I tried MP and then APM-P too. If I update the firmware in Qground for an ArduPlane, the only craft that seems to work, I can then also use it in APM-P or MP and it works there too! The other 2 programs, APM-P and MP can't update the board for anything at all! However I don't have a plane and want the PX4 to work for a copter but none of the 3 programs will work for that so how do I fix that problem and get the PX4 to work for copters? Is there any way to tell what firmware is installed on the PX4 or what kind of craft it is configured for by looking at any of the programs? There doesn't seem to be any display of what kind of craft it is controlling which seems to be a serious omission.

On Wed, Aug 20, 2014 at 8:33 PM, Don Gagne notifications@github.com wrote:

I'm a bit confused as to what exactly you are doing. You can't mix usage of APM Planner/Mission Planner with QGroundControl. APM Planner/Mission Planner use the APM Firmware. QGroundControl uses the PX4FMU firmware. In general if you are using APM Firmware on a Pixhawk you use either APM Planner or Mission Planner. If you are using PX4FMU Firmware on a Pixhawk you use QGroundControl.

On Aug 20, 2014, at 3:04 PM, stevec5000 notifications@github.com wrote:

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne notifications@github.com wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 notifications@github.com wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52874749 .

[DonLakeFlyer]

Still don’t understand how you are flashing ArduPlane firmware using QGroundControl. I don’t see how that is possible. The steps should be:

• Boot QGC - connect to your board
• Vehicle Setup / Firmware Upgrade which only give you the option to install PX4FMU firmware. Select stable, then click Upgrade.
• Vehicle Setup / Airframe Config - Select the airframe that matches what you have
• Then work your way through Sensor and Radio Calibration

In order to

On Aug 20, 2014, at 9:19 PM, stevec5000 notifications@github.com wrote:

I'm just trying to get it to work for the first time to use with a quadcopter and it turns out that I can mix firmware, at least for the plane. So far all I have is the PX4 connected with a USB cable to a Windows laptop. I tried Qground first for the copter because that's what Pixhawk recommends but when that didn't work I tried MP and then APM-P too. If I update the firmware in Qground for an ArduPlane, the only craft that seems to work, I can then also use it in APM-P or MP and it works there too! The other 2 programs, APM-P and MP can't update the board for anything at all! However I don't have a plane and want the PX4 to work for a copter but none of the 3 programs will work for that so how do I fix that problem and get the PX4 to work for copters? Is there any way to tell what firmware is installed on the PX4 or what kind of craft it is configured for by looking at any of the programs? There doesn't seem to be any display of what kind of craft it is controlling which seems to be a serious omission.

On Wed, Aug 20, 2014 at 8:33 PM, Don Gagne notifications@github.com wrote:

I'm a bit confused as to what exactly you are doing. You can't mix usage of APM Planner/Mission Planner with QGroundControl. APM Planner/Mission Planner use the APM Firmware. QGroundControl uses the PX4FMU firmware. In general if you are using APM Firmware on a Pixhawk you use either APM Planner or Mission Planner. If you are using PX4FMU Firmware on a Pixhawk you use QGroundControl.

On Aug 20, 2014, at 3:04 PM, stevec5000 notifications@github.com wrote:

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne notifications@github.com wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 notifications@github.com wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52874749 .

— Reply to this email directly or view it on GitHub.

[stevec5000]

It's simple, just do the first 3 steps. Well, not really that easy since it tends to fail about 40 times before it ever does the upgrade and then connects but eventually it works!

On Wed, Aug 20, 2014 at 9:38 PM, Don Gagne notifications@github.com wrote:

Still don't understand how you are flashing ArduPlane firmware using QGroundControl. I don't see how that is possible. The steps should be:

• Boot QGC - connect to your board
• Vehicle Setup / Firmware Upgrade which only give you the option to install PX4FMU firmware. Select stable, then click Upgrade.
• Vehicle Setup / Airframe Config - Select the airframe that matches what you have
• Then work your way through Sensor and Radio Calibration

In order to

On Aug 20, 2014, at 9:19 PM, stevec5000 notifications@github.com wrote:

I'm just trying to get it to work for the first time to use with a quadcopter and it turns out that I can mix firmware, at least for the plane. So far all I have is the PX4 connected with a USB cable to a Windows laptop. I tried Qground first for the copter because that's what Pixhawk recommends but when that didn't work I tried MP and then APM-P too. If I update the firmware in Qground for an ArduPlane, the only craft that seems to work, I can then also use it in APM-P or MP and it works there too! The other 2 programs, APM-P and MP can't update the board for anything at all! However I don't have a plane and want the PX4 to work for a copter but none of the 3 programs will work for that so how do I fix that problem and get the PX4 to work for copters? Is there any way to tell what firmware is installed on the PX4 or what kind of craft it is configured for by looking at any of the programs? There doesn't seem to be any display of what kind of craft it is controlling which seems to be a serious omission.

On Wed, Aug 20, 2014 at 8:33 PM, Don Gagne notifications@github.com wrote:

I'm a bit confused as to what exactly you are doing. You can't mix usage of APM Planner/Mission Planner with QGroundControl. APM Planner/Mission Planner use the APM Firmware. QGroundControl uses the PX4FMU firmware. In general if you are using APM Firmware on a Pixhawk you use either APM Planner or Mission Planner. If you are using PX4FMU Firmware on a Pixhawk you use QGroundControl.

On Aug 20, 2014, at 3:04 PM, stevec5000 notifications@github.com wrote:

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne < notifications@github.com> wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 notifications@github.com

wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52874749>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52877863 .

[DonLakeFlyer]

Those steps do not flash ArduPlane firmware onto the board. They flash the PX4FMU firmware onto the board which is a completely different thing. If you are new to this whole thing and want to set up a quad or the like then I would recommend Mission Planner plus the APM Copter firmware. At this point that combination is more user friendly to people just starting out since there is more mature documentation on the 3drobotics.com site. QGroundControl is catching up, but not there yet for people just getting started.

To hopefully clear things up firmware for the PX4 comes from two different sources:

• 3D Robotics and the whole APM line of things (APM Copter, APM Plane, …) - this will only work correctly with Mission Planner or APM Planner
• pixhawk.org which has the PX4FMU version of the firmware - this will only work with QGroundControl.

On Aug 20, 2014, at 9:53 PM, stevec5000 notifications@github.com wrote:

It's simple, just do the first 3 steps. Well, not really that easy since it tends to fail about 40 times before it ever does the upgrade and then connects but eventually it works!

On Wed, Aug 20, 2014 at 9:38 PM, Don Gagne notifications@github.com wrote:

Still don't understand how you are flashing ArduPlane firmware using QGroundControl. I don't see how that is possible. The steps should be:

• Boot QGC - connect to your board
• Vehicle Setup / Firmware Upgrade which only give you the option to install PX4FMU firmware. Select stable, then click Upgrade.
• Vehicle Setup / Airframe Config - Select the airframe that matches what you have
• Then work your way through Sensor and Radio Calibration

In order to

On Aug 20, 2014, at 9:19 PM, stevec5000 notifications@github.com wrote:

I'm just trying to get it to work for the first time to use with a quadcopter and it turns out that I can mix firmware, at least for the plane. So far all I have is the PX4 connected with a USB cable to a Windows laptop. I tried Qground first for the copter because that's what Pixhawk recommends but when that didn't work I tried MP and then APM-P too. If I update the firmware in Qground for an ArduPlane, the only craft that seems to work, I can then also use it in APM-P or MP and it works there too! The other 2 programs, APM-P and MP can't update the board for anything at all! However I don't have a plane and want the PX4 to work for a copter but none of the 3 programs will work for that so how do I fix that problem and get the PX4 to work for copters? Is there any way to tell what firmware is installed on the PX4 or what kind of craft it is configured for by looking at any of the programs? There doesn't seem to be any display of what kind of craft it is controlling which seems to be a serious omission.

On Wed, Aug 20, 2014 at 8:33 PM, Don Gagne notifications@github.com wrote:

I'm a bit confused as to what exactly you are doing. You can't mix usage of APM Planner/Mission Planner with QGroundControl. APM Planner/Mission Planner use the APM Firmware. QGroundControl uses the PX4FMU firmware. In general if you are using APM Firmware on a Pixhawk you use either APM Planner or Mission Planner. If you are using PX4FMU Firmware on a Pixhawk you use QGroundControl.

On Aug 20, 2014, at 3:04 PM, stevec5000 notifications@github.com wrote:

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne < notifications@github.com> wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 notifications@github.com

wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52874749>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52877863 .

— Reply to this email directly or view it on GitHub.

[stevec5000]

I though it might be different and not work either but all 3 programs seem to have copied each other and they all use Navlink so it all works together. You should just try it instead of continuing to argue about it. Anyway, to get back to the original subject, why doesn't Qground work for anything but a Plane and how can that be fixed?

On Wed, Aug 20, 2014 at 10:10 PM, Don Gagne notifications@github.com wrote:

Those steps do not flash ArduPlane firmware onto the board. They flash the PX4FMU firmware onto the board which is a completely different thing. If you are new to this whole thing and want to set up a quad or the like then I would recommend Mission Planner plus the APM Copter firmware. At this point that combination is more user friendly to people just starting out since there is more mature documentation on the 3drobotics.com site. QGroundControl is catching up, but not there yet for people just getting started.

To hopefully clear things up firmware for the PX4 comes from two different sources:

• 3D Robotics and the whole APM line of things (APM Copter, APM Plane, ...)
• this will only work correctly with Mission Planner or APM Planner
• pixhawk.org which has the PX4FMU version of the firmware - this will only work with QGroundControl.

On Aug 20, 2014, at 9:53 PM, stevec5000 notifications@github.com wrote:

It's simple, just do the first 3 steps. Well, not really that easy since it tends to fail about 40 times before it ever does the upgrade and then connects but eventually it works!

On Wed, Aug 20, 2014 at 9:38 PM, Don Gagne notifications@github.com wrote:

Still don't understand how you are flashing ArduPlane firmware using QGroundControl. I don't see how that is possible. The steps should be:

• Boot QGC - connect to your board
• Vehicle Setup / Firmware Upgrade which only give you the option to install PX4FMU firmware. Select stable, then click Upgrade.
• Vehicle Setup / Airframe Config - Select the airframe that matches what you have
• Then work your way through Sensor and Radio Calibration

In order to

On Aug 20, 2014, at 9:19 PM, stevec5000 notifications@github.com wrote:

I'm just trying to get it to work for the first time to use with a quadcopter and it turns out that I can mix firmware, at least for the plane. So far all I have is the PX4 connected with a USB cable to a Windows laptop. I tried Qground first for the copter because that's what Pixhawk recommends but when that didn't work I tried MP and then APM-P too. If I update the firmware in Qground for an ArduPlane, the only craft that seems to work, I can then also use it in APM-P or MP and it works there too! The other 2 programs, APM-P and MP can't update the board for anything at all! However I don't have a plane and want the PX4 to work for a copter but none of the 3 programs will work for that so how do I fix that problem and get the PX4 to work for copters? Is there any way to tell what firmware is installed on the PX4 or what kind of craft it is configured for by looking at any of the programs? There doesn't seem to be any display of what kind of craft it is controlling which seems to be a serious omission.

On Wed, Aug 20, 2014 at 8:33 PM, Don Gagne notifications@github.com

wrote:

I'm a bit confused as to what exactly you are doing. You can't mix usage of APM Planner/Mission Planner with QGroundControl. APM Planner/Mission Planner use the APM Firmware. QGroundControl uses the PX4FMU firmware. In general if you are using APM Firmware on a Pixhawk you use either APM Planner or Mission Planner. If you are using PX4FMU Firmware on a Pixhawk you use QGroundControl.

On Aug 20, 2014, at 3:04 PM, stevec5000 notifications@github.com

wrote:

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne < notifications@github.com> wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 < notifications@github.com>

wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52874749>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52877863>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52879160 .

[DonLakeFlyer]

I’m not arguing. I’m trying to keep you from crashing hundred’s of dollars of equipment into the ground. As someone that has worked in the source code for QGgroundControl and APM Planner as well as the source code for both sets of firmware, please take my word for it. It may seem like it works, but it doesn’t.

As far as QGroundControl only goes: Send me the exact steps you are using and what goes wrong and I’ll try to help you out, or if there is a bug fix it.

On Aug 21, 2014, at 12:15 AM, stevec5000 notifications@github.com wrote:

I though it might be different and not work either but all 3 programs seem to have copied each other and they all use Navlink so it all works together. You should just try it instead of continuing to argue about it. Anyway, to get back to the original subject, why doesn't Qground work for anything but a Plane and how can that be fixed?

On Wed, Aug 20, 2014 at 10:10 PM, Don Gagne notifications@github.com wrote:

Those steps do not flash ArduPlane firmware onto the board. They flash the PX4FMU firmware onto the board which is a completely different thing. If you are new to this whole thing and want to set up a quad or the like then I would recommend Mission Planner plus the APM Copter firmware. At this point that combination is more user friendly to people just starting out since there is more mature documentation on the 3drobotics.com site. QGroundControl is catching up, but not there yet for people just getting started.

To hopefully clear things up firmware for the PX4 comes from two different sources:

• 3D Robotics and the whole APM line of things (APM Copter, APM Plane, ...)
• this will only work correctly with Mission Planner or APM Planner
• pixhawk.org which has the PX4FMU version of the firmware - this will only work with QGroundControl.

On Aug 20, 2014, at 9:53 PM, stevec5000 notifications@github.com wrote:

It's simple, just do the first 3 steps. Well, not really that easy since it tends to fail about 40 times before it ever does the upgrade and then connects but eventually it works!

On Wed, Aug 20, 2014 at 9:38 PM, Don Gagne notifications@github.com wrote:

Still don't understand how you are flashing ArduPlane firmware using QGroundControl. I don't see how that is possible. The steps should be:

• Boot QGC - connect to your board
• Vehicle Setup / Firmware Upgrade which only give you the option to install PX4FMU firmware. Select stable, then click Upgrade.
• Vehicle Setup / Airframe Config - Select the airframe that matches what you have
• Then work your way through Sensor and Radio Calibration

In order to

On Aug 20, 2014, at 9:19 PM, stevec5000 notifications@github.com wrote:

I'm just trying to get it to work for the first time to use with a quadcopter and it turns out that I can mix firmware, at least for the plane. So far all I have is the PX4 connected with a USB cable to a Windows laptop. I tried Qground first for the copter because that's what Pixhawk recommends but when that didn't work I tried MP and then APM-P too. If I update the firmware in Qground for an ArduPlane, the only craft that seems to work, I can then also use it in APM-P or MP and it works there too! The other 2 programs, APM-P and MP can't update the board for anything at all! However I don't have a plane and want the PX4 to work for a copter but none of the 3 programs will work for that so how do I fix that problem and get the PX4 to work for copters? Is there any way to tell what firmware is installed on the PX4 or what kind of craft it is configured for by looking at any of the programs? There doesn't seem to be any display of what kind of craft it is controlling which seems to be a serious omission.

On Wed, Aug 20, 2014 at 8:33 PM, Don Gagne notifications@github.com

wrote:

I'm a bit confused as to what exactly you are doing. You can't mix usage of APM Planner/Mission Planner with QGroundControl. APM Planner/Mission Planner use the APM Firmware. QGroundControl uses the PX4FMU firmware. In general if you are using APM Firmware on a Pixhawk you use either APM Planner or Mission Planner. If you are using PX4FMU Firmware on a Pixhawk you use QGroundControl.

On Aug 20, 2014, at 3:04 PM, stevec5000 notifications@github.com

wrote:

There must be some difference since it works for a Plane but not for any of the Copters. I can configure the Plane in Qground then it works not only in that but in APM Planner 2.0 and Mission Planner too but only Qground can configure it as a Plane, not the other two, and none of them can configure it as a copter. So, whatever the problem is how do I fix it?

On Wed, Aug 20, 2014 at 11:24 AM, Don Gagne < notifications@github.com> wrote:

Sounds more like a firmware problem than a QGroundControl problem. There isn't any different as to how firmware is flashed based on the Airframe Config you have set.

On Aug 19, 2014, at 9:18 AM, stevec5000 < notifications@github.com>

wrote:

After Qt was fixed in Issue 810 and Firmware Update capability was restored in Issue 822 it still doesn't work properly using Windows 7 on the PX4 for anything but Planes. If I try to update firmware for any of the copters (and the program doesn't crash) it seems to work, says it's erasing the flash, then says it's updating the firmware and seems to finish OK at the end but the blue LED never comes on and it can't connect with the comm port. When the firmware is updated for a Plane it works OK, blue LED comes on and it will connect with the comm port and receive flight data with everything seeming to work even the GPS.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52820110>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52874749>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52877863>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-52879160 .

— Reply to this email directly or view it on GitHub.

[stevec5000]

On Thu, Aug 21, 2014 at 9:24 AM, Don Gagne notifications@github.com wrote:

I'm not arguing. I'm trying to keep you from crashing hundred's of dollars of equipment into the ground. As someone that has worked in the source code for QGgroundControl and APM Planner as well as the source code for both sets of firmware, please take my word for it. It may seem like it works, but it doesn't.

As far as QGroundControl only goes: Send me the exact steps you are using and what goes wrong and I'll try to help you out, or if there is a bug fix it.

I don't have anything to crash yet since I'm just trying to get the PX4 to work. I bought a quadcopter kit but there's no point in even building it if the flight controller can't ever be made to work. I'm basically just trying to follow the Setup Instructions in the Pixhawk Quick Start Guide, rev. 7. The Qground program is so buggy and inconsistent that I get different errors and different results each time but I can usually get down to step 3, loading the firmware and selecting the type of aircraft. I've never been able to do the sensor calibration. Here's the log of what happened this time:

1. Vehicle Setup
2. Firmware Upgrade
3. Clicked Scan

"Detecting boards.. Starting Uploader to read bootloader data Found PX4 board on port COM12 "There is usually a LONG WAIT HERE, sometimes it FREEZES!" [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] bootloader not responding (attempting to reset..) [PX4 Uploader] Attempting reboot.. Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] bad sync 0x21,0x20 [PX4 Uploader] bootloader not responding (attempting to reset..) [PX4 Uploader] Attempting reboot.. Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] synced to bootloader [PX4 Uploader] found bootloader revision: 3 [PX4 Uploader] found board ID: 5 - PX4FMU v1.x [PX4 Uploader] board rev: 0 Board found with ID #5. "Often FREEZES here too!!" Found board with ID #5 Downloading firmware file http://px4.oznet.ch/stable/px4fmu-v1_default.px4 Attempting to upload file: C:/Users/stevec/Downloads/px4fmu-v1_default.px4 Found PX4 board on port COM12 [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] synced to bootloader [PX4 Uploader] decoding JSON (C:/Users/stevec/Downloads/px4fmu-v1_default.px4) [PX4 Uploader] description: Firmware for the PX4FMU board [PX4 Uploader] GIT identity: first_pos_control_flight-5394-ge9b0ee7-dirty [PX4 Uploader] loaded file for board ID 5 [PX4 Uploader] uncompressed image size: 1031744 [PX4 Uploader] firmware size: 1031744 bytes, expected 1031744 bytes [PX4 Uploader] using firmware from C:/Users/stevec/Downloads/px4fmu-v1_default.px4 [PX4 Uploader] found bootloader revision: 3 [PX4 Uploader] found board ID: 5 - PX4FMU v1.x [PX4 Uploader] board rev: 0 [PX4 Uploader] flash size: 1032192 bytes ( 1.0 MiB) [PX4 Uploader] erase... [PX4 Uploader] programming 1031744 bytes... [PX4 Uploader] verify... [PX4 Uploader] update complete (time: 40.91 s) Upload succeeded."

After this last step is finished it usually FREEZES and the Air Frame Config never comes READY! This time however Air Frame Config was ready, Selected Hexacopter, Apply, Reset, Selected Sensor Calib, Error Message says ALL DATA LINKS LOST, Green Connect button at top right DISAPPEARED off the screen! At this point can't go any farther.

[DonLakeFlyer]

Ok, I can repro all sorts of nasty things. The Windows build seems to be quite the basket case right now. I’ll try to see what I can do.

On Aug 21, 2014, at 10:56 AM, stevec5000 notifications@github.com wrote:

On Thu, Aug 21, 2014 at 9:24 AM, Don Gagne notifications@github.com wrote:

I'm not arguing. I'm trying to keep you from crashing hundred's of dollars of equipment into the ground. As someone that has worked in the source code for QGgroundControl and APM Planner as well as the source code for both sets of firmware, please take my word for it. It may seem like it works, but it doesn't.

As far as QGroundControl only goes: Send me the exact steps you are using and what goes wrong and I'll try to help you out, or if there is a bug fix it.

I don't have anything to crash yet since I'm just trying to get the PX4 to work. I bought a quadcopter kit but there's no point in even building it if the flight controller can't ever be made to work. I'm basically just trying to follow the Setup Instructions in the Pixhawk Quick Start Guide, rev. 7. The Qground program is so buggy and inconsistent that I get different errors and different results each time but I can usually get down to step 3, loading the firmware and selecting the type of aircraft. I've never been able to do the sensor calibration. Here's the log of what happened this time:

1. Vehicle Setup
2. Firmware Upgrade
3. Clicked Scan

"Detecting boards.. Starting Uploader to read bootloader data Found PX4 board on port COM12 "There is usually a LONG WAIT HERE, sometimes it FREEZES!" [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] bootloader not responding (attempting to reset..) [PX4 Uploader] Attempting reboot.. Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] could not open interface Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] bad sync 0x21,0x20 [PX4 Uploader] bootloader not responding (attempting to reset..) [PX4 Uploader] Attempting reboot.. Starting Uploader to read bootloader data Found PX4 board on port COM12 [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] synced to bootloader [PX4 Uploader] found bootloader revision: 3 [PX4 Uploader] found board ID: 5 - PX4FMU v1.x [PX4 Uploader] board rev: 0 Board found with ID #5. "Often FREEZES here too!!" Found board with ID #5 Downloading firmware file http://px4.oznet.ch/stable/px4fmu-v1_default.px4 Attempting to upload file: C:/Users/stevec/Downloads/px4fmu-v1_default.px4 Found PX4 board on port COM12 [PX4 Uploader] scanning for bootloader.. [PX4 Uploader] synced to bootloader [PX4 Uploader] decoding JSON (C:/Users/stevec/Downloads/px4fmu-v1_default.px4) [PX4 Uploader] description: Firmware for the PX4FMU board [PX4 Uploader] GIT identity: first_pos_control_flight-5394-ge9b0ee7-dirty [PX4 Uploader] loaded file for board ID 5 [PX4 Uploader] uncompressed image size: 1031744 [PX4 Uploader] firmware size: 1031744 bytes, expected 1031744 bytes [PX4 Uploader] using firmware from C:/Users/stevec/Downloads/px4fmu-v1_default.px4 [PX4 Uploader] found bootloader revision: 3 [PX4 Uploader] found board ID: 5 - PX4FMU v1.x [PX4 Uploader] board rev: 0 [PX4 Uploader] flash size: 1032192 bytes ( 1.0 MiB) [PX4 Uploader] erase... [PX4 Uploader] programming 1031744 bytes... [PX4 Uploader] verify... [PX4 Uploader] update complete (time: 40.91 s) Upload succeeded."

After this last step is finished it usually FREEZES and the Air Frame Config never comes READY! This time however Air Frame Config was ready, Selected Hexacopter, Apply, Reset, Selected Sensor Calib, Error Message says ALL DATA LINKS LOST, Green Connect button at top right DISAPPEARED off the screen! At this point can't go any farther. — Reply to this email directly or view it on GitHub.

[DonLakeFlyer]

It looks like one problem is that on Windows (only?) QObject::connect is not using a Qt::QueuedConnection when the emitter and receiver are on different threads, and instead calling the signal direct which in turn causes a assert/crash. Need to build my own Qt5 windows debug version to trace through the Qt code. Possible cause is an unregistered MetaType. But I'm not seeing any debug output to that affect. What fun!

[DonLakeFlyer]

The firmware crash is caused by using delete on the Socket in UDPLink instead of deleteLater. This causes the delete to happen on the wrong thread. Looks like the way to get clean with these issues is to run with QT_FATAL_WARNINGS environment variable set so that you can't ignore the debug warnings that are output. I'm working on cleaning this up, then I'll run TeamCity unit test builds this way as a starting point to not letting these creep back in.

[LorenzMeier]

@DonLakeFlyer This is extremely appreciated!

[DonLakeFlyer]

FYI: The problems are not Windows only. It's just that windows version of Qt5 tends to crash out when it hits them. Where for example OSX just keep plodding along likely causing many small to large issues.

[DonLakeFlyer]

@stevec5000 New builds are posted to: http://www.qgroundcontrol.org/downloads. Please give this a try to see if it is any better. Report back any problems.

[stevec5000]

Thanks for the update. Just wondering though, isn't there an older version that used to work OK? What caused all the problems recently?

On Sat, Aug 23, 2014 at 10:16 AM, Don Gagne notifications@github.com wrote:

@stevec5000 https://github.com/stevec5000 New builds are posted to: http://www.qgroundcontrol.org/downloads. Please give this a try to see if it is any better. Report back any problems.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53159191 .

[stevec5000]

Also, this would be easier to keep straight if all the files didn't have the same name. Maybe the revision could be incorporated into the file name?

On Mon, Aug 25, 2014 at 9:20 AM, steve c stevec5000@gmail.com wrote:

Thanks for the update. Just wondering though, isn't there an older version that used to work OK? What caused all the problems recently?

On Sat, Aug 23, 2014 at 10:16 AM, Don Gagne notifications@github.com wrote:

@stevec5000 https://github.com/stevec5000 New builds are posted to: http://www.qgroundcontrol.org/downloads. Please give this a try to see if it is any better. Report back any problems.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53159191 .

[DonLakeFlyer]

Yes these are all new problems. Unfortunately the older more stable build was towed before it was known these existed. Two major changes happened in the last few weeks:

1) We moved from Qt4 to Qt5 2) Many object were moved to there own threads to improve ui responsiveness

The codebase is still working it’s way through bugs introduced by those changes.

On Aug 25, 2014, at 9:20 AM, stevec5000 notifications@github.com wrote:

Thanks for the update. Just wondering though, isn't there an older version that used to work OK? What caused all the problems recently?

On Sat, Aug 23, 2014 at 10:16 AM, Don Gagne notifications@github.com wrote:

@stevec5000 https://github.com/stevec5000 New builds are posted to: http://www.qgroundcontrol.org/downloads. Please give this a try to see if it is any better. Report back any problems.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53159191 .

— Reply to this email directly or view it on GitHub.

[stevec5000]

I tried out the new version and it's a big improvement! For the first time I was able to configure the PX4 as a quadcopter (I think) and even got as far as calibrating the first 2 sensors but it took several tries. It still works intermittently but I finally got it to work and had the following problems:

1. It still freezes doing Firmware Update after clicking Scan, saying: "Found PX4 board on port Com12" and usually wouldn't go any farther. Sometimes pressing Reset on the PX4 would make it go on and display the box to click update but not always. Sometimes it got an error saying "Wrong Board ID".
2. When doing Airframe Config for copters it sometimes turned the screen White and froze but sometime went on and continued to work.
3. When doing Sensor Calibration it would always do the first 2 but the third one failed when it said "Left:X+X-Y+Y-Z+". Less serious problems but still annoying are:
4. No way to tell what kind of aircraft is configured since it always shows a plane. I think it was set for a quadcopter but not sure.
5. Uninstall doesn't work to remove the older version to try a new one. The program doesn't show up in Windows Uninstall a Program! Going to Start, Programs, in the Qgroundcontrol folder it has an Uninstall option but it doesn't work! There is an Uninstall located in the Program folder on C: that works to delete all the files though.

On Mon, Aug 25, 2014 at 9:25 AM, Don Gagne notifications@github.com wrote:

Yes these are all new problems. Unfortunately the older more stable build was towed before it was known these existed. Two major changes happened in the last few weeks:

1) We moved from Qt4 to Qt5 2) Many object were moved to there own threads to improve ui responsiveness

The codebase is still working it's way through bugs introduced by those changes.

On Aug 25, 2014, at 9:20 AM, stevec5000 notifications@github.com wrote:

Thanks for the update. Just wondering though, isn't there an older version that used to work OK? What caused all the problems recently?

On Sat, Aug 23, 2014 at 10:16 AM, Don Gagne notifications@github.com wrote:

@stevec5000 https://github.com/stevec5000 New builds are posted to: http://www.qgroundcontrol.org/downloads. Please give this a try to see if it is any better. Report back any problems.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53159191>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53287477 .

[DonLakeFlyer]

1 I think this may be a firmware/bootloader problem not QGC

2 At what point?

3 Fail in what way?

4 You can go back to Airframe Config and your selection should be highlighted in blue

5 Yup. Already an Issue open for it.

On Aug 26, 2014, at 7:58 AM, stevec5000 notifications@github.com wrote:

I tried out the new version and it's a big improvement! For the first time I was able to configure the PX4 as a quadcopter (I think) and even got as far as calibrating the first 2 sensors but it took several tries. It still works intermittently but I finally got it to work and had the following problems:

1. It still freezes doing Firmware Update after clicking Scan, saying: "Found PX4 board on port Com12" and usually wouldn't go any farther. Sometimes pressing Reset on the PX4 would make it go on and display the box to click update but not always. Sometimes it got an error saying "Wrong Board ID".
2. When doing Airframe Config for copters it sometimes turned the screen White and froze but sometime went on and continued to work.
3. When doing Sensor Calibration it would always do the first 2 but the third one failed when it said "Left:X+X-Y+Y-Z+". Less serious problems but still annoying are:
4. No way to tell what kind of aircraft is configured since it always shows a plane. I think it was set for a quadcopter but not sure.
5. Uninstall doesn't work to remove the older version to try a new one. The program doesn't show up in Windows Uninstall a Program! Going to Start, Programs, in the Qgroundcontrol folder it has an Uninstall option but it doesn't work! There is an Uninstall located in the Program folder on C: that works to delete all the files though.

On Mon, Aug 25, 2014 at 9:25 AM, Don Gagne notifications@github.com wrote:

Yes these are all new problems. Unfortunately the older more stable build was towed before it was known these existed. Two major changes happened in the last few weeks:

1) We moved from Qt4 to Qt5 2) Many object were moved to there own threads to improve ui responsiveness

The codebase is still working it's way through bugs introduced by those changes.

On Aug 25, 2014, at 9:20 AM, stevec5000 notifications@github.com wrote:

Thanks for the update. Just wondering though, isn't there an older version that used to work OK? What caused all the problems recently?

On Sat, Aug 23, 2014 at 10:16 AM, Don Gagne notifications@github.com wrote:

@stevec5000 https://github.com/stevec5000 New builds are posted to: http://www.qgroundcontrol.org/downloads. Please give this a try to see if it is any better. Report back any problems.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53159191>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53287477 .

— Reply to this email directly or view it on GitHub.

[DonLakeFlyer]

Also for #3 I assume you talking about Magnetometer calibration?

On Aug 26, 2014, at 9:11 AM, Donald Gagne don@thegagnes.com wrote:

1 I think this may be a firmware/bootloader problem not QGC

2 At what point?

3 Fail in what way?

4 You can go back to Airframe Config and your selection should be highlighted in blue

5 Yup. Already an Issue open for it.

On Aug 26, 2014, at 7:58 AM, stevec5000 notifications@github.com wrote:

I tried out the new version and it's a big improvement! For the first time I was able to configure the PX4 as a quadcopter (I think) and even got as far as calibrating the first 2 sensors but it took several tries. It still works intermittently but I finally got it to work and had the following problems:

1. It still freezes doing Firmware Update after clicking Scan, saying: "Found PX4 board on port Com12" and usually wouldn't go any farther. Sometimes pressing Reset on the PX4 would make it go on and display the box to click update but not always. Sometimes it got an error saying "Wrong Board ID".
2. When doing Airframe Config for copters it sometimes turned the screen White and froze but sometime went on and continued to work.
3. When doing Sensor Calibration it would always do the first 2 but the third one failed when it said "Left:X+X-Y+Y-Z+". Less serious problems but still annoying are:
4. No way to tell what kind of aircraft is configured since it always shows a plane. I think it was set for a quadcopter but not sure.
5. Uninstall doesn't work to remove the older version to try a new one. The program doesn't show up in Windows Uninstall a Program! Going to Start, Programs, in the Qgroundcontrol folder it has an Uninstall option but it doesn't work! There is an Uninstall located in the Program folder on C: that works to delete all the files though.

On Mon, Aug 25, 2014 at 9:25 AM, Don Gagne notifications@github.com wrote:

Yes these are all new problems. Unfortunately the older more stable build was towed before it was known these existed. Two major changes happened in the last few weeks:

1) We moved from Qt4 to Qt5 2) Many object were moved to there own threads to improve ui responsiveness

The codebase is still working it's way through bugs introduced by those changes.

On Aug 25, 2014, at 9:20 AM, stevec5000 notifications@github.com wrote:

Thanks for the update. Just wondering though, isn't there an older version that used to work OK? What caused all the problems recently?

On Sat, Aug 23, 2014 at 10:16 AM, Don Gagne notifications@github.com wrote:

@stevec5000 https://github.com/stevec5000 New builds are posted to: http://www.qgroundcontrol.org/downloads. Please give this a try to see if it is any better. Report back any problems.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53159191>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-53287477 .

— Reply to this email directly or view it on GitHub.

[stevec5000]

1. It still freezes doing Firmware Update after clicking Scan, saying: "Found PX4 board on port Com12" and usually wouldn't go any farther. Sometimes pressing Reset on the PX4 would make it go on and display the box to click update but not always. Sometimes it got an error saying "Wrong Board ID".

1 I think this may be a firmware/bootloader problem not QGC

No, that's the first thing on line 3 in the window and happens before it tries to access or download the firmware. It's not reassuring to know there is one other place to have problems though.

1. When doing Airframe Config for copters it sometimes turned the screen White and froze but sometime went on and continued to work.

2 At what point?

When I first clicked on Airframe Config the screen turned white for almost 10 secs., first time it's done that. Then, after selecting the type of craft and clicking on Reset in the lower right corner it turns white again sometimes.

1. When doing Sensor Calibration it would always do the first 2 but the third one failed when it said "Left:X+X-Y+Y-Z+".

3 I assume you talking about Magnetometer calibration?

No, it's accelerometer calibration on the right that says ":X+X-Y+Y-Z+" I can never find any combination of movements that will satisfy it but I'm not sure what it's asking for, probably not a program problem.

1. No way to tell what kind of aircraft is configured since it always shows a plane. I think it was set for a quadcopter but not sure.

4 You can go back to Airframe Config and your selection should be

highlighted in blue.

Ok, great, it did stay highlighted but since it doesn't indicate it anywhere else I wasn't sure.

1. Uninstall doesn't work to remove the older version to try a new one.

5 Yup. Already an Issue open for it.

6. When I try to do the firmware update manually in Advanced mode it

keeps setting the Com port to Com3 which is very annoying since I don't have a Com3. I noticed that it says something about Com3 in the DOS box when the program is first started by the command line instruction too. Is there a way to remove any references to Com3?

[stevec5000]

I just tried the 9-1-14 release. It seems to work well if the PX4 is already configured but getting it to do a firmware update is still a problem. After clicking Scan it says "Found PX4 on Com 12" but then just sits there for a long time. I tried unplugging the USB cable then resetting the board which gave me a string of messages saying "Could Not Open Interface". After a while it finally did work but the DOS windows had a long string of messages saying "warn: list update" and one that said "Autopilot icon image did not load". I'm not sure if those messages are serious but the program itself ran good this time and never crashed or gave any error messages.

On Wed, Aug 27, 2014 at 11:18 AM, steve c stevec5000@gmail.com wrote:

1. It still freezes doing Firmware Update after clicking Scan, saying: "Found PX4 board on port Com12" and usually wouldn't go any farther. Sometimes pressing Reset on the PX4 would make it go on and display the box to click update but not always. Sometimes it got an error saying "Wrong Board ID".

1 I think this may be a firmware/bootloader problem not QGC

No, that's the first thing on line 3 in the window and happens before it tries to access or download the firmware. It's not reassuring to know there is one other place to have problems though.

1. When doing Airframe Config for copters it sometimes turned the screen White and froze but sometime went on and continued to work.

2 At what point?

When I first clicked on Airframe Config the screen turned white for almost 10 secs., first time it's done that. Then, after selecting the type of craft and clicking on Reset in the lower right corner it turns white again sometimes.

1. When doing Sensor Calibration it would always do the first 2 but the third one failed when it said "Left:X+X-Y+Y-Z+".

3 I assume you talking about Magnetometer calibration?

No, it's accelerometer calibration on the right that says ":X+X-Y+Y-Z+" I can never find any combination of movements that will satisfy it but I'm not sure what it's asking for, probably not a program problem.

1. No way to tell what kind of aircraft is configured since it always shows a plane. I think it was set for a quadcopter but not sure.

4 You can go back to Airframe Config and your selection should be

highlighted in blue.

Ok, great, it did stay highlighted but since it doesn't indicate it anywhere else I wasn't sure.

1. Uninstall doesn't work to remove the older version to try a new one.

5 Yup. Already an Issue open for it.

6. When I try to do the firmware update manually in Advanced mode it keeps

setting the Com port to Com3 which is very annoying since I don't have a Com3. I noticed that it says something about Com3 in the DOS box when the program is first started by the command line instruction too. Is there a way to remove any references to Com3?

[stevec5000]

Tried the 9-3-14 release and there is a big improvement at the beginning! When I clicked Scan it found the PX4 and gave me the Update option right away! Ran into a new problem later on though. When I clicked Airframe Config and selected a Hexcopter and clicked Apply & Restart it didn't work and I got an error saying "Parameter sync with UAS not yet complete". Couldn't go any farther after that. Reset the PX4 and restarted the program but it wouldn't let me get back to the Airframe Config option. I had to do firmware update again but this time I selected the Beta firmware and it worked to let me select the airframe type. That time it worked without an error.

On Tue, Sep 2, 2014 at 7:36 AM, steve c stevec5000@gmail.com wrote:

I just tried the 9-1-14 release. It seems to work well if the PX4 is already configured but getting it to do a firmware update is still a problem. After clicking Scan it says "Found PX4 on Com 12" but then just sits there for a long time. I tried unplugging the USB cable then resetting the board which gave me a string of messages saying "Could Not Open Interface". After a while it finally did work but the DOS windows had a long string of messages saying "warn: list update" and one that said "Autopilot icon image did not load". I'm not sure if those messages are serious but the program itself ran good this time and never crashed or gave any error messages.

On Wed, Aug 27, 2014 at 11:18 AM, steve c stevec5000@gmail.com wrote:

1. It still freezes doing Firmware Update after clicking Scan, saying: "Found PX4 board on port Com12" and usually wouldn't go any farther. Sometimes pressing Reset on the PX4 would make it go on and display the box to click update but not always. Sometimes it got an error saying "Wrong Board ID".

1 I think this may be a firmware/bootloader problem not QGC

No, that's the first thing on line 3 in the window and happens before it tries to access or download the firmware. It's not reassuring to know there is one other place to have problems though.

1. When doing Airframe Config for copters it sometimes turned the screen White and froze but sometime went on and continued to work.

2 At what point?

When I first clicked on Airframe Config the screen turned white for almost 10 secs., first time it's done that. Then, after selecting the type of craft and clicking on Reset in the lower right corner it turns white again sometimes.

1. When doing Sensor Calibration it would always do the first 2 but the third one failed when it said "Left:X+X-Y+Y-Z+".

3 I assume you talking about Magnetometer calibration?

No, it's accelerometer calibration on the right that says ":X+X-Y+Y-Z+" I can never find any combination of movements that will satisfy it but I'm not sure what it's asking for, probably not a program problem.

1. No way to tell what kind of aircraft is configured since it always shows a plane. I think it was set for a quadcopter but not sure.

4 You can go back to Airframe Config and your selection should be

highlighted in blue.

Ok, great, it did stay highlighted but since it doesn't indicate it anywhere else I wasn't sure.

1. Uninstall doesn't work to remove the older version to try a new one.

5 Yup. Already an Issue open for it.

6. When I try to do the firmware update manually in Advanced mode it keeps

setting the Com port to Com3 which is very annoying since I don't have a Com3. I noticed that it says something about Com3 in the DOS box when the program is first started by the command line instruction too. Is there a way to remove any references to Com3?

[stevec5000]

Just tried the 9-15-14 release and updating the firmware on the PX4 and configuring it as a copter all worked perfectly! At the beginning of Firmware update, after finding the PX4, it did take a long time, several minutes, before the Update box popped up but when it did then if finally worked. However, after connecting to the board and selecting Mission, Control, under the wide box: Arm System, if I click Start it gives the message "Unsupported", if I click Land nothing happens but if I click Halt it Crashes the program every time! I was going to do a Mini dump but in Regedit there is no LocalDumps key. Do I have to add that manually then put in the values for DumpFolder, DumpCount, DumpType and CustomDumpFlags?

[DonLakeFlyer]

Yes you are going to have to create the keys yourself. Can you create a full dump setup, then get it to crash, save the file, then you can remove the reg keys.

On Sep 15, 2014, at 9:38 AM, stevec5000 notifications@github.com wrote:

Just tried the 9-15-14 release and updating the firmware on the PX4 and configuring it as a copter all worked perfectly! At the beginning of Firmware update, after finding the PX4, it did take a long time, several minutes, before the Update box popped up but when it did then if finally worked. However, after connecting to the board and selecting Mission, Control, under the wide box: Arm System, if I click Start it gives the message "Unsupported", if I click Land nothing happens but if I click Halt it Crashes the program every time! I was going to do a Mini dump but in Regedit there is no LocalDumps key. Do I have to add that manually then put in the values for DumpFolder, DumpCount, DumpType and CustomDumpFlags?

— Reply to this email directly or view it on GitHub.

[stevec5000]

I created the reg keys and tried it but it didn't save any dump file. Since I'm not a programmer I doubt if I did it right. Hopefully I won't need to use the Arm features.

On Mon, Sep 15, 2014 at 2:56 PM, Don Gagne notifications@github.com wrote:

Yes you are going to have to create the keys yourself. Can you create a full dump setup, then get it to crash, save the file, then you can remove the reg keys.

On Sep 15, 2014, at 9:38 AM, stevec5000 notifications@github.com wrote:

Just tried the 9-15-14 release and updating the firmware on the PX4 and configuring it as a copter all worked perfectly! At the beginning of Firmware update, after finding the PX4, it did take a long time, several minutes, before the Update box popped up but when it did then if finally worked. However, after connecting to the board and selecting Mission, Control, under the wide box: Arm System, if I click Start it gives the message "Unsupported", if I click Land nothing happens but if I click Halt it Crashes the program every time! I was going to do a Mini dump but in Regedit there is no LocalDumps key. Do I have to add that manually then put in the values for DumpFolder, DumpCount, DumpType and CustomDumpFlags?

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-55665338 .

[DonLakeFlyer]

Steve send me your real email address to don@thegagnes.com. I’ll create a .reg file for you to double click to set it up and email to it you.

On Sep 15, 2014, at 3:32 PM, stevec5000 notifications@github.com wrote:

I created the reg keys and tried it but it didn't save any dump file. Since I'm not a programmer I doubt if I did it right. Hopefully I won't need to use the Arm features.

On Mon, Sep 15, 2014 at 2:56 PM, Don Gagne notifications@github.com wrote:

Yes you are going to have to create the keys yourself. Can you create a full dump setup, then get it to crash, save the file, then you can remove the reg keys.

On Sep 15, 2014, at 9:38 AM, stevec5000 notifications@github.com wrote:

Just tried the 9-15-14 release and updating the firmware on the PX4 and configuring it as a copter all worked perfectly! At the beginning of Firmware update, after finding the PX4, it did take a long time, several minutes, before the Update box popped up but when it did then if finally worked. However, after connecting to the board and selecting Mission, Control, under the wide box: Arm System, if I click Start it gives the message "Unsupported", if I click Land nothing happens but if I click Halt it Crashes the program every time! I was going to do a Mini dump but in Regedit there is no LocalDumps key. Do I have to add that manually then put in the values for DumpFolder, DumpCount, DumpType and CustomDumpFlags?

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-55665338 .

— Reply to this email directly or view it on GitHub.

[stevec5000]

I got it to work with directions from here: https://kb.acronis.com/content/38195. Where should I send the dump file?

[DonLakeFlyer]

Crash is fixed with OpenSLL install.

[stevec5000]

Don, even though the program didn't crash it still is really flaky and has a lot of problems and didn't work until after I tried it half a dozen times! Sometimes when I try to do the firmware update it will say it can't find the board or the board has the wrong ID or the file is the wrong type or it will say it found the PX4 but then stop and not go any farther. I finally got it to work but not until I exited and restarted the program, rebooted the PX4 and unplugged the USB cable and plugged it back into the PX4 a few times.

On Sun, Oct 12, 2014 at 11:10 AM, Don Gagne notifications@github.com wrote:

Closed #827 https://github.com/mavlink/qgroundcontrol/issues/827.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#event-177403489.

[DonLakeFlyer]

Yes, I found this as well when I tried it. I haven’t had time to look at it yet. I forgot to open a new issue for just this flakiness. I’ll do that.

On Oct 12, 2014, at 4:30 PM, stevec5000 notifications@github.com wrote:

Don, even though the program didn't crash it still is really flaky and has a lot of problems and didn't work until after I tried it half a dozen times! Sometimes when I try to do the firmware update it will say it can't find the board or the board has the wrong ID or the file is the wrong type or it will say it found the PX4 but then stop and not go any farther. I finally got it to work but not until I exited and restarted the program, rebooted the PX4 and unplugged the USB cable and plugged it back into the PX4 a few times.

On Sun, Oct 12, 2014 at 11:10 AM, Don Gagne notifications@github.com wrote:

Closed #827 https://github.com/mavlink/qgroundcontrol/issues/827.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#event-177403489.

— Reply to this email directly or view it on GitHub.

[DonLakeFlyer]

Issue #893

On Oct 12, 2014, at 6:50 PM, Donald Gagne don@thegagnes.com wrote:

Yes, I found this as well when I tried it. I haven’t had time to look at it yet. I forgot to open a new issue for just this flakiness. I’ll do that.

On Oct 12, 2014, at 4:30 PM, stevec5000 notifications@github.com wrote:

Don, even though the program didn't crash it still is really flaky and has a lot of problems and didn't work until after I tried it half a dozen times! Sometimes when I try to do the firmware update it will say it can't find the board or the board has the wrong ID or the file is the wrong type or it will say it found the PX4 but then stop and not go any farther. I finally got it to work but not until I exited and restarted the program, rebooted the PX4 and unplugged the USB cable and plugged it back into the PX4 a few times.

On Sun, Oct 12, 2014 at 11:10 AM, Don Gagne notifications@github.com wrote:

Closed #827 https://github.com/mavlink/qgroundcontrol/issues/827.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#event-177403489.

— Reply to this email directly or view it on GitHub.

[Rotorbl4de]

After reading what kind of issues stevec5000 was going through, I had experienced these and worked through them, now I want to go back to the APM firmware, is this possible?

I recently built a quad and I swapped the Pixhawk over from a tricopter where I had used APM Mission Planner to configure months ago. After revisiting the Pixhawk information on the web I ended up installing Qgroundcontrol and upgrading my firmware, loading a quad config, successfully went through sensor and radio calibration. I'd like to go back to using the APM Mission Planner 2 instead of the Qgroundcontrol and I am wondering is there a way to use the QGroundcontrol v 2.2.0 stable to load the APM firmware because now the APM Mission Planner doesn't seem to like the Pixhawk FMU firmware?

When I use APM Mission Planner 2 now it gives me a "certificate of authenticity check failed" error and now it thinks my pixhawk is a clone. I am reading up on it for a work around.

I need to spend a night reading up on this. I am confused about APM vs PX4 and need to find the pros and cons. Sorry if this post may belong in another thread!

[stevec5000]

Qgroundcontrol works pretty well now that it's been updated and had lots of bugs fixed doesn't it? Can you tell any difference in one firmware versus the other one? Anyway, it doesn't matter which ground control program you used to configure the quadcopter since after it's configured and calibrated you can just use the remote control to fly it.

On Sat, Dec 13, 2014 at 7:21 PM, Rotorbl4de notifications@github.com wrote:

I have made it through the setup of my Pixhawk a few months ago using APM's Missionplanner and had it working successfully in a tricopter config with flight modes and all calibration working.

I recently built a quad and I swapped the Pixhawk over and I knew I was going to have to change the config and check everything out again in regards to calibration and other settings. Revisiting the Pixhawk information on the web I ended up installing Qgroundcontrol and upgrading my firmware, loading a quad config, going through sensor and radio calibrations just fine.

I got used to the APM Mission Planner and I was wondering if there is a way for me to use the Qgroundcontrol v2.2.0 stable to load the APM firmware so I can go back to using that software?

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66900027 .

[Rotorbl4de]

My issue is resolved, I was able flash firmware and a config onto the copter with APM Planner 2.0. All I had to do was press continue and it uploaded the firmware, I guess I freaked out when I saw the authenticity error check. I figured there was no going back to using the old Mission planner software. I had spent so much time learning and troubleshooting that APM Planner 2 and Qgroundstation felt uncomfortable. I also didn't really realize they all kind of do the same thing.

I had gone into the DJI world for a while with a couple Y6 configs and now I intend to set up the Pixhawk on those builds and to experience the difference in tuning and flying them. I need to knock a bit of rust off now that I am coming back to the the APM and PX4 world.

The issues I had with Qground station was it seemed finicky about upgrading the firmware and there is a song and dance I had to do several times to upgrade the firmware, this is spelled out in the link above Issue #893.

I maidened this 730mm X quad and everything is fine now.

QGroundcontrol looks and seems like great software, I just need to give it a fair chance!

[DonLakeFlyer]

"The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware.”

Can you let us know if that was a recent problem? Or a number of weeks back. The firmware upgrade problem was discovered to be a hardware issue (after much really hard work and diagnosis by multiple people). Firmware upgrade with the latest QGC and latests firmware revs should be very smooth. If it isn’t please let me know. You would have run into exactly the same problem with any of the ground station clients. You would not have run into it with the APM firmware though since the size of that firmware was below the !M mark.

On Dec 13, 2014, at 9:08 PM, Rotorbl4de notifications@github.com wrote:

My issue resolved, I was able flash firmware and a config onto the copter with APM Planner 2.0.

The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware. I am also unfamiliar with Qround Control V2.2.0 and that is really the only issue I have with the software and I will definitely give it more of a try now that I am back to flying my Pixhawk. I had gone into the DJI world the last few months with a couple Y6 configs and I intend to set up the Pixhawk on those and experience the difference in tuning and flying.

With APM Planner all I had to do was press continue and it uploaded the firmware, I guess I freaked out when I saw the authenticity error check and figured there was no going back and that being able to use the old mission planner software was out of the question, but that isn't the cast. I flashed the firmware with APM Planner 2.0 and again felt a little unfamiliar and uncomfortable with that software so I went back to the older Mission planner software and everything is good. Telemetry radios work, all bells and whistles where I remembered.

I just maidened this 730mm X quad and now that I know it hovers well, 25 minutes with a 500 gram payload I will get back into Pixhawk mood and do more reading before I post.

QGroundcontrol looks and seems like great software, I just need to give it a fair chance!

— Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66903127.

[stevec5000]

Don, is there a hardware problem that needs to be fixed? I don't know about his problem but the last release I tried worked fine to upgrade the firmware.

On Sun, Dec 14, 2014 at 5:33 PM, Don Gagne notifications@github.com wrote:

"The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware."

Can you let us know if that was a recent problem? Or a number of weeks back. The firmware upgrade problem was discovered to be a hardware issue (after much really hard work and diagnosis by multiple people). Firmware upgrade with the latest QGC and latests firmware revs should be very smooth. If it isn't please let me know. You would have run into exactly the same problem with any of the ground station clients. You would not have run into it with the APM firmware though since the size of that firmware was below the !M mark.

On Dec 13, 2014, at 9:08 PM, Rotorbl4de notifications@github.com wrote:

My issue resolved, I was able flash firmware and a config onto the copter with APM Planner 2.0.

The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware. I am also unfamiliar with Qround Control V2.2.0 and that is really the only issue I have with the software and I will definitely give it more of a try now that I am back to flying my Pixhawk. I had gone into the DJI world the last few months with a couple Y6 configs and I intend to set up the Pixhawk on those and experience the difference in tuning and flying.

With APM Planner all I had to do was press continue and it uploaded the firmware, I guess I freaked out when I saw the authenticity error check and figured there was no going back and that being able to use the old mission planner software was out of the question, but that isn't the cast. I flashed the firmware with APM Planner 2.0 and again felt a little unfamiliar and uncomfortable with that software so I went back to the older Mission planner software and everything is good. Telemetry radios work, all bells and whistles where I remembered.

I just maidened this 730mm X quad and now that I know it hovers well, 25 minutes with a 500 gram payload I will get back into Pixhawk mood and do more reading before I post.

QGroundcontrol looks and seems like great software, I just need to give it a fair chance!

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66903127>.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66937715 .

[DonLakeFlyer]

It’s only an issue if the firmware size goes over the 1Meg mark. Once that was discovered, changes were made to reduce the px4fmu firmware size to below 1Meg. So at this point there is no longer a problem.

On Dec 14, 2014, at 4:55 PM, stevec5000 notifications@github.com wrote:

Don, is there a hardware problem that needs to be fixed? I don't know about his problem but the last release I tried worked fine to upgrade the firmware.

On Sun, Dec 14, 2014 at 5:33 PM, Don Gagne notifications@github.com wrote:

"The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware."

Can you let us know if that was a recent problem? Or a number of weeks back. The firmware upgrade problem was discovered to be a hardware issue (after much really hard work and diagnosis by multiple people). Firmware upgrade with the latest QGC and latests firmware revs should be very smooth. If it isn't please let me know. You would have run into exactly the same problem with any of the ground station clients. You would not have run into it with the APM firmware though since the size of that firmware was below the !M mark.

On Dec 13, 2014, at 9:08 PM, Rotorbl4de notifications@github.com wrote:

My issue resolved, I was able flash firmware and a config onto the copter with APM Planner 2.0.

The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware. I am also unfamiliar with Qround Control V2.2.0 and that is really the only issue I have with the software and I will definitely give it more of a try now that I am back to flying my Pixhawk. I had gone into the DJI world the last few months with a couple Y6 configs and I intend to set up the Pixhawk on those and experience the difference in tuning and flying.

With APM Planner all I had to do was press continue and it uploaded the firmware, I guess I freaked out when I saw the authenticity error check and figured there was no going back and that being able to use the old mission planner software was out of the question, but that isn't the cast. I flashed the firmware with APM Planner 2.0 and again felt a little unfamiliar and uncomfortable with that software so I went back to the older Mission planner software and everything is good. Telemetry radios work, all bells and whistles where I remembered.

I just maidened this 730mm X quad and now that I know it hovers well, 25 minutes with a 500 gram payload I will get back into Pixhawk mood and do more reading before I post.

QGroundcontrol looks and seems like great software, I just need to give it a fair chance!

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66903127>.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66937715 .

— Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66938476.

[stevec5000]

Since I have a ver. 1.7 PX4 with only 1Meg of memory, is that why all the other programs like Mission Planner and APM Planner won't work?

On Sun, Dec 14, 2014 at 5:59 PM, Don Gagne notifications@github.com wrote:

It's only an issue if the firmware size goes over the 1Meg mark. Once that was discovered, changes were made to reduce the px4fmu firmware size to below 1Meg. So at this point there is no longer a problem.

On Dec 14, 2014, at 4:55 PM, stevec5000 notifications@github.com wrote:

Don, is there a hardware problem that needs to be fixed? I don't know about his problem but the last release I tried worked fine to upgrade the firmware.

On Sun, Dec 14, 2014 at 5:33 PM, Don Gagne notifications@github.com wrote:

"The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware."

Can you let us know if that was a recent problem? Or a number of weeks back. The firmware upgrade problem was discovered to be a hardware issue (after much really hard work and diagnosis by multiple people). Firmware upgrade with the latest QGC and latests firmware revs should be very smooth. If it isn't please let me know. You would have run into exactly the same problem with any of the ground station clients. You would not have run into it with the APM firmware though since the size of that firmware was below the !M mark.

On Dec 13, 2014, at 9:08 PM, Rotorbl4de notifications@github.com wrote:

My issue resolved, I was able flash firmware and a config onto the copter with APM Planner 2.0.

The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware. I am also unfamiliar with Qround Control V2.2.0 and that is really the only issue I have with the software and I will definitely give it more of a try now that I am back to flying my Pixhawk. I had gone into the DJI world the last few months with a couple Y6 configs and I intend to set up the Pixhawk on those and experience the difference in tuning and flying.

With APM Planner all I had to do was press continue and it uploaded the firmware, I guess I freaked out when I saw the authenticity error check and figured there was no going back and that being able to use the old mission planner software was out of the question, but that isn't the cast. I flashed the firmware with APM Planner 2.0 and again felt a little unfamiliar and uncomfortable with that software so I went back to the older Mission planner software and everything is good. Telemetry radios work, all bells and whistles where I remembered.

I just maidened this 730mm X quad and now that I know it hovers well, 25 minutes with a 500 gram payload I will get back into Pixhawk mood and do more reading before I post.

QGroundcontrol looks and seems like great software, I just need to give it a fair chance!

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66903127>.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66937715>

.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66938476>.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66938616 .

[DonLakeFlyer]

They should be fine.

On Dec 26, 2014, at 5:15 AM, stevec5000 notifications@github.com wrote:

Since I have a ver. 1.7 PX4 with only 1Meg of memory, is that why all the other programs like Mission Planner and APM Planner won't work?

On Sun, Dec 14, 2014 at 5:59 PM, Don Gagne notifications@github.com wrote:

It's only an issue if the firmware size goes over the 1Meg mark. Once that was discovered, changes were made to reduce the px4fmu firmware size to below 1Meg. So at this point there is no longer a problem.

On Dec 14, 2014, at 4:55 PM, stevec5000 notifications@github.com wrote:

Don, is there a hardware problem that needs to be fixed? I don't know about his problem but the last release I tried worked fine to upgrade the firmware.

On Sun, Dec 14, 2014 at 5:33 PM, Don Gagne notifications@github.com wrote:

"The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware."

Can you let us know if that was a recent problem? Or a number of weeks back. The firmware upgrade problem was discovered to be a hardware issue (after much really hard work and diagnosis by multiple people). Firmware upgrade with the latest QGC and latests firmware revs should be very smooth. If it isn't please let me know. You would have run into exactly the same problem with any of the ground station clients. You would not have run into it with the APM firmware though since the size of that firmware was below the !M mark.

On Dec 13, 2014, at 9:08 PM, Rotorbl4de notifications@github.com wrote:

My issue resolved, I was able flash firmware and a config onto the copter with APM Planner 2.0.

The issues I had with Qground station really was it seemed finicky about upgrading the firmware and there was a song and dance I had to do several times and it finally upgraded the firmware. I am also unfamiliar with Qround Control V2.2.0 and that is really the only issue I have with the software and I will definitely give it more of a try now that I am back to flying my Pixhawk. I had gone into the DJI world the last few months with a couple Y6 configs and I intend to set up the Pixhawk on those and experience the difference in tuning and flying.

With APM Planner all I had to do was press continue and it uploaded the firmware, I guess I freaked out when I saw the authenticity error check and figured there was no going back and that being able to use the old mission planner software was out of the question, but that isn't the cast. I flashed the firmware with APM Planner 2.0 and again felt a little unfamiliar and uncomfortable with that software so I went back to the older Mission planner software and everything is good. Telemetry radios work, all bells and whistles where I remembered.

I just maidened this 730mm X quad and now that I know it hovers well, 25 minutes with a 500 gram payload I will get back into Pixhawk mood and do more reading before I post.

QGroundcontrol looks and seems like great software, I just need to give it a fair chance!

Reply to this email directly or view it on GitHub <

https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66903127>.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66937715>

.

Reply to this email directly or view it on GitHub < https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66938476>.

Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-66938616 .

— Reply to this email directly or view it on GitHub https://github.com/mavlink/qgroundcontrol/issues/827#issuecomment-68140681.