eLinux.org - User contributions [en]

ECE497 Notes on Ubuntu and Audio Cape

2013-02-21T02:34:35Z

Mmoravec: Greg Larmore's notes on the audio cape

To install Ubuntu on the BeagleBone follow the instructions at http://elinux.org/BeagleBoardUbuntu

In Ubuntu, to get ALSA to work with the BeagleBone Audio cape, the following modules should be specified in '/etc/modules'

snd_soc_tlv320aic3x
snd_soc_davinci
snd_soc_davinci_mcasp
snd_soc_evm

You can test the audio by running `speaker-test`. Also running `aplay -l` will show a list of available sound cards. If the sound card is not shown, run `lsmod` and `dmesg` and make sure the kernel modules above have loaded without errors.

Rakarrack is a very nice open source audio effects processor that looks just like a guitar pedalboard. It uses the Jack Audio Connection Kit to stream audio allowing for realtime audio effects

Start by installing jackd2. This requires a patch for the current version (1.9.10) on ARM (see http://jack-audio.10948.n7.nabble.com/Jack-Devel-jack2-on-ARM-patch-td15962.html). Run the recipe found at that page (copied below with a couple modifications).

wget http://jack-audio.10948.n7.nabble.com/attachment/15962/0/jack2_armel.diff
apt-get source jackd2
cd jackd2-1.9.8~dfsg.4+20120529git007cdc37
patch -p1 -i ../jack2_armel.diff
dpkg-buildpackage -rfakeroot -uc -b
cd ..
sudo dpkg -i libjack-jackd2-0_1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1_armhf.deb jackd2_1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1_armhf.deb

Then install Rakarrack by running the following:

sudo apt-get install rakarrack

The installation should install jackd as a dependency. To check the installed jack packages run the following:

dpkg --get-selections | grep jack

You should see something like this:

ubuntu@arm:~$ dpkg --get-selections | grep jack
jack deinstall
jackd install
jackd1 deinstall
jackd2 install
libjack-jackd2-0:armhf install
libjack0:armhf deinstall
qjackctl deinstall

Now you should be able to run the rakarrack GUI. Use `ssh -X ubuntu@192.168.0.XXX` to connect to the BeagleBone with X11 forwarding and then run `rakarrack`. The program should be able to find jackd by itself. If not try killing the jack processes and restart rakarrack. One way to do this is run `ps -AL | grep jack`, and then run `kill -9` with the pid number.

If you have problems with jackd not running you can try running in manually (make sure it is not running in the background first). Run `jackd -d alsa` and the output should look somethings like the following:

ubuntu@arm:/etc$ jackd -d alsa
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2013 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 16 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 16 periods for playback

When Rakarrack opens, it may warn you that your CPU is not fast enough to run some of the audio effects (e.g. convolutron). See (http://forums.fedoraforum.org/archive/index.php/t-254181.html) for some tips on mitigating performance problems. If you crash jackd, you can easily kill its processes as shown above and restart Rakarrack (there is no need to reboot or anything).

Some things to improve performance (a bit...)

Increase clock speed of BeagleBone by running the following:

sudo cpufreq-set -f 720MHz
sudo cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq

The output of that last command should be '720000'

Also in Rakarrack go to 'Settings->Preferences->Audio' and lower all the downsample settings to '4000' and the up to 'Fastest'

With these settings, I was able to get the Expander, Sustainer, Looper, and Dual Flange to work without crasing jackd

[[Category:EmbeddedBeagleClass]]
[[Category:ECE497 |Notes]]

ECE497 Notes on Creating a Beaglebone Cape

2013-02-15T02:34:50Z

Mmoravec:

[[Category:ECE497 |Notes]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Even if you just interested in a fun DIY project, capes are an awesome way to learn a lot about circuit design and embedded systems. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle. Whichever program you use, a trick you can use is to find capes that use components in them that you are using in your design. Find the capes at the links below and download their respective OrCAD or Eagle files and find pads and footprints for your design. If you do this, make sure to reference the design that you used. Otherwise, pads and footprints can also be found by googling the respective part: "msp430 footprint"

Their are advantages to using OrCAD over Eagle. There are more examples and you can run simulations in PSpice before laying out the board in OrCAD. Rose-Hulman also continues to buy licenses for the complete OrCAD suite.

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
*[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

*The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
*[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD.

== The Physical Layout ==
Laying out a PCB can be incredibly difficult. Understanding whether you want 1, 2, or 3 layer boards, how thick should the traces be, how close should the components be placed together, and more are often incredibly overwhelming at first. I cannot stress enough how helpful it would be to attend a PCB workshop that Dr. Simoni holds. He usually has at least one a year. If you cannot make it to a workshop, there are still plenty of resources that you can use to quickly design a PCB.
*Ask Dr. Simoni for his PCB videos. They are not operational currently on the internet, but I believe he still has copies of the videos on his computer
*http://www.expresspcb.com/expresspcbhtm/tips.htm has tips on PCB layout. Definitely a must read for any PCB newbie.
*http://www.robotroom.com/PCB-Layout-Tips.html
*http://www.alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf *****Excellent Tutorial*****

Really the best advice from one Rose student to another is to start asking questions. The lab techs at Rose-Hulman are incredibly helpful if you are respectful. Mark Crosby is the man to ask if you need a PCB printed. After you believe that your circuit is correct, print as many PCBs as needed until it works correctly. Each board that Mark prints is roughly $20. At Rose, you are only able to print a maximum of 2 layers on a board. If you want to print more than that, you will have to send your PCB to a company to get it printed. The cheapest printing that I found in my time at Rose was at 4pcb.com. They can do almost anything and can get the board back to you in as little as 3 days if you pay for the expensive shipping.

ECE497 Notes on Creating a Beaglebone Cape

2013-02-15T02:34:03Z

Mmoravec:

[[Category:ECE497]]
[[Category:Notes]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Even if you just interested in a fun DIY project, capes are an awesome way to learn a lot about circuit design and embedded systems. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle. Whichever program you use, a trick you can use is to find capes that use components in them that you are using in your design. Find the capes at the links below and download their respective OrCAD or Eagle files and find pads and footprints for your design. If you do this, make sure to reference the design that you used. Otherwise, pads and footprints can also be found by googling the respective part: "msp430 footprint"

Their are advantages to using OrCAD over Eagle. There are more examples and you can run simulations in PSpice before laying out the board in OrCAD. Rose-Hulman also continues to buy licenses for the complete OrCAD suite.

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
*[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

*The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
*[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD.

== The Physical Layout ==
Laying out a PCB can be incredibly difficult. Understanding whether you want 1, 2, or 3 layer boards, how thick should the traces be, how close should the components be placed together, and more are often incredibly overwhelming at first. I cannot stress enough how helpful it would be to attend a PCB workshop that Dr. Simoni holds. He usually has at least one a year. If you cannot make it to a workshop, there are still plenty of resources that you can use to quickly design a PCB.
*Ask Dr. Simoni for his PCB videos. They are not operational currently on the internet, but I believe he still has copies of the videos on his computer
*http://www.expresspcb.com/expresspcbhtm/tips.htm has tips on PCB layout. Definitely a must read for any PCB newbie.
*http://www.robotroom.com/PCB-Layout-Tips.html
*http://www.alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf *****Excellent Tutorial*****

Really the best advice from one Rose student to another is to start asking questions. The lab techs at Rose-Hulman are incredibly helpful if you are respectful. Mark Crosby is the man to ask if you need a PCB printed. After you believe that your circuit is correct, print as many PCBs as needed until it works correctly. Each board that Mark prints is roughly $20. At Rose, you are only able to print a maximum of 2 layers on a board. If you want to print more than that, you will have to send your PCB to a company to get it printed. The cheapest printing that I found in my time at Rose was at 4pcb.com. They can do almost anything and can get the board back to you in as little as 3 days if you pay for the expensive shipping.

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T21:13:44Z

Mmoravec:

[[Category:ECE497]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Even if you just interested in a fun DIY project, capes are an awesome way to learn a lot about circuit design and embedded systems. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle. Whichever program you use, a trick you can use is to find capes that use components in them that you are using in your design. Find the capes at the links below and download their respective OrCAD or Eagle files and find pads and footprints for your design. If you do this, make sure to reference the design that you used. Otherwise, pads and footprints can also be found by googling the respective part: "msp430 footprint"

Their are advantages to using OrCAD over Eagle. There are more examples and you can run simulations in PSpice before laying out the board in OrCAD. Rose-Hulman also continues to buy licenses for the complete OrCAD suite.

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
*[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

*The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
*[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD.

== The Physical Layout ==
Laying out a PCB can be incredibly difficult. Understanding whether you want 1, 2, or 3 layer boards, how thick should the traces be, how close should the components be placed together, and more are often incredibly overwhelming at first. I cannot stress enough how helpful it would be to attend a PCB workshop that Dr. Simoni holds. He usually has at least one a year. If you cannot make it to a workshop, there are still plenty of resources that you can use to quickly design a PCB.
*Ask Dr. Simoni for his PCB videos. They are not operational currently on the internet, but I believe he still has copies of the videos on his computer
*http://www.expresspcb.com/expresspcbhtm/tips.htm has tips on PCB layout. Definitely a must read for any PCB newbie.
*http://www.robotroom.com/PCB-Layout-Tips.html
*http://www.alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf *****Excellent Tutorial*****

Really the best advice from one Rose student to another is to start asking questions. The lab techs at Rose-Hulman are incredibly helpful if you are respectful. Mark Crosby is the man to ask if you need a PCB printed. After you believe that your circuit is correct, print as many PCBs as needed until it works correctly. Each board that Mark prints is roughly $20. At Rose, you are only able to print a maximum of 2 layers on a board. If you want to print more than that, you will have to send your PCB to a company to get it printed. The cheapest printing that I found in my time at Rose was at 4pcb.com. They can do almost anything and can get the board back to you in as little as 3 days if you pay for the expensive shipping.

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T21:07:40Z

Mmoravec: /* The Physical Layout */

[[Category:ECE497]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape other than the fact that you will be able to implement almost every functionality you can think of all on one PCB. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle. Whichever program you use, a trick you can use is to find capes that use components in them that you are using in your design. Find the capes at the links below and download their respective OrCAD or Eagle files and find pads and footprints for your design. If you do this, make sure to reference the design that you used. Otherwise, pads and footprints can also be found by googling the respective part: "msp430 footprint"

Their are advantages to using OrCAD over Eagle. There are more examples and you can run simulations in PSpice before laying out the board in OrCAD. Rose-Hulman also continues to buy licenses for the complete OrCAD suite.

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
*[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

*The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
*[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD.

== The Physical Layout ==
Laying out a PCB can be incredibly difficult. Understanding whether you want 1, 2, or 3 layer boards, how thick should the traces be, how close should the components be placed together, and more are often incredibly overwhelming at first. I cannot stress enough how helpful it would be to attend a PCB workshop that Dr. Simoni holds. He usually has at least one a year. If you cannot make it to a workshop, there are still plenty of resources that you can use to quickly design a PCB.
*Ask Dr. Simoni for his PCB videos. They are not operational currently on the internet, but I believe he still has copies of the videos on his computer
*http://www.expresspcb.com/expresspcbhtm/tips.htm has tips on PCB layout. Definitely a must read for any PCB newbie.
*http://www.robotroom.com/PCB-Layout-Tips.html
*http://www.alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf *****Excellent Tutorial*****

Really the best advice from one Rose student to another is to start asking questions. The lab techs at Rose-Hulman are incredibly helpful if you are respectful. Mark Crosby is the man to ask if you need a PCB printed. After you believe that your circuit is correct, print as many PCBs as needed until it works correctly. Each board that Mark prints is roughly $20. At Rose, you are only able to print a maximum of 2 layers on a board. If you want to print more than that, you will have to send your PCB to a company to get it printed. The cheapest printing that I found in my time at Rose was at 4pcb.com. They can do almost anything and can get the board back to you in as little as 3 days if you pay for the expensive shipping.

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T21:04:39Z

Mmoravec:

[[Category:ECE497]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape other than the fact that you will be able to implement almost every functionality you can think of all on one PCB. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle. Whichever program you use, a trick you can use is to find capes that use components in them that you are using in your design. Find the capes at the links below and download their respective OrCAD or Eagle files and find pads and footprints for your design. If you do this, make sure to reference the design that you used. Otherwise, pads and footprints can also be found by googling the respective part: "msp430 footprint"

Their are advantages to using OrCAD over Eagle. There are more examples and you can run simulations in PSpice before laying out the board in OrCAD. Rose-Hulman also continues to buy licenses for the complete OrCAD suite.

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
*[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

*The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
*[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD.

== The Physical Layout ==
Laying out a PCB can be incredibly difficult. Understanding whether you want 1, 2, or 3 layer boards, how thick should the traces be, how close should the components be placed together, and more are often incredibly overwhelming at first. I cannot stress enough how helpful it would be to attend a PCB workshop that Dr. Simoni holds. He usually has at least one a year. If you cannot make it to a workshop, there are still plenty of resources that you can use to quickly design a PCB.
*Ask Dr. Simoni for his PCB videos. They are not operational currently on the internet, but I believe he still has copies of the videos on his computer
*http://www.expresspcb.com/expresspcbhtm/tips.htm has tips on PCB layout. Definitely a must read for any PCB newbie.
*http://www.robotroom.com/PCB-Layout-Tips.html
*http://www.alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf *****Excellent Tutorial*****

Really the best advice from one Rose student to another is to start asking questions. The lab techs at Rose-Hulman are incredibly helpful if you are respectful. Mark Crosby is the man to ask if you need a PCB printed. After you believe that your circuit is correct, print as many PCBs as needed until it works correctly. At Rose, you are only able to print a maximum of 2-layers on a board. If you want to print more than that, you will have to send your PCB to a company to get it printed. The cheapest printing that I found in my time at Rose was at 4pcb.com. They can do almost anything and can get the board back to you in as little as 3 days if you pay for the expensive shipping.

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:59:56Z

Mmoravec: Adding a lot more information about board layout

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:50:31Z

Mmoravec: /* Building a Schematic */

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:45:15Z

Mmoravec: /* Building a Schematic */

[[Category:ECE497]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape other than the fact that you will be able to implement almost every functionality you can think of all on one PCB. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle. Whichever program you use, a trick you can use is to find capes that use components in them that you are using in your design. Find the capes at the links below and download their respective OrCAD or Eagle files and find pads and footprints for your design. If you do this, make sure to reference the design that you used. Otherwise, pads and footprints can also be found by googling the respective part: "eagle footprint msp430"

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
*[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

*The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
*[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD.

;

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:42:34Z

Mmoravec: /* Building a Schematic */

[[Category:ECE497]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape other than the fact that you will be able to implement almost every functionality you can think of all on one PCB. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle.

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
*[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

*The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
*[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD. There are a few that were not however.

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:41:39Z

Mmoravec:

[[Category:ECE497]]
[[Category:EmbeddedBeagleClass]]

So you are thinking about building a Beaglebone cape? Awesome! There are a lot of reasons to make a cape other than the fact that you will be able to implement almost every functionality you can think of all on one PCB. In 2012, beagleboard.org and circuitco held a [http://beagleboard.org/capecontest Beagle Cape competition] and gave the top three design entries $1000 dollars plus lifetime royalties on sales of the cape on circuitco. You could also try to get your cape licensed and sold by Adafruit, Sparkfun, or other DIY websites separately. Good Luck!

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

When choosing parts that you want on your cape, realize that some parts are easier to put on PCBs than others. Try looking up libraries for the parts you want to use by googling "msp430 allegro library" or "msp430 Eagle library." If there is not library, you will likely have to create a pad and footprint for the part.

== Tools Needed ==
[[File:EagleCadSymbol.png]]

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

[[File:Cadence_logo3.gif]]

Cadence Allegro is licensed to the Rose-Hulman, so it is free to Rose students. Allegro is a little bit harder overall to make PCB's in, but it is supported by the ECE department. Ask Dr. Simoni for help on the PCB. He has a website with video tutorials and other walk-throughs to help you with the process. Rose-Hulman licenses it free for use for any current students. It can be downloaded from the DFS folder. The folder also has instructions on how to install it.

Allegro PCB is licensed by the school and used by many professional organizations throughout the world. See Dr. Simoni for advanced help.

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

After the evaluation modules are ordered, grab your breadboard such as:

[[File:Breadboard.jpg]]

and begin placing components and wiring everything together.

Realize that if you need any help with the power supplies or other aspect of wiring, refer to the datasheets of the parts you are using. For example, the [http://www.ti.com/lit/ds/symlink/msp430g2553.pdf datasheet] for the MSP430 that I mentioned before indicates that it needs a power supply voltage between 2.2 and 3.6. This means that the 3.3V VCC coming out of the Beaglebone would work perfectly in powering the MSP430.

== Building a Schematic ==

After prototyping, you know where each of the wires is to be routed. The next step is to connect all of the components together in your CAD program of choice. There are excellent circuit layout examples to follow in both OrCAD and Eagle.

[[File:EagleCadSymbol.png]]

There are fewer Eagle examples, but a few excellent examples include:
[http://ioclk.com/wp-content/uploads/2012/11/QiLiCape-ioclk.v01.rar QiLiCape] Credit goes to http://ioclk.com/beagebone-qilicape-a-wireless-power-charger-cape-for-beaglebone/

The Adafruit prototype board https://github.com/adafruit/Adafruit-BeagleBone-ProtoBoard

[[File:Cadence_logo3.gif]]

Excellent Cadence Examples include:
[http://beagleboardtoys.info/index.php?title=Main_Page CircuitCo Examples] Most of the capes on this page where designed in OrCAD. There are a few that were not however.

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:19:16Z

Mmoravec: /* First Step: Prototyping */

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:15:10Z

Mmoravec: /* First Step: Prototyping */

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T20:14:59Z

Mmoravec: /* First Step: Prototyping */

File:Breadboard.jpg

2013-02-12T20:14:22Z

Mmoravec:

ECE497 Notes on Creating a Beaglebone Cape

2013-02-12T19:57:31Z

Mmoravec: /* Tools Needed */

File:Cadence logo3.gif

2013-02-12T19:56:05Z

Mmoravec:

File:EagleCadSymbol.png

2013-02-12T19:48:49Z

Mmoravec: eagle cad symbol

eagle cad symbol

ECE497 Notes on Creating a Beaglebone Cape

2013-02-07T15:51:23Z

Mmoravec: Updating page with more information

ECE497 Notes on Creating a Beaglebone Cape

2013-02-07T14:56:42Z

Mmoravec: Updating page with more information

BeagleStomp Cape

2012-12-30T18:06:03Z

Mmoravec:

== Overview ==
This project is a cape for a Beaglebone linux computer [http://beagleboard.org/bone Beaglebone Website] that turns the Beagle into a guitar effects system. The cape officially supports [http://dashersw.github.com/pedalboard.js/ PedalBoard.js] as the guitar effects processor. Input ports allow the user to connect switches and pedals to the board to control the guitar effects on the fly.

== Features ==
The BeagleStomp Cape includes high quality audio processing with an easy to use web interface and customizable input options.

== Materials ==
The schematic was created with free, Eagle CAD software [http://www.cadsoftusa.com/ Eagle Site]. The schematics we have created are open source and located on GitHub [https://github.com/larmoreg/StompCape Git Repository]. The GitHub site houses all of the documentation including datasheets and our bill of materials.

BeagleStomp Cape

2012-12-30T18:04:31Z

Mmoravec: creating a page for our beaglestomp cape.

== Overview ==
This project is a cape for a Beaglebone linux computer [http://beagleboard.org/bone] that turns the Beagle into a guitar effects system. The cape officially supports [http://dashersw.github.com/pedalboard.js/ PedalBoard.js] as the guitar effects processor. Input ports allow the user to connect switches and pedals to the board to control the guitar effects on the fly.

== Features ==
The BeagleStomp Cape includes high quality audio processing with an easy to use web interface and customizable input options.

== Materials ==
The schematic was created with free, Eagle CAD software [http://www.cadsoftusa.com/]. The schematics we have created are open source and located on GitHub [https://github.com/larmoreg/StompCape]. The GitHub site houses all of the documentation including datasheets and our bill of materials.

ECE497 Notes on Creating a Beaglebone Cape

2012-12-13T15:00:48Z

Mmoravec:

[[Category:ECE497]]
[[Category:EmbeddedBeagleClass]]

This will be the introduction to the page

== Design Decisions ==

The first issue that must be tackled is what exactly you want on your cape. There is a [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Google Spreadsheet] that lists most Beaglebone capes that have been completed or are in the process of being completed. If the cape you are building does not have components on it that are in the repository, it is probably time to ask yourself whether the beaglebone supports the hardware you have selected.

Also, if your cape idea is really similar to one in the repository, I wouldn't get too down about it. Paypal is really similar to Google Checkout, Wirecard, and Moneybookers, but continues to be the standout internet money handling service for various reasons. Basically, I would suggest continuing to work on your idea. Especially if it offers something unique that the other solutions in the repository do not include.

== Tools Needed ==

Eagle CAD is an open source schematic layout and PCB editor environment that is used by most of the PCB open source community. You can find the latest version of Eagle [http://www.cadsoftusa.com/download-eagle/?language=en here].

== First Step: Prototyping ==

No Beaglebone cape is known to work until all of the suggested components are prototyped together with various development boards and a Beaglebone. Texas Instruments has many development kits listed on their website product pages. For example, if you navigate to the page for a common [http://www.ti.com/product/msp430g2553 MSP430 Processor] you will find on the right side of the page links to evaluation modules, development tools, and other information.

The other place to look for prototyping information is on the product page itself at vendors like Digikey, Mouser, and Allied Electronics. The MSP430 that we just looked at on the TI website can also be found on the [http://www.mouser.com/ProductDetail/Texas-Instruments/MSP430G2553IPW28/?qs=sGAEpiMZZMsuBfEaN9EhVfH4Abelljmf Mouser website] where you can buy it for $2.00. See also that the Mouser website has information such as a datasheet and schematic footprints for the specific product.

== Building a Schematic ==

Eagle CAD is a fully featured CAD program that can be had for the low price of $0 as long as you are okay with these limitations:
*The useable board area is limited to 100 x 80 mm (4 x 3.2 inches).
*Only two signal layers can be used (Top and Bottom).
*The schematic editor can only create one sheet.

Pads and footprints are the metal conductors that the components going on the PCB are soldered. An example footprint is shown below for an MSP430 processor.

ECE497 Notes on Creating a Beaglebone Cape

2012-12-13T14:13:40Z

Mmoravec: /* First Step: Prototyping */

ECE497 Notes on Creating a Beaglebone Cape

2012-12-13T14:11:39Z

Mmoravec: added more information and another section

ECE497 Notes on Creating a Beaglebone Cape

2012-12-06T14:38:31Z

Mmoravec: /* Tools Needed */

ECE497 Notes on Creating a Beaglebone Cape

2012-12-06T14:36:47Z

Mmoravec: Creating a page that talks about how to go about designing a Beaglebone Cape.

ECE497 Project: XBee

2012-11-13T04:36:50Z

Mmoravec: /* Wireless 2-Axis Thumb Joystick */

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[User:Shinnsm|Stephen Shinn]], [[User:Mmoravec|Matt Moravec]], [[User:Duganje|Josh Dugan]].

== Grading Template ==

I'm using the following template to grade. Each slot is 10 points.
0 = Missing, 5=OK, 10=Wow!

<pre style="color:red">
00 Executive Summary
05 Installation Instructions
01 User Instructions
00 Highlights
00 Theory of Operation
00 Work Breakdown
00 Future Work
00 Conclusions
00 Demo
00 Late
Comments: I'm looking forward to seeing this.

Score: 06/100
</pre>

== Executive Summary ==

The XBee project involves taking two series-one XBee modules and interfacing them with the various sensors that have been documented in our ECE497 group. Our goal was to create wiki sections which expand on the sensors to include sample wireless communication documentation and source code.

We have successfully connected to the XBee radios from the Bones and sent data using the <code>/dev/ttyO</code> file system. We have also successfully done wireless implementations of the force sensitive resistor, the magnetometer, and the joystick alone a set of functions for expanding this to any sensor.

In conclusion, we're using XBee modules to communicate from one Bone to another. We have successfully communicated wirelessly with three sensors: the force sensitive resistor, magnetometer, and joystick. We hope that these instructions and code libraries are useful to hobbyists who wish to implement their own wireless solutions with the BeagleBone.

== General Installation Instructions ==

=== Hardware ===

The very first step is to solder your XBee module, see [http://www.ladyada.net/make/xbee/solder.html the instructions here]. Once the module is assembled, you may wire-up the XBee module to the BeagleBone's serial ports. The table below describes how to hook up the module to UART2 on the Bone:

{| class="wikitable" style="text-align:center;" width=300px
! align="center"| XBee
! Bone, P9 header
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

The image below shows the configuration:

[[File:XBeeBoneConnection.jpg|450px|XBee module connected to a BeagleBone.]]

=== Software ===

Our git repo for this project is available here: [https://github.com/duganje/ECE497_XBEE.git https://github.com/duganje/ECE497_XBEE.git]. To begin, run
beagle$ git clone https://github.com/duganje/ECE497_XBEE.git
to clone he repository. This contains three folders with examples of XBee implementation for specific sensors and <code>XBee.c</code>, which contains helper functions for using the XBee. You are now able to send data wirelessly using the <code>SendIntXbee()</code> and <code>ReceiveIntXbee()</code> functions. Repeat this procedure on a separate BeagleBone and use the same functions to receive and reply data.


== 0.5" Force Sensitive Resistor ==

These instructions are for interfacing the [[SparkFun: 0.5" Force Sensitive Resistor|0.5" Force Sensitive Resistor]] with the XBee.

=== Required Items ===

*2 x [http://adafruit.com/products/513 BeagleBone]
*2 x [http://www.adafruit.com/products/128 XBee Module]
*2 x [http://www.adafruit.com/products/126 XBee Adaptor Kit]
*1 x [https://www.sparkfun.com/products/9375 0.5" Force Sensitive Resistor]
*1 x 27kΩ resistor

=== Hardware ===

First we will connect the force-sensitive resistor to the Bone (P9 header). A 27kΩ resistor is used to connect the 3.3V source (pin 3) from the Bone to one pin of the force-sensitive resistor. Then, the other pin of the force-sensitive resistor is connected to ground (pin 1). An analog pin (AIN) on the Bone connects to the node containing both resistors, and values can be read off of that AIN. AIN5 (pin 36) is being used to read values on the Bone.

Next we will connect the XBee module to the Bone. The table below describes the necessary wiring.

{| class="wikitable" style="text-align:center;" width=300px
! align="center"| XBee
! Bone, P9 header
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

With everything wired-up, your connections should match the image below. Click on the image to view the full resolution.

[[File:ForceResistorXBee.jpg|600px|Picture of connection|link=http://elinux.org/images/3/3b/ForceResistorXBee.jpg]]

=== Software ===

We're going to start with these two pieces of code as a reference and combine them:

*[https://github.com/shinnsm/ECE497/blob/master/MiniProject02/miniProj2.c Code to interface with the force sensitive resistor]
*[https://github.com/duganje/ECE497_XBEE/blob/master/XBee.c Code to interface with the XBee module]

Running the code for the force sensitive resistor produces a value from 0 to 4096 depending on how much pressure is applied to the resistor. The harder the resistor is squeezed, the lower this value is. On line 46 of the force sensitive resistor code, <code>analogValue</code> is constantly updated and stores this number.

The instructions now fork depending on whether you're setting up the sending XBee code or the receiving XBee code. When you're done you will have two C programs, one running on each Bone.

==== Sending ====

Start with the [https://github.com/shinnsm/ECE497/blob/master/MiniProject02/miniProj2.c resistor code] as a base and add the following include to the top of the file to add our XBee library (available [https://github.com/duganje/ECE497_XBEE here]):

#include "XBee.h"

Next, add a call to <code>initializeXbee()</code> in <code>main</code> of the resistor code before the while loop begins.

In the <code>while</code> loop after the value of <code>analogValue</code> is updated, add this line:

sendIntXbee(analogValue);

This will send the integer analog value to the receiving XBee. Now the number is constantly being sent in the while loop.

==== Receiving ====

Start with the [https://github.com/duganje/ECE497_XBEE/blob/master/XBee.c XBee code] as a base and create a <code>main</code> function. First in <code>main</code>, add a call to <code>initializeXbee()</code> to setup the Bone to use the module.

Next, add a while loop to <code>main</code> which continuously receives the integer analog value from the other Bone using the <code>receiveIntXbee()</code> function. Once the integer value is received, you're free to use that information for whatever purpose you wish. The example code below should give you an idea of how this is done:

<pre>void main(int argc, char **argv, char **envp) {
// Initialize XBee
initializeXbee();

// Keep going
while (1) {
int analogValue = receiveIntXbee();

// Do anything based on analog value
if (analogValue < 1000)
ButtonPressedFunction();
}
}</pre>

==== Sample ====

===== Required Items =====

* LED
* 220Ω resistor

===== Instructions =====

Based on the instructions above, I've created a sample set of programs. Using two Bones, the send program runs on one and the receive program runs on another. The "send" Bone includes an XBee module and the force sensitive resistor, [[ECE497 Project: XBee#Hardware 2|hooked-up as described here]]. The second Bone includes the XBee module hooked-up in the same way with the addition of an LED connected to pin 12 (GPIO1_28) of the Bone. Connect the ground pin of the LED to the Bone's ground (pin 1) using a 220Ω resistor.

Running both programs emulates the original function of the [https://github.com/shinnsm/ECE497/blob/master/MiniProject02/miniProj2.c force resistor sample code], the only difference being that the data is now sent wirelessly from one Bone to another.

*[https://github.com/duganje/ECE497_XBEE/blob/master/ForceResistor/sendResistor.c Send Program]
*[https://github.com/duganje/ECE497_XBEE/blob/master/ForceResistor/receiveResistor.c Receive Program]

To easily run the programs, follow these steps (you can skip the first step if you have already clone the repository):
beagle$ git clone https://github.com/duganje/ECE497_XBEE.git
beagle$ cd ECE497_XBEE
beagle$ cd ForceResistor
beagle$ make

This will create 2 executables: '''sendResistor''' and '''receiveResistor'''. Run the programs by running:

beagle$ ./sendResistor

on the Bone connected to the XBee and the force sensitive resistor and

beagle$ ./receiveResistor

on the Bone connected to the XBee and the LED.

You will then be able to squeeze the force sensitive resistor and see the LED light up on the other BeagleBone. We've created a [[ECE497 Project: XBee#Force Sensitive Resistor YouTube Demo|YouTube demo]] of this program in action.

== Wireless 2-Axis Thumb Joystick ==

These instructions are for interfacing the [[Adafruit: 2-Axis Thumb Joystick|2-Axis Thumb Joystick]] with the XBee. This application could be useful in a wireless controller setting.

=== Required Items ===

*2 X [http://adafruit.com/products/513 BeagleBone]
*2 X [http://www.adafruit.com/products/128 XBee Module]
*2 X [http://www.adafruit.com/products/126 XBee Adaptor Kit]
*1 X [[Adafruit: 2-Axis Thumb Joystick|2-Axis Thumb Joystick]]

=== BeagleBone Wiring Instructions ===

On your first BeagleBone, wire pins 36 and 38 to your two analog inputs. Wire the Beagle's 1.8V VCC output, pin 32, to the VCC input of the Joystick. Finally, wire the select GPIO signal to the GPIO_7 pin or pin 42.

Wire the XBee as shown in the table below:
{| class="wikitable" style="text-align:center;" width=300px
! align="center"| XBee
! Bone, P9 header
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

The pinout and visual implementation are shown below.

[[File:Bone_P9_pinout.jpg|x400px]] [[File:XBee_and_Adafruit_Joystick.jpg|x400px]]

On the second BeagleBone, wire the XBee exactly as the first XBee (as described in the table above).

Don't hook up any other hardware to the second XBee as it will be acting as an information hub.

=== Usage Instructions ===

On both BeagleBones, clone this repository: https://github.com/duganje/ECE497_XBEE.git
Use the following to run the joystick code (you can skip the first step if you have already cloned the repository):

beagle$ git clone https://github.com/duganje/ECE497_XBEE.git
beagle$ cd ECE497_XBEE
beagle$ cd 2AxisJoystick
beagle$ make

This will create 2 executables: '''joystickSend''' and '''joystickReceive'''. Run the code by doing:

beagle$ ./joystickSend

on the Bone connected to the XBee and the joystick and:

beagle$ ./joystickReceive

on the Bone connected to just the XBee.

== Magnetometer ==

These instructions are for interfacing the [[Sparkfun: HMC5883L Magnetometer|HMC5883L Magnetometer]] with the XBee.

=== Required Items ===

*2 x [http://adafruit.com/products/513 BeagleBone]
*2 x [http://www.adafruit.com/products/128 XBee Module]
*2 x [http://www.adafruit.com/products/126 XBee Adaptor Kit]
*1 x [https://www.sparkfun.com/products/10530? Magnetometer Breakout Board]

===Hardware===

The XBee radios should be connected to both Beagles as shown in the table below.

{| class="wikitable" style="text-align:center;" width=300px
! align="center"| XBee
! Bone, P9 header
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

The Magnetometer should be connected to one BeagleBone as described in the [[Sparkfun: HMC5883L Magnetometer|hardware]] section of the Magnetometer page. Ground and Vcc on the Magnetometer should be connected to pins 1 and 3 respectively on header P9 of the bone. SCL and SDA on the Magnetometer should be connected to pins 19 and 20 on P9 to use I2C bus 3. Two 4.7kΩ resistors should also be connected between SCL and Vcc and between SDA and Vcc. Below is a picture of the Beagle connected to the Magnetometer and the XBee.

[[File:XBEE_MAG.jpg|600px|Picture of connections]]

===Software===

The goal is to have the two BeagleBones attached to XBee radios with the one connected to the Magnetometer taking data and transmitting this data to the other Bone which will print the measured data.

I started with the code to collect data from the Magnetometer and the code to send data using the XBee radios. Here are the links to these two programs:
*[https://github.com/duganje/ECE497_duganje/blob/master/MiniProject02/miniproject02.c Code to gather magnetometer data]
*[https://github.com/duganje/ECE497_XBEE/blob/master/XBee.c Code to interface with the XBee module]

The code for the magnetometer uses I2C to read the values for the X, Y and Z-Axes and print these values to the terminal. The XBee code contains helper functions to transmit data wirelessly. I have written two programs: one to collect and transmit the magnetometer data and the other to receive and display this data.

====Sending====

*[https://github.com/duganje/ECE497_XBEE/blob/master/Magnetometer/sendMag.c Tranmitting Magnetometer Data Code]

The code uses [https://github.com/MarkAYoder/BeagleBoard-exercises/tree/master/i2c I2C code] from [[EBC Exercise 12 I2C]] and helper functions from [https://github.com/duganje/ECE497_XBEE/blob/master/XBee.c XBee.c].

The program uses:

i2cget(i2cbus, address, daddress);

to get the data from the magnetometer and

sendShortXbee(val);

to send these values to the receiving XBee.

====Receiving====

*[https://github.com/duganje/ECE497_XBEE/blob/master/Magnetometer/receiveMag.c Receiving Magnetometer Data Code]

The receiving code uses:

receiveShortXbee();

to read the values for each axis.

Because we do not have a way to synchronize the two XBees, the receiving program must be started first to ensure the data is receive in the correct order.

In the Highlights section, there is a video demo of the complete program.

===Running the Code===
Use the following to run the magnetometer code (you can skip the first step if you have already clone the repository):

beagle$ git clone https://github.com/duganje/ECE497_XBEE.git
beagle$ cd ECE497_XBEE
beagle$ cd Magnetometer
beagle$ make

This will create 2 executables: '''receiveMag''' and '''sendMag'''. Run the code by doing:

beagle$ ./sendMag

on the Bone connected to the XBee and the magnetometer and:

beagle$ ./receiveMag

on the Bone connected to just the XBee.

== General Usage ==

These instructions are a general how-to for using the XBee with any sensor.

After cloning our repository to your favorite location, include the necessary header file, <code>XBee.h</code>. In your <code>main.c</code> file or your program, first run: <pre>initializeXbee();</pre> which sets the pins we will need to communicate with the XBee using UART 2. Then in your <code>main.c</code> file, call: <pre>sendIntXbee(yourInt);</pre> with <code>yourInt</code> being any integer data you would like to transmit. On your 2nd BeagleBone, call: <pre>receiveIntXbee();</pre> which will return the integer which was sent through <code>sendIntXbee(int yourInt)</code> on the 1st board.

The send and receive functions can be easily modified to send any data type, as shown in <code>XBee.c</code> with the following functions:

<pre>sendShortXbee(short yourShort);</pre>
<pre>receiveShortXbee();</pre>

== Highlights ==

Our project is able to send and receive wireless data for a whole range of possible implementations. We've created YouTube demos for the three sensor implementations we've described so far:

=== Force Sensitive Resistor YouTube Demo ===
{{#ev:youtube|Ds_BWsrvy1I}}

=== 2-Axis Thumb Joystick YouTube Demo ===
{{#ev:youtube|9t1MQGYNOt4}}

=== Magnetometer YouTube Demo ===
{{#ev:youtube|99bFqE54UHM}}

== Theory of Operation ==

The main theory of operation is based on Linux's use of files. UART files on the Bone represent serial connections. With an XBee connected to the Bone's UART 2 as shown above, sent and received messages are written to <code>/dev/ttyO2</code> (the O is an uppercase O, not a zero). The BeagleBone's UARTs are accessed through <code>/dev/ttyO'''x'''</code>, where <code>'''x'''</code> is the UART number. Our code uses this and reads the file to receive a message and writes to the file to send a message. Any XBee's on the same network wil receive the message and we can do anything we want with it.

== Work Breakdown ==

=== Milestones ===

*Monday, 10/29 - XBee hardware received. (done)
*Thursday, 11/1 - XBee Bones are connected and commands can be sent. (done)
*Monday, 11/5 - Initial sensor implementation. (done)
*Thursday, 11/8 - Package language implemented between Bones. (done)
*Sunday, 11/11 - YouTube demo uploaded. (done)
*Monday, 11/12 - All documentation complete. (done)
*Tuesday, 11/13 - Everything complete & all code ''makes''. (done)

=== Completed Work ===

* Soldering XBee's - Matt Moravec
* Initial communication methods - Stephen Shinn
* Expanded communication methods - Josh Dugan
* Initialization method - Josh Dugan
* Force Sensitive Resistor implementation and demo - Stephen Shinn
* Magnetometer implementation and demo - Josh Dugan
* 2-Axis Thumb Joystick implementation and demo - Matt Moravec

== Future Work ==

The following are some additional things that could be done with this project:

* Create and document interfaces for more sensors
* Back-and-forth 2-sensor communication
* Create a practical application such as a wireless doorbell

== Conclusions ==

In conclusion, we created an XBee wireless communication library for BeagleBone and adapted three sensors to use it. We've also documented general usage instructions for adapting XBee to use any type of sensor. We have not found a comprehensive source for how to use XBee modules with the BeagleBone, so our code and instructions are online with the intention that others use them as a reference.

We were unable to get a working program with 2-way communication with 2 XBees each sending and receiving data because of synchronization problems. Addressing this would require the development of a communication protocol to prevent deadlocks and to ensure the receiving program knows what the data is when it receives it. This would be a logical next step in terms of future work for this project.

Using the wireless modules is interesting, and there is a number of things you can do with them. We've listed a few ideas above which could be done in the future. One interesting idea would be to create a practical XBee application that someone could actually use in their home or work life. With a few XBees around the house, one could have a small network for sending data and using a sensor to control Christmas lights or something.

{{YoderFoot}}

ECE497 Project: XBee

2012-11-08T01:17:35Z

Mmoravec: /* 2-Axis Thumb Joystick */

ECE497 Project: XBee

2012-11-08T00:59:56Z

Mmoravec: /* BeagleBone Wiring Instructions */

ECE497 Project: XBee

2012-11-08T00:58:59Z

Mmoravec: /* 2-Axis Thumb Joystick */

ECE497 Project: XBee

2012-11-08T00:56:54Z

Mmoravec: /* Installation Instructions */

ECE497 Project: XBee

2012-11-08T00:56:22Z

Mmoravec: /* Specific Sensor Instructions */

ECE497 Project: XBee

2012-11-08T00:42:56Z

Mmoravec: /* 2-Axis Thumb Joystick */

File:XBee and Adafruit Joystick.jpg

2012-11-06T17:32:46Z

Mmoravec: connection between the XBee and analog joystick.

connection between the XBee and analog joystick.

User:Mmoravec

2012-11-06T16:52:55Z

Mmoravec: updated to make sure my page is being sorted appropriatelly

I'm in Mark Yoder's ECE 497 Beagleboard class. This user page is not used for much right now.

[[ECE497 - 32-bit Embedded Linux, Rose-Hulman]]

[[Category:ECE497 |Um]]

ECE497 Project: XBee

2012-11-04T18:43:39Z

Mmoravec: /* User Instructions */

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[User:Shinnsm|Stephen Shinn]], [[User:Mmoravec|Matt Moravec]], [[User:Duganje|Josh Dugan]].

== Executive Summary ==

The XBee project involves taking two series-one XBee modules and interfacing them with the various sensors that have been documented in our ECE497 group. Our goal is to create wiki pages which expand on the sensors to include sample wireless communication documentation and source code.

Right now the various sensors have been documented and are working. We've received the XBee modules and soldered them as required. So far we've been able to send a receive messages from an XBee connected to a Windows PC to one connected to a Bone, and vice versa. We've started development on C code which is used to send and receive commands on the Bone. When finished, we'll have a library of methods for communication.

Our next step is to move to Bone-to-Bone communication and to be able to control our sensors wirelessly from one Bone to the other.

In conclusion, we're using XBee modules to communicate from one Bone to another. A protocol is in development and will be used for controlling sensors wirelessly.

== Installation Instructions ==

=== Hardware ===

The very first step is to solder your XBee module, see [http://www.ladyada.net/make/xbee/solder.html the instructions here]. Once the module is assembled, you may wire-up the XBee module to the BeagleBone's serial ports. The table below describes how to hook up the module to UART2 on the Bone:

{|
! align="left"| XBee
! Bone
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

The image below shows the configuration:

[[File:XBeeBoneConnection.jpg|450px|XBee module connected to a BeagleBone.]]

=== Software ===

Our git repo for this project is available here: [https://github.com/duganje/ECE497_XBEE github.com/duganje/ECE497_XBEE]. To begin, download the <code>serial.c</code> file which houses our communication methods. You are now able to send data wirelessly using the <code>SendIntXbee()</code> and <code>ReceiveIntXbee()</code> functions. Repeat this procedure on a separate BeagleBone and use the same functions to receive and reply data.

== User Instructions ==

TO DO: How to use the send and receive functions. Include screenshots.

After cloning our repository to your favorite location, include the necessary header file, <code>XBee.h</code> (not created yet). In your <code>main.c</code> file or your program, first run: <pre>initializeXbee();</pre> which sets the pins we will need to communicate to the XBee. Then in your main.c call: <pre>sendIntXbee(int yourInt);</pre> with chars as a string characters you choose. On your 2nd BeagleBone, call: <pre>receiveIntXbee();</pre> which will return the integers which were sent through <code>sendIntXbee(int yourInt)</code> on the 1st board.


== Highlights ==

TBD: Showcase an example of a sensor controlling something wireless.

== Theory of Operation ==

The main theory of operation is based on Linux's use of files. With an XBee connected to the Bone's UART, sent and received messages are written to the ttyO2 file. Our code uses this and reads the file to receive a message and writes to the file to send a message. Any XBee's on the same network wil receive the message and we can do anything we want with it.


== Work Breakdown ==

=== Milestones ===

*Monday, 10/29 - XBee hardware received. (done)
*Thursday, 11/1 - XBee Bones are connected and commands can be sent. (done)
*Monday, 11/5 - Initial sensor implementation.
*Thursday, 11/8 - Package language implemented between Bones.
*Sunday, 11/11 - YouTube demo uploaded.
*Monday, 11/12 - All documentation complete.
*Tuesday, 11/13 - Presentation day; PowerPoint complete.

=== Completed Work ===

* Soldering XBee's - Matt Moravec
* Initial communication methods - Stephen Shinn
* Expanded communication methods - Josh Dugan

=== To Do ===

* Sensor implementation: starting with the sensors that we interfaced earlier in the class
* Wiki pages

== Future Work ==
TBD

== Conclusions ==
TBD

{{YoderFoot}}

ECE497 Project: XBee

2012-11-02T16:15:06Z

Mmoravec: /* User Instructions */

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[User:Shinnsm|Stephen Shinn]], [[User:Mmoravec|Matt Moravec]], [[User:Duganje|Josh Dugan]].

== Executive Summary ==

The XBee project involves taking two series-one XBee modules and interfacing them with the various sensors that have been documented in our ECE497 group. Our goal is to create wiki pages which expand on the sensors to include sample wireless communication documentation and source code.

Right now the various sensors have been documented and are working. We've received the XBee modules and soldered them as required. So far we've been able to send a receive messages from an XBee connected to a Windows PC to one connected to a Bone, and vice versa. We've started development on C code which is used to send and receive commands on the Bone. When finished, we'll have a library of methods for communication.

Our next step is to move to Bone-to-Bone communication and to be able to control our sensors wirelessly from one Bone to the other.

In conclusion, we're using XBee modules to communicate from one Bone to another. A protocol is in development and will be used for controlling sensors wirelessly.

== Installation Instructions ==

=== Hardware ===

The very first step is to solder your XBee module, see [http://www.ladyada.net/make/xbee/solder.html the instructions here]. Once the module is assembled, you may wire-up the XBee module to the BeagleBone's serial ports. The table below describes how to hook up the module to UART2 on the Bone:

{|
! align="left"| XBee
! Bone
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

The image below shows the configuration:

http://i.imgur.com/zm4uu.jpg

=== Software ===

Our git repo for this project is available here: [https://github.com/duganje/ECE497_XBEE github.com/duganje/ECE497_XBEE]. To begin, download the C file which houses our communication methods. You are now able to send data wirelessly using the SendXbee() and ReceiveXbee() functions. Repeat this procedure on a separate BeagleBone and use the same functions to receive and reply data.


== User Instructions ==

TO DO: How to use the send and receive functions. Include screenshots.

After cloning our repository to your favorite location, include the necessary header file, XBee.h. In your main.c file or your program, first run <pre>initializeXBee();</pre> which sets the pins we will need to communicate to the XBee. Then in your main.c call <pre>sendXBee(chars);</pre> with chars as a string characters you choose. On your 2nd beagleboard, call <pre>receiveXBee();</pre> which will return the string of characters which were sent through <pre>sendXBee();</pre> on the 1st board.


== Highlights ==

TBD: Showcase an example of a sensor controlling something wireless.

== Theory of Operation ==

The main theory of operation is based on Linux's use of files. With an XBee connected to the Bone's UART, sent and received messages are written to the ttyO2 file. Our code uses this and reads the file to receive a message and writes to the file to send a message. Any XBee's on the same network wil receive the message and we can do anything we want with it.


== Work Breakdown ==

=== Milestones ===

*Monday, 10/29 - XBee hardware received. (done)
*Thursday, 11/1 - XBee Bones are connected and commands can be sent. (done)
*Monday, 11/5 - Initial sensor implementation.
*Thursday, 11/8 - Package language implemented between Bones.
*Sunday, 11/11 - YouTube demo uploaded.
*Monday, 11/12 - All documentation complete.
*Tuesday, 11/13 - Presentation day; PowerPoint complete.

=== Completed Work ===

* Soldering XBee's - Matt Moravec
* Initial communication methods - Stephen Shinn
* Expanded communication methods - Josh Dugan

=== To Do ===

* Sensor implementation: starting with the sensors that we interfaced earlier in the class
* Wiki pages

== Future Work ==
TBD

== Conclusions ==
TBD

{{YoderFoot}}

ECE497 Project: XBee

2012-11-02T14:50:57Z

Mmoravec: /* To Do */

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[User:Shinnsm|Stephen Shinn]], [[User:Mmoravec|Matt Moravec]], [[User:Duganje|Josh Dugan]].

== Executive Summary ==

The XBee project involves taking two series-one XBee modules and interfacing them with the various sensors that have been documented in our ECE497 group. Our goal is to create wiki pages which expand on the sensors to include sample wireless communication documentation and source code.

Right now the various sensors have been documented and are working. We've received the XBee modules and soldered them as required. So far we've been able to send a receive messages from an XBee connected to a Windows PC to one connected to a Bone, and vice versa. We've started development on C code which is used to send and receive commands on the Bone. When finished, we'll have a library of methods for communication.

Our next step is to move to Bone-to-Bone communication and to be able to control our sensors wirelessly from one Bone to the other.

In conclusion, we're using XBee modules to communicate from one Bone to another. A protocol is in development and will be used for controlling sensors wirelessly.

== Installation Instructions ==

=== Hardware ===

The very first step is to solder your XBee module, see [http://www.ladyada.net/make/xbee/solder.html the instructions here]. Once the module is assembled, you may wire-up the XBee module to the BeagleBone's serial ports. The table below describes how to hook up the module to UART2 on the Bone:

{|
! align="left"| XBee
! Bone
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

The image below shows the configuration:

<PIC>

=== Software ===

Our git repo for this project is available here: [https://github.com/duganje/ECE497_XBEE github.com/duganje/ECE497_XBEE]. To begin, download the C file which houses our communication methods. You are now able to send data wirelessly using the SendXbee() and ReceiveXbee() functions. Repeat this procedure on a separate BeagleBone and use the same functions to receive and reply data.

== User Instructions ==
TO DO: How to use the send and receive functions. Include screenshots.

After cloning our repository to your favorite location, include the necessary header file, XBee.h. In your main.c file or your program, first run initializeXBee(); which sets the pins we will need to communicate to the XBee. Then in your main.c call sendXBee(chars); with chars as a string characters you choose. On your 2nd beagleboard, call receiveXBee(); which will return the string of characters which were sent through sendXBee() on the 1st board.



== Highlights ==
TBD: Showcase an example of a sensor controlling something wireless.

== Theory of Operation ==

The main theory of operation is based on Linux's use of files. With an XBee connected to the Bone's UART, sent and received messages are written to the ttyO2 file. Our code uses this and reads the file to receive a message and writes to the file to send a message. Any XBee's on the same network wil receive the message and we can do anything we want with it.


== Work Breakdown ==
=== Milestones ===
*Monday, 10/29 - XBee hardware received. (done)
*Thursday, 11/1 - XBee Bones are connected and commands can be sent. (done)
*Monday, 11/5 - Initial sensor implementation.
*Thursday, 11/8 - Package language implemented between Bones.
*Sunday, 11/11 - YouTube demo uploaded.
*Monday, 11/12 - All documentation complete.
*Tuesday, 11/13 - Presentation day; PowerPoint complete.

=== Completed Work ===
* Soldering XBee's - Matt Moravec
* Initial communication methods - Stephen Shinn
* Expanded communication methods - Josh Dugan

=== To Do ===
* Sensor implementation: starting with the sensors that we interfaced earlier in the class
* Wiki pages


== Future Work ==
TBD

== Conclusions ==
TBD

{{YoderFoot}}

ECE497 Project: XBee

2012-11-02T14:49:40Z

Mmoravec: /* User Instructions */

[[Category:ECE497 |Project]]
{{YoderHead}}

Team members: [[User:Shinnsm|Stephen Shinn]], [[User:Mmoravec|Matt Moravec]], [[User:Duganje|Josh Dugan]].

== Executive Summary ==

The XBee project involves taking two series-one XBee modules and interfacing them with the various sensors that have been documented in our ECE497 group. Our goal is to create wiki pages which expand on the sensors to include sample wireless communication documentation and source code.

Right now the various sensors have been documented and are working. We've received the XBee modules and soldered them as required. So far we've been able to send a receive messages from an XBee connected to a Windows PC to one connected to a Bone, and vice versa. We've started development on C code which is used to send and receive commands on the Bone. When finished, we'll have a library of methods for communication.

Our next step is to move to Bone-to-Bone communication and to be able to control our sensors wirelessly from one Bone to the other.

In conclusion, we're using XBee modules to communicate from one Bone to another. A protocol is in development and will be used for controlling sensors wirelessly.

== Installation Instructions ==

=== Hardware ===

The very first step is to solder your XBee module, see [http://www.ladyada.net/make/xbee/solder.html the instructions here]. Once the module is assembled, you may wire-up the XBee module to the BeagleBone's serial ports. The table below describes how to hook up the module to UART2 on the Bone:

{|
! align="left"| XBee
! Bone
|-
|GND
|Ground, port 1
|-
|3V
|3.3V, port 3
|-
|TX
|RX, port 22
|-
|RX
|TX, port 21
|}

The image below shows the configuration:

<PIC>

=== Software ===

Our git repo for this project is available here: [https://github.com/duganje/ECE497_XBEE github.com/duganje/ECE497_XBEE]. To begin, download the C file which houses our communication methods. You are now able to send data wirelessly using the SendXbee() and ReceiveXbee() functions. Repeat this procedure on a separate BeagleBone and use the same functions to receive and reply data.

== User Instructions ==
TO DO: How to use the send and receive functions. Include screenshots.

After cloning our repository to your favorite location, include the necessary header file, XBee.h. In your main.c file or your program, first run initializeXBee(); which sets the pins we will need to communicate to the XBee. Then in your main.c call sendXBee(chars); with chars as a string characters you choose. On your 2nd beagleboard, call receiveXBee(); which will return the string of characters which were sent through sendXBee() on the 1st board.



== Highlights ==
TBD: Showcase an example of a sensor controlling something wireless.

== Theory of Operation ==

The main theory of operation is based on Linux's use of files. With an XBee connected to the Bone's UART, sent and received messages are written to the ttyO2 file. Our code uses this and reads the file to receive a message and writes to the file to send a message. Any XBee's on the same network wil receive the message and we can do anything we want with it.


== Work Breakdown ==
=== Milestones ===
*Monday, 10/29 - XBee hardware received. (done)
*Thursday, 11/1 - XBee Bones are connected and commands can be sent. (done)
*Monday, 11/5 - Initial sensor implementation.
*Thursday, 11/8 - Package language implemented between Bones.
*Sunday, 11/11 - YouTube demo uploaded.
*Monday, 11/12 - All documentation complete.
*Tuesday, 11/13 - Presentation day; PowerPoint complete.

=== Completed Work ===
* Soldering XBee's - Matt Moravec
* Initial communication methods - Stephen Shinn
* Expanded communication methods - Josh Dugan

=== To Do ===
* Sensor implementation
* Wiki pages

== Future Work ==
TBD

== Conclusions ==
TBD

{{YoderFoot}}

Adafruit: XBee Module Series 1

2012-10-29T01:14:21Z

Mmoravec: Update picture

[[Category:ECE497]] [[Category:Adafruit]]

[[File:Xbeemodule_MED.jpg]]
== Overview ==

The Adafruit XBee series 1 modules use the 802.15.4 protocol to communicate with each other in a point-to-point, multipoint or mesh network. The modules communicate to an embedded device or a computer through a serial connection. The XBee modules can be purchased from Adafruit [http://www.adafruit.com/products/128 here]. We also used a plug in board in order to speed development which can be bought [http://www.adafruit.com/products/126 here]. The plug-in board allows the user to plug the board into a breadboard and start communicating with other modules immediately.

== Inputs and Outputs ==

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

File:Xbeemodule MED.jpg

2012-10-29T01:13:34Z

Mmoravec: XBee Series 1 module.

XBee Series 1 module.

Adafruit: XBee Module Series 1

2012-10-29T01:11:18Z

Mmoravec: Created page for our XBee module

[[Category:ECE497]] [[Category:Adafruit]]

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit XBee series 1 modules use the 802.15.4 protocol to communicate with each other in a point-to-point, multipoint or mesh network. The modules communicate to an embedded device or a computer through a serial connection. The XBee modules can be purchased from Adafruit [http://www.adafruit.com/products/128 here]. We also used a plug in board in order to speed development which can be bought [http://www.adafruit.com/products/126 here]. The plug-in board allows the user to plug the board into a breadboard and start communicating with other modules immediately.

== Inputs and Outputs ==

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

ECE497 Project: XBee

2012-10-23T16:21:06Z

Mmoravec: /* Executive Summary */

ECE497 Contributions and Project Status

2012-10-23T16:02:11Z

Mmoravec: /* Project Status */

[[Category:ECE497 |Contributions]]
{{YoderHead}}

== Fall 2012 ==

=== Project Status ===

Please edit this page and add your project to this list. Copy my [[ECE497 Project Template]] to your own eLinux page and include the title of your project in the name of the page.

Please make the list alphabetical by family name.

Take a look at what you and others have contributed.

{|
|-
! Name
! Contributions
! Project
! git repository
|-
| [[User:atniptw | Tom Atnip]]
|
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/atniptw/ atniptw]
|-
| [[User:larmorgs | Greg Larmore]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/larmorgs/ larmorgs]
|-
| [[User:jessebrannon | Jesse Brannon]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/brannojs/ brannojs]
|-
| [[User:Xinyu1991 | Xinyu Cheng]]
|
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/xinyu1991]
|-
| [[User:correlbn | Bryan Correll]]
| [[Special:Contributions/correlbn|contrib]]
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/correlbn/My-Beagle-Project/ Correlbn]
|-
| [[User:draneaw | Alex Drane]]
|
| [[ECE497 draneaw Project | My Beagle Project]]
| [https://github.com/draneaw/My-Beagle-Project draneaw]
|-
| [[User:duganje | Josh Dugan]]
|
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/duganje/ duganje]
|-
| [[User:Geislekj | Kevin Geisler]]
|
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/geislekj/ geislekj]
|
|-
| [[User:chris.good | Christopher A Good]]
| [[Special:Contributions/Chris.good|contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/goodca/ goodca]
|
|-
| [[User:hansenrl | Ross Hansen]]
| [[Special:Contributions/hansenrl|contrib]]
| [[ECE497 Project AutoPilot | AutoPilot]]
| [https://github.com/hansenrl/ Hansenrl]
|
|-
| [[User:jungeml | Michael Junge]]
| [[Special:Contributions/jungeml|contrib]]
| [[ECE497 Project AutoPilot | AutoPilot]]
| [https://github.com/jungeml/ Jungeml]
|-
|
|-
| [[User:Lix | Xia Li]]
| [[Special:Contributions/Lix|contrib]]
| [[ECE497 Lix Project | My Beagle Project]]
| [https://github.com/1984xiali/ xiali]
|-
| [[User:mmoravec | Matthew Moravec]]
| [[Special:Contributions/mmoravec|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/mmoravec/ mmoravec]
|-
| [[User:ngop | Peter Ngo]]
|
| [[ECE497 ngop Project: Beaglebone PRU|Beaglebone PRU]]
| [https://github.com/ngop/ ngop]
|
|-
| [[User:shinnsm|Stephen Shinn]]
| [[Special:Contributions/shinnsm|contrib]]
| [[ECE497 Project: XBee|XBee]]
| [https://github.com/shinnsm shinnsm]
|-
| [[User:Yoder | Mark A. Yoder]]
| [[Special:Contributions/Yoder | contrib]]
| [[ECE497 Project Template | My Beagle Project]]
| [https://github.com/MarkAYoder MarkAYoder]
|-
| [[User:Popenhjc | James Popenhagen]]
|
| [[BeagleBone PRU | BeagleBone PRU]]
| [https://github.com/popenhjc/ popenhjc]
|-
| [[User:Whiteer | Elias White]]
|
| [[ECE497 whiteer Project | My Beagle Project]]
| [https://github.com/whiteer whiteer]
|-
| [[User:ruff | Ruffin White]]
|
| [[ECE497 Beagle VNS | Beagle VNS]]
| [https://github.com/ruffsl/ ruffsl]
|
|-
| [[User:Richarsm | Sean Richardson]]
|
| [[ECE497 richarsm Project | My Beagle Project]]
| [https://github.com/seanrich Sean Richardson]
|-
| [[User:Millerap | Andrew Miller]]
|
| [[ECE 497 millerap Project | My Beagle Project]]
| [https://github.com/millerap millerap]
|-|
| [[User:Astroricks | Yue Zhang]]
|
| [[ECE497 Yue Zhang Project | My Beagle Project]]
| [https://github.com/Astroricks/Beagle-Project Yue Zhang]
|-
| [[User:Lobdeljt | John Lobdell]]
|
| [[ECE 497 lobdeljt Project | My Beagle Project]]
| [https://github.com/jtlobdell jtlobdell]
|-
|
|}

== Winter 2011-2012 ==

=== Contributions ===

# [[Special:Contributions/Yuming | Yuming Cao]]
# [[Special:Contributions/Yifei | Yifei Li]]
# [[Special:Contributions/Harrisgw | Greg Harrison]]
# [[Special:Contributions/mac | Jack Ma]]
# [[Special:Contributions/Gemini91 | Guanqun Wang]]
# [[Special:Contributions/Yanj | Mona Yan]]
# [[Special:Contributions/Yoder | Mark A. Yoder]]
# [[Special:Contributions/Yuhasmj | Michael Yuhas]]
# [[Special:Contributions/Ziyi Zhang | Ziyi Zhang]]
# [[Special:Contributions/Zitnikdj | David Zitnik]]
# [[Special:Contributions/Zitnikdj | Alex Drane]]
# [[Special:Contributions/jessebrannon | Jesse Brannon]]
# [[Special:Contributions/larmorgs | Greg Larmore]]
# [[Special:Contributions/jungeml | Michael Junge]]
# [[Special:Contributions/millerap | Andrew Miller]]
# [[Special:Contributions/correlbn | Bryan Correll]]

=== Project Status ===

# [[User:Yoder | Mark A. Yoder]], [[ECE497 Project Template | My Beagle Project]]
# [[user:Yanj|Mona Yan]] and [[user:Harrisgw| Greg Harrison]], [[PS EYE QT PROJECT | Playstation Eye Audio with Qt]]
# [[user:Caogecym | Yuming Cao]] and [[user:Ziyi Zhang | Ziyi Zhang]], [[Node.js Weather Station]]
# [[user:Yifei| Yifei Li]] and [[user:Gemini91| Guanqun Wang]], [[ Kinect Project | Play games using Kinect on Beagleboard]]
# [[user:Yuhasmj| Michael J. Yuhas]] and [[user:mac | Jack Ma]], [[ Multiple Partitions via U-boot | Multiple Partitions via U-boot ]]
# [[user:Zitnikdj| David Zitnik]], [[ ECE497 Project: Twitter Java Application | Twitter Java Application ]]

{{YoderFoot}}

Talk:Adafruit: 2-Axis Thumb Joystick

2012-10-01T15:47:10Z

Mmoravec:

Include some sample code that shows how to read it. - Updated and fixed 9/28/2012 MJM

--Prof. Yoder

Talk:Adafruit: 2-Axis Thumb Joystick

2012-10-01T15:46:58Z

Mmoravec:

Include some sample code that shows how to read it. - Updated and fixed 9/28/2012

--Prof. Yoder

Adafruit: 2-Axis Thumb Joystick

2012-09-29T04:00:47Z

Mmoravec: /* BeagleBone Usage */

[[Category:ECE497]] [[Category:Adafruit]]

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kOhm pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

I have written a small program which displays the x-Axis and y-Axis positions in the terminal. It can be found in a git repository [http://github.com/mmoravec/Adafruit_Joystick_Utility here].

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

Adafruit: 2-Axis Thumb Joystick

2012-09-24T15:52:39Z

Mmoravec:

[[Category:ECE497]] [[Category:Adafruit]]

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kOhm pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

Adafruit: 2-Axis Thumb Joystick

2012-09-24T15:49:25Z

Mmoravec: /* BeagleBone Usage */

[[Category:ECE497]]

[[File:2axisthumbstick_MED.jpg]]
== Overview ==

The Adafruit: 2-Axis Thumb Joystick uses 2 10 kOhm pots which are adjusted by moving the joystick. The joystick and development board can be purchased from the [https://www.adafruit.com/products/512 Adafruit Website]. The joystick is simplistic enough that Adafruit does not provide a datasheet.

From the Manufactorer:
''This mini-kit makes it easy to mount a PSP/Xbox-like thumb joystick to your project. The thumbstick is an analog joystick - more accurate and sensitive than just 'directional' joysticks - with a 'press in to select' button. Since it's analog, you'll need to analog reading pins on your microcontroller to determine X and Y. Having an extra digital input will let you read the switch. ''

== Inputs and Outputs ==

The Adafruit joystick takes a supply voltage (Vs) of up to 5V. The analog outputs have a direct correlation to the resistance observed by the analog joystick. At the resting position, the resistance in both axis is at its middle resistance or 5k. At either extreme of the range of motion, there is either enough resistance for the analog inputs to register a 0 or so little resistance that the supply line to the analog input looks open.

== BeagleBone Usage ==

The BeagleBone can support up to 8 analog inputs and has the ability to supply an analog 1.8 V voltage and an analog ground. I have connected my beagle as shown after soldering the joystick and some wires to the dev board:

[[File:BeagleBone_Adafruit_2axis_Joystick_mmoravec.jpg|300px]]

The pinout is as shown:

[[File:Bone_P9_pinout.jpg|300px]]

Pins 36 and 38 I have wired to the 0-1.8V analog inputs. I have wired VCC to the Beagle's 1.8V analog VCC output(pin 32). The ground wire from the joystick is wired to the analog ground on the beagle(pin 34). The select GPIO signal I have routed to the GPIO_7 pin(pin 42).

Using this configuration one can take the analog inputs with the GPIO selector and do about anything that requires two axises of movement and a selection knob. If you need some help interfacing with the analog ports or the GPIO ports, check out Dr. Yoder's succinct exercise at [http://elinux.org/EBC_Exercise_10_Flashing_an_LED Analog and GPIO Info]

Enjoy!

Adafruit: 2-Axis Thumb Joystick

2012-09-21T06:04:52Z

Mmoravec: /* BeagleBone Usage */