I would like to have more information especially if it works with official Ardupilot or if it use a custom version, as there is a link in the site to download their version of MissionPlanner.
@anbello I do not recommend proceeding with this company. They advertise âbetter altitude hold by softwareâ indicating that they are not using standard ArduPilot firmware, but I believe the GPL software license under which ArduPilot is distributed mandates that if you copy-and-modify the software, you must also release your new software to the public. The spirit is that since you got it for free from others, so you need to keep it free for others to use/modify too.
EDIT: To be fair, I am assuming they copied-and-modified ArduPilot for their firmware. But I do NOT know this to be a fact.
Sorry for the wrong copied / pasted link.
What captured my attention was also the really low price on aliexpress.
I totally agree on the open source argument and GPL use.
If they copied-and-modified ArduPilot for their firmware i would like to see the source on github.
Hello friends,
This is low cost, small size and light weight flight control board, I dont have good knowledge of board electronic.
Can any one please clear me in simple way that this board can applicable for latest Arduplane firmware same as we use regular Pixhawk . I have to use for Vtol fixed motor tailsitter, where four servo out will use.
Please guide as early as possible.
Thanks
I donâthink you can use Ardupilot project firmware with this board, they have a custom version of Mission Planner on their site and seems that also the firmware is customized.
I was asked to follow up on this.
I have confirmed with radiolink that they have made modifications to ArduPilot, although I donât know the specifics. Radiolink declined my request for access to their modified source code (but the gpl doesnât require them to give it to me, as I havenât bought one of these).
âofficialâ ArduPilot will not run on these flight controllers, although this could be resolved if radiolink share their changes.
"better altitude hold by software" indicating that they are not
using standard ArduPilot firmware, but I believe the GPL
software license under which ArduPilot is distributed mandates
that if you copy-and-modify the software, you must also release
your new software to the public. The spirit is that since you
got it for free from others, so you need to keep it free for
others to use/modify too.
Sorry, common misconception.
The act of copying and pasting the code into their own code doesnât mean
they must release their source code to the public. It does become covered
under the GPL, however, and is constrained by the GPL in various ways.
One of the critical things being covered by the GPL means is that if they
distribute a binary produced from that source code they must also notify
that user of the availability of the source code and produce that source
code on demand, licensed under the GPL.
This isnât to say they company in question hsa done this - Iâve no idea.
But it takes a customer who cares enough to find out.
Thank you! Iâd like to make sure I understand:
0) If they copied any significant portion of ArduPilot in developing their
software, and
If a person obtains their product (with their software on it), and
That person requests the source code,
then
they must deliver the source code to that person.
A failure to deliver their source code to that user (who requested it) is a
violation of the GPL.
Do I have that right?
Well⌠make available, not necessarily deliver But what youâve got
there is correct AFAIK. Also note that the source code delivered has to
be licensed under the GPL.
Veiwing the change log it looks like they only changed some param file since the fork for the firmware. And I didnât search for a fork of the MP software but using it it looks like a radiolink branded version of the MP 1.3.49.6 and changed to use their github address instead of the official.
I tried using the original MP to flash it and it gave an error of firmware not compatible.
I used their MP to flash then the original MP to set it up.
It seems the firmware file has a board type of 3 versus original is 11⌠I am debating changing the original board type to match this new mini pix and see if it will flash, but of course this could brick the mini pix⌠I donât see any changes to the firmware in the forked plane. Anyone have thoughts, if the firmware isnât compatible will the mini pix be reflashable to the radiolink version?
O, something I hadnât considered I guess is they could not have committed the changesâŚ
Looking over the changes to MP I can see they use a board PID that the original MP doesnât like, not sure why⌠i get the error below when using the original MP to try and flash, then it tries and dies with incompatible firmware:
It looks like the only time the px4rl is used is when flashing firmware⌠havenât found any code yet that does things differently in MP based on this board type.