My name is John Loughlin my company, Stanton Concepts, has developed what we hope to be the world's first open source lock system. The lock is comprised of a very simple but very secure purely mechanical lock cylinder, a portable electro-mechanical key (Robotic Dialer) that could be as smart or dumb as an application requires and management software. More detailed info can be found in the peer reviewed white paper "Security Through Transparency: An Open Source Approach", Journal Of Physical Security, http://jps.anl.gov also at our website www.stantonconcepts.us
Several patents have been filed, 2 have recently been allowed.
We feel the robotic dialer is a natural for open source hardware development but are struggling to find a suitable license. The lock cylinder is in limited production.
If there is anyone out there willing share their thoughts on the issues and implications of open source hardware including non-commerical v. fully un-restricted licensing it would be very much appreciated.
John Loughlin
--------------------------------------------------------------------------------
Top
Open Source Hardware Licensing
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: Open Source Hardware Licensing
hi john! this is very interesting! thanks for the post!johnloughlin wrote:If there is anyone out there willing share their thoughts on the issues and implications of open source hardware including non-commerical v. fully un-restricted licensing it would be very much appreciated.
since you have a patent and you want to go open source hardware you should look at the chumby. they have patents and they're open source hardware. have you looked at their license, docs, etc?
http://wiki.chumby.com/mediawiki/index. ... mby_one.3F
so if i could speculate. you'd like to be able to allow others to make a project of yours and allow commercial use, is that correct? and because you patents you can allow use provided the makers also put anything in the same license (like the chumby).
is this correct?
-
- Posts: 3
- Joined: Mon Dec 14, 2009 3:37 pm
Re: Open Source Hardware Licensing
Thanks Adafruit- We are looking at the Chumby, TAPR as well as other Open Source Hardware licenses. Still struggling to find the right fit.
Our open source lock comprised of 3 elements (lock, Dialer, Management Software). Our current thinking is to make the Robotic Dialer and managment software avavailable for open source development.
Because the possible features and functions for the dialer are virtually limitless (GPS, biometrics, encryption, RFID, cellular and wireless etc.), the strategy of Stanton Concepts is to first provide a basic platform that includes an inexpensive and widely used PIC microcontroller (Microchip PIC16F917), motor controller, clock and EPROM and a DC servomotor. The basic dialer can store a multitude of lock combinations, uses PIN based access control, has programmable time out periods for specific locks and operators, and keeps a record of all activity. The dialer also has an USB interface to facilitate communication with a PC or Mac. This basic platform may be used for real world physical security applications or as a development platform and is available now from www.securitysnobs.com
The Robotic Dialer is a natural for Open Source development. The lock cylinders may be part of an installed base perhaps located in uncontrolled environments but the dialer is portable and free to evolve independently and in real time. There is really no limit to the technology the Robotic Dialer could employ. The dialer could also be well suited for an iPhone or similar application.
The potential number of real world applications could be very large and might include private, commercial and governmental applications.
We are seriously considering allowing others to develope the dialer for private or commercial use royalty free.
John
Our open source lock comprised of 3 elements (lock, Dialer, Management Software). Our current thinking is to make the Robotic Dialer and managment software avavailable for open source development.
Because the possible features and functions for the dialer are virtually limitless (GPS, biometrics, encryption, RFID, cellular and wireless etc.), the strategy of Stanton Concepts is to first provide a basic platform that includes an inexpensive and widely used PIC microcontroller (Microchip PIC16F917), motor controller, clock and EPROM and a DC servomotor. The basic dialer can store a multitude of lock combinations, uses PIN based access control, has programmable time out periods for specific locks and operators, and keeps a record of all activity. The dialer also has an USB interface to facilitate communication with a PC or Mac. This basic platform may be used for real world physical security applications or as a development platform and is available now from www.securitysnobs.com
The Robotic Dialer is a natural for Open Source development. The lock cylinders may be part of an installed base perhaps located in uncontrolled environments but the dialer is portable and free to evolve independently and in real time. There is really no limit to the technology the Robotic Dialer could employ. The dialer could also be well suited for an iPhone or similar application.
The potential number of real world applications could be very large and might include private, commercial and governmental applications.
We are seriously considering allowing others to develope the dialer for private or commercial use royalty free.
John
-
- Posts: 188
- Joined: Wed Jul 30, 2008 5:17 pm
Re: Open Source Hardware Licensing
So you've created essentially a combination lock that needs a motorized tool to open? I'm afraid I do not appreciate the point. Most of the benefits of an electronic lock are lost. For example, you can't be sure you have a record of people entering or leaving. Neither can you change the key (without swapping the barrel).
Anyway, open source licenses are generally pretty simple. They deal with a limited set of questions. Mainly, do derivative works have to be open source, or how the derivative works give credit to the original authors. Rarely do they make more complex stipulations such as different terms for commercial use, royalties, etc. Although, you are free to do that. Really you can set whatever terms you want (even unenforceable ones). The only problem is people may debate you whether your license is "really" open source even if it gives people a lot of freedom. This is a problem Microsoft had.
You probably won't have anyone doing anything interesting with your stuff until after you start selling your product, successfully. You probably wish it was the other way around.
Anyway, open source licenses are generally pretty simple. They deal with a limited set of questions. Mainly, do derivative works have to be open source, or how the derivative works give credit to the original authors. Rarely do they make more complex stipulations such as different terms for commercial use, royalties, etc. Although, you are free to do that. Really you can set whatever terms you want (even unenforceable ones). The only problem is people may debate you whether your license is "really" open source even if it gives people a lot of freedom. This is a problem Microsoft had.
You probably won't have anyone doing anything interesting with your stuff until after you start selling your product, successfully. You probably wish it was the other way around.
-
- Posts: 3
- Joined: Mon Dec 14, 2009 3:37 pm
Re: Open Source Hardware Licensing
Hi Alex-
Actually one of the primary benefits of the system is that the key is technologically independent from the lock. The key can employ the latest technology (encryption, biometrics, gps, auditing etc.) and evolve in real time. The lock is highly resistant to manipulation (picking) and wholly mechanical. The lock's combination can be reset mechanically. One can install a lock and come back several years later to open it with perhaps a 10th generation key. The lock and key are future proof.
We're leaning towards a share and share alike, unrestricted, as simple as possible license for the key.
Your last point is a good one. We're building momentum with certain niche applications but feel the potential for wide spread use is quite large.
Actually one of the primary benefits of the system is that the key is technologically independent from the lock. The key can employ the latest technology (encryption, biometrics, gps, auditing etc.) and evolve in real time. The lock is highly resistant to manipulation (picking) and wholly mechanical. The lock's combination can be reset mechanically. One can install a lock and come back several years later to open it with perhaps a 10th generation key. The lock and key are future proof.
We're leaning towards a share and share alike, unrestricted, as simple as possible license for the key.
Your last point is a good one. We're building momentum with certain niche applications but feel the potential for wide spread use is quite large.
Please be positive and constructive with your questions and comments.