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.
1 Like
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.
1 Like
Thanks to all for valuable guidelines.
Could you say if its possible to control servos with this board (two 5v servos in a small flying wing) ?
I encourage all users to avoid this company and to avoid this product.
"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?
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.
The license isn’t actually all that difficult to read, and is quite
interesting, really. The GNU General Public License v3.0 - GNU Project - Free Software Foundation
Also, a key feature is the notification stuff - the user must be informed
of the license.
Seller cleared that this product not applicable for latest firmware or any updates. . . . So really APM user should not have to go with that product.
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.
curiosity got the better of me, downloaded there mission planner …won’t connect… 32/64 bit issue?so far not so good
No links to price or supply on their website.
Emailed them but as yet no reply.
Looking a lot like vapourware.
got one from https://www.aliexpress.com/store/product/Radiolink-Mini-PIX-Flight-Control- $36.00 US but ??
that link won’t work, go to aliexpress and look for radiolink minipix
I got mine off of amazon. Flys my z84 just fine… had to add a bigger cap to the power board, would reboot when going from 0 throttle to full quickly. No power on the servo rail so I added a 5v regulator to my setup.
different USB conn worked…looks like it’s going to work for most applications but not TVBS or other exotic stuff
The changes to their Ardupilot fork vs. the original is here:
this might be wrong, seems to load all, hmmm