From f9b559649ad13435f3fc87055aa0913954e484e1 Mon Sep 17 00:00:00 2001 From: Kelsey Breseman Date: Sun, 13 Sep 2015 18:48:49 -0700 Subject: [PATCH 1/7] moved usage info to blinky and added gpio page --- _layouts/default.html | 4 +- blinky.md | 3 ++ finished.md | 2 +- usage.html => gpio.html | 2 +- gpio.md | 80 +++++++++++++++++++++++++++++++++++++ modules.md | 2 +- modules/_module_footer.html | 4 +- usage.md | 78 ------------------------------------ 8 files changed, 90 insertions(+), 85 deletions(-) rename usage.html => gpio.html (77%) create mode 100644 gpio.md delete mode 100644 usage.md diff --git a/_layouts/default.html b/_layouts/default.html index 23d8a16..6111b8c 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -88,7 +88,7 @@

tweet
  • - usage + gpio
  • finish @@ -147,7 +147,7 @@

  • - 5. usage + 5. gpio
  • 6. finished diff --git a/blinky.md b/blinky.md index 0268745..cb215c0 100644 --- a/blinky.md +++ b/blinky.md @@ -56,6 +56,9 @@ to run your code in Tessel's RAM. **Look at your Tessel!** The blue and green LEDs on your Tessel's LED panel should blink back and forth. **Bonus:** mess with the code to make the LEDs blink in sync. + +**Bonus 2:** what if you want to save blinky to your Tessel? There's a command for that! Try `t2 push blinky.js`, then unplug your Tessel and plug it back in again. Wait for it to boot up, then... lights will blink! Tired of the blinking lights? `t2 erase` will clear the saved code. Learn more `t2` commands by running `t2 -h` or looking at the [T2 CLI docs](https://tessel.io/docs/cli). + diff --git a/finished.md b/finished.md index 150a470..48d4812 100644 --- a/finished.md +++ b/finished.md @@ -28,6 +28,6 @@ You've completed the Tessel Tutorial!
    - Prev: CLI Usage + Prev: GPIO
    diff --git a/usage.html b/gpio.html similarity index 77% rename from usage.html rename to gpio.html index 92b97d9..89a8b33 100644 --- a/usage.html +++ b/gpio.html @@ -3,6 +3,6 @@ --- {% capture include_install %} -{% include_relative usage.md %} +{% include_relative gpio.md %} {% endcapture %} {{ include_install | markdownify }} diff --git a/gpio.md b/gpio.md new file mode 100644 index 0000000..e89799f --- /dev/null +++ b/gpio.md @@ -0,0 +1,80 @@ +{::options parse_block_html="true" /} + +
    +
    + +# Beyond Modules + +
    +
    + +Tessel's two module ports are not just for modules! They can also be used as flexible, simply addressable GPIO (general purpose input/output) pins. + +What does that mean? It means you're not limited to Tessel's ten-pin modules. In theory, you can connect nearly any electronic device or sensor to Tessel! + +
    +
    + +![](https://raw.githubusercontent.com/rwaldron/tessel-io/master/fritzing/tessel.png) + +
    +
    + +
    +
    + +### Community modules + +For an experience nearly as easy as Tessel's ten-pin module experience, take a look at the [Community Modules](https://tessel.io/modules#third-party). + +These are hardware components for which members of the community have created npm libraries, documentation, and wiring information. + +Here are a few: + +
    +
    + +
    +
    + +
    +
    + +
    +
    +
    +
    + +
    +
    + +
    + +
    +
    + +
    +To see more community-created modules (or to add one you've made!) go to [tessel.io/modules](https://tessel.io/modules#third-party). + +### Making your own Modules + +If no one has made the module you want yet, you can be the first! There are a lot of cool components on [SparkFun](//sparkfun.com) and [Adafruit](//adafruit.com) that are fairly easy to connect to Tessel. + +In case you've never built anything with hardware before, we've put up an introduction at [tessel.io/diy](//tessel.io/diy) that should get you up and running. + +Share what you've made, and if you need help, [just ask](https://forums.tessel.io/c/community-modules). Happy inventing! + +
    +
    + +
    + +
    +
    + Prev: Modules +
    + +
    + Next: Finished +
    +
    diff --git a/modules.md b/modules.md index 2888e75..b0d08cc 100644 --- a/modules.md +++ b/modules.md @@ -53,7 +53,7 @@ Modules should be plugged in so that all of the electrical components are on the
    ## Choose a module below to get up and running -If you've already tried out your modules, move on to [Usage.](usage.html) +If you've already tried out your modules, move on to [other uses for the module ports.](gpio.html) * [Accelerometer](modules/accelerometer.html) * [Ambient (Light + Sound)](modules/ambient.html) diff --git a/modules/_module_footer.html b/modules/_module_footer.html index 3e16229..3bafb5a 100644 --- a/modules/_module_footer.html +++ b/modules/_module_footer.html @@ -3,7 +3,7 @@

    Choose another module

    Or if you're all set, move on to CLI usage.

    +"../gpio.html">other uses for the module port.

    - Next: CLI + Next: Beyond modules
    diff --git a/usage.md b/usage.md deleted file mode 100644 index 30fd778..0000000 --- a/usage.md +++ /dev/null @@ -1,78 +0,0 @@ -{::options parse_block_html="true" /} - -
    -
    - -# Some useful commands... - -You can look at all the options of Tessel's CLI by running - -`t2 -h` - -Or go to the [Tessel 2 CLI docs](//tessel.io/docs/cli). Here are a few of the most useful ones: - -### `t2 run `` - -This command loads code into RAM on Tessel. When Tessel is reset (or the script ends with CTRL + C), Tessel loses the code. This command is useful for running code while developing, and is used throughout this tutorial. - -This command is shown in the [blinky example.](blinky.html) - -`t2 run blinky.js` - -{% highlight sh %} ->> Bundling directory ... ->> Deploying bundle ... ->> Running script ... ->> "I'm blinking! (Press CTRL + C to stop)" ->> "I'm blinking! (Press CTRL + C to stop)" ->> "I'm blinking! (Press CTRL + C to stop)" ->> ... -{% endhighlight %} - -### `t2 push ` - -This command saves code into flash memory on Tessel. This means that Tessel auto-runs this code when powered. The code will stay on here even if you restart Tessel. - -If you "tessel run" while you have code saved in Flash, the new code will run until the Tessel is reset, and then Tessel will switch back to the code from Flash. - -From your "tessel-code" directory, where you saved blinky.js, - -`t2 push blinky.js` - -{% highlight sh %} ->> Bundling directory ... ->> Deploying bundle ... ->> Running script ... ->> Finished deployment -{% endhighlight %} - -### `t2 erase` - -This command erases any JavaScript code saved to Tessel's flash memory. The firmware is left unchanged. If you push buggy code to Tessel, an erase can remove your code. - -Try unplugging and replugging in your Tessel after you have loaded the blinky code in Flash (tessel push). After a few seconds, you should see the LEDs start to blink. - -Now run: - -`t2 erase` - -{% highlight sh %} ->> Attempting to erase filesystem -{% endhighlight %} - -This will erase the blinky code from Tessel, and the LEDs will stop blinking. - -
    -
    - -
    - -
    -
    - Prev: Modules -
    - -
    - Next: Finished! -
    -
    From 4d9a57c92d73f107fafb09bfacf12d7094e2d495 Mon Sep 17 00:00:00 2001 From: Kelsey Breseman Date: Sun, 13 Sep 2015 21:37:55 -0700 Subject: [PATCH 2/7] add link to hardware api docs --- gpio.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gpio.md b/gpio.md index e89799f..3c07754 100644 --- a/gpio.md +++ b/gpio.md @@ -8,7 +8,7 @@
    -Tessel's two module ports are not just for modules! They can also be used as flexible, simply addressable GPIO (general purpose input/output) pins. +Tessel's two module ports are not just for modules! They can also be used as flexible, simply [addressable GPIO](//tessel.io/docs/hardwareAPI) (general purpose input/output) pins. What does that mean? It means you're not limited to Tessel's ten-pin modules. In theory, you can connect nearly any electronic device or sensor to Tessel! From 2f07c8d0a988d93432543f1fc84923464598b930 Mon Sep 17 00:00:00 2001 From: Kelsey Breseman Date: Sun, 13 Sep 2015 21:40:40 -0700 Subject: [PATCH 3/7] filename consistency in blinky --- blinky.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blinky.md b/blinky.md index cb215c0..b364fb3 100644 --- a/blinky.md +++ b/blinky.md @@ -57,7 +57,7 @@ to run your code in Tessel's RAM. **Bonus:** mess with the code to make the LEDs blink in sync. -**Bonus 2:** what if you want to save blinky to your Tessel? There's a command for that! Try `t2 push blinky.js`, then unplug your Tessel and plug it back in again. Wait for it to boot up, then... lights will blink! Tired of the blinking lights? `t2 erase` will clear the saved code. Learn more `t2` commands by running `t2 -h` or looking at the [T2 CLI docs](https://tessel.io/docs/cli). +**Bonus 2:** what if you want to save blinky to your Tessel? There's a command for that! Try `t2 push index.js`, then unplug your Tessel and plug it back in again. Wait for it to boot up, then... lights will blink! Tired of the blinking lights? `t2 erase` will clear the saved code. Learn more `t2` commands by running `t2 -h` or looking at the [T2 CLI docs](https://tessel.io/docs/cli).
    From 57f33dee62de133575bed432c153cf955c545781 Mon Sep 17 00:00:00 2001 From: Kelsey Breseman Date: Sun, 13 Sep 2015 23:16:55 -0700 Subject: [PATCH 4/7] extra bonus --- blinky.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blinky.md b/blinky.md index b364fb3..dcd395a 100644 --- a/blinky.md +++ b/blinky.md @@ -57,7 +57,7 @@ to run your code in Tessel's RAM. **Bonus:** mess with the code to make the LEDs blink in sync. -**Bonus 2:** what if you want to save blinky to your Tessel? There's a command for that! Try `t2 push index.js`, then unplug your Tessel and plug it back in again. Wait for it to boot up, then... lights will blink! Tired of the blinking lights? `t2 erase` will clear the saved code. Learn more `t2` commands by running `t2 -h` or looking at the [T2 CLI docs](https://tessel.io/docs/cli). +**Extra bonus:** what if you want to save blinky to your Tessel? There's a command for that! Try `t2 push index.js`, then unplug your Tessel and plug it back in again. Wait for it to boot up, then... lights will blink! Tired of the blinking lights? `t2 erase` will clear the saved code. Learn more `t2` commands by running `t2 -h` or looking at the [T2 CLI docs](https://tessel.io/docs/cli).
    From 93b8f6cb53c05857274fdc8a1885d96e97eee982 Mon Sep 17 00:00:00 2001 From: Kelsey Breseman Date: Tue, 15 Sep 2015 22:10:43 -0700 Subject: [PATCH 5/7] link fix --- _layouts/default.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_layouts/default.html b/_layouts/default.html index 4ad37ec..a631d10 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -150,7 +150,7 @@

    5. tweet

  • - 6. gpio + 6. gpio
  • 7. finished From 2dc0824241b81b82d4c9ec9abdea6cb8f5ac2ceb Mon Sep 17 00:00:00 2001 From: Kelsey Breseman Date: Tue, 15 Sep 2015 22:44:26 -0700 Subject: [PATCH 6/7] improvements to gpio page --- gpio.md | 28 +++++++++++----------------- 1 file changed, 11 insertions(+), 17 deletions(-) diff --git a/gpio.md b/gpio.md index 3c07754..e84252d 100644 --- a/gpio.md +++ b/gpio.md @@ -6,49 +6,41 @@ # Beyond Modules
    -
    - -Tessel's two module ports are not just for modules! They can also be used as flexible, simply [addressable GPIO](//tessel.io/docs/hardwareAPI) (general purpose input/output) pins. +
    -What does that mean? It means you're not limited to Tessel's ten-pin modules. In theory, you can connect nearly any electronic device or sensor to Tessel! +[![](https://raw.githubusercontent.com/rwaldron/tessel-io/master/fritzing/tessel.png)](https://github.com/rwaldron/tessel-io/tree/master/fritzing)
    -
    +
    -![](https://raw.githubusercontent.com/rwaldron/tessel-io/master/fritzing/tessel.png) +Tessel's two module ports are not just for modules– they can also be used as flexible, simply [addressable GPIO](//tessel.io/docs/hardwareAPI) (general purpose input/output) pins. +What does that mean? It means you're not limited to Tessel's ten-pin modules. In theory, you can connect nearly any electronic device or sensor to Tessel! + +### Community modules
    -### Community modules - For an experience nearly as easy as Tessel's ten-pin module experience, take a look at the [Community Modules](https://tessel.io/modules#third-party). These are hardware components for which members of the community have created npm libraries, documentation, and wiring information. -Here are a few: +For example:
    - +
    -
    -
    - -
    -
    - -
    @@ -56,6 +48,8 @@ Here are a few:
    To see more community-created modules (or to add one you've made!) go to [tessel.io/modules](https://tessel.io/modules#third-party). +_Note: we're still building out Tessel 2's firmware, so you might hit some bugs trying to use community modules. If you do, please report them! We're collecting status reports on community modules [here](https://github.com/tessel/hardware-modules/issues/5)._ + ### Making your own Modules If no one has made the module you want yet, you can be the first! There are a lot of cool components on [SparkFun](//sparkfun.com) and [Adafruit](//adafruit.com) that are fairly easy to connect to Tessel. From d99cd71bf455f82048704b164be5d56ff99c6b6a Mon Sep 17 00:00:00 2001 From: Kelsey Breseman Date: Wed, 16 Sep 2015 19:47:57 -0700 Subject: [PATCH 7/7] improvements to gpio page --- gpio.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gpio.md b/gpio.md index e84252d..12bb2e6 100644 --- a/gpio.md +++ b/gpio.md @@ -38,7 +38,7 @@ For example:
    - +