Programming the Real World: Javascript for Makerspchristensen
Hardware is becoming easier to design and manufacture, approaching the ease of software. This presentation:
- takes you on a tour of the changes in hardware
- a crash course in building circuits
- teaches the basics of using and programming Arduino
- introduces Javascript libraries for controlling hardware and robots
- how to get involved with hardware projects
If you'd like me to present this or similar content at your event, please contact me: peter at pchristensen dot com
UI Beyond the Browser - Software for Hardware Projectspchristensen
Hardware is becoming easier to design and manufacture, approaching the ease of software. This presentation:
- takes you on a tour of the changes in hardware
- a crash course in building circuits
- teaches the basics of using and programming Arduino
- introduces Javascript libraries for controlling hardware and robots
- how to get involved with hardware projects
If you'd like me to present this or similar content at your event, please contact me: peter at pchristensen dot com
Introducción al Open hardware y primeros pasos con Arduino. primera sesión del Laboratorio de fabricación digital de la Universidad Pública de Navarra
http://apptivismo.org/laboratorio-fabricacion-digital
Programming the Real World: Javascript for Makerspchristensen
Hardware is becoming easier to design and manufacture, approaching the ease of software. This presentation:
- takes you on a tour of the changes in hardware
- a crash course in building circuits
- teaches the basics of using and programming Arduino
- introduces Javascript libraries for controlling hardware and robots
- how to get involved with hardware projects
If you'd like me to present this or similar content at your event, please contact me: peter at pchristensen dot com
UI Beyond the Browser - Software for Hardware Projectspchristensen
Hardware is becoming easier to design and manufacture, approaching the ease of software. This presentation:
- takes you on a tour of the changes in hardware
- a crash course in building circuits
- teaches the basics of using and programming Arduino
- introduces Javascript libraries for controlling hardware and robots
- how to get involved with hardware projects
If you'd like me to present this or similar content at your event, please contact me: peter at pchristensen dot com
Introducción al Open hardware y primeros pasos con Arduino. primera sesión del Laboratorio de fabricación digital de la Universidad Pública de Navarra
http://apptivismo.org/laboratorio-fabricacion-digital
Open source hardware is a term slowly working its way into many new projects and efforts, but what is it? There are a few definitions, some of which come from “open source software,” which is usually considered software’s “source code under a license (or arrangement such as the public domain) that permits users to study, change, and improve the software, and to redistribute it in modified or unmodified form.” So how does this translate to hardware? This session will focus on electronic hardware, the layers they can be divided into, different document types, licensing concerns, and a show-and-tell of hardware. Because of the openness of the movement it is increasingly being tied to Web 2.0 services.
L'open hardware dans l'électronique (et au delà...)Robert Viseur
Depuis les années quatre-vingt, l’open source se développe dans le domaine logiciel avec des succès répétés et illustrés par des communautés populaires comme Linux, Mozilla ou Apache. Les pratiques open source en matière de licences, de modèles d’affaires et de méthodes de développement ont progressivement essaimé vers d’autres domaines que le logiciel, donnant naissance à l’open data, l’open content, l’open hardware ou encore l’open cloud. Les succès récents, dans le domaine de l’électronique, de familles de produits comme Arduino ou Elphel, démontrent que la révolution qui s’est opérée dans le domaine logiciel s’apprête aujourd’hui à se produire dans le celui du matériel. L’exposé proposera dès lors de faire le point sur les types de projets et les projets actuellement actifs dans le domaine de l’open hardware (OpenCollector, OpenCores, Arduino, BeagleBoard, NanoNote,…). Il inclura une présentation des moyens de protection généralement utilisés (Creative Commons, GPL, LGPL,…) ainsi que des entreprises actuellement actives dans ce secteur en développement (Arduino, Gaisler, Elphel,…). En pratique, si l’open hardware est surtout connu pour ses applications dans le domaine électronique, il englobe également des objets de la vie quotidienne et concerne petit à petit des biens inattendus comme les automobiles. Le secteur automobile voit ainsi les pratiques de co-création se développer depuis quelques années, avec des initiatives telles que le concours de design Peugeot ou la plate-forme participative dédiée à la Fiat Mio. Les pratiques open source s’y développent également, avec des sociétés ou projets comme OSVehicule, Local Motors ou Wikispeed, mêlant création de “Commons”, utilisation de technologies open hardware, exploitation d’outils de fabrication numérique, mise en œuvre de méthodologies Agile et adoption d’architectures modulaires. Cette présentation fera également le point sur ces tendances émergentes et tentera d’en dresser les perspectives.
RGB LED in Arduino with an Oscilloscope
• Generating QR Code
• 3D Printing
• Web Video Cam
• Digi Clock with Real Time Clock
• Android SeekBar to Arduino LED Matrix
Ubucon 2013, licensing and packaging OSSNuno Brito
As developers of open source and free software, we share our code freely with the world. It feels great. The problem is when someone points out that the code can't be used for some odd reason. Either because of missing license information or because the reported licenses are incompatible.
If you're writing code then you shouldn't miss this talk. We'll be showing which licenses you should avoid mixing (for e.g Apache v2 inside GPL v2) and other tips to avoid a licensing headache. In the end we'll talk about the SPDX format introduced by the Linux Foundation and show practical examples.
My accompanying slides to my video blog.
This episode is about open source software and open source hardware.
See video: https://www.youtube.com/watch?v=5ynE_KbDaS0
See my Video Blog: https://www.youtube.com/channel/UCtUcgFWvhZbknS5LxvfbMrw
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
The Arduino is what is known as a Physical or Embedded Computing platform, which means that it is an interactive system that through the use of hardware, firmware and software can interact with its environment.
We code a RGB LED light on the Arduino board and a breadboard on which we switch off or on the light by a browser on an android device with our own web server and their COM protocols.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Open source hardware is a term slowly working its way into many new projects and efforts, but what is it? There are a few definitions, some of which come from “open source software,” which is usually considered software’s “source code under a license (or arrangement such as the public domain) that permits users to study, change, and improve the software, and to redistribute it in modified or unmodified form.” So how does this translate to hardware? This session will focus on electronic hardware, the layers they can be divided into, different document types, licensing concerns, and a show-and-tell of hardware. Because of the openness of the movement it is increasingly being tied to Web 2.0 services.
L'open hardware dans l'électronique (et au delà...)Robert Viseur
Depuis les années quatre-vingt, l’open source se développe dans le domaine logiciel avec des succès répétés et illustrés par des communautés populaires comme Linux, Mozilla ou Apache. Les pratiques open source en matière de licences, de modèles d’affaires et de méthodes de développement ont progressivement essaimé vers d’autres domaines que le logiciel, donnant naissance à l’open data, l’open content, l’open hardware ou encore l’open cloud. Les succès récents, dans le domaine de l’électronique, de familles de produits comme Arduino ou Elphel, démontrent que la révolution qui s’est opérée dans le domaine logiciel s’apprête aujourd’hui à se produire dans le celui du matériel. L’exposé proposera dès lors de faire le point sur les types de projets et les projets actuellement actifs dans le domaine de l’open hardware (OpenCollector, OpenCores, Arduino, BeagleBoard, NanoNote,…). Il inclura une présentation des moyens de protection généralement utilisés (Creative Commons, GPL, LGPL,…) ainsi que des entreprises actuellement actives dans ce secteur en développement (Arduino, Gaisler, Elphel,…). En pratique, si l’open hardware est surtout connu pour ses applications dans le domaine électronique, il englobe également des objets de la vie quotidienne et concerne petit à petit des biens inattendus comme les automobiles. Le secteur automobile voit ainsi les pratiques de co-création se développer depuis quelques années, avec des initiatives telles que le concours de design Peugeot ou la plate-forme participative dédiée à la Fiat Mio. Les pratiques open source s’y développent également, avec des sociétés ou projets comme OSVehicule, Local Motors ou Wikispeed, mêlant création de “Commons”, utilisation de technologies open hardware, exploitation d’outils de fabrication numérique, mise en œuvre de méthodologies Agile et adoption d’architectures modulaires. Cette présentation fera également le point sur ces tendances émergentes et tentera d’en dresser les perspectives.
RGB LED in Arduino with an Oscilloscope
• Generating QR Code
• 3D Printing
• Web Video Cam
• Digi Clock with Real Time Clock
• Android SeekBar to Arduino LED Matrix
Ubucon 2013, licensing and packaging OSSNuno Brito
As developers of open source and free software, we share our code freely with the world. It feels great. The problem is when someone points out that the code can't be used for some odd reason. Either because of missing license information or because the reported licenses are incompatible.
If you're writing code then you shouldn't miss this talk. We'll be showing which licenses you should avoid mixing (for e.g Apache v2 inside GPL v2) and other tips to avoid a licensing headache. In the end we'll talk about the SPDX format introduced by the Linux Foundation and show practical examples.
My accompanying slides to my video blog.
This episode is about open source software and open source hardware.
See video: https://www.youtube.com/watch?v=5ynE_KbDaS0
See my Video Blog: https://www.youtube.com/channel/UCtUcgFWvhZbknS5LxvfbMrw
International Journal of Engineering Research and Applications (IJERA) is an open access online peer reviewed international journal that publishes research and review articles in the fields of Computer Science, Neural Networks, Electrical Engineering, Software Engineering, Information Technology, Mechanical Engineering, Chemical Engineering, Plastic Engineering, Food Technology, Textile Engineering, Nano Technology & science, Power Electronics, Electronics & Communication Engineering, Computational mathematics, Image processing, Civil Engineering, Structural Engineering, Environmental Engineering, VLSI Testing & Low Power VLSI Design etc.
The Arduino is what is known as a Physical or Embedded Computing platform, which means that it is an interactive system that through the use of hardware, firmware and software can interact with its environment.
We code a RGB LED light on the Arduino board and a breadboard on which we switch off or on the light by a browser on an android device with our own web server and their COM protocols.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
7. I see no social imperative for free
hardware designs like the
imperative for free software.
Freedom to copy software is an
important right because it is easy
now--any computer user can do it.
Freedom to copy hardware is not as
important, because copying
hardware is hard to do.
On quot;Free Hardwarequot;
Richard Stallman - Linux Today, 1999
8. There are a few definitions, some of which come from quot;open
source software,quot; which is usually considered software's quot;source
code under a license (or arrangement such as the public
domain) that permits users to study, change, and improve the
software, and to redistribute it in modified or unmodified form.quot;
So how does this translate to hardware?
Electronic hardware can be divided up into layers, each of which
could have different document types and licensing concerns.
10. Hardware / Mechanical Diagrams
Dimensions for enclosures,
mechanical subsystems, etc.
For 2D models, preferred
document type is vector
graphics file, with dimension
prints, DXF, or AI, etc.
Materials.
RepRap - motor drive screw block, open source 3D printer.
11.
12. Schematics & Circuit Diagrams
Symbolic diagrams of
electronic circuitry, includes
parts list (sometimes
inclusively).
Preferred document type is
any sort of image (PDF,
BMP, GIF, PNG, etc).
Often paired with matching
layout diagram. Chumby - Power supply, open source beanbag computer.
13.
14. Parts List (BOM)
What parts are used, where to get
them, part numbers, etc.
Ideally - have data sheets, generic,
easy to get, notes and
specifications. No fucking NDAs
please.
Standard format is a text file, BOM
(bill of materials).
Often included with or part of the Parts list from the open source Roland 303 MIDI synth
schematic. clone, the x0xb0x.
15. Parts lists from the open source embedded Asterisk IP PBX
http://www.rowetel.com/ucasterisk/hardware.html
http://svn.astfin.org/hardware/ip04/trunk/ip04_bom.xls
16. Layout Diagrams
Diagrams of the physical layout
of electronic circuitry, including
the placement of parts, the
PCB copper prints, and a drill
file. This is often paired with a
schematic. Preferred
distribution is Gerber RS274x
and Excellon (for drills).
These are like PostScript for
printers but the primitives aren't
text and arcs, they're lines of
solder and components. Make: Daisy - Open source MP3 player.
17.
18. Core/Firmware
The source code runs on a
microcontroller/microprocessor often
in C, Assembly. In some cases, the
code may be the design of the chip
hardware itself (in VHDL/Verilog/RTL,
etc...).
Preferred distribution: text file with
source code in it, as well as compiled
'binary' for the chip.
Language and architecture is
irrelevant.
Open core 8080 compatible CPU code snippet from
executing the 8080 instruction set.
19. Software/API
The source code that
communicates or is used with the
electronics from a computer (if
applicable).
Any drivers necessary for the
chipset.
Preferred format is source code
and binaries.
We don’t think tools count.
Arduino IDE
21. Licensing
Because hardware is mostly based on patents,
not copyright, different licenses may be better.
Creative Commons, GPL / LGPL, BSD, MIT
The TAPR Open Hardware License (2/07)
Chumby HDK License (3/07)
23. Evil Mad Scientists uses...
Copyright...
Attribution-Share Alike 3.0:
http://creativecommons.org/licenses/by-sa/3.0/
GPL:
http://www.gnu.org/copyleft/gpl.html
GNU Free Documentation License
http://en.wikipedia.org/wiki/
GNU_Free_Documentation_License
Circuit board was design - in gEDA PCB:
http://www.gpleda.org/
24. Arduino... CC’ed with trademarked name
http://arduino.cc/en/Main/FAQ
Is Arduino open-source?
Yes. The source code for the Java environment is released under the
GPL, the C/C++ microcontroller libraries under the LGPL, and the
schematics and CAD files under Creative Commons Attribution Share-
Alike licenses.
I want to design my own board; what should I do?
The reference designs for the Arduino boards are available from the
hardware page. They're licensed under a Creative Commons
Attribution Share-Alike license, so you are free to use and adapt them
for your own needs without asking permission or paying a fee. If
you're looking to make something of interest to the community, we'd
encourage you to discuss your ideas on the hardware development
forum so that potential users can offer suggestions.
What should I call my boards?
If you're making your own board, come up with your own name! This
will allow people identify you with your products and help you to build
a brand. Be creative: try to suggest what people might use the board
for, or emphasize the form factor, or just pick a random word that
sounds cool. quot;Arduinoquot; is a trademark of Arduino team and should not
be used for unofficial variants. If you're interested in having your
design included in the official Arduino product line, please see the So
you want to make an Arduino document and contact the Arduino
team. Note that while we don't attempt to restrict uses of the quot;duinoquot;
suffix, its use causes the Italians on the team to cringe (apparently it
sounds terrible); you might want to avoid it.
25. DIY Drones
http://diydrones.com/
Code License:
Apache License 2.0
Content License:
Creative Commons 3.0 BY-SA
ArduPilot is a full-featured autopilot based on the
Arduino open-source hardware platform. It uses
infrared (thermopile) sensors for stabilization and GPS
for navigation.
The hardware is available from Sparkfun for $24.95.
The software comes in two varieties: 1.0 (navigation-
only, requires a third-party stabilization system) and
2.0 (navigation and stabilization integrated into one).
Both require the free Arduino IDE to edit and upload
the code to the Ardupilot board.
26. TAPR Open Hardware License (quot;OHLquot;)
http://www.tapr.org/ohl.html
“The TAPR Open Hardware License (quot;OHLquot;) provides a framework
for hardware projects that is similar to the one used for Open Source
software. This isn't as straight-forward as it seems because legal
concepts that work well for software (such as copyright and copyleft)
don't neatly fit when dealing with hardware products and the
documentation used to create them”.
TAPR = “Tucson Amateur Packet Radio” - they no longer has any direct connections with Tuscon, Arizona.
27. TAPR Open Hardware License (quot;OHLquot;)
http://www.tapr.org/ohl.html
Like the GNU General Public License, the OHL is designed to guarantee your freedom
to share and to create. It forbids anyone who receives rights under the OHL to deny
any other licensee those same rights to copy, modify, and distribute documentation,
and to make, use and distribute products based on that documentation.
Unlike the GPL, the OHL is not primarily a copyright license. While copyright protects
documentation from unauthorized copying, modification, and distribution, it has little to
do with your right to make, distribute, or use a product based on that documentation.
For better or worse, patents play a significant role in those activities. Although it does
not prohibit anyone from patenting inventions embodied in an Open Hardware design,
and of course cannot prevent a third party from enforcing their patent rights, those
who benefit from an OHL design may not bring lawsuits claiming that design infringes
their patents or other intellectual property.
The OHL addresses unique issues involved in the creation of tangible, physical things,
but does not cover software, firmware, or code loaded into programmable devices. A
copyright-oriented license such as the GPL better suits these creations.
28. TAPR Open Hardware License (quot;OHLquot;)
http://www.tapr.org/ohl.html
How can you use the OHL, or a design based upon it?
While the numbered sections of the agreement take
precedence over this preamble, here is a summary:
You may modify the documentation and make products based upon
it.
You may use products for any legal purpose without limitation.
You may distribute unmodified documentation, but you must include
the complete package as you received it.
You may distribute products you make to third parties, if you either
include the documentation on which the product is based, or make it
available without charge for at least three years to anyone who
requests it.
29. TAPR Open Hardware License (quot;OHLquot;)
http://www.tapr.org/ohl.html
You may distribute modified documentation or
products based on it, if you:
License your modifications under the OHL.
Include those modifications, following the requirements stated
below.
Attempt to send the modified documentation by email to any
of the developers who have provided their email address. This
is a good faith obligation -- if the email fails, you need do
nothing more and may go on with your distribution.
30. TAPR Open Hardware License (quot;OHLquot;)
http://www.tapr.org/ohl.html
If you create a design that you want to license under
the OHL, you should:
Include the OHL document in a file named LICENSE.TXT (or LICENSE.PDF)
that is included in the documentation package.
If the file format allows, include a notice like quot;Licensed under the TAPR Open
Hardware License (www.tapr.org/OHL)quot; in each documentation file. While not
required, you should also include this notice on printed circuit board artwork
and the product itself; if space is limited the notice can be shortened or
abbreviated.
Include a copyright notice in each file and on printed circuit board artwork.
If you wish to be notified of modifications that others may make, include your
email address in a file named quot;CONTRIB.TXTquot; or something similar.
31. TAPR Open Hardware License (quot;OHLquot;)
http://www.tapr.org/ohl.html
Any time the OHL requires you to make documentation available to
others, you must include all the materials you received from the
upstream licensors. In addition, if you have modified the
documentation:
You must identify the modifications in a text file (preferably named
quot;CHANGES.TXTquot;) that you include with the documentation. That file must
also include a statement like quot;These modifications are licensed under the
TAPR Open Hardware License.quot;
You must include any new files you created, including any manufacturing
files (such as Gerber files) you create in the course of making products.
You must include both quot;beforequot; and quot;afterquot; versions of all files you
modified.
*You may include files in proprietary formats, but you must also include
open format versions (such as Gerber, ASCII, Postscript, or PDF) if your
tools can create them.
32. TAPR Noncommercial Hardware License (quot;NHLquot;)
http://www.tapr.org/ohl.html
The TAPR Noncommercial Hardware License
TAPR has created another license, the TAPR Noncommercial
Hardware License (quot;NCLquot;), which is identical to the OHL apart from
adding a limitation that products based on NCL designs may only be
made for noncommercial uses. While we appreciate that a
commercial use limitation may be appropriate in some cases, we
encourage you to use the OHL if you can, as it more closely follows
the Open Source software philosophy.
33. Does anyone use TAPR?
We’re not sure...
But we get asked a lot...
In a recent email with TAPR - John w9DDD
wrote...
“All TAPR projects were pretty much designed prior to
the writing of the OHL document. HPSDR projects
which TAPR supports by making them available as kits
or A&T units were done originally under the NCL.
Recently the [discontinued] Penelope project was
released to OHL.”
34. Chumby HDK License Agreement
http://www.chumby.com/developers/agreement
quot;Chumby HDKquot; means the schematics, mask works, flat
patterns, and specifications for the Chumby Device provided
by Chumby under this Agreement.
Chumby grants you a license to use the Chumby HDK to hack
your Chumby Device. In return, we ask that you: keep the
Chumby Service on an even playing field with any other
service you want to point your Chumby Device to; grant us a
license related to your modifications and derivatives, when and
if you make them available to others; and agree to the other
terms...
3.2 License to Modified Devices. You retain your ownership
rights in your innovations. If you publish, distribute, or
otherwise make available any Modified Device or any related
descriptions or specifications, you hereby automatically grant
to Chumby a non-exclusive, transferable, perpetual,
irrevocable, royalty-free, and worldwide right and license under
all Intellectual Property Rights to use, reproduce, modify,
create derivative works of, and distribute and to make, have
made, use, import, offer to sell and sell, and otherwise exploit
such Modified Devices and any modifications, improvements,
or enhancements they embody.
35. (Some) Business models
Arduino - Assembled dev boards (100k units), resellers / direct
Chumby - Direct to customer (VC funded)
BugLabs - Direct to customer (VC funded)
BeagleBoard - DigiKey & TI sponsored (one to watch)
RepRap / Fab@Home - 3rd party sells kits
Rowetel - 3rd party manufacturing
DIY Drones - 3rd party manufacturing
Adafruit - kits, direct to customer/wholesale/rev share
Evil Mad Scientist laboratories - kits, direct to customer/wholesale
Make - Halo / reselling kits, some dev funding...
SparkFun - Halo / Ecosystem + rev share