Licensing and Intellectual property
Our technology is based on the Open Source paradigm as we believe that there’s no more room for closed innovation today. You are free to create your commercial products: this is perfectly in line with our licensing.
OpenPicus supports the Open Source Hardware Association efforts and strives for 100% compliance with the initiative definitions. Here you can find the most common questions about Licensing and Intellectual Property.
Can I use openPicus or Flyport Brands?
No, you can't. Those are the only things that you can't use in your product: in few words, the naming of your products can't include neither openPicus nor Flyport.
MyOpenPicus Board = Not OK
MyPicus = OK
Flyport Car = Not OK
Catport = OK
RoboFlyport = Not OK
Can I use openPicus schematics to create a commercial product?
Yes you can, even for commercial purposes: Our schematics are released under CC-BY 3.0 .We just ask you to give a clear attribution to openPicus when releasing the product.
A good attribution is "Powered by openPicus technology"
Can I use openPicus software to create a comemrcial product?
Yes you can, but please note that:
- FreeRTOS has its own license
- The openPicus Framework (eg: tcp/ip stack, email sender, FTP, etc...) is available under LGPL v3.0
- The Code Samples, Applications, Projects and Libraries are available in Apache License 2.0
In few words:
- you release software that links (uses) unaltered code from openPicus (both Framework or Code Samples, App notes, etc...) without any implication on your license choice.
- if you tweak the framework code you shall release it under an LGPLv3 compliant license.
Can I modify the IDE code?
The IDE Software is released under GPLv3 - You can download the source here
Installation & the IDE
What do I need to install the Flyport IDE?
A Windows computer or a Linux/MacOSX computer capable of emulating a Windows environment.
How do I program a Flyport module?
An IDE environment is provided for free to let you create your applications running on Flyport. The language used to program the modules is C/C++-like. Flyport modules are based on PIC microcontrollers. The developer just need C/C++ experise to create the application: Flyport manages all the required network interfacing, internet communications protocols and the internal Webserver.
What do I need to program and use a Flyport module?
To get started with the Flyport you will need:
- A Flyport module (either the Flyport Ethernet or the Flyport WiFi)
- A programmer (like the miniUSB Programmer)
- The free IDE and compiler
- A computer running Microsoft Windows (or capable of emulating a Windows environment)
New users are recommended to get started with a Starter Kit.
Each kit contains Flyport module and anything you need to program it, including a Nest carrier board that allows you to easily connect sensors and actuators.
For more information read the Getting Started guide.
What is so cool about this technology?
Flyport is a great technology that comes with some very important features:
- It is designed both for makers, prototype developers and companies since it can be easily integrated into a finished product
- It is low cost
- It is an open platform
- It has everything you need to get started with your projects: You don't need to worry about connectivity, external libraries, communication protocols and thread programming! It is all there!
- The GPIOs are more than enough even for your most demanding project, plus the fact that the pins are remappable at runtime level!
- It comes with great accessories that make your development easier. Next carrier boards are designed to speed up your development.
- It has a great community of makers and users that contribute on projects, tutorials, libraries and knowledge
Is this a good platform for IoT (Internet of Things) and smart objects?
Absolutely! Flyport features exactly what these applications need:
- Connectivity (Wired or wireless)
- Embedded Web Server
- Ad-hoc and Infrastructure WiFi mode
- Sleep and Hibernate low power modes
- Comes with accessories that allow direct connectivity to sensors and actuators (check the Grove Nest)
- Small size
- Low cost