This is a discussion to focus the feedback and support of ardupilot on the PixRacer board from AUAV.co.

We believe that all teething problems encountered are now resolved and so we recommend people load Copter-3.3.4 which is available for all multicopters through the Mission Planner's (and other GCS's) Install Firmware screens.  Note that because regular Pixhawks are still on Copter-3.3.3 the install icon may show Copter-3.3.3 but rest assured, Copter-3.3.4 will be installed (you can check the version by looking at the very top of the Mission Planner).

Views: 95727

Reply to This

Replies to This Discussion

Hmm, 

Don't know from where you got that "accurate" info.

Both PX4 and ArduPilot share a common structure of drivers and operating system.

The release of a off cycle version of ArduPilot Copter 3.3.4 was done only to have a release version with support for the PixRacer, because the development version (3.4dev) already had that support (the necessary drivers), so it was back ported to 3.3.

Ardupilot is a team effort and each member has a broad skill set. Some of the support for the drivers of the PixRacer was indeed done by dev team members of ArduPilot and both PX4 and Ardupilot use that. 

ArduPilot Copter release cycle is longer than PX4, and that might seem that a release version of PX4 had direct support from the beginning, but I'm not sure at the moment of the timeframe.

You are correct that the 3.4 release version of ArduPilot Copter has some significant internal changes (and user facing too) and all those changes take time to test throughly because we have both a large number of supported hardware platforms (including the PixRacer) and a huge number of users with an astonishing variety of platforms.


Michael Burmeister said:

I think your a little confused here.  3.4 has nothing to do with PixRacer.  3.4 is all about new motor mixing and terrain following.  The fact that Pixracer works with this release is a side note that one of the developer decided to do.  If you want support for the Pixracer you should be using the PX4 flight stack as they made changes just for that hardware.

As far as making clones work with the firmware, I believe that they try to make all hardware regardless of who made it work.

This is where DJI and Apple excel as they do not release any hardware that is not fully supported by the firmware.

You can achieve both purposes with either a PixRacer or a PixHawk. Check the number of ports and their type so that you can plug all the extra stuff you might need.



Marcell Kovacs said:



Michael Burmeister said:

I think your a little confused here.  3.4 has nothing to do with PixRacer.  3.4 is all about new motor mixing and terrain following.  The fact that Pixracer works with this release is a side note that one of the developer decided to do.  If you want support for the Pixracer you should be using the PX4 flight stack as they made changes just for that hardware.

As far as making clones work with the firmware, I believe that they try to make all hardware regardless of who made it work.

This is where DJI and Apple excel as they do not release any hardware that is not fully supported by the firmware.

Well, I wasnt confused until your post :)

So this is the reason for having a 3.3-pixracer branch with not-merged, pixracer specific changes on github. And my understanding pixracer supports both PX4 and Ardupilot as well, was wrong. On PX4, i have other issues, but lets not get into that on this forum.

What is the recommended FC for:

- 250 size quadcopter. (not racing, just learning to fly, test autopilot, hacking, having fun with DIY sensors like sonar, run self-written-scripts, servo camera tilt stabilization)

- 450 size quadcopter for hobby aerial photography, supporting about the same than 250.

Its ok if i have to solder, read documentation, measure voltages, create special cables, do configuration etc.

The only requirement is that it needs to 'work', and have a longer-than-APM lifespan (expecting updates for at least a year).

Thanks a lot for clarification.

Thanks guys. Ordered one. I have big hopes this will work. :)

For the comment from Luis:

The release of a off cycle version of ArduPilot Copter 3.3.4 was done only to have a release version with support for the PixRacer, because the development version (3.4dev) already had that support (the necessary drivers), so it was back ported to 3.3.

This is good to hear, but there is something different in the startup scripts (compared to 3.3.4pixracer) preventing my ugly clone to start up. There is no retry anymore in the boor process. Do you have any information on this? Maybe do you know a revision where it was removed? I would try to hack it back.

You can check the revisions history and work on your fork until you manage to make it work. The code commits are well documented, so it's not too difficult. I haven't looked at that part of the code for a long long time.

For me it just works :)

Marcell Kovacs said:

Thanks guys. Ordered one. I have big hopes this will work. :)

For the comment from Luis:

The release of a off cycle version of ArduPilot Copter 3.3.4 was done only to have a release version with support for the PixRacer, because the development version (3.4dev) already had that support (the necessary drivers), so it was back ported to 3.3.

This is good to hear, but there is something different in the startup scripts (compared to 3.3.4pixracer) preventing my ugly clone to start up. There is no retry anymore in the boor process. Do you have any information on this? Maybe do you know a revision where it was removed? I would try to hack it back.

Marcell,

Pixracer is flying fine with current Ardupilot master and Randy mentioned somewhere that AC3.4rc2 will be rebased on master. Just a guess, but there have been some updates in the PX4Firmware which might be responsible preventing your clone to start.

Best regards,

Thorsten



Marcell Kovacs said:

Hi Philip,

This is great news. See it in stock.

Will ArduCopter 3.4 and later versions support pixracer?

post by Michael: "3.4 has nothing to do with PixRacer." scares me a bit. how is it then?

3.3.4 (Pixracer) works on the clone. When default 3.3.3 (current stable) is selected in MP that's what will install.  3.4Rc1, Arduplane 3.6 and the latest PX4 do not work.

Thorsten said:

Marcell,

Pixracer is flying fine with current Ardupilot master and Randy mentioned somewhere that AC3.4rc2 will be rebased on master. Just a guess, but there have been some updates in the PX4Firmware which might be responsible preventing your clone to start.

Best regards,

Thorsten



Marcell Kovacs said:

Hi Philip,

This is great news. See it in stock.

Will ArduCopter 3.4 and later versions support pixracer?

post by Michael: "3.4 has nothing to do with PixRacer." scares me a bit. how is it then?

Hi, what command do I need to make a firmware for Pixracer? With make px4-v2 and trying to write the firmware to the Pixracer, MP tells me, an Error: Firmware not suitable for this board.

In fact, I'm trying to make a HIL-firmware to play a bit around with missions, without risking my plane or copter. :)

Kind regards

Tobias

@Tobias,

Pixracer is a FMUv4 board, so you need "make px4-v4" instead.

Note that you don't need a special firmware for HIL in plane, just set the HIL_MODE parameter to 1 in a normal firmware.

Also, HIL isn't really very good for simulation, SITL is much better. For planes you may like to look at a posting I did recently on using SITL with X-Plane 10:

http://ardupilot.org/dev/docs/sitl-with-xplane.html

Cheers, Tridge

Wow, thank you very much! Excactly what I was looking for. :)

When I'm setting HIL_mode to 1 and restart my Pixracer, my radio is not recognized anymore?!?

Status update. Seems the issue is introduced in px4firmware. Baro and accep seems to be conflicting. After a few try starting /reseting baro, it starts providing data, but accel stops working (mpu6000). Reproducible with px4 latest beta and master and 3.4rc1 and master. Havent find any related commit yet. (This is still the ugly clone. Genuine is on its way to me)

Can I use PX4FLOW with a PixRacer(AC3.3.4)?

Reply to Discussion

RSS

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service