• This Week in Tessel: the awesome community issue!

    Friday, July 29, 2016

    Hello, Tesselators!


    Vision and Forward Motion: Development Updates

    Kelsey Breseman of the Tessel Project Steering Committee has just published a post with the Project’s long-term vision: Where are we going with Tessel? Rust, Reach, and Fractal

    International Nodebots Day

    NodeBots Day is world wide event where people learn how to control the physical world with JavaScript. Each event has experts on hand to help attendees build their projects and start them on the path to building awesome devices. Overall, it’s about getting together, collaborating and hacking. And lots of JavaScript. This year some events will using the new Johnny-Five Inventor’s Kit (J5IK), which includes the Tessel 2!

    International Nodebots Day: July 30

    More Tessel: Links Roundup

    Things to try

    Things to watch and read

    That’s all for this week! Feel free to submit to the next newsletter. In the meantime, see you online.

    With love,
    Everyone at the Tessel Project

    This Week in Tessel is where we highlight the latest news, projects, and events, from code, to community, to hardware manufacturing.

    #update #updates #this week in tessel #twit

  • Where are we going with Tessel? Rust, Reach, and Fractal

    Friday, July 15, 2016

    The Tessel Project’s mission is to create a fully open source hardware & software platform that makes it easy and intuitive to develop Internet-connected devices.

    With Tessel 1, we tackled the “easy and intuitive” part of that mission statement. This is the main strength of the Tessel platform. Thus far, we’ve best fulfilled these two of our core philosophies:

    Developer experience is paramount. Tessel should be the fastest way to build an idea, regardless of your background (or lack thereof) in electrical engineering or computer programming. Branding, documentation, and engineering design decisions should always take this into account.

    Device design should focus on user experience rather than on implementation. Tessel uses high level languages and modular plug & play hardware (see philosophy here) so that device creators can fully prototype and test device functionality before worrying about optimization and implementation specifics.

    We kept these values with Tessel 2, and began efforts to help developers scale. This pushes toward another core belief:

    Tessel should be practical to use. Tessel as a platform cannot have a big impact unless it is cost effective, reliable, and available for purchase. It needs to be possible to purchase Tessel hardware at affordable prices, from quantity one up to production-level quantities (10,000+).

    (Emphasis added.)

    Where we are: the vision of Tessel 2

    When we designed Tessel 2, we envisioned it as the basis of full-scale products. At the core of its design was the key idea:

    People should be able to scale the tools they use for prototyping all the way into production.

    This is a radical idea.

    If you’re a Node developer, this prototyping –> production path feels familiar. Design is an iterative process; you understand technology and needs better as you build. Modularity lets you swap out packaged components according to your needs. Both Node.JS and Tessel subscribe to modularity. Node has proven out that this approach can scale to production.

    In hardware, this is nearly unheard of. It is common to build a first prototype to show technical viability, then throw it out. For production, you start again from scratch to design a PCB that works with parts you can get at the x1000 scale.

    With Tessel 2, we say: you shouldn’t have to. This concept drove the following design decisions:

    • We chose components so that you can use the same ones in production. Every part used for Tessel 2 will continue to be manufactured and supported for a few years. Each can be sourced in low (100x) quantities.
    • Tessel 2 was designed in KiCad. This is perhaps the only free, open, fully-featured electrical engineering design tool available. Beyond publishing our design files, we want to make sure you can change and build on what we’ve created.
    • Tessel 2 is physically laid out so that you can easily remove features. A block diagram of Tessel’s hardware corresponds to its physical layout, so if you don’t need e.g. the ethernet port, you can remove it from the design (and save yourself the cost of the header) in your final product.

    Tessel 2 block diagram

    This takes open source hardware (OSHW) beyond just licensing. We want you to take our designs and use the parts of them you need in your own products. With your help, we can push the boundaries of OSHW. OSHW should be a platform for serious product development, not only a sharing marketplace for makers.

    Openness promotes innovation. Tessel is fully open source, hardware and software, so that developers can create and build on these efforts, as projects and as products, without worry of legal hassle. This project seeks to expand and promote openness as a movement in both software and hardware, and be a leader in community developed hardware.

    At the crossroads

    Now that we’ve shipped Tessel 2, there are several things we could do:

    1. Keep adding features in software, like support for more languages or features
    2. Build more modules to expand the platform
    3. Work on a “Tessel 3” that is an evolution of the board
    4. Work on a “Tessel X” that uses some of the same tooling but suits a different niche
    5. Something else, which approaches the mission in a different way

    This is where the Steering Committee comes in: we determine the project’s vision and create plans for future development. This is our first major vision decision since we moved to an open governance model.

    Here are the factors that drive this decision:

    • Mission and core principles

    • Logistical implications of our decisions

    • Needs of our community

    Critically, we need to pick projects that are well-scoped and highly focused. This lets us make measurable progress with the time and person-power we have available.

    All of these projects are arguably worthwhile. Which is best?

    Fulfilling the vision

    Coming back to the core, we want to build the OSHW movement through our platform. Tessel 2’s vision is well suited to this problem: the product lets people from varying backgrounds create products quickly and easily.

    We’ve come some of the way towards making Tessel 2 the base for a product you can take to market. But we’re not all the way there yet. Here are some of the issues we see:

    1. It’s not easy for most of the Tessel community to take the tools we’ve created so far and go to market. What do you do after you have a prototype– efficiency changes? Printing your own boards? Even if you knew what to do after building a prototype on Tessel 2, you might not know how to do it.

    2. Connected device products tend to exist in a networked configuration. This usually involves several low-cost, low-power devices. A standard for usability in this vein is the ability to run on a battery for months to years. This makes Tessel 2 not well suited to a lot of product applications.

    3. You can optimize to a point, but at the end of the day you are running JavaScript. This might not be as efficient or as reliable as you want your product to be. Additionally, you might have needs that are not supported in the language.

    A path forward: Rust, Reach, and Fractal

    We think we can work on these problems such that their solutions build upon each other. Here’s the idea:

    1. Work on improved Rust support. The Rust language executes code much faster and more robustly than JavaScript. It should serve well in production. The code is pretty legible, and it’s a welcoming community with good documentation. We’ve already begun tooling for this on the tessel-rust repo. Work on Rust doesn’t mean reduced support for or interest in JavaScript. We think they have the potential to play well together. Both will have first-class support.

    2. Build on this for our Tessel Reach project: cheap, low-power boards. Think of a Reach board as a wireless extension cable from a Tessel 2 to a module– this is how it should feel to use one. You can see a bit more detail on this issue.

    3. Use the JavaScript –> Rust compilation work to begin building the Fractal project. Fractal is software tooling to help you optimize your prototype into production. Explicit hardware requirements and memory-efficient software can let us begin to suggest hardware optimization. This would move toward comprehensible messaging. Examples might be: “Compile to Rust and reduce your file size of X to Y.” “You aren’t using Module Port B, remove it?” and “You’re only using Y memory- you may want to consider this cheaper chip (link)”.

    What do you think?

    This is the beginning of a plan. It’s an outline of a roadmap of a vision, and it’s going to be a lot of work.

    For me, it’s an inspiration. I want to work in the context of a grand plan. And it’s my hope that this grand plan excites and inspires you, too.

    When it comes down to it, that’s the crux. What do you think? Is this something you’re excited about building, and do these tools feel like they would be useful to you? Per our final core philosophy:

    Community matters. This project should be a welcoming, inclusive, and respectful place. It’s important to communicate, to question, and to come together.

    Please reach out on this issue, share your knowledge and use cases, and let us know what you think. We need to hear if you’re excited, if you’re unexcited, or if there’s something in particular you want to do. Because in the end, the Tessel Project is built out of the community, and we can’t do it without you.

    See you soon.

    Kelsey Breseman, on behalf of the Tessel Project Steering Committee

    #tessel project #vision #rust #reach #fractal #kelsey breseman #steering committee #open governance #open source #OSHW #mission #core philosophies

  • Meet a Tesselator - Nick Hehr

    Thursday, July 7, 2016

    Nick Hehr at Disneyland

    What is your favorite fiction/non-fictional robot?

    My favorite robot is Wall-E, which is not a surprise if you know about my admiration for Disney/Pixar animation. I really like Wall-E’s curiosity and sense for exploration, while imaging how various everyday items could be used in different ways.

    Wall-E lightbulb gif

    How did you discover Tessel?

    I kept seeing all these neat hardware projects and hearing great talks by folks like Suz Hinton and Francis Gulotta in the New York JavaScript meetup community, but I didn’t have an idea of what to build for the longest time. Once I finally came up with an idea, the Tessel 2 was the best match for the constraints of the project (JavaScript-friendly, affordable price, open source). Then I got the chance to meet some folks from the Tessel team at the jQuery Dev Summit 2015 and the experience left me wanting to continue working with the platform even more.

    What’s your role / what have you contributed to Tessel?

    I started contributing to the Tessel project at the jQuery Dev Summit, where I met some of the project founders, starting with some documentation and then experimenting with new features for t2-cli. One of my favorite contributions has been adding the ability to start a wifi signal (access point) on the Tessel using t2-cli, as well as adding that ability to the tessel node firmware. Recently, I was invited to join the steering committee for the project, which I happily accepted. I look forward to helping the Tessel project become a welcoming and inclusive community for folks to get started with hardware development.

    What is something you enjoyed building with Tessel?

    One of my early projects was something I built for a local meetup talk, showing how I got started with Tessel as someone new to hardware. With a plain t-shirt, an Adafruit Gemma, some sewable LEDs, and a Tessel 2, I served a web app through a Tessel access point that allowed folks in the audience to control the lights on my shirt. It was really fun to create an interactive hardware demo that didn’t depend on the event’s wifi network to work. The most difficult part for the whole project ended up being the sewing! All the detail for building that project can be found in this repo.

    What advice do you have for aspiring Tessel contributors?

    No matter what your experience with hardware or open source, there is usually some way to start contributing to the project. It could be documentation, tutorials, community outreach, design, or code, all are important for the continued maintenance and development of Tessel. The Tessel team is always working to improve how folks are introduced to the project, so any constructive feedback or questions about the contribution experience is extremely helpful.

    #meet a tesselator

  • Ramping up Rust, Backing away from Python, Johnny Five Inventor's Kit, Tessel Talks

    Thursday, June 30, 2016

    Hello, Tesselators!


    Multiple language support

    Ramping up Rust

    We’ve long been intrigued by the Rust Programming Language, and have lately been pushing forward for a more native Rust support experience, including easy deploy from the t2 command line tool.

    We will have a beta version of Rust support available in the next CLI release. We’re using a remote cross-compilation server to build Rust projects for Tessel (so you don’t even need Rust installed on your computer) but plan to switch to defaulting to rustup in the near future so Rustaceans can easily cross-compile locally.

    Currently, support is limited to blinking LEDs on Tessel 2, but our next step is to build out support for all the Tessel 2 hardware with the tessel-rust repository. We’ll also need to port all of our module libraries from JavaScript to Rust; this could be an excellent way to learn more about Rust, so please get in touch in the #rust-lang channel of Tessel Slack if you’re interested in contributing or reviewing code!

    Backing away from Python

    Ever since our announcement of Python on Tessel 2 last year, we’ve been waiting eagerly for a crowd of Pythonistas to charge in and excitedly exclaim, “I want that! I want to make that happen!”

    However, we haven’t seen it. The basic pathway for Python on Tessel 2 has been proven out, but we haven’t heard from anyone who’s interested in taking on full support - or even much interest for using it. So we’re letting it go. You’ll see it disappear from the homepage soon. We can always pick up from here if the enthusiasm arrives.

    Introducing the Johnny Five Inventor’s Kit

    We’re very excited to announce that a collaboration with Bocoup and Sparkfun has recently come to fruition in the form of the Johnny Five Inventor’s Kit.

    The Tessel 2-based kit focuses on electronics learning, with breadboards and standard electronic components rather than modules. If you’ve ever been interested in prototyping beyond Tessel modules, the detailed and beginner-friendly new experiment guide will walk you through it.

    Talks and projects from the community

    Recent Tessel talks:

    In time for the 4th of July, try making your own any-color VR fireworks with this Tessel 2 + Oculus project by Ron Dagdag.

    See Tesselators at events around the world:

    • Kelsey and Flaki are speakers at RuhrJS in Bochum, Germany on July 2-3.
    • Jon and Kelsey will give a Tessel 2 hackathon with prizes at Fullstack in London on July 13-15.
    • Keep an eye out for more speaking announcements soon!

    Want to give talks and join Tessel’s speaker community? Find opportunities and make announcements on the #events-speaking channel of the Tessel Slack.

    Development updates

    • On Tessel’s command line, the latest releases include some patching and corrections, improvements to the crash reporter tool which helps us identify and debug issues, and some background work for multiple language support.
    • In the firmware, recent releases have improved Windows USB driver support and added a few features to GPIO use of the module ports.

    Want more updates?

    You can always find our weekly steering committee notes here for the cutting edge of Tessel Project updates.

    Want to write this newsletter? It’s an easy way to stay on top of Tessel development and be a participating member of the community. Reach out to @kelsey on Tessel Slack if you’re interested.

    Until next time,

    the Tessel team

    #update #updates #this week in tessel #twit #python #rust #tessel #sparkfun

  • Tessel 2 Has Shipped!

    Monday, April 11, 2016

    We are thrilled to announce that Tessel 2 has shipped to all domestic and international pre-orders.

    This is one of the first times a distributed, unpaid team of open source contributors has shipped a physical product. We are proud to be a part of the open source hardware movement.

    Huge thanks to everyone who has contributed so far to the Tessel Project. Whether you’re a core contributor, someone who found a typo to fix, or one of our test subjects for the start experience: thank you. We value what you’ve done.

    “This sounds like a cool project, how can I get involved?”

    New contributors are always welcome! Here are a few ways to get involved:

    You can read more about how the Tessel Project works as an organization under open governance on the Tessel Project repo.

    “I just got my Tessel 2, what do I do?”

    The best place to start with your Tessel 2 is at tessel.io/start. You can find tutorials there for everything from blinking lights to tweeting to creating your own local internet.

    If you’re interested in trying something off the beaten path - electrical fun, advanced hacks, and more, check out tessel.io/docs. If you’re new to hardware, don’t worry! They’re intended to be accessible to electrical newbies - and if they’re not, please file an issue to let us know.

    We’re continuing to update the start experience and the Tessel 2 docs, so please check back again!

    “But wait, I don’t think mine shipped!” - if this is you, please contact support@tessel.io, and we will figure it out. Please do note that orders from Seeed Studio’s page are fulfilled by Seeed directly.

    “What’s next for the Tessel Project?”

    Phew, shipping one product was a lot of work! Realistically, there will be some bugfixing to do as all of you let us know how it’s going and what you’re working on.

    As far as a next product- no promises, but we have some ideas….

    Partially, it’s up to you: what do you want to see? What’s the best way we can further the Tessel Project Mission?

    Much love,

    The Tessel Project team

    #update #updates #shipping #tessel #tessel 2 #oshw

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