Total: 0,00 €


Planet buglabs-community

  • Friday, November 4, 2011 - 11:22
    node.js for BUG 2.0

    It was interesting to see the new Beagleboard "bone" project announcement today.  Particularly because of some software that ships with it; a browser-based development environment targeting the JavaScript language.  Given the popularity of the JavaScript language and a completely hosted environment, I can see how this is a great way to remove a lot of the annoying and error-prone steps to getting started with embedded development.  

    As a first step to see how this vision could be executed on BUG, I built Node.js and it's dependencies for BUG 2.0 and prepared a simple installer script.  Unzip the tarball on your BUG and run install.sh.  From there you can run the 'hello world' program also included to verify it's working.

  • Saturday, October 15, 2011 - 01:52
    Java 7 (OpenJDK/IcedTea) for the BUG 2.0

    For anyone interested in Java 7, I have built OpenJDK 7 (via IcedTea) for BUG 2.0 (Angstrom, armv7, Zero VM).  The binaries are available here.  The binaries are not provided as Angstrom opkgs, so the installation process is manual. This is because it was built natively on a BUG, rather than using the OpenEmbedded cross compiling build system.  You'll also need to install libcups2 via opkg if you want to replace the Java 6 JRE to run BUG applications.  Here is my installation steps, assuming the j2re-image tarball is decompressed in /home/root:


    $ mkdir -p /usr/lib/jvm/java-7-openjdk/jre
    $ mv ~/j2re-image/* /usr/lib/jvm/java-7-openjdk/jre
    $ rm /usr/bin/java
    $ ln -s /usr/lib/jvm/java-7-openjdk/jre/bin/java /usr/bin/java
    $ opkg install libcups2

    Now if you restart Felix (via Knapsack if you are running a 3.0 release), you'll notice that the JVM running is java.runtime.version = 1.7.0_147-icedtea-b147 via http://bug/support.html.  This is provided on an experimental basis and I would not be surprised if problems pop up!

    An interesting benefit that IcedTea 7 provides (other than ARM compatibility via Zero) is alternative VM implementations CACAO and JamVM.  The binary build I have provided unfortunately does not include these but I'm going to try and build them.  Hopefully I can get Zero, Shark, CACAO, and JamVM all happily living inside the BUG!  :)

    Special thanks to xranby@irc.oftc.net#openjdk for his invaluable assistance!


  • Monday, September 12, 2011 - 07:32
    4 days and counting to the Open Hardware Summit!

    We've got 4 days to go until the Open Hardware Summit! And it's coming together marvelously. Don't forget to get your ticket!

    The Open Hardware Summit is a venue to discuss and draw attention to the rapidly growing open source hardware movement. Speakers at the Summit include world renowned leaders from industry, academia and the DIY community. The summit focuses on hardware as a system through a series of discussions and panels on BUSINESS, LAW, MANUFACTURING, SCALING, DESIGN and EDUCATION. The one-day Summit seeks to empower companies, large and small, to produce electronic objects in an open source fashion.

    Our speaker lineup includes a Keynote from the Arduino Team; Myriam Ayass, the lawyer who wrote an Open Hardware License at CERN from the OSHW definition; talks from sucessful open source hardware business owners; artists; and hardware hackers.

    We also are announcing an Open Hardwre Scholarship this year! Get $2,000 USD to begin your open source hardware project. Follow the instructions on the Scholarship page, but act fast - Entries are due on Sept. 14th.

    Please join us!

  • Thursday, August 4, 2011 - 22:13
    Support the Open Hardware Summit!

    Sponsor the Summit!

    Sponsorship for the Open Hardware Summit is open! Special thanks to our sponsors who have already donated.

    The summit is in its second iteration in partnership with MAKE and Makerfaire at the New York Hall of Science. Last year, 350 people came together to share knowledge about bringing open hardware to market, solving issues around open design, protocols and licensing. Many more people watched online and got involved in the conversation through the forums and twitter. Together with support from you, we have gained more momentum as a team. The definition we signed last year was turned into a license by CERN. We held a logo competition which received 129 submissions and chose one by popular vote. The summit continues to be about the DIY, Maker, small scale (and growing to large) fabrication movements and Open Hardware, and legalese around open source hardware.

    By sponsoring the Open Hardware Summit you’ll be fostering the open source hardware movement. Read more about Why to Sponsor.

    Sponsor Levels

    SUPPORTER: $300-$1,499

    • ONE complimentary ticket to the Summit
    • Your logo will appear on the banner, website and program
    • You will be able to add one (1) item in the goodie bag.

    ENTHUSIAST $1,500 – $3,999

    • TWO complimentary tickets to the Summit
    • Your logo will appear on the main section in the banner, website and program
    • You will be able to add one (1) item in the goodie bag.

    FANATIC $4,000 – $5,000

    • TWO complimentary tickets with RESERVED SEATS in the auditorium
    • Your logo will appear on the main section in the banner, website and program
    • You will be able to add one (1) item in the goodie bag.

    This is a non-profit event. Extra funds from sponsorship will be put toward a scholarship for creating open hardware.

    Would you like to Sponsor?

    Your donation is tax deductible. Thanks to Eyebeam Art and Technology center, our non-profit fiscal sponsor for handling the finances.

  • Monday, June 6, 2011 - 17:18
    Open Hardware Summit 2011 - Call for Submissions

    * * * Please Redistribute * * *

    The Open Hardware Summit (OHS) invites submissions for the second annual summit, to be held on September 15, 2011 in New York City. The Open Hardware Summit is a venue to present, discuss, and learn about open hardware of all kinds. The summit examines open hardware and its relation to other issues, such as software, design, business, and law. We are seeking submissions for talks, breakout sessions, and demos from individuals and groups working with open hardware and related areas. Submissions are due by June 24, 2011. Notification of accepted proposals will happen by August 1st.

    Since the first Open Hardware Summit in 2010, we have seen the open hardware movement continue to flourish. The Open-Source Hardware Definition was announced, the OSHW logo was selected by a popular vote, an open source oil spill cleaning robot got more than $33,000 in crowd funding, Google adopted the open hardware movement’s biggest success story, Arduino, as its platform and our very own keynote speaker, Limor Fried, was featured on the front page of Wired Magazine – to name a few. Needless to say, open hardware is getting BIG.

    Submission topics

    Topics of interest for the summit include, but are not limited to:

    • Lessons learned from past projects
    • Legal and intellectual property implications of open-source hardware
    • Means of supporting collaboration and community interaction
    • Manufacturing
    • Distributed development and its relationship to physical goods
    • Digital fabrication (e.g. laser cutters and 3D printers)
    • Software design tools (CAD / CAM)
    • DIY technology
    • Ways to share information about hardware that’s not captured in source files
    • Business models
    • Manufacturing on demand
    • Competition and collaboration
    • Sustainability of open hardware products (e.g. how to unmake things)
    • Industrial design
    • “open-washing” (green washing for open source)
    • Open-hardware in the enterprise
    • Specific product domains: e.g. science, agriculture, communications, medicine

    And any other topic you think relates to openness and hardware. We want to hear all about it!

    Types of submissions

    You may submit proposals for one or more of the following formats:


    • Expected duration for talks is between 5 and 20 minutes, depending on the number and quality of submissions.
    • We expect all talks to be plenary (i.e. presented to the entire summit audience).
    • Talk submissions primarily containing marketing for a product will not be accepted. However, talks that share knowledge and insight derived from work on commercial products are welcome.

    Breakout session

    • Depending on submissions, there may be an opportunity to organize breakout sessions with smaller groups (5-40) to discuss a particular topic
    • We expect breakout sessions to occur during a single time-slot of approximately 1 to 2 hours.
    • Breakout session submissions should include an overview of the content and plan for the session.
    • You are encouraged to co-author breakout session submissions with other interested parties but sessions will be open to general summit attendees.

    Project Demo

    • This is a casual show and tell session that will take place during the end-of-day drinks.
    • You are encouraged to include pictures as part of your demo submissions.
    • Please include all demo requirements: amount and type of space (e.g. “one 3×3 foot table and one chair” or “a 5 × 5 section of wall with at least 10 feet in front of it”), power requirements (note: we cannot provide any power adaptors). Please keep in mind this is an informal project demo, and complex requirements/constraints (internet, light/sound conditions etc) will be difficult to accommodate.
    • It will be your responsibility to carry/assemble/set up/disassemble your demo. We cannot provide any support for the receiving, storing, or shipping of demos.
    • Note: If submitting a project demo, Your project MUST be working by the time of the summit.

    Submission format

    • Submissions should be formatted as plain text of no more than 1,000 words in length and include ALLof the following:
    • The type of submission (talk, breakout session, or demo)
    • A title
    • A bio of the speaker(s) (That’s you!)
    • What you intend to talk about, the topic for your breakout session, or a description of your demo
    • An explanation the importance of your submission to the open-hardware community
    • A maximum of TWO photos that help explain your topic of submission (optional)

    Submissions should be emailed to proposals [AT] openhardwaresummit.org with the subject line “Open Hardware Summit submission” followed by the type of submission in parentheses (e.g. “Open Hardware Summit submission (breakout session)”). Deadline is JUNE 24th, 2011 BY 11:59pm (EST). Accepted submissions WILL BE PUBLISHED on the OHS website.

    For more information

    For more details about the Open Hardware Summit, see the website at openhardwaresummit.org Please direct questions about submissions to the Review Chair, David Mellis, at

    mellis [AT] media.mit.edu.

    Please direct other questions about the summit to General Chairs Alicia Gibb and Ayah Bdeir at

    info [AT] openhardwaresummit.org

    Thank you and we hope to see you in September!

  • Wednesday, June 1, 2011 - 23:09
    BUG Software R2.1.0 (based on linaro 2.6.35) now available

    Greetings BUGgers!

    TL;DR: http://wiki.buglabs.net/index.php/Changelog_2.1.0

    Release R2.1.0 is available for download.  This is a major release, utilizing a new kernel and networking API, intended for general customer use with BUGbase YT (2.0) hardware.  

    The build artifacts can be found at:




    For instructions on how to upgrade, please see:  http://wiki.buglabs.net/index.php/Software:Update_Your_BUG_Memory_Card


    An SDK release is targeted for compatibility with this release.  Stay tuned for an email regarding the SDK.


    There is no longer a redmine roadmap associated with this release, as redmine.buglabs.net is volatile at the moment due to a reorganization around our new Software Development sprints, and testing the use of pivotaltracker as our project management portal.  However, there are release notes itemizing what has been done between this and the last release, R2.0.2:



    Redmine activity associated with this project:


    Pivotal activity associated with this project:


    SVN log, from R2.0.2 to R2.1.0, for those interested in the granular activity around our OSGi stack:
    svn log -r 12986:13129 svn://bugcamp.net/bug/trunk


    Known Issues for this project:


    This release is tagged in SVN at:


    The oe layer to this release is tagged at github as well:


    In addition to the usual documentation on our wiki, there is also a Getting Started guide, in pdf form, in /home/root on the BUG SD card.  You can generate this document on the fly, thanks to Jonathan Dahan:


  • Wednesday, June 1, 2011 - 21:24
    Processing & BUG

    While using processing on ARM (via openjdk-6-zero) has been done for quite some time, (even using the Arduino IDE), we just got it working on BUG.

    Just running sketches couldn't be easier.  Processing 1.5.1 allows sketches to be exported as applications:

    created on: 06/01/11

    After hitting that, you should see the Sketch's jar in tie .pde's directory.  scp that up to bug using your favorite scp client, and just:

    java -jar Sketch.jar.

    Here's the pointillism example (in processing-1.5.1/modes/java/examples/Basics/Image/Pointillism/):

    created on: 06/01/11

    Running the IDE on BUG is pretty easy too, though I'm not sure why you'd want to...


    opkg update; opkg install openjdk-6-jdk
    wget http://processing.googlecode.com/files/processing-1.5.1-linux.tgz
    tar xzvf processing-1.5.1-linux.tgz
    cd processing-1.5.1
    rm -fr java
    ln -s /usr/lib/jvm/java-6-openjdk/ java

    After that, just ./processing and close the dialog regarding openjdk-6.  I'd suggest using it with our video module, as 320x240 isn't ideal for writing processing sketches ;D

  • Friday, May 6, 2011 - 23:16
    Solution Sprint #1 - BUGtunes

    The Challenge: Use BUG in a
    meaningful way... today


    The Proposal: Make BUG a
    wireless music server everyone can collaboratively add music to,
    create playlists with, and use.


    First: We white board the
    idea, add in possible functionality, then sketch the concept.


    1. Use Jack Server

    2. BUGmpd connect to JACK

    3. Hook up the Traffic
      Light in a meaningful way

    4. Bot Bundle “Gong”


    So now we have a quick
    outline of what we want to do. Port JACK (http://jackaudio.org/)
    to the BUG, and have that BUG control the music we listen to.

    created on: 05/06/11

    created on: 05/06/11





    The Hardware:

    1 BUGbase 2.0

    1 BUGstinger

    1 BUGvonhippel

    1 Ethernet cable (may be
    over WiFi later, but for now, ethernet is more reliable)

    1 Pair of Speakers

    1 Rusty old computer (To
    hold the music – move to cloud services later?)

    1 Traffic Light


    Step 1. Tinker:

    created on: 05/06/11

    First, Andrew Turley writes
    his wish list, then he clutters it with junk


    Step 2: Prototype the
    Traffic lights:

    created on: 05/06/11

    Andrew Tergis and Jonathan
    Dahan discuss the intricacies of controlling a traffic light with the
    BUG. What should the light do? Where should it be placed? How do we
    Future Proof it?


    For now, the traffic light
    will give Buggers some visual feedback of the popularity of the song
    currently playing. Green means no one hates it, Yellow means it has
    been tagged as annoying, Red means GONG, and the song is banned from
    the playlist for the next week or so.


    Step 3: Get to work:

    created on: 05/06/11




    Step 4: Hook up the parts:

    created on: 05/06/11

    Plug it in Turley! You can
    do it! What a sweet looking Ethernet cable.




    Step 5: Turn it on:

    created on: 05/06/11

    Pretty Lights!



    Step 6: Make it go!

    created on: 05/06/11

    OK, so it isn't beautiful,
    yet, and we don't have the traffic light set up, yet, and it's pretty
    obvious it isn't wireless, yet... but it works!



                                                                                 The Software:






    We used relaxx as our Music
    Player Deamon, which makes it act like a regular MP3 player, except
    this one is usable from the web. Now all employees can send their
    music to the server, add songs to the playlist, and even skip the bad
    songs that our Sales Engineer plays. Yes, we are sick of “Where
    Brooklyn At?” Vish, but thanks for playing.


    The Future:

    Well we gave ourselves a day
    to complete the project. We now have music playing from the BUG, and
    the traffic light is working, but we don't have the IRC bot set up to
    “Gong” and switch songs yet. I have been advised that this is a
    small fix that will occur next Friday before we start Solution Sprint
    #2: The Rise of MotherBug 2.

    Check out the lights!

    created on: 05/06/11


    Nice work team :-)

    Here is a little more about how we actually did it:



    Friday fun-days are proving
    fruitful. What would YOU do with a BUG and a day?