Skip to content

Reach is a remote I/O board for connecting to sensors.

Notifications You must be signed in to change notification settings

tessel/reach-wg

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

53 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Reach Working Group

Code of Conduct

We're designing Tessel Reach: a remote I/O board for connecting to sensors.

The point of Tessel Reach is to enable low-power internet-connected devices to be programmed in high-level languages - an extension of Tessel into the low-power realm, and a sensible/accessible way to connect many distributed sensor nodes to form a sensor ecosystem.

Tessel and Reach form star network whose origin is Tessel and points are Reach modules. The Tessel 2 is the entry point for the programmer.

Reach modules are low-power sensor nodes placed around a room or environment.

How to get involved:

What we're working on (and how you can help!)

Reach is a work in progress. To ship Reach, there are three projects to work on:

Interaction

Current Draft: How do you interact with Reach?

How do you interface with a network of sensors? How do you perform autodiscovery? And when talking to a sensor, what is the API like to control its I/O interfaces? We're investigating these questions by designing an API proposal that we can easily prototype and test in a few common scenarios.

Firmware

Read this to get started with Reach's firmware.

We want to build a realtime firmware that can handle asynchronous radio communication, enter and wake from low power sleep modes, can handle a novel protocol design communicating with T2, and which exposes the full range of I/O. We are currently prototyping with the ESP32 architecture: we recommend using the Sparkfun ESP32 Thing with a corresponding tutorial. (You can also choose another dev kit like the DevKitC from Adafruit, with some adjustments to your setup.)

Hardware

Our goal is to design an ESP32 board that allows us to rapidly test out our product requirements, get out prototype hardware to contributors, and test out real world workloads like speed, power consumption, and radio range. See hardware-esp32/ for a work in progress schematic and BOM.

License

Software licensed under MIT or Apache 2.0, at your option.

Hardware designs licensed under CC-BY-SA.