• Tessel at Conferences

    Saturday, June 6, 2015

    6/8/15– Kelsey Breseman

    It’s conference season, and there are a lot of open calls for speakers! Consider presenting in the hardware/IoT space with Tessel– audiences are curious about the new field, and we’re here to support you.

    Why give a talk?

    Being a speaker is the most effective (and I think most enjoyable) way to experience a conference. You stand on a stage and talk about something you find interesting for just a few minutes. Then, for the rest of the conference, you’ll be approached by people who want to talk to you about that same interesting thing.

    As a speaker, you’re providing part of the conference’s value. Other speakers go to a conference to learn from each other, including you. You’ll likely get to know and talk to the people you went to the conference to see, because they came to see you as well.

    Organizers, particularly in the JS community, recognize the value you’re adding to the conference and work to make it easier for you. Speakers generally get free entry to the conference, and often airfare/lodging covered as well. If you’re interested in the conference, it’s definitely worth considering becoming a speaker.

    What can I talk about?

    Present whatever you’re excited about sharing! Have you made a cool project? Do you have ideas about the connected world? What insights do you have into open source projects and communities? I’ve given Tessel-related talks on human-computer interaction, the Node community, projects, and technical details of the project. It all depends on the audience and what you have to share.

    Or if you’re just excited about sharing the technology, many conferences offer workshop sessions and hackathons. This is my personal favorite “speaker” role– helping people build something in the physical world, often for the first time. If you’re interested in doing this, please reach out to me (kelsey at technical.io)! Since you likely don’t have 20 Tessels to run a workshop, we’re happy to lend you some.

    Get inspired by previous talks!

    First-time speakers: I’d like to offer you a note of particular encouragement. New faces, fresh perspectives, are particularly sought out by conference organizers. See the next section for Calls for Speakers.

    How can we help?

    We’re here to support you! Join us on Tessel’s community chat on Slack– we have an #events-speaking channel where you can come to ask questions or find someone to preview your talk. We also sometimes announce relevant conferences there, some of which are specifically asking for Tessel talks.

    You can also find a great number of calls for papers/calls for speakers on Lanyrd, a directory of conferences.

    When you’re building your slides, please feel free to borrow (with credit) from previous presentations! You can also find Tessel-related image assets on the press page. Videos of some past Tessel-related talks can be seen here.

    Leading up to your talk, please reach out! We are always excited to help promote your Tessel talk on Twitter and the forums. We’ll retweet photos from your presentation, and would love to share your slides as well– submit pull requests on the presentations repo!

    Get out there! And don’t hesitate to ask me for advice or talk suggestions– I’m @selkeymoonbeam on Twitter.


    #speaking #workshops #conferences #presenter #speaker #kelsey breseman #presenting #cfp

  • This Week in Tessel – June 3, 2015

    Friday, June 5, 2015

    Developing Tessel 2

    Latest Tessel boards from our manufacturer! We had fifteen new Tessel 2 boards come in this shipment. 13 of these worked out of the box, and the last two were brought online with a small amount of manufacturing rework and firmware tweaks. Left to test in this batch: evaluate that all 10-pin modules operate correctly on the new boards (finishing our API implementation in the process), as well as writing more comprehensive tests for our test rig. Barring any surprises, we’ll be able to witness our next manufacturing run of Tessels in China in person!


    Zac Colley made a new community module! Connect a thermal printer to Tessel using the tessel-thermalprinter module. Includes configuration for different typefaces and barcodes.

    A presentation of “Yodazone” by Anubhooti Pareek. Help relieve stress, powered by Tessel and PubNub.

    Communicate with LEGO TECHNIC Power Functions—LEGO motors, lights, and power source units)— with this Tessel module by Andrew Cashmore.

    Using the Tessel Camera module with the Project Oxford Face APIs, by Thomas Conté.


    The Time I Took my 6 Year Old to a Hackathon, by Tim Lytle.

    Remote Control and Monitoring for Tessel Servo, by PubNub HQ.

    Tessel around the world:

    SAP held a Tessel CodeJam in the Netherlands. Microsoft Azure held an IoT hackathon in Stockholm. Tessel was at WearHacks Paris, a wearables + IoT hackathon. Wouter Verweirder presented Node on hardware at Hookedfest in Belgium.

    In our next issue, we’ll have a progress update on our manufacturing timeline, as well as several new tools to get started developing for Tessel 2. Follow us on our blog, or on Twitter at @technicalhumans. Enjoy your week! — The Tessel Team


  • Tessel Project joins Dojo Foundation under open governance

    Thursday, May 21, 2015

    5/20/15– Tim Ryan

    We have an exciting announcement to make: Ownership and direction of the Tessel Project now belongs to a Steering Committee which exists independently of Technical Machine. This group exists as part of the Dojo Foundation. [ Tweet This ] [ Learn More ]

    Tessel has become the infrastructure to prototype and build Internet-connected devices, and the starting point for makers and developers to make their ideas into reality. The Internet of Things is still very young, and we at Technical Machine want to capitalize on the opportunity to make a huge impact on these technologies as they increasingly become part of our lives.

    The Tessel Project spins out the development of Tessel, its module ecosystem, and its intuitive tooling, while retaining the manufacturing relationships and expertise gained from selling Tessel the past two years. All royalties off of selling hardware will be reinvested into the project’s own development and outreach. Our goal is an open source project that rivals the availability, manufacturing capacity, and support of more established, but often locked-down hardware solutions.

    This move to open governance borrows heavily from io.js’s Technical Committee model. It adopts explicit communication policies, clear avenues for contribution, and a culture of encouraging new contributions. By moving toward open governance, we’re hoping to make the Tessel Project a leader and a model for an open community-driven project in the hardware space.

    Passionate about Nodebots, education, or makerspaces? Interested in exploring new concepts or bringing entire products to market? Get involved as a collaborator, and you’ll be supported by a community with like-minded goals and ambitions. Or join us on Slack and share your feedback. We’d love to hear from you!

    All the best,

    Tim, Jon, Kelsey, Jia, Eric, Kevin, Kwyn, and Ken

    PS: The Tessel 2 CLI can be worked on today without needing hardware by using the Tessel 2 Virtual Machine. There are plenty of open issues that we can use help on. What ideas will you bring to Tessel?

    #tessel #tessel 2 #hardware #open source #governance #io.js #node.js #javascript #web developers #dojo #announcement

  • This Week in Tessel — May 13, 2015

    Wednesday, May 13, 2015

    Developing Tessel 2

    Manufacturing Update We’re eagerly anticipating a shipment from our manufacturer of fifteen prototype boards, expected in the next two weeks. This marks the fourth revision of Tessel 2 and the expected final design before full manufacturing.

    Developing for Tessel without Tessel The process for developing for Tessel 2 today is getting easier. Last week Jon McKay wrote a post on contributing to Tessel 2 without hardware. To make this process even easier, we are designing a command line tool to simply t2-vm run so you can get started with Tessel in just two lines.

    Rust Support How will the familiar Tessel experience be used to program in Rust? t2 init --lang rust <project_name> now creates a new Cargo project! Currently the process for targeting Rust code for a Tessel 2 is messy, but we’re working on cross-compiling the Rust standard library without needing additional tools. More Rust examples will be demoed in the upcoming weeks.

    Test Rig Eric Kolker spent time playing mechanical engineer this week. A blog post about Tessel’s entire testing process will come later, but here are some pretty renders of the publicly available test rig.

    Renders of our Test Rig


    Tessel-powered cereal dispenser As part of Fullstack Academy’s Tessel hack day, student Carlos Mendoza created an automatic cereal dispenser (or kibble dispenser?) that dispenses food at the behest of a webapp.

    New projects:

    Community Updates

    Tessel Worldwide Matteo Collina held a Tessel Workshop as part of JSDay in Verona, Italy. Plenty of hardware, plenty of cool hacks! Tessel was also spotted around the US at Fullstack Bootcamp in NYC as part of a Tessel Hack Day, apresentation at OpenWest Conf in Utah by Kevin Sidwar, and at IoT World in San Francisco.

    This Week in Tessel is sent out every Wednesday! In the next week we’ll have some exciting news for the Tessel project. Talk to you soon. — The Tessel Team

    #tessel #this week in tessel #hardware #manufacturing #design #javascript #node #io.js #code #international #updates

  • Contributing to Tessel 2 Without Hardware

    Thursday, May 7, 2015

    5/7/15– Jon McKay

    How to contribute to the Tessel project

    We’ve received quite a few inbound requests asking how folks can get involved in the development of Tessel 2. That’s why we’re excited to release a Virtual Box image that will enable you to emulate a Tessel 2 from your computer and even use your computer’s USB ports as Tessel 2 USB ports. Follow along for a quick guide on how to get up and running with the VM.

    Edit: the VM development process has been improved and you can find updated documentation on the vm repo.

    Tessel 2 features two 10-pin module ports for lower-level microcontroller peripherals and two USB ports for peripherals like flash drives, 3G dongles, and webcams. You can use the VM start building USB modules like this Node wrapper that works with most off-the-shelf webcams. It’s a great way to become a part of the core contributors before the actual hardware is generally available.

    You’ll need to install Vagrant (version 1.6 or greater) as a prerequisite. After that, you’ll need to pull down the CLI, generate an SSH key, and connect to the shiny new VM:

    # Clone the CLI repo
    > ~/projects/ git clone git@github.com:tessel/t2-cli.git
    # Link it so you can develop and use it globally
    > ~/projects/ cd t2-cli; npm link --local;
    # Generate the SSH key to use with the VM
    > ~/projects/t2-cli t2 key generate
    # From the containing folder, clone the VM repo
    > ~/projects git clone git@github.com:tessel/t2-vm.git
    # Download dependencies
    > ~/projects/ cd t2-vm; vagrant plugin install vagrant-triggers;
    # Start up the VM
    > ~/projects vagrant up

    At this point, you should be able to search for all advertising devices and list them on the command line (using mDNS):

    > ~/projects/t2-vm t2 list
    > INFO Scanning for connections...
    > INFO LAN CONNECTION ip: , name:  Tessel-080027AF44E2 , Authorized:  true

    And then you can deploy code

    # From the CLI repo...
    > ~/projects/t2-cli t2 run test/test-deploy-script.js
    > INFO Connecting to Tessel...
    > INFO Connected over LAN. IP ADDRESS:
    > INFO Bundling up code...
    > INFO Bundled. Writing to T2.... 4096
    > INFO Deployed.
    > INFO Running script...
    > If I had an actual LED, it would be on right now...
    > If I had an actual LED, it would be off right now...
    > If I had an actual LED, it would be on right now...

    Biggest issues to tackle

    We recently completed the entire spec for the Tessel 2 CLI on our forums and added Github issues for each feature that needs to be written. There are still a lot of interesting features to build for the CLI and these issues are the lowest hanging fruit.

    In addition, there are a couple of larger issues that could use some love. Please do get in touch if you’d like to get involved with these features:

    • @allanca started working on a binary server that can inject pre-compiled versions of modules with binary dependencies into bundles being deployed onto a Tessel. We need to get these changes rolled into the new CLI and the actual server deployed.
    • @nplus11 has started porting Tessel libraries to Rust including the Tessel interface and the Accelerometer Module. The CLI needs to be modified to accept Rust projects as well as JavaScript and the rest of the modules need to be ported from JS to Rust (that might be a little harder without the hardware).

    Get in touch

    We’re looking forward to see more of what the community cooks up. Get in touch with us on IRC (#tessel) or on the Forums if you have any questions or suggestions.

    #jon mckay #tessel #design #contributing #open source

August 2018

January 2018

July 2017

February 2017

November 2016

October 2016

September 2016

August 2016

July 2016

June 2016

April 2016

March 2016

February 2016

November 2015

September 2015

August 2015

July 2015

June 2015

May 2015

March 2015

February 2015

January 2015

December 2014

November 2014

October 2014

September 2014

August 2014

July 2014

June 2014

May 2014

April 2014

March 2014

February 2014

January 2014

December 2013

November 2013

October 2013

September 2013

August 2013

July 2013