We(Flytron.com) were thinking about turning our projects to opensource for a long time. But we were not sure about the way and procedures.

Then, this weekend I read and inspired Chris Anderson's great 10 Rules of Maker Businesses article. His all of the rules %100 right about our business. We find same rules after 2 years work except Opensource side of this job.


After this great article, we (me and Bora) decided to opensource development of our all projects. This is very hard for us because we have 20+ different products. Writing the manuals and explaining the codes will take long time but we will.


At first, we will share the design and codes of our RXBee (Xbee based radio tx/rx for robotic servo controls). Then the OpenFARC (Opensoruce far aerial control) project will follow them. I hope you will like it.


Thanks Chris :)


If you want to see how we cook the delicious electronics, please visit our blog. We will post everything there on every day.


Thanks for reading

Melih

Views: 65

Tags: electronics, flytron, opensource

Comment by Russkel on November 23, 2010 at 7:13am
Bravo. :)
Comment by Paul Mather on November 23, 2010 at 10:11am
Melih, good luck! I know the world will love an open source OSD!
Comment by Mark Grennan on November 23, 2010 at 12:59pm
I want!
Comment by Renato Aranghelovici on November 23, 2010 at 2:49pm
Let the revolution begin !
Comment by Matthias Badaire on November 23, 2010 at 4:43pm
Ready to click buy as soon as the source is availanle on : http://www.flytron.com/simpleosd.htm
HappyKillMore, I am confused .. why don't you release remzbi's osd source code then ?? did I miss something ?
Comment by Renato Aranghelovici on November 23, 2010 at 11:31pm
Because remzibi OSD firmware itself is not HK work.
Comment by viky on November 24, 2010 at 2:39am
Open FARC is interesting one.
Comment by Paul Mather on November 24, 2010 at 6:34am
Yes, Matthias, Renato is right. Remzibi wrote the firmware for the OSD. He did/does not want to make it opensource. My PC program only configures the BIN file that gets written the EEPROM. I thought about making mine opensource, but I'm using a few 3rd party ActiveX controls for the COM port and input boxes that would require each user to purchase that wanted to edit the source.
Comment by Mark Grennan on November 24, 2010 at 6:55am
I'm ok with the firmware not being open source as long as the hardware is open. Hardware has intrinsic value. Software is more imperial. If someone is unsure they can recover their can protect their value by open source-ing the code I'm OK with that. It doesn't mean they will get a return. Software is to easy to copy.

As long as the hardware is open, you can write your own code; maybe better code; maybe code to do something completely different.

I've seen revolutions happen and empires made because someone (Linus) allowed others to see and work with what they had done while others (CP/M, Novel) faded away having once owned the industry because they couldn't believe their users would help them innovate.

Can I get an amen.

Comment

You need to be a member of DIY Drones to add comments!

Join DIY Drones

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service