diff --git a/_includes/breadcrumbs.html b/_includes/breadcrumbs.html index 212b1982e..0f9337aad 100644 --- a/_includes/breadcrumbs.html +++ b/_includes/breadcrumbs.html @@ -1,4 +1,4 @@ -{% assign parent_dirs=page.url | replace_first: '/', '' | split: '/' %} +{% assign parent_dirs=page.url | replace_first: '/', '' | split: '/' %} {% assign link='/' %}
    {% assign position = 1 %} diff --git a/_includes/icon.html b/_includes/icon.html new file mode 100644 index 000000000..c3e61544c --- /dev/null +++ b/_includes/icon.html @@ -0,0 +1,9 @@ +{% comment %} + +This template provides icons to match bootstrap alerts. + +Parameters: + +type: A name that matches an alert. Valid values are "success", info", "warning" and "danger". + +{% endcomment %}{% assign name = include.type %}{% if name == "success" %}{% assign name = "ok" %}{% elsif name == "info" %}{% assign name = "info-sign" %}{% elsif name == "warning" %}{% assign name = "alert" %}{% elsif name == "danger" %}{% assign name = "exclamation-sign" %}{% endif %} \ No newline at end of file diff --git a/_includes/screenshot.html b/_includes/screenshot.html index 6d585e3b3..4110b3e26 100644 --- a/_includes/screenshot.html +++ b/_includes/screenshot.html @@ -1 +1,10 @@ -{% if include.caption %}

    {{ include.caption }}

    {% endif %}     \ No newline at end of file +{% comment %} + +Used to format a screenshot. + +Parameters: + +source: The url of the image +caption: (optional) A caption that is displayed under the image. + +{% endcomment %}{% if include.caption %}

    {{ include.caption }}

    {% endif %}     \ No newline at end of file diff --git a/_includes/youtube-embed.html b/_includes/youtube-embed.html index a8be47b69..dd802eb23 100644 --- a/_includes/youtube-embed.html +++ b/_includes/youtube-embed.html @@ -1,4 +1,4 @@ -{% if page.youtube_video_id %} +{% if page.youtube_video_id %} {% assign video_id = page.youtube_video_id %} {% elsif include.youtube_video_id %} {% assign video_id = include.youtube_video_id %} diff --git a/_layouts/docs.html b/_layouts/docs.html index a094d7318..cf2d9c03c 100644 --- a/_layouts/docs.html +++ b/_layouts/docs.html @@ -2,13 +2,14 @@ layout: page --- +
    {% include breadcrumbs.html %}
    {% if page.kernel_version %}
    - + {% include icon.html type="info" %} This docs page is for kernel version {{ page.kernel_version }}
    {% endif %} diff --git a/docs/getting-started.md b/docs/getting-started.md index 433f43bb4..d98c1cb94 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -16,18 +16,26 @@ First, here are the things you need before starting: on the EV3. **All cards larger than 32GB will not work with the EV3!** * A computer with an adapter for the SD card. You will need administrator user permissions on this computer. -* A way to communicate. For the EV3, this can be one of the following: - * USB cable (the one that comes with the EV3) - * USB WiFi dongle - * USB Ethernet (wired) dongle - * Bluetooth +* A way to communicate. + + For the EV3, this can be one of the following: + + * USB cable (the one that comes with the EV3) + * USB WiFi dongle + * USB Ethernet (wired) dongle + * Bluetooth + For Raspberry Pi you will need to use the wired Ethernet connection first. + With PiStorms the EV3 options will work too since you have a screen to configure + them on. -
    - - The instructions on this page only apply to releases dated September -2015 or later. Older releases are no longer supported. -
    + +{% include icon.html type="warning" %} +The instructions on this page only apply to releases dated December +2015 or later. Older releases are no longer supported. There are many major changes +in the December release, so if something seems broken or the documentation seems incorrect, +please [open an issue on GitHub]({{ site.github.url }}/support){: .alert-link}. +{: .alert .alert-warning} ## Step 1: Download the latest ev3dev image file @@ -44,7 +52,7 @@ decompress it (such as [7-Zip] on Windows). ## Step 2: Copy the image on to the SD card
    - + {% include icon.html type="danger" %} This will erase everything on your SD card! Backup your files If you do not want to lose them!
    @@ -55,20 +63,38 @@ sounds the easiest to you: * **Linux** * [Command Line](../tutorials/writing-sd-card-image-linux-command-line) * [Ubuntu (graphical interface)](../tutorials/writing-sd-card-image-ubuntu-disk-image-writer) -* **Mac OS X** - * [Command Line](../tutorials/writing-sd-card-image-mac-command-line) +* **OS X** + * [Command Line](../tutorials/writing-sd-card-image-osx-command-line) + * [Apple Pi Baker (graphical interface)](../tutorials/writing-sd-card-image-osx-apple-pi-baker) * **Windows** * [Win32DiskImager (graphical interface)](../tutorials/writing-sd-card-image-win32diskimager)
    - + {% include icon.html type="info" %} For more detailed information and more alternatives, check out this page for RaspberryPi. Much of the information there is applicable to ev3dev.
    +
    +
    +{% include icon.html type="warning" %} +Raspberry Pi Only! +
    +
    +You must make some changes to `config.txt` to enable support for BrickPi or +PiStorms before you put your SD card in your Raspberry Pi. + +You may have to remove the SD card from your host computer and plug it back in +after flashing it in order for it to be detected. In your file browser, open +up `EV3DEV_BOOT`. This contains a file named `config.txt`. Open `config.txt` +in your favorite text editor and follow the instructions in the file to enable +either BrickPi or PiStorms. +
    +
    + {% include inline-screenshot.html source="/images/brickman/main-menu.png" caption="When the boot is complete, the LEDs will turn green and you will see something like this on the screen" %} ## Step 3: Boot ev3dev @@ -81,11 +107,12 @@ LEDs indicate disk (SD card) activity. **Note:** If you are using Raspberry Pi hardware without a screen, just wait for the Activity LED to stop flashing, then go to the next step. -After one or two minutes, the screen will go blank. This happens on the first boot -only. The first boot takes a little longer than subsequent boots because the EV3 +After about one minute, the screen will go blank. This happens on the first boot +only. The first boot takes longer than subsequent boots because the EV3 has to create a unique SSH host ids and take care of a few other housekeeping items. After another minute or two, you will see the *brickman loading...* screen. - +If nothing has happened after five minutes, something is not right - check the +troubleshooting tips below. You will notice the number in the battery in the upper right corner. This displays the remaining voltage of the power supply. It is not possible to @@ -95,17 +122,16 @@ data may be lost. Keep in mind, that is may take a much longer time from 8V to 6.5V than from 6.5V down to 5V!
    -
    - Troubleshooting tips if your EV3 won't boot -
    -
    -
      -
    • Make sure nothing is plugged into the EV3 (USB/sensors/motors/etc.)
      • -
    • Try writing the image to the SD card again.
      • -
    • You may have a bad/incompatible SD card - try a different SD card.
      • -
    • Check the condition of the EV3 batteries.
      • -
    -
    +
    +{% include icon.html type="info" %} +Troubleshooting tips if your EV3 won't boot +
    +
    +* Make sure nothing is plugged into the EV3 (USB/sensors/motors/etc.) +* Try writing the image to the SD card again. +* You may have a bad/incompatible SD card - try a different SD card. +* Check the condition of the EV3 batteries. +
    ## Step 4: Setup a network connection @@ -113,100 +139,71 @@ data may be lost. Keep in mind, that is may take a much longer time from 8V to There are lots of choices here. Your choice depends on what type of connection you want to use and on the OS of your host computer, so pick the one that applies: -* Ethernet over USB (just requires the USB cable that comes with the EV3) +* __Ethernet over USB__ (just requires the USB cable that comes with the EV3) * [Connecting to the Internet](../tutorials/connecting-to-the-internet-via-usb) tutorial -* USB Ethernet dongle (as in the kind with an RJ45 connector) - * If your network has a DHCP server, this will "just work". See (non-existent) brickman - docs for more info. -* USB WiFi Dongle +* __USB Ethernet dongle__ (as in the kind with an RJ45 connector) + * If your network has a DHCP server, this will "just work". +* __USB WiFi Dongle__ * Hopefully you can figure it out. I'm putting off writing detailed docs until brickman is a bit more stable. -* Bluetooth +* __Bluetooth__ * Note: Bluetooth may not work on the first boot. Please reboot if you see "???" after you power on Bluetooth. * [Connecting to the Internet](../tutorials/connecting-to-the-internet-via-bluetooth) tutorial -**Note:** For Raspberry Pi you must use the wired Ethernet port to connect for the -first time. The default host name is `ev3dev-rpi` or `ev3dev-rpi2` depending -on which model you have. You can setup additional connections using the +{% include icon.html type="info" %} +For Raspberry Pi with no display, you must use the wired Ethernet port +to connect for the first time. You can setup additional connections using the `connmanctl` command. +{: class="alert alert-info"} ## Step 5: First things to do with ev3dev Here are some suggestions of some things you should do to get ev3dev setup. +These commands are run on the EV3 in a terminal window. See the networking +tutorials above if you don't know how to open terminal window and connect via SSH. -### Change your root password +### Change your password -The default root password is r00tme - those are zeros, not "Ohs". +The default password is `maker`. - root@ev3dev:~# passwd + robot@ev3dev:~$ passwd Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully -### Set up a new user - -Replace `user` with your actual user name and `First Last` with your real name -(if you want it on the EV3 - you can leave it blank too). Don't miss the -command to assign groups hiding at the end. - - root@ev3dev:~# adduser user - Adding user `user' ... - Adding new group `user' (1001) ... - Adding new user `user' (1001) with group `user' ... - Creating home directory `/home/user' ... - Copying files from `/etc/skel' ... - Enter new UNIX password: - Retype new UNIX password: - passwd: password updated successfully - Changing the user information for user - Enter the new value, or press ENTER for the default - Full Name []: First Last - Room Number []: - Work Phone []: - Home Phone []: - Other []: - Is the information correct? [Y/n] y - root@ev3dev:~# usermod -a -G sudo,ev3dev,plugdev,audio,video,input,bluetooth,i2c user - ### Set the time zone - root@ev3dev:~# dpkg-reconfigure tzdata + robot@ev3dev:~$ sudo dpkg-reconfigure tzdata Then just follow the instructions on the screen. -**NOTE:** The EV3 does not have a battery backup for the realtime clock. +{% include icon.html type="info" %} +The EV3 and Raspberry Pi do not have a battery backup for the realtime clock. Whenever you remove the batteries, the clock will be reset. If the EV3 is connected to the Internet, the clock will be automatically set via NTP, otherwise, you can manually set the date/time with the `date` command. - +{: class="alert alert-info"} ### Set the locale You can skip this if en-US is OK. - root@ev3dev:~# dpkg-reconfigure locales + robot@ev3dev:~$ sudo dpkg-reconfigure locales ### Update packages -
    - - If you are a beginner with Linux and/or Debian, you should skip updating packages - for now. We are working on some major changes and things will be inconsisent with the - documentation if you upgrade. -
    - Make sure your EV3 is connected to the Internet first. Updating the packages for the first time will take minutes. The duration depends on the speed class of the SD card and on the updates involved. - root@ev3dev:~# apt-get update - root@ev3dev:~# apt-get upgrade - root@ev3dev:~# apt-get dist-upgrade + robot@ev3dev:~$ sudo apt-get update + robot@ev3dev:~$ sudo apt-get upgrade + robot@ev3dev:~$ sudo apt-get dist-upgrade If a new kernel package is installed, you will need to reboot. - root@ev3dev:~# reboot + robot@ev3dev:~$ sudo reboot ## Step 6: Do something awesome @@ -244,7 +241,7 @@ hang of it, you can even write your own interface library and have it listed her When you are ready to wish your EV3 goodnight, turn if off by pressing the *back* button from the main menu in brickman or pressing and holding the *back* button from any screen in brickman. This will open a dialog where you can select -*Power Off* to turn off the EV3. +*Power Off* to turn off the EV3. (Running `sudo poweroff` in a terminal works too.) [microSD]: https://en.wikipedia.org/wiki/Secure_Digital#SD [microSDHC]: https://en.wikipedia.org/wiki/Secure_Digital#SDHC diff --git a/docs/index.html b/docs/index.html index b705b7c4c..f7a431a9d 100644 --- a/docs/index.html +++ b/docs/index.html @@ -5,7 +5,7 @@
    - + {% include icon.html type="info" %} ev3dev is a community-maintained project that relies on people's contributions.
    diff --git a/docs/tutorials/connecting-to-the-internet-via-bluetooth.md b/docs/tutorials/connecting-to-the-internet-via-bluetooth.md index 2cdcf4d1b..2e2993350 100644 --- a/docs/tutorials/connecting-to-the-internet-via-bluetooth.md +++ b/docs/tutorials/connecting-to-the-internet-via-bluetooth.md @@ -3,100 +3,121 @@ title: Connecting to the Internet via Bluetooth subject: Networking --- -__Note:__ If you do not need to access the Internet from the EV3 brick, consider -using [tethering] instead. +{% include icon.html type="info" %} +If you do not need to access the Internet from the EV3 brick, consider +using [tethering]{: .alert-link} instead. +{: .alert .alert-info} [tethering]: /docs/tutorials/using-bluetooth-tethering ---- - -These instructions are for [brickman v0.5.0](http://www.ev3dev.org/news/2015/02/24/Package-Release/). +{% include icon.html type="warning" %} +These instructions are for [brickman v0.7.0](http://www.ev3dev.org/news/2015/12/15/Package-Release/){: .alert-link}. If you are using an older version, please upgrade. +{: .alert .alert-warning} -* {: tab="Android"}Note: These instructions were written using Android 4.1.2 - but should work for other versions as well. +* {: tab="Android"}{% include icon.html type="info" %} + These instructions were written using Android 4.1.2 but they should work for + other versions as well. + {: .alert .alert-info} 1. On the EV3, first verify that Bluetooth is powered on. In brickman, open the *Wireless and Networks* menu and select *Bluetooth*. Make sure the *Powered* checkbox is checked. The Bluetooth icon next to the battery in the - status bar also indicates that Bluetooth is powered on. + status bar also indicates that Bluetooth is powered on. Furthermore, make sure + the *Visible* box is checked to make the EV3 discoverable. - {% include screenshot.html source="/images/brickman/bluetooth-powered-no-devices.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-powered-visible-no-devices.png" %} 2. On your Android device, open *System settings* and make sure *Bluetooth* is turned on. - {% include screenshot.html source="/images/Android/Bluetooth/settings-bluetooth-on.png" %} + {% include screenshot.html source="/images/android/4.1.2/settings-bluetooth-on.png" %} 3. Then go to *Tethering & Mobile Hotspot* and turn on *Bluetooth tethering* - {% include screenshot.html source="/images/Android/Bluetooth/tethering-enabled.png" %} + {% include screenshot.html source="/images/android/4.1.2/tethering-enabled.png" %} 4. Go back to *Settings* and open *Bluetooth* and select your EV3 to pair it. - {% include screenshot.html source="/images/Android/Bluetooth/searching.png" %} + {% include screenshot.html source="/images/android/4.1.2/searching.png" %} 5. Confirm the passkey on both devices when requested. - {% include screenshot.html source="/images/Android/Bluetooth/pairing-request.png" %} - {% include screenshot.html source="/images/Android/Bluetooth/brickman-pairing.png" %} + {% include screenshot.html source="/images/android/4.1.2/pairing-request.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-droid4-confirm-passkey.png" %} 6. On the EV3, find your Android in the list of Bluetooth devices and and select it. - {% include screenshot.html source="/images/Android/Bluetooth/brickman-device-selected.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-droid4-selected.png" %} 7. You should have a *Network Connection* button. Select it to open the network connection settings. (You can also find the connection in *Wireless and Networks > All Network Connections*.) - {% include screenshot.html source="/images/Android/Bluetooth/brickman-device.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-droid4-network-connection-selected.png" %} - Then select *Connect*. + {% include icon.html type="info" %} + The *Connect* button pictured above is used to connect other Bluetooth + services. It **will not** connect the network connection. We need to use + *Connect* on the *Network Connection* screen below instead. + {: .alert .alert-info} - {% include screenshot.html source="/images/Android/Bluetooth/brickman-network-connection.png" %} + 8. Then select *Connect*. - *State* should change to *Online*. Go to the *IPv4* tab. It will show - the IP address of your EV3. + {% include screenshot.html source="/images/brickman/networking-droid4-connect-selected.png" %} - {% include screenshot.html source="/images/Android/Bluetooth/brickman-ip.png" %} + 9. *State* should change to *Online*. The Bluetooth icon will also indicate + that you are connected and the IP address will be displayed at the top + of the screen. - 8. For `ssh` access to the EV3 on Android, you can use an app call [ConnectBot]. + {% include screenshot.html source="/images/brickman/networking-droid4-connect-selected-online.png" %} - Run ConnectBot and start a new connection. Do this by entering `root@` + 10. For `ssh` access to the EV3 on Android, you can use an app called [ConnectBot]. + + Run ConnectBot and start a new connection. Do this by entering `robot@` where `` is the one seen on the EV3. Then press Enter on the keyboard to connect. - {% include screenshot.html source="/images/Android/Bluetooth/connectbot-1.png" %} + {% include icon.html type="info" %} + Ignore `root` in the screenshot. It is from an older version of ev3dev. + `robot` is the correct user name. + {: .alert .alert-info} + + {% include screenshot.html source="/images/android/4.1.2/connectbot-1.png" %} + {% include icon.html type="info" %} If you have never connected before, you will prompted to confirm the authenticity of the host, so select *Yes* when prompted. + {% include screenshot.html source="/images/android/4.1.2/connectbot-2.png" %} + {: .alert .alert-info} - {% include screenshot.html source="/images/Android/Bluetooth/connectbot-2.png" %} + 11. Enter your password. The default password is `maker`. - The default root password is `r00tme`. + {% include screenshot.html source="/images/android/4.1.2/connectbot-3.png" %} - {% include screenshot.html source="/images/Android/Bluetooth/connectbot-3.png" %} + 12. And you should be connected. - And you are connected. - - {% include screenshot.html source="/images/Android/Bluetooth/connectbot-4.png" %} + {% include screenshot.html source="/images/android/4.1.2/connectbot-4.png" %} [ConnectBot]: https://connectbot.org/ -* {: tab="Mac OSX"} +* {: tab="Mac OSX"}{% include icon.html type="info" %} + These instructions were written using OS X 10.10 but should work for other versions as well. + {: .alert .alert-info} 1. On the EV3, first verify that Bluetooth is powered on. In brickman, open the *Wireless and Networks* menu and select *Bluetooth*. Make sure the *Powered* checkbox is checked. The Bluetooth icon next to the battery in the - status bar also indicates that Bluetooth is powered on. + status bar also indicates that Bluetooth is powered on. (*Visible* doesn't + actually matter here.) - {% include screenshot.html source="/images/brickman/bluetooth-powered-no-devices.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-powered-visible-no-devices.png" %} 2. On your host computer, open *System Preferences* and go to *Bluetooth*. This will make your host computer discoverable. - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Bluetooth.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Bluetooth.png" %} 3. On the EV3, select *Start Scan* on the *Bluetooth* menu. It should find your computer. @@ -110,88 +131,89 @@ If you are using an older version, please upgrade. 5. Confirm the passkey on both devices when requested. {% include screenshot.html source="/images/brickman/bluetooth-confirm-passkey.png" %} - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/Pairing-Request.png" %} + {% include screenshot.html source="/images/osx/10.10/Pairing-Request.png" %} - 6. On your Mac, open up *System Preferences* and select *Network*. + 6. On your Mac, in *System Preferences*, go back and select *Network*. - {% include screenshot.html source="/images/OSXRNDIS/SystemPreferencesNetwork.png" %} + {% include screenshot.html source="/images/osx/10.9/SystemPreferencesNetwork.png" %} 7. If you do not already have a Bluetooth PAN device, click on the `+` icon in the lower left area to add a new network device. You'll need to select *Bluetooth PAN* in the drop down box. Click *Create* when you are done. - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Add-PAN.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Network-Add-PAN.png" %} 8. You may or may not see your EV3 listed next to *Device:* as shown. If you don't - see it, don't worry, thats normal. Click *Apply* to save your + see it, don't worry, that is normal. Click *Apply* to save your changes, but don't connect yet. In fact, don't try to use the *Connect* button you see here. It is for [tethering] and won't work for the connection we are setting up here. Instead, we will initiate the connection from the EV3 itself later. - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN.png" %} 9. To share our Internet connection with the EV3. Go back to *System Preferences* and select *Sharing*. - {% include screenshot.html source="/images/OSXRNDIS/SystemPreferencesSharing.png" %} + {% include screenshot.html source="/images/osx/10.9/SystemPreferencesSharing.png" %} - Click *Internet Connection* on the left, but don't check the box yet. On + 10. Click *Internet Connection* on the left, but don't check the box yet. On the right, *Share your connection from:* will be *Wi-Fi* (or *Ethernet* if you have a wired connection). Then check the box next to *Bluetooth PAN* - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Sharing-Bluetooth-PAN.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Sharing-Bluetooth-PAN.png" %} - Now check the box next to *Internet Connection* on the left to enable it. + 11. Now check the box next to *Internet Connection* on the left to enable it. Read the warning and then click *Start*. - {% include screenshot.html source="/images/OSXRNDIS/Sharing-Internet-Connection-Warning.png" %} + {% include screenshot.html source="/images/osx/10.9/Sharing-Internet-Connection-Warning.png" %} - 10. Back on the EV3, you should have a *Network Connection* button. Select it to + 12. Back on the EV3, you should have a *Network Connection* button. Select it to open the network connection settings. (You can also find the connection in *Wireless and Networks > All Network Connections*.) - {% include screenshot.html source="/images/brickman/bluetooth-device-network-connection.png" %} - - On the *IPv4* tab, select *Change...*. - - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-change-selected.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-my-computer-0-network-connection-selected.png" %} - Then choose *Load Mac Defaults*. + {% include icon.html type="info" %} + The *Connect* button pictured above is used to connect other Bluetooth + services. It **will not** connect the network connection. We need to use + *Connect* on the *Network Connection* screen below instead. + {: .alert .alert-info} - {% include screenshot.html source="/images/brickman/networking-load-mac-defaults.png" %} - - The settings on the *IPv4* tab will remain blank because we are not - connected yet. On the *Conn.* tab, check the box for *Connect automatically*. + 13. Select *Connect* here. You can also check the box for *Connect automatically*. This way you don't have to connect manually after you reboot. - {% include screenshot.html source="/images/brickman/networking-connect-automatically-selected.png" %} - - Then select *Connect*. *State* should change to *Online*. Go back to - the *IPv4* tab. It will show the IP address of your EV3. + {% include screenshot.html source="/images/brickman/networking-my-computer-0-connect-selected.png" %} - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-with-mac-defaults.png" %} + 14. *State* should change to *Online* to indicate that the EV3 has an Internet + connection. - 11. For `ssh` access to the EV3 under OS X, you can use the good old `ssh` - program from the terminal window. I'm sure there are other solutions, and - if you send me your suggestions I'll add them to a list. + {% include screenshot.html source="/images/brickman/networking-my-computer-0-disconnect-selected-online.png" %} - In a terminal, run the following command. + 15. For `ssh` access to the EV3 under OS X, you can use the good old `ssh` + program in Terminal. In a terminal, run the following command. - host:~ user$ ssh root@192.168.2.3 + ssh robot@ev3dev.local +
    +
    + {% include icon.html type="info" %} If you have never connected before, you will prompted to confirm the authenticity of the host, so type `yes` when prompted. - - The authenticity of host '192.168.2.3 (192.168.2.3)' can't be established. +
    +
    + 
    +            The authenticity of host 'ev3dev.local (192.168.2.3)' can't be established.
             RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
             Are you sure you want to continue connecting (yes/no)? yes
             Warning: Permanently added '192.168.2.3' (RSA) to the list of known hosts.
+
    +
    +
    - The default root password is `r00tme`. + 16. Enter your password. The default password is `maker`. - root@192.168.3.1's password: - Linux ev3dev 3.3.0-0-ev3dev #2 PREEMPT Wed Mar 19 20:10:05 CDT 2014 armv5tejl + robot@ev3dev's password: _____ _ _____ _|___ / __| | _____ __ / _ \ \ / / |_ \ / _` |/ _ \ \ / / @@ -206,43 +228,49 @@ If you are using an older version, please upgrade. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. - root@ev3dev:~# + robot@ev3dev:~$ -* {: tab="Ubuntu"} +* {: tab="Ubuntu"}{% include icon.html type="info" %} + These instructions were written using Ubuntu 14.04 and the default desktop. + It should work for other versions of Ubuntu, derivatives of Ubuntu and + desktop environments as well. + {: .alert .alert-info} 1. The default Bluetooth and network settings in Ubuntu do not have support for this, so first you need to install `blueman` on your host computer. sudo apt-get install blueman - Additionally, the default Ubuntu Unity desktop does not show the `blueman-applet` + {% include icon.html type="info" %} + The default Ubuntu Unity desktop does not show the `blueman-applet` icon in the notification tray. If you would like to enable this, please see - [this](http://askubuntu.com/questions/574460/blueman-indicator-missing). + [this](http://askubuntu.com/questions/574460/blueman-indicator-missing){: .alert-link}. + {: .alert .alert-info} 2. Run `blueman-services` from a terminal. (Or if you have the tray icon, right-click on it and choose "Local Services...") 3. Go to network. Ensure you activated *Network Access Point (NAP)* and *dnsmasq*. For *PAN support* choose *NetworkManager* but for *DUN-support* - choose *Blueman*. + choose *Blueman*. Then click *Close*. - {% include screenshot.html source="/images/Ubuntu-Bluetooth/blueman-services-network.png" %} + {% include screenshot.html source="/images/ubuntu/15.10/blueman-services-network.png" %} - Then click *Close*. - - Note: If your EV3 is already paired, you will need to remove it and pair it + {% include icon.html type="info" %} + If your EV3 is already paired, you will need to remove it and pair it again so that it will see the new network service. + {: .alert .alert-info} 4. On the EV3, first verify that Bluetooth is powered on. In brickman, open the *Wireless and Networks* menu and select *Bluetooth*. Make sure the *Powered* checkbox is checked. The Bluetooth icon next to the battery in the status bar also indicates that Bluetooth is powered on. - {% include screenshot.html source="/images/brickman/bluetooth-powered-no-devices.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-powered-visible-no-devices.png" %} 5. On your host computer, make sure Bluetooth is powered on and visible. - {% include screenshot.html source="/images/Ubuntu-Bluetooth/bluetooth-app-indicator-powered-visible.png" %} + {% include screenshot.html source="/images/ubuntu/15.10/bluetooth-app-indicator-powered-visible.png" %} 6. On the EV3, select *Start Scan* on the *Bluetooth* menu. It should find your computer. @@ -258,38 +286,52 @@ If you are using an older version, please upgrade. {% include screenshot.html source="/images/brickman/bluetooth-confirm-passkey.png" %} - 9. Choose *Network Connection*. + 12. You should have a *Network Connection* button. Select it to + open the network connection settings. (You can also find the connection + in *Wireless and Networks > All Network Connections*.) + + {% include screenshot.html source="/images/brickman/bluetooth-my-computer-0-network-connection-selected.png" %} - {% include screenshot.html source="/images/brickman/bluetooth-device-network-connection.png" %} + {% include icon.html type="info" %} + The *Connect* button pictured above is used to connect other Bluetooth + services. It **will not** connect the network connection. We need to use + *Connect* on the *Network Connection* screen below instead. + {: .alert .alert-info} - 10. On the Conn. tab, check the box for Connect automatically. This way you - don’t have to connect manually after you reboot. + 13. Select *Connect* here. You can also check the box for *Connect automatically*. + This way you don't have to connect manually after you reboot. - {% include screenshot.html source="/images/brickman/networking-connect-automatically-selected.png" %} + {% include screenshot.html source="/images/brickman/networking-my-computer-0-connect-selected.png" %} - Then select Connect. State should change to Online. Go back to the IPv4 tab. - It will show the IP address of your EV3 (your IP address will be different - than pictured). + 14. *State* should change to *Online* to indicate that the EV3 has an Internet + connection. - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-with-mac-defaults.png" %} + {% include screenshot.html source="/images/brickman/networking-my-computer-0-disconnect-selected-online.png" %} - 11. Now we are going to connect to the EV3 using ssh. Note: your IP address - may be different. + 11. Now we are going to connect to the EV3 using ssh. In a terminal, run the + following command. - user@host:~$ ssh root@10.25.9.98 + ssh robot@ev3dev.local +
    +
    + {% include icon.html type="info" %} If you have never connected before, you will prompted to confirm the authenticity of the host, so type `yes` when prompted. - +
    +
    + 
                 The authenticity of host '10.25.9.98 (10.25.9.98)' can't be established.
             ECDSA key fingerprint is be:9e:66:8b:d1:14:b8:8a:ea:4c:6e:07:2d:d9:68:05.
             Are you sure you want to continue connecting (yes/no)? yes
             Warning: Permanently added '10.25.9.98' (ECDSA) to the list of known hosts.
+
    +
    +
    - The default root password is `r00tme`. + 12. Enter your password when prompted. The default password is `maker`. - root@10.25.9.98's password: - Linux ev3dev 3.3.0-0-ev3dev #2 PREEMPT Wed Mar 19 20:10:05 CDT 2014 armv5tejl + robot@ev3dev's password: _____ _ _____ _|___ / __| | _____ __ / _ \ \ / / |_ \ / _` |/ _ \ \ / / @@ -304,7 +346,7 @@ If you are using an older version, please upgrade. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. - root@ev3dev:~# + robot@ev3dev:~$ * {: tab="Windows"}__HELP WANTED!__ See [issue #287](https://github.com/ev3dev/ev3dev/issues/287). {: tab-list="os"} diff --git a/docs/tutorials/connecting-to-the-internet-via-usb.md b/docs/tutorials/connecting-to-the-internet-via-usb.md index 4220907a0..14c362f0e 100644 --- a/docs/tutorials/connecting-to-the-internet-via-usb.md +++ b/docs/tutorials/connecting-to-the-internet-via-usb.md @@ -3,126 +3,102 @@ title: Connecting to the Internet via USB subject: Networking --- - -__Note:__ If you do not need to access the Internet from the EV3 brick, consider -using [tethering] instead. +{% include icon.html type="info" %} +If you do not need to access the Internet from the EV3 brick, consider +using [tethering]{: .alert-link} instead. +{: class="alert alert-info"} [tethering]: /docs/tutorials/using-usb-tethering ---- - -These instructions are for [brickman v0.5.0](http://www.ev3dev.org/news/2015/02/24/Package-Release/). +{% include icon.html type="warning" %} +These instructions are for [brickman v0.7.0](http://www.ev3dev.org/news/2015/12/15/Package-Release/){: .alert-link}. If you are using an older version, please upgrade. +{: .alert .alert-warning} -* {: tab="OS X"} - These instructions were written using OS X version 10.9, - but should work for other versions as well. - {:class="alert alert-info"} - - +* {: tab="Mac OSX"}{% include icon.html type="warning" %} If you are using OS X version 10.11, this won't work. Apple broke the USB/CDC gadget driver and has not fixed it yet (as of version 10.11.2). Please - [file a bug with Apple](https://bugreport.apple.com/) and politely ask them + [file a bug with Apple](https://bugreport.apple.com/){: .alert-link} and politely ask them to fix it. - {:class="alert alert-warning"} + {: class="alert alert-warning"} - 1. On the EV3, first verify that the CDC driver is enabled. In brickman, - open the *Wireless and Networks* menu and select *USB*. Make sure *CDC* is - selected and active. + {% include icon.html type="info" %} + These instructions were written using OS X version 10.9, but should work for + other versions as well. + {: class="alert alert-info"} - {% include screenshot.html source="/images/brickman/usb-cdc-active.png" %} + 1. Use the USB cable provided with the EV3 to connect the EV3 to your Mac. + On your Mac, open up *System Preferences* and select *Network*. - 2. On your Mac, open up *System Preferences* and select *Network*. + {% include screenshot.html source="/images/osx/10.9/SystemPreferencesNetwork.png" %} - {% include screenshot.html source="/images/OSXRNDIS/SystemPreferencesNetwork.png" %} - - 3. Once you get the *Network* dialog, click on the `+` icon in the lower left + 2. Once you get the *Network* dialog, click on the `+` icon in the lower left area to add a new network device. You'll need to select the CDC Composite Gadget in the drop down box. The name will be similar to what is shown below. I have renamed the service "ev3dev" so it's easier to keep track of later. Click *Create* when you are done. - {% include screenshot.html source="/images/OSXRNDIS/AddNewDevice.png" %} + {% include screenshot.html source="/images/osx/10.9/AddNewDevice.png" %} - 4. Click *Apply* to save your changes. After a short time, the ev3dev entry + 3. Click *Apply* to save your changes. After a short time, the ev3dev entry (or whatever you named it) should show connected and have a Self-Assigned - IP address - - {% include screenshot.html source="/images/OSXRNDIS/CDC-Connected.png" %} - - 5. If you don't need to access the Internet from your EV3 over this - connection, manually configure the IP address to `192.168.2.1`. Note: - you won't be able to update packages without an Internet connection. - - TODO: Need detailed description with screenshots. + IP address. - Then skip to step 7. + {% include screenshot.html source="/images/osx/10.9/CDC-Connected.png" %} - If you do want to be able to connect to the Internet from the EV3, continue - with the next step. - - 6. To share our Internet connection with the EV3. Go back to *System + 4. To share our Internet connection with the EV3, go back to *System Preferences* and select *Sharing*. - {% include screenshot.html source="/images/OSXRNDIS/SystemPreferencesSharing.png" %} + {% include screenshot.html source="/images/osx/10.9/SystemPreferencesSharing.png" %} - Click *Internet Connection* on the left, but don't check the box yet. On + 5. Click *Internet Connection* on the left, but don't check the box yet. On the right, *Share your connection from:* will be *Wi-Fi* (or *Ethernet* if you have a wired connection). Also check the box next to *CDC Composite Gadget* - {% include screenshot.html source="/images/OSXRNDIS/Sharing-Internet-Connection.png" %} + {% include screenshot.html source="/images/osx/10.9/Sharing-Internet-Connection.png" %} - Now check the box next to *Internet Connection* on the left to enable it. + 6. Now, check the box next to *Internet Connection* on the left to enable it. Read the warning and then click *Start*. - {% include screenshot.html source="/images/OSXRNDIS/Sharing-Internet-Connection-Warning.png" %} + {% include screenshot.html source="/images/osx/10.9/Sharing-Internet-Connection-Warning.png" %} - 7. Now, we need to assign an IP address to our EV3. In brickman, go to - *Networking* and select *Manage connections...*, then select the *Wired* - connection. + 7. Time to switch to the EV3. On the EV3, go to *Wireless and Networks* and + select *All Network Connections*, then select the *Wired* connection. {% include screenshot.html source="/images/brickman/networking-connections-wired-only.png" %} - On the *IPv4* tab, select *Change...*. - - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-change-selected.png" %} - - Then choose *Load Mac Defaults*. - - {% include screenshot.html source="/images/brickman/networking-load-mac-defaults.png" %} - - The settings on the *IPv4* tab will remain blank because we are not - connected yet. On the *Conn.* tab, check the box for *Connect automatically*. - This way you don't have to connect manually after you reboot. - - {% include screenshot.html source="/images/brickman/networking-connect-automatically-selected.png" %} - - Then select *Connect*. *State* should change to *Online*. Go back to - the *IPv4* tab. It will show the IP address of your EV3. + 9. The *Status* should change to *Connecting* and then *Online* to indicate + that you are in fact connected to the Internet. You can also check the + *Connect automatically* box so that this connection will come up automatically + in the future. - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-with-mac-defaults.png" %} + {% include screenshot.html source="/images/brickman/wired-status-online-connect-automatically-selected.png" %} - 8. For `ssh` access to the EV3 under OS X, you can use the good old `ssh` - program from the terminal window. I'm sure there are other solutions, and - if you send me your suggestions I'll add them to a list. + 9. For `ssh` access to the EV3 under OS X, you can use the good old `ssh` + program from the terminal window. In a terminal, run the following command. - In a terminal, run the following command. + ssh robot@ev3dev.local - host:~ user$ ssh root@192.168.2.3 - - If you have never connected before, you will prompted to confirm the +
    +
    + {% include icon.html type="info" %} + If you have never connected before, you will be prompted to confirm the authenticity of the host, so type `yes` when prompted. - - The authenticity of host '192.168.2.3 (192.168.2.3)' can't be established. +
    +
    + 
    +            The authenticity of host 'ev3dev.local (192.168.2.3)' can't be established.
             RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
             Are you sure you want to continue connecting (yes/no)? yes
-            Warning: Permanently added '192.168.2.3' (RSA) to the list of known hosts.
+            Warning: Permanently added 'ev3dev.local' (RSA) to the list of known hosts.
+
    +
    +
    - The default root password is `r00tme`. + 10. Enter your password when prompted. The default password is `maker`. - root@192.168.3.1's password: - Linux ev3dev 3.3.0-0-ev3dev #2 PREEMPT Wed Mar 19 20:10:05 CDT 2014 armv5tejl + robot@ev3dev's password: _____ _ _____ _|___ / __| | _____ __ / _ \ \ / / |_ \ / _` |/ _ \ \ / / @@ -137,447 +113,237 @@ If you are using an older version, please upgrade. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. - root@ev3dev:~# + robot@ev3dev:~$ -* {: tab="Ubuntu"}Note: This instructions are written for Ubuntu 14.04 using - the default desktop (aka Unity). +* {: tab="Ubuntu"}{% include icon.html type="info" %} + These instructions were written using Ubuntu 15.10 and the default desktop + (aka Unity). However, the instructions should work for other versions of Ubuntu + and its derivatives as well as other desktops like GNOME Shell, Cinnamon + and MATE. + {:class="alert alert-info"} - 1. On the EV3, first verify that the CDC driver is enabled. In brickman, - open the *Wireless and Networks* menu and select *USB*. Make sure *CDC* is - selected and active. + 1. On your host computer, with the EV3 connected via USB, open up the + network application indicator (1). You should already see an entry for + *LEGO Group EV3+ev3dev* (2). Click *Edit Connections...* (3) to open + `nm-connection-manager`. - {% include screenshot.html source="/images/brickman/usb-cdc-active.png" %} + {% include screenshot.html source="/images/ubuntu/15.10/network-application-indicator-edit-connections.png" %} - 2. On your host computer, with the EV3 connected via USB, open up *System Settings* and select *Network* + 2. In the *Network Connections* dialog, click the *Add...* button. - {% include screenshot.html source="/images/Ubuntu-CDC/System-Settings-Network.png" %} + {% include screenshot.html source="/images/ubuntu/15.10/network-connections-add.png" %} - 3. In the *Network* dialog, you should see a Wired connection that says - *Connecting*. It may say *Disconnected* instead if it has timed out already. - You can also idetentify the connection by the *Hardware Address* - it will - start with `12:16:53`. Click the *Options...* button for this connection. + 3. Make sure *Ethernet* is selected (1) and then click *Create...* (2). - {% include screenshot.html source="/images/Ubuntu-CDC/Network-Connecting.png" %} + {% include screenshot.html source="/images/ubuntu/15.10/choose-a-connection-type.png" %} - 4. In the dialog that open, change the *Connection Name* to whatever you want - (using *ev3dev* here). Select the *IPv4 Settings* tab and change the - *Method* to *Shared to other computers*. + 4. Enter a *Connection Name* (1) and select the *Device MAC Address* of your + EV3 from the list (2). The name can be anything you like. The MAC address + will always start with `12:16:53`, so choose that one. - {% include screenshot.html source="/images/Ubuntu-CDC/Network-Options.png" %} + {% include screenshot.html source="/images/ubuntu/15.10/editing-ev3dev-ethernet.png" %} - Click *Save...* when you are done. The connection will now say that it is - connected. + {% include icon.html type="info" %} + If the MAC address starts with `32:16:53` instead of `12:16:53`, this means + it is using the wrong USB configuration (technically speaking it is + trying to use RNDIS instead of CDC, which kind of works but is not as good). + Unplug your USB cable and plug it back in. + {: .alert .alert-info} - {% include screenshot.html source="/images/Ubuntu-CDC/Network-Connected.png" %} + 5. Then click on the *IPv4 Settings* tab (1) and change the *Method* to + *Shared to other computers* (2). Click *Save* (3) when you are done. - 5. Now, we need to assign an IP address to our EV3. In brickman, go to - *Wireless and Networks* and select *All Network Connections*, then select - the *Wired* connection with the USB icon. + {% include screenshot.html source="/images/ubuntu/15.10/editing-ev3dev-ipv4-settings.png" %} - {% include screenshot.html source="/images/brickman/networking-connections-wired-only.png" %} - - On the *IPv4* tab, select *Change...*. + 6. There may be a message that the network is connected. Don't believe it. + We still have to tell the EV3 to connect. You can close the *Network + Connections* dialog. We are done with it. - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-change-selected.png" %} + {% include screenshot.html source="/images/ubuntu/15.10/network-connections-close.png" %} - Then choose *Load Linux Defaults*. + 7. Now, we need to assign an IP address to our EV3. In brickman, go to + *Wireless and Networks* and select *All Network Connections*, then select + the *Wired* connection with the USB icon. - {% include screenshot.html source="/images/brickman/networking-load-linux-defaults.png" %} + {% include screenshot.html source="/images/brickman/networking-connections-wired-only.png" %} - The settings on the *IPv4* tab will remain blank because we are not - connected yet. On the *Conn.* tab, check the box for *Connect automatically*. - This way you don't have to connect manually after you reboot. + 8. Then select *Connect*. - {% include screenshot.html source="/images/brickman/networking-connect-automatically-selected.png" %} + {% include screenshot.html source="/images/brickman/wired-status-disconnected-connect-selected.png" %} - Then select *Connect*. *State* should change to *Online*. Go back to - the *IPv4* tab. It will show the IP address of your EV3. + 9. The *Status* should change to *Connecting* and then *Online* to indicate + that you are in fact connected to the Internet. You can also check the + *Connect automatically* box so that this connection will come up automatically + in the future. - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-with-linux-defaults.png" %} + {% include screenshot.html source="/images/brickman/wired-status-online-connect-automatically-selected.png" %} - 6. Now we are going to connect to the EV3 using ssh. + 10. Now we are going to connect to the EV3 using ssh. Type the following + command in a terminal window. - user@host:~$ ssh root@10.42.0.3 + ssh robot@ev3dev.local - If you have never connected before, you will prompted to confirm the +
    +
    + {% include icon.html type="info" %} + If you have never connected before, you will be prompted to confirm the authenticity of the host, so type `yes` when prompted. - - The authenticity of host '10.42.0.3 (10.42.0.3)' can't be established. - ECDSA key fingerprint is be:9e:66:8b:d1:14:b8:8a:ea:4c:6e:07:2d:d9:68:05. +
    +
    + 
    +            The authenticity of host 'ev3dev.local (10.42.0.228)' can't be established.
+            ECDSA key fingerprint is SHA256:LjEw+uEG5x7kl9LwVeynjeybuBHT3VQB5simpcVqmu8.
             Are you sure you want to continue connecting (yes/no)? yes
-            Warning: Permanently added '10.42.0.3' (ECDSA) to the list of known hosts.
+            Warning: Permanently added 'ev3dev.local,10.42.0.228' (ECDSA) to the list of known hosts.
+            Warning: Permanently added '10.42.0.228' (ECDSA) to the list of known hosts.
+
    +
    +
    - The default root password is `r00tme`. + 11. Enter your password when prompted. The default password is `maker`. - root@10.42.0.3's password: - Linux ev3dev 3.3.0-0-ev3dev #2 PREEMPT Wed Mar 19 20:10:05 CDT 2014 armv5tejl + robot@ev3dev.local's password: _____ _ _____ _|___ / __| | _____ __ / _ \ \ / / |_ \ / _` |/ _ \ \ / / | __/\ V / ___) | (_| | __/\ V / \___| \_/ |____/ \__,_|\___| \_/ - + Debian jessie on LEGO MINDSTORMS EV3! - + The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. - + Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. - root@ev3dev:~# - - -* {: tab="Windows"} - - * {: tab="7/8"} - - 1. On the EV3, first verify that the RNDIS driver is enabled. In brickman, - open the *Wireless and Networks* menu and select *USB*. Make sure *RNDIS* - is selected and active. - - {% include screenshot.html source="/images/brickman/usb-rndis-active.png" %} - - 2. Connect your EV3 to your Windows computer using the USB cable that came with - the EV3. - - 3. When it is connected, Windows will automatically install a driver for it. - **It installs the wrong driver!** We need to fix this. Open up *Control - Panel > Hardware and Sound* and select *Device Manager* - - {% include screenshot.html source="/images/WindowsRNDIS/control-panel-hard-and-sound-device-manager.png" %} - - 4. In *Device Manager*, find your EV3's RNDIS device. It is under *Network - Adapters > USB Ethernet/RNDIS Gadget*. - - {% include screenshot.html source="/images/WindowsRNDIS/device-manager-ethernet-usb-rndis-gadget.png" %} - - 5. Double-click it and select the *Drivers* tab. It says that it is using an - Acer driver, which doesn't work properly with ev3dev. Click *Update - driver...* to change the driver. - - {% include screenshot.html source="/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-acer.png" %} - - 6. Select *Browse my computer for driver software*. - - {% include screenshot.html source="/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget.png" %} - - 7. Then *Let me pick from a list of device drivers on my computer*. - - {% include screenshot.html source="/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-2.png" %} - - 8. Uncheck the box that says *Show compatible hardware*. In the *Manufacturer* - list, pick *Microsoft Corporation* (in Windows 8, pick *Microsoft*). In - the *Network Adapter* list, pick *Remote NDIS Compatible Device*. Then - click *Next*. - - {% include screenshot.html source="/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-3.png" %} - - 9. Windows thinks we don't know what we are doing, but really we do, so click - *Yes*. - - {% include screenshot.html source="/images/WindowsRNDIS/update-driver-warning.png" %} - - 10. When it is done installing, click *Close*. - - {% include screenshot.html source="/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-4.png" %} - - 11. Yea! We have the right driver now! Click *Close* again. You can close the - *Device Manager* too. We are done with it. - - {% include screenshot.html source="/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-microsoft.png" %} - - 12. Now, open up the *Network and Sharing Center* either using the notification - tray icon or using *Control Panel > Network and Internet > Network and - Sharing Center*. Click on *Change adapter settings*. - - {% include screenshot.html source="/images/WindowsRNDIS/Network-and-Sharing-Center-Change-adapter-settings.png" %} - - 13. There will be a connection that says *USB Ethernet/RNDIS Gadget*. - - {% include screenshot.html source="/images/WindowsRNDIS/Network-Connections.png" %} - - 14. This is the EV3. Let's rename it so it is easy to identify. Right-click the - *USB Ethernet/RNDIS* adapter and select *Rename*. Call it EV3 or whatever - you like. - - {% include screenshot.html source="/images/WindowsRNDIS/Network-Connections-Rename.png" %} - - 15. If you don't need to access the Internet from your EV3 over this - connection, manually configure the IP address to `192.168.137.1`. Note: - you won't be able to update packages without an Internet connection. - - TODO: Need detailed description with screenshots. + robot@ev3dev:~$ - Then skip to step 18. - If you do want to be able to connect to the Internet from the EV3, continue - with the next step. - - 16. To share our Internet connection with the EV3, Double-click the other - network connection (**not** the one we just renamed). This will show the - connection status. If you have more than one other connection, you will - want to verify that this connection is indeed the Internet connection. - - {% include screenshot.html source="/images/WindowsRNDIS/Local-Area-Connection-Status.png" %} - - 17. Click on the *Properties* button. In the window that opens, select the - *Sharing* tab and check the box that says *Allow other network users to - connect through this computer's Internet connection*. - - {% include screenshot.html source="/images/WindowsRNDIS/Local-Area-Connection-Properties-Sharing.png" %} - - If you have more than two network connections, it will ask for a "Home - networking connection". If you see this, select your EV3's network adapter - from the list (this will be called *EV3* if you renamed it earlier in the - guide). - - {% include screenshot.html source="/images/WindowsRNDIS/Local-Area-Connection-Properties-Sharing-with-Extra-Selection.png" %} - - Click *OK* when you are done and close the status window as well. Windows - will automatically reconfigure your other network connections. - - 18. Now, we need to assign an IP address to our EV3. In brickman, go to - *Networking* and select *Manage connections...*, then select the *Wired* - connection. - - {% include screenshot.html source="/images/brickman/networking-connections-wired-only.png" %} - - On the *IPv4* tab, select *Change...*. - - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-change-selected.png" %} - - Then choose *Load Windows Defaults*. - - {% include screenshot.html source="/images/brickman/networking-load-windows-defaults.png" %} - - The settings on the *IPv4* tab will remain blank because we are not - connected yet. On the *Conn.* tab, check the box for *Connect automatically*. - This way you don't have to connect manually after you reboot. - - {% include screenshot.html source="/images/brickman/networking-connect-automatically-selected.png" %} - - Then select *Connect*. *State* should change to *Online*. Go back to - the *IPv4* tab. It will show the IP address of your EV3. - - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-with-windows-defaults.png" %} - - 19. Now we are going to connect to the EV3 using ssh. To do this, you need a - program called [PuTTY]. - - Start PuTTY. In the *PuTTY Configuration* window, type the IP address that - we just saw (`192.168.137.3`). Then click the *Open* button to connect. - - {% include screenshot.html source="/images/WindowsRNDIS/WindowsRNDISPutty.png" %} - - The first time you connect, you'll get a warning about the new RSA fingerprint. - - {% include screenshot.html source="/images/WindowsRNDIS/WindowsRNDISPuttyFingerprint.png" %} - - Once you're connected, type in the userid as `root` and the password as `r00tme` and you should be connected. - - {% include screenshot.html source="/images/WindowsRNDIS/WindowsRNDISPuttyConnected.png" %} - - * {: tab="10"} - 1. On the EV3, first verify that the RNDIS driver is enabled. In brickman, - open the *Wireless and Networks* menu and select *USB*. Make sure *RNDIS* - is selected and active. - - {% include screenshot.html source="/images/brickman/usb-rndis-active.png" %} - - 2. Connect your EV3 to your Windows computer using the USB cable that came with - the EV3. - - 3. When it is connected, Windows will automatically install a driver for it. - **It installs the wrong driver!** We need to fix this. We've created - a Windows .inf file to work around this. Right-click [linux.inf] and - select *Save Link As...* to download the file (if you don't right-click, - it will just open in the browser). - - 4. Now, we need to reboot your computer in a mode that allows unsigned - drivers. Make sure all other programs are closed and all your work - is saved. Then open up Windows Settings (*Start > Settings*). Select - *Update & security*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/windows-settings-update-and-security.png" %} - - 5. Select *Recovery* in the list on the left, then click *Restart Now*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/windows-settings-recovery-restart-now.png" %} - - 6. Windows will start to shut down, then it will give you some options. - Choose *Troubleshoot*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/restart-options.png" scale="30" %} - - 7. Then choose *Advanced Options*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/restart-troubleshoot.png" scale="30" %} - - 8. Then *Startup Settings*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/restart-advanced-options.png" scale="70" %} - - 9. And finally click *Restart*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/restart-startup-settings.png" scale="70" %} - - 10. After your computer reboots, you will be prompted with a menu. Press - *7* to *Disable driver signature enforcement*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/startup-settings.png" scale="50" %} - - 11. After Windows finishes booting and you have logged in, in the search - bar, type in *Device Manager* and then click to open it. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/start-menu-device-manager.png" %} - - 12. In *Device Manager*, find your EV3's RNDIS device. It is under *Network - Adapters > USB Ethernet/RNDIS Gadget*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-rndis-gadget.png" %} - - For some people, this may appear as a COM port instead. Look under - *Ports (COM & LPT) > USB Serial Device (COM6)*. **Note:** The number - in COM6 may be different. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-serial-device.png" %} - - 13. Double-click it and select the *Drivers* tab. It says that it is using an - Acer driver, which doesn't work properly with ev3dev. Click *Update - driver...* to change the driver. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-acer.png" %} - - 14. Select *Browse my computer for driver software*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget.png" %} - - 15. Then *Let me pick from a list of device drivers on my computer*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-2.png" %} - - 16. Select *Have Disk*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-3.png" %} - - 17. Click *Browse...*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/install-from-disk-1.png" %} - - 18. Navigate to the location that you saved the `linux.inf` file earlier. - Select it and click *Open*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/locate-file-linux-inf.png" %} - - 19. Click *OK*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/install-from-disk-2.png" %} - - 20. Pick *Remote NDIS Compatible Device* from the list, then click *Next*. - - {% include screenshot.html source="/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-4.png" %} - - 21. Windows doesn't like the fact that our .inf file is not signed. Don't - worry, it just installs the Microsoft RNDIS driver (which is signed). - Nothing really dangerous here. Click *Install this driver software anyway*. +* {: tab="Windows"}{% include icon.html type="info" %} + These instructions were written using Windows 10, but should work on Windows + 7 and 8 as well. + {:class="alert alert-info"} - {% include screenshot.html source="/images/screenshots/windows/10/rndis/windows-security-install-anyway.png" %} + 1. Before connecting the USB cable, go ahead and open *Devices and Printers* + on your computer. It is in the *Control Panel* under *Hardware and Sound*. + (Or just type *Devices and Printers* in the start menu.) - 21. When it is done installing, click *Close*. + {% include screenshot.html source="/images/windows/10/devices-and-printers.png" %} - {% include screenshot.html source="/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-5.png" %} + 2. Connect your EV3 to your Windows computer using the USB cable that came + with the EV3. You should see an unknown device pop up right away. - 22. Yea! We have the right driver now! Click *Close* again. You can close the - *Device Manager* too. We are done with it. + {% include screenshot.html source="/images/windows/10/devices-and-printers-new-device.png" %} - {% include screenshot.html source="/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-ev3dev.png" %} + 3. Wait a minute for Windows install the driver. It will detect the EV3 + as a *Remote NDIS Compatible Device*. - 23. Now, open up the *Network & Internet* settings either using the notification - tray icon or the Start menu. Select *Ethernet* on the left, then click - on *Change adapter options*. + {% include screenshot.html source="/images/windows/10/devices-and-printers-rndis.png" %} - {% include screenshot.html source="/images/screenshots/windows/10/rndis/settings-network-and-internet-ethernet.png" %} + {% include icon.html type="info" %} + PROTIP: You can get an icon that looks like an actual EV3 by installing + [Programmable Brick Icons](https://github.com/ev3dev/PBrickIcons){: .alert-link}. + Follow the link for more information. + {% include screenshot.html source="https://raw.githubusercontent.com/ev3dev/PBrickIcons/master/demo1.png" %} + {:class="alert alert-info"} - 24. There will be a connection that says *USB Ethernet/RNDIS Gadget*. + 4. Right-click the *Remote NDIS Compatible Device* and select *Network Settings*. + This takes you to the *Network and Sharing Center*. - {% include screenshot.html source="/images/screenshots/windows/10/rndis/network-connections.png" %} + {% include screenshot.html source="/images/windows/10/devices-and-printers-context-menu-network-settings.png" %} - 25. This is the EV3. Let's rename it so it is easy to identify. Right-click the - *USB Ethernet/RNDIS* adapter and select *Rename*. Call it EV3 or whatever - you like. + 5. In the *Network and Sharing Center*, make a note of which connection is + your Internet connection (1) and then click on *Change adapter settings* + (2). In this example, our Internet connection is **Network 5**. - {% include screenshot.html source="/images/screenshots/windows/10/rndis/network-connections-rename.png" %} + {% include screenshot.html source="/images/windows/10/network-and-sharing-center-change-adapter-settings.png" %} - 26. If you don't need to access the Internet from your EV3 over this - connection, manually configure the IP address to `192.168.137.1`. Note: - you won't be able to update packages without an Internet connection. + 6. There will be a connection that says *Remote NDIS Compatible Device* (1). + This is the EV3. Let's rename it so it is easy to identify. Right-click + the adapter and select *Rename* (2). Call it EV3 or whatever you like. - TODO: Need detailed description with screenshots. + {% include screenshot.html source="/images/windows/10/network-connections-context-menu-rename.png" %} - Then skip to step 18. + 7. To share our Internet connection with the EV3, double-click the Internet + network connection that you noted earlier (**not** the one we just + renamed). This will show the connection status. - If you do want to be able to connect to the Internet from the EV3, continue - with the next step. + {% include screenshot.html source="/images/windows/10/network-connections-internet-adapter.png" %} - 27. To share our Internet connection with the EV3, Double-click the other - network connection (**not** the one we just renamed). This will show the - connection status. If you have more than one other connection, you will - want to verify that this connection is indeed the Internet connection. - Click on the *Properties* button. + 8. If you have more than one other connection, you will want to verify that + this connection is indeed the Internet connection (1). Then, click on the + *Properties* button (2). - {% include screenshot.html source="/images/screenshots/windows/10/rndis/ethernet-status.png" %} + {% include screenshot.html source="/images/windows/10/local-area-connection-status.png" %} - 28. In the window that opens, select the *Sharing* tab and check the box - that says *Allow other network users to connect through this computer's - Internet connection*. + 9. In the window that opens, select the *Sharing* tab (1) and check the box + that says *Allow other network users to connect through this computer's + Internet connection* (2). - {% include screenshot.html source="/images/screenshots/windows/10/rndis/ethernet-properties-sharing.png" %} + {% include screenshot.html source="/images/windows/10/local-area-connection-properties-sharing.png" %} - Click *OK* when you are done and close the status window as well. Windows - will automatically reconfigure your other network connections. + {% include icon.html type="info" %} + If you have more than two network connections, it will ask for a "Home + networking connection". If you see this, select your EV3's network adapter + from the list (this will be called *EV3* if you renamed it earlier in the + guide). + {% include screenshot.html source="/images/windows/8/local-area-connection-properties-sharing-with-extra-selection.png" %} + {: class="alert alert-info"} - 29. Now, we need to assign an IP address to our EV3. In brickman, go to - *Networking* and select *Manage connections...*, then select the *Wired* - connection. + {% include icon.html type="warning" %} + Windows Internet Connection Sharing is temperamental. Sometimes it just + stops working for no reason. If this happens, just turn it off (by unchecking + *Allow other...* and clicking *OK*) and then turn it back on. It should + start working again. + {: class="alert alert-warning"} - {% include screenshot.html source="/images/brickman/networking-connections-wired-only.png" %} + 10. Click *OK* when you are done and close the status window as well. Windows + will automatically reconfigure your other network connections. - On the *IPv4* tab, select *Change...*. + 11. Now, we need to do some setting up on the EV3. Go to *Networking* and + select *Manage connections...*, then select the *Wired* connection. - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-change-selected.png" %} + {% include screenshot.html source="/images/brickman/networking-connections-wired-only.png" %} - Then choose *Load Windows Defaults*. + 12. Internet Connection Sharing on Windows is temperamental, so we are going + to use a static IP address to make it a bit more reliable. Select *IPv4* on the menu. - {% include screenshot.html source="/images/brickman/networking-load-windows-defaults.png" %} + {% include screenshot.html source="/images/brickman/wired-status-disconnected-ipv4-selected.png" %} - The settings on the *IPv4* tab will remain blank because we are not - connected yet. On the *Conn.* tab, check the box for *Connect automatically*. - This way you don't have to connect manually after you reboot. + 13. Select *Change...*. - {% include screenshot.html source="/images/brickman/networking-connect-automatically-selected.png" %} + {% include screenshot.html source="/images/brickman/wired-status-disconnected-ipv4-empty.png" %} - Then select *Connect*. *State* should change to *Online*. Go back to - the *IPv4* tab. It will show the IP address of your EV3. + 14. Then choose *Load Windows Defaults*. - {% include screenshot.html source="/images/brickman/networking-ipv4-tab-with-windows-defaults.png" %} + {% include screenshot.html source="/images/brickman/networking-load-windows-defaults.png" %} - 30. Now we are going to connect to the EV3 using ssh. To do this, you need a - program called [PuTTY]. + 15. The settings on the *IPv4* screen will remain blank because we are not + connected yet. Go back to the previous screen and check the box for + *Connect automatically*. This way you don't have to connect manually + after you reboot. Then select *Connect*. *State* should change to + *Online* to indicate that your EV3 is connected to the Internet. - Start PuTTY. In the *PuTTY Configuration* window, type the IP address that - we just saw (`192.168.137.3`). Then click the *Open* button to connect. + {% include screenshot.html source="/images/brickman/wired-status-online-connect-selected.png" %} - {% include screenshot.html source="/images/WindowsRNDIS/WindowsRNDISPutty.png" %} + 16. Now we are going to connect to the EV3 using ssh. To do this, you need a + program called [PuTTY]. Start PuTTY. In the *PuTTY Configuration* window, + type in `ev3dev`. Then click the *Open* button to connect. - The first time you connect, you'll get a warning about the new RSA fingerprint. + {% include screenshot.html source="/images/windows/10/putty-configuration-ev3dev.png" %} - {% include screenshot.html source="/images/WindowsRNDIS/WindowsRNDISPuttyFingerprint.png" %} + {% include icon.html type="info" %} + The first time you connect, you'll get a warning about the new fingerprint. + This is normal. Just click *Yes* to continue. You won't see this again + unless you re-flash your SD card. + {% include screenshot.html source="/images/windows/10/putty-security-alert.png" %} + {: class="alert alert-info"} - Once you're connected, type in the userid as `root` and the password as `r00tme` and you should be connected. + Once you are connected, type in your username (`robot`) and your password + (`maker` if you haven't changed it yet) and then you should be logged in. - {% include screenshot.html source="/images/WindowsRNDIS/WindowsRNDISPuttyConnected.png" %} - {: tab-list="os-version"} + {% include screenshot.html source="/images/windows/10/putty-robot-at-ev3dev.png" %} {: tab-list="os"} diff --git a/docs/tutorials/using-bluetooth-tethering.md b/docs/tutorials/using-bluetooth-tethering.md index 82d479a7d..8c92f1110 100644 --- a/docs/tutorials/using-bluetooth-tethering.md +++ b/docs/tutorials/using-bluetooth-tethering.md @@ -3,17 +3,21 @@ title: Using Bluetooth Tethering subject: Networking --- -__Note:__ When using tethering, the EV3 brick will act as a network server. This +{% include icon.html type="info" %} +When using tethering, the EV3 brick will act as a network server. This means there is little to no configuration that needs to be done on your host computer which makes it easy to setup and use. However, you __cannot access the Internet from your EV3 using tethering__. If you want to be able to update packages or do anything else that requires an Internet connection, you will need to set up another connection instead of or in addition to a tethering connection. +{: .alert .alert-info} --- -These instructions are for [brickman v0.5.0](http://www.ev3dev.org/news/2015/02/24/Package-Release/). +{% include icon.html type="warning" %} +These instructions are for [brickman v0.7.0](http://www.ev3dev.org/news/2015/12/15/Package-Release/){: .alert-link}. If you are using an older version, please upgrade. +{: .alert .alert-warning} * {: tab="Mac OSX"} 1. On the EV3, first verify that Bluetooth is powered on. In brickman, @@ -21,7 +25,7 @@ If you are using an older version, please upgrade. *Powered* checkbox is checked. The Bluetooth icon next to the battery in the status bar also indicates that Bluetooth is powered on. - {% include screenshot.html source="/images/brickman/bluetooth-powered-no-devices.png" %} + {% include screenshot.html source="/images/brickman/bluetooth-powered-visible-no-devices.png" %} 2. Go back to *Wireless and Networks* and select *Tethering*. Enable tethering via Bluetooth by checking the box next to *Bluetooth*. @@ -31,7 +35,7 @@ If you are using an older version, please upgrade. 3. On your host computer, open *System Preferences* and go to *Bluetooth*. This will make your host computer discoverable. - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Bluetooth.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Bluetooth.png" %} 4. On the EV3, go back to *Wireless and Networks* and select *Bluetooth* again, then select *Start Scan*. It should find your computer. @@ -42,57 +46,63 @@ If you are using an older version, please upgrade. {% include screenshot.html source="/images/brickman/bluetooth-my-computer-not-paired.png" %} - __Note:__ If you have already paired your EV3 with your host computer, you + {% include icon.html type="info" %} + If you have already paired your EV3 with your host computer, you will need to select *Remove* and then re-pair in order for the host computer to see the new tethering network connection. + {: .alert .alert-info} 6. Confirm the passkey on both devices when requested. {% include screenshot.html source="/images/brickman/bluetooth-confirm-passkey.png" %} - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/Pairing-Request.png" %} + {% include screenshot.html source="/images/osx/10.10/Pairing-Request.png" %} 7. On your Mac, open up *System Preferences* and select *Network*. - {% include screenshot.html source="/images/OSXRNDIS/SystemPreferencesNetwork.png" %} + {% include screenshot.html source="/images/osx/10.9/SystemPreferencesNetwork.png" %} 8. If you do not already have a Bluetooth PAN device, click on the `+` icon in the lower left area to add a new network device. You'll need to select *Bluetooth PAN* in the drop down box. Click *Create* when you are done. - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Add-PAN.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Network-Add-PAN.png" %} 9. Click *Apply* first to save your changes, then select your EV3 next to *Device:* and click *Connect*. - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN.png" %} 10. Here, you can see that the EV3 assigned us the address *192.168.1.2*. The last two numbers may be different for you. The IP address of your EV3 will be the same as the number you see here with the last number replaced by *1*. So, in the case, the EV3 is at *192.168.1.1*. - {% include screenshot.html source="/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN-Connected.png" %} + {% include screenshot.html source="/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN-Connected.png" %} 11. For `ssh` access to the EV3 under OS X, you can use the good old `ssh` - program from the terminal window. I'm sure there are other solutions, and - if you send me your suggestions I'll add them to a list. + program from the terminal window. In a terminal, run the following command. - In a terminal, run the following command. - - host:~ user$ ssh root@192.168.1.1 + ssh robot@ev3dev.local +
    +
    + {% include icon.html type="info" %} If you have never connected before, you will prompted to confirm the authenticity of the host, so type `yes` when prompted. - +
    +
    + 
                 The authenticity of host '192.168.1.1 (192.168.1.1)' can't be established.
             RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
             Are you sure you want to continue connecting (yes/no)? yes
             Warning: Permanently added '192.168.1.1' (RSA) to the list of known hosts.
+
    +
    +
    - The default root password is `r00tme`. + 12. Enter your password when prompted. The default password is `maker`. - root@192.168.1.1's password: - Linux ev3dev 3.3.0-0-ev3dev #2 PREEMPT Wed Mar 19 20:10:05 CDT 2014 armv5tejl + robot@ev3dev's password: _____ _ _____ _|___ / __| | _____ __ / _ \ \ / / |_ \ / _` |/ _ \ \ / / @@ -107,21 +117,27 @@ If you are using an older version, please upgrade. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. - root@ev3dev:~# + robot@ev3dev:~$ * {: tab="Ubuntu"} - HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287). + {% include icon.html type="warning" %} + HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287){: .alert-link}. + {: .alert .alert-warning} * {: tab="Windows"} * {: tab="7"} - HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287). + {% include icon.html type="warning" %} + HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287){: .alert-link}. + {: .alert .alert-warning} This is mostly figured out for Windows 8 [here](https://github.com/ev3dev/ev3dev/issues/232#issuecomment-69801370). Windows 7 looks a bit different, so it needs its own instructions. * {: tab="8"} - HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287). + {% include icon.html type="warning" %} + HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287){: .alert-link}. + {: .alert .alert-warning} This is mostly figured out [here](https://github.com/ev3dev/ev3dev/issues/232#issuecomment-69801370). We just need someone to make it pretty. diff --git a/docs/tutorials/using-brickstrap-to-cross-compile.md b/docs/tutorials/using-brickstrap-to-cross-compile.md new file mode 100644 index 000000000..2daf30069 --- /dev/null +++ b/docs/tutorials/using-brickstrap-to-cross-compile.md @@ -0,0 +1,217 @@ +--- +title: Using Brickstrap to Cross-Compile +subject: Cross-Compiling +--- + +* Table of Contents +{:toc} + +Brickstrap is the tool that we use to create the SD card images for ev3dev. But, +it turns out that it is super-useful for working with compiled languages on +the EV3! +{: .lead .clearfix} + +## Getting Brickstrap + +
    +{% include icon.html type="info" %} +To help preserve our sanity, we are only going to officially +support using brickstrap on one OS, namely Ubuntu trusty. Also, we only +support 64-bit host machines (there are some unresolved issues that prevent +brickstrap from working correctly on 32-bit). So, if you are not already +running [trusty](http://www.ubuntu.com/download/server){: .alert-link}, +you will need to install it in a +[virtual machine](https://www.virtualbox.org/wiki/Downloads){: .alert-link}. +We recommend installing the server version because it requires less memory +and you don't need a graphical desktop for what we are doing. + +TODO: Need to create a page for setting up a VM and move this info there +because it applies to more than just brickstrap. For now, there is plenty +of documentation on setting up a VM floating around the web - just do a search. + +Also, you will find it easier to ssh into the VM so that you can have multiple +terminals open at once rather than trying to use the console in VirtualBox. +To do this, you will want to change the network adapter from NAT (default) +to bridged in the VirtualBox settings before starting the VM. +
    + +Brickstrap is available as a .deb package from the ev3dev.org package repository. +Once you have trusty up and running, run the following commands to install the +`brickstrap` package. + + sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 2B210565 + sudo apt-add-repository "deb http://ev3dev.org/debian trusty main" + sudo apt-get update + sudo apt-get install brickstrap + +Next, there are a few things we need to take care of. `brickstrap` uses a +library called `libguestfs` to build the disk image. There is some setup +required to use this. + + # create a supermin appliance + sudo update-guestfs-appliance + # add yourself to the kvm group + # need to log out and back in for this to take effect + sudo usermod -a -G kvm + # fix permissions on /boot/vmlinuz* + sudo chmod +r /boot/vmlinuz* + +And you need to add yourself to `/etc/subuid` and `/etc/subgid` to be able to +use uid/gid mapping. + + sudo usermod --add-subuids 200000-265534 --add-subgids 200000-265534 $USER + +{% include icon.html type="info" %} +Check out the [brickstrap Github page]{: .alert-link} +for the most up-to-date information on brickstrap. +{: .alert .alert-info} + +[brickstrap Github page]: https://github.com/ev3dev/brickstrap + +## Creating a Virtual Environment + +Now, create an empty directory to work in. You can name it whatever you like. +I am calling it `brickstrap`. + + mkdir brickstrap + cd brickstrap + +Then, build an image. Right now there are 3 *flavors* of ev3dev. +The `-b` option is the "board" definition that is used to build the image +It should either be `ev3-ev3dev-jessie` if you are using the EV3, +`rpi-ev3dev-jessie` for Raspberry Pi 0/1 or `rpi2-ev3dev-jessie` for Raspberry Pi 2. +The `-d` option is the name of the directory that will be created. The `create-rootfs` +command tells brickstrap to build a file system but to not actually create an +image file. This will take 20 to 30 minutes or longer depending on the speed of +your machine and Internet connection. + + brickstrap -b ev3-ev3dev-jessie -d ev3-dev-env create-rootfs + +## Working in the Brickstrap Shell + +Once `brickstrap` has finished creating the root filesystem, you can get a bash +shell inside of the directory that was created. This is almost like working in +a virtual machine except that qemu is used to run individual commands instead +of the whole thing being run inside of a virtual environment. + + brickstrap -b ev3-ev3dev-jessie -d ev3-dev-env shell + +Now, you can install packages and run programs almost just as if you were on the +actual EV3. Don't forget to run `apt-get update` first! For starters, you will +want to install `build-essential`. If you want to use any extra libraries, most +have `-dev` packages that you will need to install. We should probably setup a +non-root user, but for now, we are going to do everything as (fake)root. + + apt-get install build-essential + +There is a magical folder called `host-rootfs` inside the brickstrap shell that +that gives you access to he filesystem of your host machine. You will want to +work there so that you can access the files that create from outside of the +brickstrap shell. This is important because some things, like ssh, will not +work inside the brickstrap shell. + + cd /host-rootfs/home/user + +## Sample Program + +Let's build the classic hello world. + + mkdir hello + cd hello + cat > hello.c << EOF + #include + + int main(void) { + printf("Hello World!\n"); + return 0; + } + EOF + gcc -o hello hello.c + ./hello + +Nice. It works inside the brickstrap shell. Now, lets get it onto the EV3. You need to open a new terminal (or exit the brickstrap shell) to do this. You may need to use an IP address instead of `ev3dev` in order to connect. + + user@host:~$ cd ~/hello + user@host:~/hello$ scp hello user@ev3dev:~/ + user@host:~/hello$ ssh user@ev3dev + user@ev3dev:~$ ./hello + +## Mounting a Remote File System + +Of course, you are not going to want to copy your program like this every time +you build it. So, in order to get around this, you can mount part of the +filesystem of your host computer on the EV3. + +You have a couple of options to do this: + +* [Use nfs](https://github.com/mindboards/ev3dev/wiki/Set-Up-An-nfs-FileShare) +* [Use sshfs]() + +Both of these options essentially do the same thing, just using a different +network protocol. They make files that physically exist on your host computer +available on the EV3 as if they were real files. + +Now, you just need two terminals open. One running the brickstrap shell where +you build your program and one connected to the EV3 so that you can run the +program. + +## Using GDB + +`gdb` is the GNU debugger. TODO: need to find a good link for intro to gdb. + +Although it is possible to run gdb directly on the EV3, you will quickly run +out of memory. To get around this, we will do remote debugging. + +On your EV3, install `gdbserver`. + + sudo apt-get install gdbserver + +And in your brickstrap shell, install `gdb` + + apt-get install gdb + +Now, let's debug our hello program. First, we need to make sure we compile with +debugging symbols (thats the `-g` flag). You will need to copy the new +executable to the EV3 too if you haven't done the *mounting a remote file system* +thing yet. + + gcc -g -o hello hello.c + +On the EV3, run `gdbserver`. `host` is the name or IP address of your host +computer (or VM) and `3333` is an arbitrary TCP port. + + gdbserver host:3333 hello + +Then back in the brickstrap shell run gdb. `target remote` tells gdb to connect +to your EV3. Host name resolution seems to have issues in the brickstrap shell, +so you are better off using the IP address of your EV3 (192.168.0.100 in this +example). And of course, the port number needs to match what you used with +gdbserver. + + gdb hello + +This starts an interactive gdb session. You have to type in the commands +on each line that starts with `(gdb)`. + + ... + Reading symbols from /host-rootfs/home/david/work/brickdm/build/hello...done. + ... + (gdb) target remote 192.168.0.100:3333 + Remote debugging using 192.168.0.144:1234 + ... + (gdb) break hello.c:4 + Breakpoint 1 at 0x8428: file hello.c, line 4. + (gdb) c + Continuing. + + Breakpoint 1, main () at hello.c:4 + 4 printf("Hello World!\n"); + (gdb) c + Continuing. + [Inferior 1 (process 1821) exited normally] + qemu: Unsupported syscall: 26 + (gdb) q + +Since gdb is running in an emulated environment using qemu, you will +occasionally see errors like the unsupported syscall above. Most errors don't +seem to cause any problems, but it may limit the use of some features of gdb. diff --git a/docs/tutorials/using-ev3-buttons.md b/docs/tutorials/using-ev3-buttons.md index 2669d68ad..0ca26f92d 100644 --- a/docs/tutorials/using-ev3-buttons.md +++ b/docs/tutorials/using-ev3-buttons.md @@ -84,7 +84,7 @@ Here is an example. It prints out 2 lines each time you press a button on the EV3 and 2 more lines each time you release a button. And of course, press CTRL+C to end. - root@ev3dev:/sys/class/leds# hexdump -e \ + root@ev3dev:~# hexdump -e \ '"timestamp:%d.%6d""\t""" 1/2 "type:%i""\t""" 1/2 "code:%3i""\t""" "value:%d\n"' \ < /dev/input/by-path/platform-gpio-keys.0-event timestamp:1391366282.119886 type:1 code: 14 value:0 diff --git a/docs/tutorials/using-usb-tethering.md b/docs/tutorials/using-usb-tethering.md index 9f4d5e015..a9cb8239c 100644 --- a/docs/tutorials/using-usb-tethering.md +++ b/docs/tutorials/using-usb-tethering.md @@ -3,24 +3,32 @@ title: Using USB Tethering subject: Networking --- -__Note:__ When using tethering, the EV3 brick will act as a network server. This +{% include icon.html type="info" %} +When using tethering, the EV3 brick will act as a network server. This means there is little to no configuration that needs to be done on your host computer which makes it easy to setup and use. However, you __cannot access the Internet from your EV3 using tethering__. If you want to be able to update packages or do anything else that requires an Internet connection, you will need to set up another connection instead of or in addition to a tethering connection. +{: .alert .alert-info} ---- - -These instructions are for [brickman v0.5.0](http://www.ev3dev.org/news/2015/02/24/Package-Release/). +{% include icon.html type="warning" %} +These instructions are for [brickman v0.7.0](http://www.ev3dev.org/news/2015/12/15/Package-Release/){: .alert-link}. If you are using an older version, please upgrade. +{: .alert .alert-warning} * {: tab="Mac OSX"} - HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287). + {% include icon.html type="warning" %} + HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287){: .alert-link}. + {: .alert .alert-warning} * {: tab="Ubuntu"} - HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287). + {% include icon.html type="warning" %} + HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287){: .alert-link}. + {: .alert .alert-warning} * {: tab="Windows"} - HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287). + {% include icon.html type="warning" %} + HELP WANTED! See [issue #287](https://github.com/ev3dev/ev3dev/issues/287){: .alert-link}. + {: .alert .alert-warning} {: tab-list="os"} diff --git a/docs/tutorials/using-xv11-lidar.md b/docs/tutorials/using-xv11-lidar.md index e4ab5cf90..82945560e 100644 --- a/docs/tutorials/using-xv11-lidar.md +++ b/docs/tutorials/using-xv11-lidar.md @@ -9,12 +9,13 @@ XV11 LIDAR communicates using UART, 8N1 at 3.3V with baud rate 115200. EV3 has all the required hardware to communicate with the LIDAR and ev3dev has the software. -
    - - The instructions on this page apply to EV3. - You can also get it working with Raspberry PI and BrickPI but BrickPI doesn't support other-uart mode for sensor port and dedicated Raspberry Pi UART GPIO pins are already taken by BrickPI. - You have to figure out some other way to get the UART. USB to UART bridge could be one option. -
    + +{% include icon.html type="warning" %} +The instructions on this page apply to EV3. +You can also get it working with Raspberry PI and BrickPI but BrickPI doesn't support +other-uart mode for sensor port and dedicated Raspberry Pi UART GPIO pins are already taken by BrickPI. +You have to figure out some other way to get the UART. USB to UART bridge could be one option. +{: .alert .alert-warning} To interface the LIDAR one has to: diff --git a/docs/tutorials/writing-sd-card-image-osx-apple-pi-baker.md b/docs/tutorials/writing-sd-card-image-osx-apple-pi-baker.md new file mode 100644 index 000000000..864045f47 --- /dev/null +++ b/docs/tutorials/writing-sd-card-image-osx-apple-pi-baker.md @@ -0,0 +1,8 @@ +--- +title: Writing an SD Card Image Using Apple Pi Baker on OS X +subject: SD Card Image +--- + +{% include icon.html type="warning" %} +HELP WANTED! See {: .alert-link}. +{: .alert .alert-warning} diff --git a/docs/tutorials/writing-sd-card-image-mac-command-line.md b/docs/tutorials/writing-sd-card-image-osx-command-line.md similarity index 95% rename from docs/tutorials/writing-sd-card-image-mac-command-line.md rename to docs/tutorials/writing-sd-card-image-osx-command-line.md index dbe022c96..67228cd50 100644 --- a/docs/tutorials/writing-sd-card-image-mac-command-line.md +++ b/docs/tutorials/writing-sd-card-image-osx-command-line.md @@ -1,6 +1,8 @@ --- -title: Writing an SD Card Image Using Mac OSX Command Line Tools. +title: Writing an SD Card Image Using Command Line Tools on OS X. subject: SD Card Image +redirect_from: + - /docs/tutorials/writing-sd-card-image-mac-command-line/ --- 1. If you have not already unzipped the ev3dev disk image, lets do that first. diff --git a/images/Android/Bluetooth/brickman-device-selected.png b/images/Android/Bluetooth/brickman-device-selected.png deleted file mode 100644 index 9f5a8ad44..000000000 Binary files a/images/Android/Bluetooth/brickman-device-selected.png and /dev/null differ diff --git a/images/Android/Bluetooth/brickman-device.png b/images/Android/Bluetooth/brickman-device.png deleted file mode 100644 index e356822f7..000000000 Binary files a/images/Android/Bluetooth/brickman-device.png and /dev/null differ diff --git a/images/Android/Bluetooth/brickman-ip.png b/images/Android/Bluetooth/brickman-ip.png deleted file mode 100644 index 7e0e9d481..000000000 Binary files a/images/Android/Bluetooth/brickman-ip.png and /dev/null differ diff --git a/images/Android/Bluetooth/brickman-network-connection.png b/images/Android/Bluetooth/brickman-network-connection.png deleted file mode 100644 index 99373296e..000000000 Binary files a/images/Android/Bluetooth/brickman-network-connection.png and /dev/null differ diff --git a/images/Android/Bluetooth/brickman-pairing.png b/images/Android/Bluetooth/brickman-pairing.png deleted file mode 100644 index bbac3f9e0..000000000 Binary files a/images/Android/Bluetooth/brickman-pairing.png and /dev/null differ diff --git a/images/Mac-OS-X/Bluetooth/Pairing-Request.png b/images/Mac-OS-X/Bluetooth/Pairing-Request.png deleted file mode 100644 index 72147d5cc..000000000 Binary files a/images/Mac-OS-X/Bluetooth/Pairing-Request.png and /dev/null differ diff --git a/images/Mac-OS-X/Bluetooth/System-Preferences-Bluetooth.png b/images/Mac-OS-X/Bluetooth/System-Preferences-Bluetooth.png deleted file mode 100644 index f91612a5e..000000000 Binary files a/images/Mac-OS-X/Bluetooth/System-Preferences-Bluetooth.png and /dev/null differ diff --git a/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Add-PAN.png b/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Add-PAN.png deleted file mode 100644 index 7d8593963..000000000 Binary files a/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Add-PAN.png and /dev/null differ diff --git a/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN-Connected.png b/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN-Connected.png deleted file mode 100644 index e3066fac7..000000000 Binary files a/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN-Connected.png and /dev/null differ diff --git a/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN.png b/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN.png deleted file mode 100644 index 6eb3e443c..000000000 Binary files a/images/Mac-OS-X/Bluetooth/System-Preferences-Network-Bluetooth-PAN.png and /dev/null differ diff --git a/images/Mac-OS-X/Bluetooth/System-Preferences-Sharing-Bluetooth-PAN.png b/images/Mac-OS-X/Bluetooth/System-Preferences-Sharing-Bluetooth-PAN.png deleted file mode 100644 index 8ef3a27fe..000000000 Binary files a/images/Mac-OS-X/Bluetooth/System-Preferences-Sharing-Bluetooth-PAN.png and /dev/null differ diff --git a/images/OSXRNDIS/AddNewDevice.png b/images/OSXRNDIS/AddNewDevice.png deleted file mode 100644 index ddd3b2963..000000000 Binary files a/images/OSXRNDIS/AddNewDevice.png and /dev/null differ diff --git a/images/OSXRNDIS/CDC-Connected.png b/images/OSXRNDIS/CDC-Connected.png deleted file mode 100644 index 569e9662f..000000000 Binary files a/images/OSXRNDIS/CDC-Connected.png and /dev/null differ diff --git a/images/OSXRNDIS/DeviceReportCDC.png b/images/OSXRNDIS/DeviceReportCDC.png deleted file mode 100644 index 737df1921..000000000 Binary files a/images/OSXRNDIS/DeviceReportCDC.png and /dev/null differ diff --git a/images/OSXRNDIS/PingWorks.png b/images/OSXRNDIS/PingWorks.png deleted file mode 100644 index 1b30791f5..000000000 Binary files a/images/OSXRNDIS/PingWorks.png and /dev/null differ diff --git a/images/OSXRNDIS/SetIPv4Address.png b/images/OSXRNDIS/SetIPv4Address.png deleted file mode 100644 index 9f501bc43..000000000 Binary files a/images/OSXRNDIS/SetIPv4Address.png and /dev/null differ diff --git a/images/OSXRNDIS/Sharing-Internet-Connection-Warning.png b/images/OSXRNDIS/Sharing-Internet-Connection-Warning.png deleted file mode 100644 index 2a4d1341b..000000000 Binary files a/images/OSXRNDIS/Sharing-Internet-Connection-Warning.png and /dev/null differ diff --git a/images/OSXRNDIS/Sharing-Internet-Connection.png b/images/OSXRNDIS/Sharing-Internet-Connection.png deleted file mode 100644 index 71034da5b..000000000 Binary files a/images/OSXRNDIS/Sharing-Internet-Connection.png and /dev/null differ diff --git a/images/OSXRNDIS/SystemPreferencesNetwork.png b/images/OSXRNDIS/SystemPreferencesNetwork.png deleted file mode 100644 index 561e05b4e..000000000 Binary files a/images/OSXRNDIS/SystemPreferencesNetwork.png and /dev/null differ diff --git a/images/OSXRNDIS/SystemPreferencesSharing.png b/images/OSXRNDIS/SystemPreferencesSharing.png deleted file mode 100644 index 4901b0ebc..000000000 Binary files a/images/OSXRNDIS/SystemPreferencesSharing.png and /dev/null differ diff --git a/images/OSXRNDIS/Ubuntu-CDC/Network-Connected.png b/images/OSXRNDIS/Ubuntu-CDC/Network-Connected.png deleted file mode 100644 index 8537d08db..000000000 Binary files a/images/OSXRNDIS/Ubuntu-CDC/Network-Connected.png and /dev/null differ diff --git a/images/OSXRNDIS/Ubuntu-CDC/Network-Connecting.png b/images/OSXRNDIS/Ubuntu-CDC/Network-Connecting.png deleted file mode 100644 index 87fd8e068..000000000 Binary files a/images/OSXRNDIS/Ubuntu-CDC/Network-Connecting.png and /dev/null differ diff --git a/images/OSXRNDIS/Ubuntu-CDC/Network-Options.png b/images/OSXRNDIS/Ubuntu-CDC/Network-Options.png deleted file mode 100644 index 3faf79586..000000000 Binary files a/images/OSXRNDIS/Ubuntu-CDC/Network-Options.png and /dev/null differ diff --git a/images/OSXRNDIS/Ubuntu-CDC/System-Settings-Network.png b/images/OSXRNDIS/Ubuntu-CDC/System-Settings-Network.png deleted file mode 100644 index a44d6a06b..000000000 Binary files a/images/OSXRNDIS/Ubuntu-CDC/System-Settings-Network.png and /dev/null differ diff --git a/images/OSXRNDIS/sshWorks.png b/images/OSXRNDIS/sshWorks.png deleted file mode 100644 index 849bf774a..000000000 Binary files a/images/OSXRNDIS/sshWorks.png and /dev/null differ diff --git a/images/Ubuntu-CDC/Network-Connected.png b/images/Ubuntu-CDC/Network-Connected.png deleted file mode 100644 index 8537d08db..000000000 Binary files a/images/Ubuntu-CDC/Network-Connected.png and /dev/null differ diff --git a/images/Ubuntu-CDC/Network-Connecting.png b/images/Ubuntu-CDC/Network-Connecting.png deleted file mode 100644 index e74970519..000000000 Binary files a/images/Ubuntu-CDC/Network-Connecting.png and /dev/null differ diff --git a/images/Ubuntu-CDC/Network-Options.png b/images/Ubuntu-CDC/Network-Options.png deleted file mode 100644 index 3faf79586..000000000 Binary files a/images/Ubuntu-CDC/Network-Options.png and /dev/null differ diff --git a/images/Ubuntu-CDC/System-Settings-Network.png b/images/Ubuntu-CDC/System-Settings-Network.png deleted file mode 100644 index a44d6a06b..000000000 Binary files a/images/Ubuntu-CDC/System-Settings-Network.png and /dev/null differ diff --git a/images/WindowsRNDIS/Local-Area-Connection-Properties-Sharing.png b/images/WindowsRNDIS/Local-Area-Connection-Properties-Sharing.png deleted file mode 100644 index 3231193a0..000000000 Binary files a/images/WindowsRNDIS/Local-Area-Connection-Properties-Sharing.png and /dev/null differ diff --git a/images/WindowsRNDIS/Local-Area-Connection-Status.png b/images/WindowsRNDIS/Local-Area-Connection-Status.png deleted file mode 100644 index 25a66fefb..000000000 Binary files a/images/WindowsRNDIS/Local-Area-Connection-Status.png and /dev/null differ diff --git a/images/WindowsRNDIS/Network-Connections-Properties.png b/images/WindowsRNDIS/Network-Connections-Properties.png deleted file mode 100644 index 61085d8d2..000000000 Binary files a/images/WindowsRNDIS/Network-Connections-Properties.png and /dev/null differ diff --git a/images/WindowsRNDIS/Network-Connections-Rename.png b/images/WindowsRNDIS/Network-Connections-Rename.png deleted file mode 100644 index 342f27b11..000000000 Binary files a/images/WindowsRNDIS/Network-Connections-Rename.png and /dev/null differ diff --git a/images/WindowsRNDIS/Network-Connections.png b/images/WindowsRNDIS/Network-Connections.png deleted file mode 100644 index c2b0b6530..000000000 Binary files a/images/WindowsRNDIS/Network-Connections.png and /dev/null differ diff --git a/images/WindowsRNDIS/Network-and-Sharing-Center-Change-adapter-settings.png b/images/WindowsRNDIS/Network-and-Sharing-Center-Change-adapter-settings.png deleted file mode 100644 index 1d93f541b..000000000 Binary files a/images/WindowsRNDIS/Network-and-Sharing-Center-Change-adapter-settings.png and /dev/null differ diff --git a/images/WindowsRNDIS/Network-and-Sharing-Center.png b/images/WindowsRNDIS/Network-and-Sharing-Center.png deleted file mode 100644 index a8e8390ed..000000000 Binary files a/images/WindowsRNDIS/Network-and-Sharing-Center.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/AddNewDevice.png b/images/WindowsRNDIS/OSXRNDIS/AddNewDevice.png deleted file mode 100644 index ddd3b2963..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/AddNewDevice.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/CDC-Connected.png b/images/WindowsRNDIS/OSXRNDIS/CDC-Connected.png deleted file mode 100644 index 569e9662f..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/CDC-Connected.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/DeviceReportCDC.png b/images/WindowsRNDIS/OSXRNDIS/DeviceReportCDC.png deleted file mode 100644 index 737df1921..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/DeviceReportCDC.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/PingWorks.png b/images/WindowsRNDIS/OSXRNDIS/PingWorks.png deleted file mode 100644 index 1b30791f5..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/PingWorks.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/SetIPv4Address.png b/images/WindowsRNDIS/OSXRNDIS/SetIPv4Address.png deleted file mode 100644 index 9f501bc43..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/SetIPv4Address.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/Sharing-Internet-Connection-Warning.png b/images/WindowsRNDIS/OSXRNDIS/Sharing-Internet-Connection-Warning.png deleted file mode 100644 index 2a4d1341b..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/Sharing-Internet-Connection-Warning.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/Sharing-Internet-Connection.png b/images/WindowsRNDIS/OSXRNDIS/Sharing-Internet-Connection.png deleted file mode 100644 index 71034da5b..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/Sharing-Internet-Connection.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/SystemPreferencesNetwork.png b/images/WindowsRNDIS/OSXRNDIS/SystemPreferencesNetwork.png deleted file mode 100644 index 561e05b4e..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/SystemPreferencesNetwork.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/SystemPreferencesSharing.png b/images/WindowsRNDIS/OSXRNDIS/SystemPreferencesSharing.png deleted file mode 100644 index 4901b0ebc..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/SystemPreferencesSharing.png and /dev/null differ diff --git a/images/WindowsRNDIS/OSXRNDIS/sshWorks.png b/images/WindowsRNDIS/OSXRNDIS/sshWorks.png deleted file mode 100644 index 849bf774a..000000000 Binary files a/images/WindowsRNDIS/OSXRNDIS/sshWorks.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISAddressSet.png b/images/WindowsRNDIS/WindowsRNDISAddressSet.png deleted file mode 100644 index c51c1e67f..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISAddressSet.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISChooseDriver.png b/images/WindowsRNDIS/WindowsRNDISChooseDriver.png deleted file mode 100644 index 0814d5682..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISChooseDriver.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISChooseNetworkDevice.png b/images/WindowsRNDIS/WindowsRNDISChooseNetworkDevice.png deleted file mode 100644 index 50df1c811..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISChooseNetworkDevice.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISDeviceManagerNotWorking.png b/images/WindowsRNDIS/WindowsRNDISDeviceManagerNotWorking.png deleted file mode 100644 index 0843be7e6..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISDeviceManagerNotWorking.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISDeviceManagerWorking.png b/images/WindowsRNDIS/WindowsRNDISDeviceManagerWorking.png deleted file mode 100644 index 58c121ee9..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISDeviceManagerWorking.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISGadgetUpdateDriver.png b/images/WindowsRNDIS/WindowsRNDISGadgetUpdateDriver.png deleted file mode 100644 index f153676de..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISGadgetUpdateDriver.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISIPv4Address.png b/images/WindowsRNDIS/WindowsRNDISIPv4Address.png deleted file mode 100644 index 63d2a87cd..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISIPv4Address.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISNetworkCenter.png b/images/WindowsRNDIS/WindowsRNDISNetworkCenter.png deleted file mode 100644 index 3fb5bbc1d..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISNetworkCenter.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISNetworkSettings.png b/images/WindowsRNDIS/WindowsRNDISNetworkSettings.png deleted file mode 100644 index 0550a3ce5..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISNetworkSettings.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISPingWorks.png b/images/WindowsRNDIS/WindowsRNDISPingWorks.png deleted file mode 100644 index cd42efa06..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISPingWorks.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISPutty.png b/images/WindowsRNDIS/WindowsRNDISPutty.png deleted file mode 100644 index 42862159d..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISPutty.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISPuttyConnected.png b/images/WindowsRNDIS/WindowsRNDISPuttyConnected.png deleted file mode 100644 index 90b443eaa..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISPuttyConnected.png and /dev/null differ diff --git a/images/WindowsRNDIS/WindowsRNDISPuttyFingerprint.png b/images/WindowsRNDIS/WindowsRNDISPuttyFingerprint.png deleted file mode 100644 index bf55e2c5a..000000000 Binary files a/images/WindowsRNDIS/WindowsRNDISPuttyFingerprint.png and /dev/null differ diff --git a/images/WindowsRNDIS/control-panel-hard-and-sound-device-manager.png b/images/WindowsRNDIS/control-panel-hard-and-sound-device-manager.png deleted file mode 100644 index 52dee7af5..000000000 Binary files a/images/WindowsRNDIS/control-panel-hard-and-sound-device-manager.png and /dev/null differ diff --git a/images/WindowsRNDIS/device-manager-ethernet-usb-rndis-gadget.png b/images/WindowsRNDIS/device-manager-ethernet-usb-rndis-gadget.png deleted file mode 100644 index 967ff5c73..000000000 Binary files a/images/WindowsRNDIS/device-manager-ethernet-usb-rndis-gadget.png and /dev/null differ diff --git a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-2.png b/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-2.png deleted file mode 100644 index d0e16a031..000000000 Binary files a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-2.png and /dev/null differ diff --git a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-3.png b/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-3.png deleted file mode 100644 index 55b359b74..000000000 Binary files a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-3.png and /dev/null differ diff --git a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-4.png b/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-4.png deleted file mode 100644 index 72048daa0..000000000 Binary files a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget-4.png and /dev/null differ diff --git a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget.png b/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget.png deleted file mode 100644 index 62f0cbd3c..000000000 Binary files a/images/WindowsRNDIS/update-driver-software-usb-ethernet-rndis-gadget.png and /dev/null differ diff --git a/images/WindowsRNDIS/update-driver-warning.png b/images/WindowsRNDIS/update-driver-warning.png deleted file mode 100644 index 2196e41d5..000000000 Binary files a/images/WindowsRNDIS/update-driver-warning.png and /dev/null differ diff --git a/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-acer.png b/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-acer.png deleted file mode 100644 index cf84cdd32..000000000 Binary files a/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-acer.png and /dev/null differ diff --git a/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-microsoft.png b/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-microsoft.png deleted file mode 100644 index c954fd785..000000000 Binary files a/images/WindowsRNDIS/usb-ethernt-rndis-gadget-properties-microsoft.png and /dev/null differ diff --git a/images/Android/Bluetooth/connectbot-1.png b/images/android/4.1.2/connectbot-1.png similarity index 100% rename from images/Android/Bluetooth/connectbot-1.png rename to images/android/4.1.2/connectbot-1.png diff --git a/images/Android/Bluetooth/connectbot-2.png b/images/android/4.1.2/connectbot-2.png similarity index 100% rename from images/Android/Bluetooth/connectbot-2.png rename to images/android/4.1.2/connectbot-2.png diff --git a/images/Android/Bluetooth/connectbot-3.png b/images/android/4.1.2/connectbot-3.png similarity index 100% rename from images/Android/Bluetooth/connectbot-3.png rename to images/android/4.1.2/connectbot-3.png diff --git a/images/Android/Bluetooth/connectbot-4.png b/images/android/4.1.2/connectbot-4.png similarity index 100% rename from images/Android/Bluetooth/connectbot-4.png rename to images/android/4.1.2/connectbot-4.png diff --git a/images/Android/Bluetooth/pairing-request.png b/images/android/4.1.2/pairing-request.png similarity index 100% rename from images/Android/Bluetooth/pairing-request.png rename to images/android/4.1.2/pairing-request.png diff --git a/images/Android/Bluetooth/searching.png b/images/android/4.1.2/searching.png similarity index 100% rename from images/Android/Bluetooth/searching.png rename to images/android/4.1.2/searching.png diff --git a/images/Android/Bluetooth/settings-bluetooth-on.png b/images/android/4.1.2/settings-bluetooth-on.png similarity index 100% rename from images/Android/Bluetooth/settings-bluetooth-on.png rename to images/android/4.1.2/settings-bluetooth-on.png diff --git a/images/Android/Bluetooth/tethering-enabled.png b/images/android/4.1.2/tethering-enabled.png similarity index 100% rename from images/Android/Bluetooth/tethering-enabled.png rename to images/android/4.1.2/tethering-enabled.png diff --git a/images/brickman/bluetooth-confirm-passkey.png b/images/brickman/bluetooth-confirm-passkey.png index 07895d887..a05d625a9 100644 Binary files a/images/brickman/bluetooth-confirm-passkey.png and b/images/brickman/bluetooth-confirm-passkey.png differ diff --git a/images/brickman/bluetooth-device-network-connection.png b/images/brickman/bluetooth-device-network-connection.png deleted file mode 100644 index 4edb237c3..000000000 Binary files a/images/brickman/bluetooth-device-network-connection.png and /dev/null differ diff --git a/images/brickman/bluetooth-droid4-confirm-passkey.png b/images/brickman/bluetooth-droid4-confirm-passkey.png new file mode 100644 index 000000000..12bd2b3d6 Binary files /dev/null and b/images/brickman/bluetooth-droid4-confirm-passkey.png differ diff --git a/images/brickman/bluetooth-droid4-network-connection-selected.png b/images/brickman/bluetooth-droid4-network-connection-selected.png new file mode 100644 index 000000000..83ceda960 Binary files /dev/null and b/images/brickman/bluetooth-droid4-network-connection-selected.png differ diff --git a/images/brickman/bluetooth-droid4-selected.png b/images/brickman/bluetooth-droid4-selected.png new file mode 100644 index 000000000..9d07aa487 Binary files /dev/null and b/images/brickman/bluetooth-droid4-selected.png differ diff --git a/images/brickman/bluetooth-my-computer-0-network-connection-selected.png b/images/brickman/bluetooth-my-computer-0-network-connection-selected.png new file mode 100644 index 000000000..5a9456a61 Binary files /dev/null and b/images/brickman/bluetooth-my-computer-0-network-connection-selected.png differ diff --git a/images/brickman/bluetooth-my-computer-not-paired.png b/images/brickman/bluetooth-my-computer-not-paired.png index acdf2a93b..503287c15 100644 Binary files a/images/brickman/bluetooth-my-computer-not-paired.png and b/images/brickman/bluetooth-my-computer-not-paired.png differ diff --git a/images/brickman/bluetooth-powered-my-computer.png b/images/brickman/bluetooth-powered-my-computer.png index 0568390ff..e2a64f3be 100644 Binary files a/images/brickman/bluetooth-powered-my-computer.png and b/images/brickman/bluetooth-powered-my-computer.png differ diff --git a/images/brickman/bluetooth-powered-no-devices.png b/images/brickman/bluetooth-powered-no-devices.png deleted file mode 100644 index bac8ea50f..000000000 Binary files a/images/brickman/bluetooth-powered-no-devices.png and /dev/null differ diff --git a/images/brickman/bluetooth-powered-visible-no-devices.png b/images/brickman/bluetooth-powered-visible-no-devices.png new file mode 100644 index 000000000..139cec805 Binary files /dev/null and b/images/brickman/bluetooth-powered-visible-no-devices.png differ diff --git a/images/brickman/main-menu.png b/images/brickman/main-menu.png index 18681a0d3..7ca255cdf 100644 Binary files a/images/brickman/main-menu.png and b/images/brickman/main-menu.png differ diff --git a/images/brickman/networking-connect-automatically-selected.png b/images/brickman/networking-connect-automatically-selected.png deleted file mode 100644 index 3a53a63c4..000000000 Binary files a/images/brickman/networking-connect-automatically-selected.png and /dev/null differ diff --git a/images/brickman/networking-connections-wired-only.png b/images/brickman/networking-connections-wired-only.png index 0b827a6a5..1f571eb21 100644 Binary files a/images/brickman/networking-connections-wired-only.png and b/images/brickman/networking-connections-wired-only.png differ diff --git a/images/brickman/networking-droid4-connect-selected-online.png b/images/brickman/networking-droid4-connect-selected-online.png new file mode 100644 index 000000000..f408f11e2 Binary files /dev/null and b/images/brickman/networking-droid4-connect-selected-online.png differ diff --git a/images/brickman/networking-droid4-connect-selected.png b/images/brickman/networking-droid4-connect-selected.png new file mode 100644 index 000000000..a8c997c6e Binary files /dev/null and b/images/brickman/networking-droid4-connect-selected.png differ diff --git a/images/brickman/networking-ipv4-tab-change-selected.png b/images/brickman/networking-ipv4-tab-change-selected.png deleted file mode 100644 index 1d3b84594..000000000 Binary files a/images/brickman/networking-ipv4-tab-change-selected.png and /dev/null differ diff --git a/images/brickman/networking-ipv4-tab-with-linux-defaults.png b/images/brickman/networking-ipv4-tab-with-linux-defaults.png deleted file mode 100644 index 9dc0767cc..000000000 Binary files a/images/brickman/networking-ipv4-tab-with-linux-defaults.png and /dev/null differ diff --git a/images/brickman/networking-ipv4-tab-with-mac-defaults.png b/images/brickman/networking-ipv4-tab-with-mac-defaults.png deleted file mode 100644 index a02dbd58e..000000000 Binary files a/images/brickman/networking-ipv4-tab-with-mac-defaults.png and /dev/null differ diff --git a/images/brickman/networking-ipv4-tab-with-windows-defaults.png b/images/brickman/networking-ipv4-tab-with-windows-defaults.png deleted file mode 100644 index 323b14ce3..000000000 Binary files a/images/brickman/networking-ipv4-tab-with-windows-defaults.png and /dev/null differ diff --git a/images/brickman/networking-load-linux-defaults.png b/images/brickman/networking-load-linux-defaults.png deleted file mode 100644 index f1768013f..000000000 Binary files a/images/brickman/networking-load-linux-defaults.png and /dev/null differ diff --git a/images/brickman/networking-load-mac-defaults.png b/images/brickman/networking-load-mac-defaults.png deleted file mode 100644 index faec2e562..000000000 Binary files a/images/brickman/networking-load-mac-defaults.png and /dev/null differ diff --git a/images/brickman/networking-load-windows-defaults.png b/images/brickman/networking-load-windows-defaults.png index 4f840e80a..a13dcbcb7 100644 Binary files a/images/brickman/networking-load-windows-defaults.png and b/images/brickman/networking-load-windows-defaults.png differ diff --git a/images/brickman/networking-my-computer-0-connect-selected.png b/images/brickman/networking-my-computer-0-connect-selected.png new file mode 100644 index 000000000..92fb4d170 Binary files /dev/null and b/images/brickman/networking-my-computer-0-connect-selected.png differ diff --git a/images/brickman/networking-my-computer-0-disconnect-selected-online.png b/images/brickman/networking-my-computer-0-disconnect-selected-online.png new file mode 100644 index 000000000..63c369efb Binary files /dev/null and b/images/brickman/networking-my-computer-0-disconnect-selected-online.png differ diff --git a/images/brickman/networking-technologies-gadget-selected.png b/images/brickman/networking-technologies-gadget-selected.png deleted file mode 100644 index 324a28f95..000000000 Binary files a/images/brickman/networking-technologies-gadget-selected.png and /dev/null differ diff --git a/images/brickman/shutdown-menu.png b/images/brickman/shutdown-menu.png index aeabb0785..27364e908 100644 Binary files a/images/brickman/shutdown-menu.png and b/images/brickman/shutdown-menu.png differ diff --git a/images/brickman/tethering-bluetooth-enabled.png b/images/brickman/tethering-bluetooth-enabled.png index cf1a6b795..69b4cffe8 100644 Binary files a/images/brickman/tethering-bluetooth-enabled.png and b/images/brickman/tethering-bluetooth-enabled.png differ diff --git a/images/brickman/usb-cdc-active.png b/images/brickman/usb-cdc-active.png deleted file mode 100644 index 0e2bb6aab..000000000 Binary files a/images/brickman/usb-cdc-active.png and /dev/null differ diff --git a/images/brickman/usb-rndis-active.png b/images/brickman/usb-rndis-active.png deleted file mode 100644 index 4dca7af58..000000000 Binary files a/images/brickman/usb-rndis-active.png and /dev/null differ diff --git a/images/brickman/wired-status-disconnected-connect-selected.png b/images/brickman/wired-status-disconnected-connect-selected.png new file mode 100644 index 000000000..0a55f645e Binary files /dev/null and b/images/brickman/wired-status-disconnected-connect-selected.png differ diff --git a/images/brickman/wired-status-disconnected-ipv4-empty.png b/images/brickman/wired-status-disconnected-ipv4-empty.png new file mode 100644 index 000000000..6258c7ee8 Binary files /dev/null and b/images/brickman/wired-status-disconnected-ipv4-empty.png differ diff --git a/images/brickman/wired-status-disconnected-ipv4-selected.png b/images/brickman/wired-status-disconnected-ipv4-selected.png new file mode 100644 index 000000000..5fc59abfd Binary files /dev/null and b/images/brickman/wired-status-disconnected-ipv4-selected.png differ diff --git a/images/brickman/wired-status-online-connect-automatically-selected.png b/images/brickman/wired-status-online-connect-automatically-selected.png new file mode 100644 index 000000000..d1b1d30f9 Binary files /dev/null and b/images/brickman/wired-status-online-connect-automatically-selected.png differ diff --git a/images/brickman/wired-status-online-connect-selected.png b/images/brickman/wired-status-online-connect-selected.png new file mode 100644 index 000000000..0d6c4fc9a Binary files /dev/null and b/images/brickman/wired-status-online-connect-selected.png differ diff --git a/images/osx/10.10/Pairing-Request.png b/images/osx/10.10/Pairing-Request.png new file mode 100644 index 000000000..6edf1b085 Binary files /dev/null and b/images/osx/10.10/Pairing-Request.png differ diff --git a/images/osx/10.10/System-Preferences-Bluetooth.png b/images/osx/10.10/System-Preferences-Bluetooth.png new file mode 100644 index 000000000..36e6ed6e9 Binary files /dev/null and b/images/osx/10.10/System-Preferences-Bluetooth.png differ diff --git a/images/osx/10.10/System-Preferences-Network-Add-PAN.png b/images/osx/10.10/System-Preferences-Network-Add-PAN.png new file mode 100644 index 000000000..7860cbafe Binary files /dev/null and b/images/osx/10.10/System-Preferences-Network-Add-PAN.png differ diff --git a/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN-Connected.png b/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN-Connected.png new file mode 100644 index 000000000..990320a97 Binary files /dev/null and b/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN-Connected.png differ diff --git a/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN.png b/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN.png new file mode 100644 index 000000000..2383c01bd Binary files /dev/null and b/images/osx/10.10/System-Preferences-Network-Bluetooth-PAN.png differ diff --git a/images/osx/10.10/System-Preferences-Sharing-Bluetooth-PAN.png b/images/osx/10.10/System-Preferences-Sharing-Bluetooth-PAN.png new file mode 100644 index 000000000..c28fbf2ce Binary files /dev/null and b/images/osx/10.10/System-Preferences-Sharing-Bluetooth-PAN.png differ diff --git a/images/osx/10.9/AddNewDevice.png b/images/osx/10.9/AddNewDevice.png new file mode 100644 index 000000000..2c1cea43c Binary files /dev/null and b/images/osx/10.9/AddNewDevice.png differ diff --git a/images/osx/10.9/CDC-Connected.png b/images/osx/10.9/CDC-Connected.png new file mode 100644 index 000000000..19356499a Binary files /dev/null and b/images/osx/10.9/CDC-Connected.png differ diff --git a/images/osx/10.9/DeviceReportCDC.png b/images/osx/10.9/DeviceReportCDC.png new file mode 100644 index 000000000..8839db5e3 Binary files /dev/null and b/images/osx/10.9/DeviceReportCDC.png differ diff --git a/images/osx/10.9/PingWorks.png b/images/osx/10.9/PingWorks.png new file mode 100644 index 000000000..ee2c3081a Binary files /dev/null and b/images/osx/10.9/PingWorks.png differ diff --git a/images/osx/10.9/SetIPv4Address.png b/images/osx/10.9/SetIPv4Address.png new file mode 100644 index 000000000..f0b0eb9af Binary files /dev/null and b/images/osx/10.9/SetIPv4Address.png differ diff --git a/images/osx/10.9/Sharing-Internet-Connection-Warning.png b/images/osx/10.9/Sharing-Internet-Connection-Warning.png new file mode 100644 index 000000000..d18b7e44e Binary files /dev/null and b/images/osx/10.9/Sharing-Internet-Connection-Warning.png differ diff --git a/images/osx/10.9/Sharing-Internet-Connection.png b/images/osx/10.9/Sharing-Internet-Connection.png new file mode 100644 index 000000000..639a0d6e6 Binary files /dev/null and b/images/osx/10.9/Sharing-Internet-Connection.png differ diff --git a/images/osx/10.9/SystemPreferencesNetwork.png b/images/osx/10.9/SystemPreferencesNetwork.png new file mode 100644 index 000000000..d993c239a Binary files /dev/null and b/images/osx/10.9/SystemPreferencesNetwork.png differ diff --git a/images/osx/10.9/SystemPreferencesSharing.png b/images/osx/10.9/SystemPreferencesSharing.png new file mode 100644 index 000000000..2c4ee0279 Binary files /dev/null and b/images/osx/10.9/SystemPreferencesSharing.png differ diff --git a/images/osx/10.9/sshWorks.png b/images/osx/10.9/sshWorks.png new file mode 100644 index 000000000..af2ff2f4d Binary files /dev/null and b/images/osx/10.9/sshWorks.png differ diff --git a/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-rndis-gadget.png b/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-rndis-gadget.png deleted file mode 100644 index db7d351bf..000000000 Binary files a/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-rndis-gadget.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-serial-device.png b/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-serial-device.png deleted file mode 100644 index 1c4378718..000000000 Binary files a/images/screenshots/windows/10/rndis/device-manager-ethernet-usb-serial-device.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/ethernet-properties-sharing.png b/images/screenshots/windows/10/rndis/ethernet-properties-sharing.png deleted file mode 100644 index 53f3e623f..000000000 Binary files a/images/screenshots/windows/10/rndis/ethernet-properties-sharing.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/ethernet-status.png b/images/screenshots/windows/10/rndis/ethernet-status.png deleted file mode 100644 index 33b6787a6..000000000 Binary files a/images/screenshots/windows/10/rndis/ethernet-status.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/install-from-disk-1.png b/images/screenshots/windows/10/rndis/install-from-disk-1.png deleted file mode 100644 index f21b29fef..000000000 Binary files a/images/screenshots/windows/10/rndis/install-from-disk-1.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/install-from-disk-2.png b/images/screenshots/windows/10/rndis/install-from-disk-2.png deleted file mode 100644 index 3d5f41b29..000000000 Binary files a/images/screenshots/windows/10/rndis/install-from-disk-2.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/locate-file-linux-inf.png b/images/screenshots/windows/10/rndis/locate-file-linux-inf.png deleted file mode 100644 index 44f4ca7db..000000000 Binary files a/images/screenshots/windows/10/rndis/locate-file-linux-inf.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/network-connections-rename.png b/images/screenshots/windows/10/rndis/network-connections-rename.png deleted file mode 100644 index a3847517d..000000000 Binary files a/images/screenshots/windows/10/rndis/network-connections-rename.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/network-connections.png b/images/screenshots/windows/10/rndis/network-connections.png deleted file mode 100644 index 130c0c6c0..000000000 Binary files a/images/screenshots/windows/10/rndis/network-connections.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/restart-advanced-options.png b/images/screenshots/windows/10/rndis/restart-advanced-options.png deleted file mode 100644 index 066cf192e..000000000 Binary files a/images/screenshots/windows/10/rndis/restart-advanced-options.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/restart-options.png b/images/screenshots/windows/10/rndis/restart-options.png deleted file mode 100644 index 5dc7cc69d..000000000 Binary files a/images/screenshots/windows/10/rndis/restart-options.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/restart-startup-settings.png b/images/screenshots/windows/10/rndis/restart-startup-settings.png deleted file mode 100644 index 82e273e3b..000000000 Binary files a/images/screenshots/windows/10/rndis/restart-startup-settings.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/restart-troubleshoot.png b/images/screenshots/windows/10/rndis/restart-troubleshoot.png deleted file mode 100644 index 1300a6379..000000000 Binary files a/images/screenshots/windows/10/rndis/restart-troubleshoot.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/settings-network-and-internet-ethernet.png b/images/screenshots/windows/10/rndis/settings-network-and-internet-ethernet.png deleted file mode 100644 index f910ed23d..000000000 Binary files a/images/screenshots/windows/10/rndis/settings-network-and-internet-ethernet.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/start-menu-device-manager.png b/images/screenshots/windows/10/rndis/start-menu-device-manager.png deleted file mode 100644 index c27ff9b88..000000000 Binary files a/images/screenshots/windows/10/rndis/start-menu-device-manager.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/startup-settings.png b/images/screenshots/windows/10/rndis/startup-settings.png deleted file mode 100644 index 337e9b94a..000000000 Binary files a/images/screenshots/windows/10/rndis/startup-settings.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/update-driver-software-browse.png b/images/screenshots/windows/10/rndis/update-driver-software-browse.png deleted file mode 100644 index f26825422..000000000 Binary files a/images/screenshots/windows/10/rndis/update-driver-software-browse.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-2.png b/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-2.png deleted file mode 100644 index 14eda30f1..000000000 Binary files a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-2.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-3.png b/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-3.png deleted file mode 100644 index b28156437..000000000 Binary files a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-3.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-4.png b/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-4.png deleted file mode 100644 index 98dc66333..000000000 Binary files a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-4.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-5.png b/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-5.png deleted file mode 100644 index 199f2fce8..000000000 Binary files a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget-5.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget.png b/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget.png deleted file mode 100644 index 63736f591..000000000 Binary files a/images/screenshots/windows/10/rndis/update-driver-software-usb-ethernet-rndis-gadget.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-acer.png b/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-acer.png deleted file mode 100644 index 5a428b286..000000000 Binary files a/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-acer.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-ev3dev.png b/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-ev3dev.png deleted file mode 100644 index 81b3d5c6a..000000000 Binary files a/images/screenshots/windows/10/rndis/usb-ethernt-rndis-gadget-properties-ev3dev.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/windows-security-install-anyway.png b/images/screenshots/windows/10/rndis/windows-security-install-anyway.png deleted file mode 100644 index 6cafc23e4..000000000 Binary files a/images/screenshots/windows/10/rndis/windows-security-install-anyway.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/windows-settings-recovery-restart-now.png b/images/screenshots/windows/10/rndis/windows-settings-recovery-restart-now.png deleted file mode 100644 index 129d756ef..000000000 Binary files a/images/screenshots/windows/10/rndis/windows-settings-recovery-restart-now.png and /dev/null differ diff --git a/images/screenshots/windows/10/rndis/windows-settings-update-and-security.png b/images/screenshots/windows/10/rndis/windows-settings-update-and-security.png deleted file mode 100644 index 00a88804c..000000000 Binary files a/images/screenshots/windows/10/rndis/windows-settings-update-and-security.png and /dev/null differ diff --git a/images/Ubuntu-Bluetooth/blueman-services-network.png b/images/ubuntu/15.10/blueman-services-network.png similarity index 100% rename from images/Ubuntu-Bluetooth/blueman-services-network.png rename to images/ubuntu/15.10/blueman-services-network.png diff --git a/images/Ubuntu-Bluetooth/bluetooth-app-indicator-powered-visible.png b/images/ubuntu/15.10/bluetooth-app-indicator-powered-visible.png similarity index 100% rename from images/Ubuntu-Bluetooth/bluetooth-app-indicator-powered-visible.png rename to images/ubuntu/15.10/bluetooth-app-indicator-powered-visible.png diff --git a/images/ubuntu/15.10/choose-a-connection-type.png b/images/ubuntu/15.10/choose-a-connection-type.png new file mode 100644 index 000000000..5b3624712 Binary files /dev/null and b/images/ubuntu/15.10/choose-a-connection-type.png differ diff --git a/images/ubuntu/15.10/editing-ev3dev-ethernet.png b/images/ubuntu/15.10/editing-ev3dev-ethernet.png new file mode 100644 index 000000000..3f66a1dea Binary files /dev/null and b/images/ubuntu/15.10/editing-ev3dev-ethernet.png differ diff --git a/images/ubuntu/15.10/editing-ev3dev-ipv4-settings.png b/images/ubuntu/15.10/editing-ev3dev-ipv4-settings.png new file mode 100644 index 000000000..c7262b63d Binary files /dev/null and b/images/ubuntu/15.10/editing-ev3dev-ipv4-settings.png differ diff --git a/images/ubuntu/15.10/network-application-indicator-edit-connections.png b/images/ubuntu/15.10/network-application-indicator-edit-connections.png new file mode 100644 index 000000000..7f6d6aea1 Binary files /dev/null and b/images/ubuntu/15.10/network-application-indicator-edit-connections.png differ diff --git a/images/ubuntu/15.10/network-connections-add.png b/images/ubuntu/15.10/network-connections-add.png new file mode 100644 index 000000000..43b188125 Binary files /dev/null and b/images/ubuntu/15.10/network-connections-add.png differ diff --git a/images/ubuntu/15.10/network-connections-close.png b/images/ubuntu/15.10/network-connections-close.png new file mode 100644 index 000000000..50ad72e1a Binary files /dev/null and b/images/ubuntu/15.10/network-connections-close.png differ diff --git a/images/windows/10/devices-and-printers-context-menu-network-settings.png b/images/windows/10/devices-and-printers-context-menu-network-settings.png new file mode 100644 index 000000000..dad40a2a7 Binary files /dev/null and b/images/windows/10/devices-and-printers-context-menu-network-settings.png differ diff --git a/images/windows/10/devices-and-printers-new-device.png b/images/windows/10/devices-and-printers-new-device.png new file mode 100644 index 000000000..f81226fb2 Binary files /dev/null and b/images/windows/10/devices-and-printers-new-device.png differ diff --git a/images/windows/10/devices-and-printers-rndis.png b/images/windows/10/devices-and-printers-rndis.png new file mode 100644 index 000000000..d308aae54 Binary files /dev/null and b/images/windows/10/devices-and-printers-rndis.png differ diff --git a/images/windows/10/devices-and-printers.png b/images/windows/10/devices-and-printers.png new file mode 100644 index 000000000..67cf5f77d Binary files /dev/null and b/images/windows/10/devices-and-printers.png differ diff --git a/images/windows/10/local-area-connection-properties-sharing.png b/images/windows/10/local-area-connection-properties-sharing.png new file mode 100644 index 000000000..4cddc6de1 Binary files /dev/null and b/images/windows/10/local-area-connection-properties-sharing.png differ diff --git a/images/windows/10/local-area-connection-status.png b/images/windows/10/local-area-connection-status.png new file mode 100644 index 000000000..7dfdeb8aa Binary files /dev/null and b/images/windows/10/local-area-connection-status.png differ diff --git a/images/windows/10/network-and-sharing-center-change-adapter-settings.png b/images/windows/10/network-and-sharing-center-change-adapter-settings.png new file mode 100644 index 000000000..1f6d62b0a Binary files /dev/null and b/images/windows/10/network-and-sharing-center-change-adapter-settings.png differ diff --git a/images/windows/10/network-connections-context-menu-rename.png b/images/windows/10/network-connections-context-menu-rename.png new file mode 100644 index 000000000..a806102ea Binary files /dev/null and b/images/windows/10/network-connections-context-menu-rename.png differ diff --git a/images/windows/10/network-connections-internet-adapter.png b/images/windows/10/network-connections-internet-adapter.png new file mode 100644 index 000000000..063abd668 Binary files /dev/null and b/images/windows/10/network-connections-internet-adapter.png differ diff --git a/images/windows/10/putty-configuration-ev3dev.png b/images/windows/10/putty-configuration-ev3dev.png new file mode 100644 index 000000000..b4a5f5dc6 Binary files /dev/null and b/images/windows/10/putty-configuration-ev3dev.png differ diff --git a/images/windows/10/putty-robot-at-ev3dev.png b/images/windows/10/putty-robot-at-ev3dev.png new file mode 100644 index 000000000..d5e25cff4 Binary files /dev/null and b/images/windows/10/putty-robot-at-ev3dev.png differ diff --git a/images/windows/10/putty-security-alert.png b/images/windows/10/putty-security-alert.png new file mode 100644 index 000000000..ad36effc1 Binary files /dev/null and b/images/windows/10/putty-security-alert.png differ diff --git a/images/WindowsRNDIS/Local-Area-Connection-Properties-Sharing-with-Extra-Selection.png b/images/windows/8/local-area-connection-properties-sharing-with-extra-selection.png similarity index 100% rename from images/WindowsRNDIS/Local-Area-Connection-Properties-Sharing-with-Extra-Selection.png rename to images/windows/8/local-area-connection-properties-sharing-with-extra-selection.png diff --git a/javascripts/style-helpers.js b/javascripts/style-helpers.js index 7845c64a7..b4ba05e1c 100644 --- a/javascripts/style-helpers.js +++ b/javascripts/style-helpers.js @@ -1,4 +1,6 @@ $(document).ready(function () { // Make
    s more visually separated $('dl').addClass('dl-horizontal'); -}) \ No newline at end of file + $('#markdown-toc').wrap('
    '); + $('#markdown-toc').addClass('list-unstyled'); +}) diff --git a/news/_posts/2015-12-30-ev3dev-jessie-2015-12-30-release.md b/news/_posts/2015-12-30-ev3dev-jessie-2015-12-30-release.md new file mode 100644 index 000000000..02f6070c8 --- /dev/null +++ b/news/_posts/2015-12-30-ev3dev-jessie-2015-12-30-release.md @@ -0,0 +1,107 @@ +--- +author: "@dlech" +title: "Announcing ev3dev-jessie-12-30 Release" +--- + +We have reached the [2015-Q4] milestone (and just barely in time). There are +significant changes in this release, so even if you are an experienced ev3dev +user, read on... + +### Reporting Issues + +Since there are so many changes with this release, we expect there to be new +issues. If you have trouble, check out the [support] page and let us know +about it. Just a friendly reminder... Please don't comment on a closed issue +(unless you are asking to re-open the issue or confirming that it is indeed fixed). +It's always best to open a new issue. It also keeps @dlech happy and sane. + +### Default User + +We are no longer using `root:r00tme` as the default user:password. The new default +user name is `robot` and the password is `maker`. Only files in `/home/robot/` +will show up in the File Browser in the Brickman user interface. + +### File Permission Issues + +We discovered that the method we were previously using to create image files +was fundamentally flawed with regard to file permissions. Basically, every file +on the image was owned by `root:root` even if it was supposed to be owned by +someone else. This caused problems with programs that relied on these file +permissions. + +This issue has been fixed, but unfortunately that means that if you are already +using ev3dev, you need to re-flash your SD card in order to fix these issues. +Don't forget to backup any important files before you re-flash! + +### Raspberry Pi + +This is the first release that support mindsensors.com [PiStorms] out of the box. +**Note:** You will need a USB keyboard or (10-digit keypad with backspace) in +order to use the Brickman user interface. + +We've also added a driver for battery indication on BrickPi+. + +### Open-Roberta Lab + +Thanks to the work of @ensonic, we now have support for +out-of-the-box. It is prevented from running by default, so you do have to start +it manually... + + sudo systemctl unmask openrobertalab.service + sudo systemctl start openrobertalab.service + +After running the commands above, it will start automatically after a reboot. +You can turn it back off by running... + + sudo systemctl stop openrobertalab.service + sudo systemctl mask openrobertalab.service + +### Bigger Font + +One of the most noticeable changes is that we are using a bigger font in the +Brickman user interface. This font looks big on the EV3 but is actually kind +of small on the PiStorms. + +Changing the font size broke lots of screens in Brickman. We have fixed most of +them, but if you find something that doesn't look right, let us know. + +### Faster Swap + +Linux uses what is called a swapfile for virtual memory. This means when your +computer (or EV3) starts to run out of RAM, it moves some of the information +to the swapfile to free up some RAM. + +Conventionally, the swapfile is a file or partition on your hard drive. Hard drives +are much slower than RAM, so when you are using too much memory your computer +starts running really slow because it is moving memory back and forth between +the fast RAM and the slow hard drive. + +With ev3dev, we are running on an SD card, which is even way slower than a hard +drive. The EV3 also only has 64MB of RAM, so it can run out of RAM rather +quickly. In the past, we have had the swapfile on the SD card in various forms, +but this is not so good for two reasons. 1) It makes the EV3 super slow when +memory is swapped and 2) it will wear out your SD card faster because of writing +to it all of the time. + +So, what can we do to make this better? In this release, we are using zram instead. +[Zram] is a relatively new Linux kernel feature that stores information compressed +in RAM. We use this to create a compressed RAM disk for the swapfile. This way +when the memory starts getting full, it is compressed to free up space. + +The processor has to do extra work to compress the information, so it still +makes the EV3 run slower, but it is actually still faster than writing to the SD +card. So, hopefully this release should run a little faster and your SD card will +last a little longer. + +**Note:** ZRAM is currently only enabled on the EV3. The Raspberry Pi images +do not have any swapfile enabled since they have plenty of RAM. + +### Download + +So, you want to download this release? Of course you do! [Click here][download]. + +[support]: http://www.ev3dev.org/support/ +[2015-Q4]: https://github.com/ev3dev/ev3dev/milestones/ev3dev-jessie%202015-Q4 +[PiStorms]: http://www.mindsensors.com/teaching-stem-with-robotics/13-pistorms-base-kit +[zram]: https://en.wikipedia.org/wiki/Zram +[download]: https://github.com/ev3dev/ev3dev/releases/tag/ev3dev-jessie-2015-12-30 diff --git a/projects/index.html b/projects/index.html index f3677cf63..d6a53121a 100644 --- a/projects/index.html +++ b/projects/index.html @@ -9,7 +9,7 @@

    - + {% include icon.html type="info" %} Would you like your project added to the list? We would! Create a page and send us a pull request.
    diff --git a/stylesheets/bootstrap-extensions.css b/stylesheets/bootstrap-extensions.css index 94d0961cd..5285e40dd 100644 --- a/stylesheets/bootstrap-extensions.css +++ b/stylesheets/bootstrap-extensions.css @@ -103,16 +103,17 @@ h1.panel-title { height: 25px; } -#markdown-toc { - display: none; -} - .alert span.glyphicon { margin-right: 8px; } .screenshot { - margin: 20px; + display: table !important; + margin: 20px auto; +} + +.screenshot > a > img { + max-height: 480px; } .inline-screenshot { @@ -123,6 +124,14 @@ h1.panel-title { max-width: 350px; } +.pull-right { + margin-left: 20px; +} + +.pull-left { + margin-right: 20px; +} + sup[id]:before { display: inline-block; } @@ -152,3 +161,7 @@ dd { dd ol, dd ul { margin-top: 10px; } + +ul + p, ol + p { + margin-top: 10.5px; +} diff --git a/support.md b/support.md index b701decf2..50bdce13a 100644 --- a/support.md +++ b/support.md @@ -23,12 +23,11 @@ developers directly unless you have a personal question.) First, before submitting an issue, please make sure that you have the latest kernel and other packages: - # as root... - apt-get update - apt-get upgrade - apt-get dist-upgrade + sudo apt-get update + sudo apt-get upgrade + sudo apt-get dist-upgrade # if a new kernel package was installed - reboot + sudo reboot Then search the existing issues (open and closed) to make sure someone else has not already reported the same problem or asked the same question. Please only