Reports.WirelessTiltSensingInAnOccupationalTherapyApplication History

Hide minor edits - Show changes to output

Changed lines 123-124 from:
%left% http://itp.nyu.edu/~rm1039/Sensors/OTAccelTool.jpg | The Evaluation Tool
to:
%left% http://itp.nyu.edu/~rm1039/Sensors/OTAccelTool.jpg | '''THE EVALUATION TOOL'''
Added lines 123-124:
%left% http://itp.nyu.edu/~rm1039/Sensors/OTAccelTool.jpg | The Evaluation Tool
Added lines 113-114:
[[<<]]
Added lines 113-116:
[[http://itp.nyu.edu/~rm1039/Sensors/sensorGraphDemo.mov | Sensor Behavior Graph Demonstration]]

[[http://itp.nyu.edu/~rm1039/Sensors/accelDemo.mov | Acceleration Demonstration]]
Changed lines 5-7 from:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a [[http://www.freescale.com/ | FreeScale MMA7260Q]] triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.95]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
to:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a [[http://www.freescale.com/ | FreeScale]] MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.95]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
Changed lines 5-7 from:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.95]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
to:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a [[http://www.freescale.com/ | FreeScale MMA7260Q]] triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.95]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
Changed lines 109-110 from:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/ZAxisGraph.jpg | The Weighted averaging formula is based on Tom Igoe's [[http://www.tigoe.net/pcomp/code/archives/picbasic_pro/000286.shtml | Code.]]
to:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/ZAxisGraph.jpg | MAX Graph. The Weighted averaging formula is based on Tom Igoe's [[http://www.tigoe.net/pcomp/code/archives/picbasic_pro/000286.shtml | Code.]]
Changed lines 109-110 from:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/ZAxisGraph.jpg | The Weighted averaging formula is based on Tom Igoe's [[http:// Code.
to:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/ZAxisGraph.jpg | The Weighted averaging formula is based on Tom Igoe's [[http://www.tigoe.net/pcomp/code/archives/picbasic_pro/000286.shtml | Code.]]
Changed lines 109-112 from:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/ZAxisGraph.jpg

The MAX patch I created to produce the 'averaged' graph includes a code that calculates the average of every 10 bytes received. It also analyzes the difference between current and previous value and smoothens the average by adding a 'weight' factor. I think this may have been an overkill averaging scheme as it produced somewhat 'choppy' values. However, the averaging still helps in trimming down data and makes the
values easier to work with.
to:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/ZAxisGraph.jpg | The Weighted averaging formula is based on Tom Igoe's [[http:// Code.

The MAX patch I created to produce the 'averaged' graph includes a code that calculates the average of every 10 bytes received. It also analyzes the difference between current and previous value and smoothens the average by adding a 'weight' factor. I think this may have been an overkill averaging scheme as it produced somewhat 'choppy'
values. However, the averaging still helps in trimming down data and makes the values easier to work with.
Changed lines 111-112 from:
This graph shows 2 versions: averaged and non-averaged values. The MAX patch I created to produce the 'averaged' graph includes a code that calculates the average of every 10 bytes received. It also analyzes the difference between current and previous value and smoothens the average by adding a 'weight' factor. I think this may have been an overkill averaging scheme as it produced somewhat 'choppy' values. However, the averaging still helps in trimming down data and makes the values easier to work with.
to:
The MAX patch I created to produce the 'averaged' graph includes a code that calculates the average of every 10 bytes received. It also analyzes the difference between current and previous value and smoothens the average by adding a 'weight' factor. I think this may have been an overkill averaging scheme as it produced somewhat 'choppy' values. However, the averaging still helps in trimming down data and makes the values easier to work with.
Changed lines 111-112 from:
This graph shows 2 versions: averaged and non-averaged values. The MAX patch I created to produce the 'averaged' graph includes a code that calculates the average of every 10 bytes received. I think this may have been an overkill averaging scheme as it produced somewhat 'choppy' values. However, the averaging still helps in trimming down data and makes the values easier to work with.
to:
This graph shows 2 versions: averaged and non-averaged values. The MAX patch I created to produce the 'averaged' graph includes a code that calculates the average of every 10 bytes received. It also analyzes the difference between current and previous value and smoothens the average by adding a 'weight' factor. I think this may have been an overkill averaging scheme as it produced somewhat 'choppy' values. However, the averaging still helps in trimming down data and makes the values easier to work with.
Changed lines 123-124 from:
'''Why Create the Tool?''' Range of motion is vital part of clinical assessment. However, despite a good degree of movement range, the extremity may achieve the movement with inferior quality.
to:
'''Why Create the Tool?''' Range of motion is vital part of clinical assessment. However, despite having a good degree of movement range, the extremity may achieve the range with inferior quality of movement. In kinesthetics, the skill of movement control is determined by the ability to move 'slowly' throughout the range, or the ability to 'stop' movement at midrange. By measuring acceleration, this device will, therefore, reflect quality of movement.
Added lines 113-114:
[[<<]]
Added lines 117-122:
'''The Device:''' An arm sleeve containing a battery-operated WiTilt linked to a MAX patch displaying visual and auditory interpretation of movement.

'''What It Measures:''' This tool is designed to produce visual and auditory feedback to changes in shoulder and elbow acceleration.

'''Why Create the Tool?''' Range of motion is vital part of clinical assessment. However, despite a good degree of movement range, the extremity may achieve the movement with inferior quality.
Changed lines 113-116 from:
to:
!!!MY O.T. APPLICATION

'''Concept:''' A Standardized Assessment of the Quality of Upper Extremity Movement Post-Stroke
Changed lines 103-104 from:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, [[http://ccrma.stanford.edu/~woony/software/w2o/instructions.html | Woon Seung Yeo]] from Stanford has figured this out, by creating [[http://ccrma.stanford.edu/~woony/software/w2o/ | W2O]] to configure the WiTilt to work with a group of MAX objects called , 'Open Sound Control' created by Chandrasekhar "Sekhar" Ramakrishnan. This system is what I am currently using in MAX to move forward with this project.
to:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patch that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, [[http://ccrma.stanford.edu/~woony/software/w2o/instructions.html | Woon Seung Yeo]] from Stanford has figured this out, by creating [[http://ccrma.stanford.edu/~woony/software/w2o/ | W2O]] to configure the WiTilt to work with a group of MAX objects called , 'Open Sound Control' created by Chandrasekhar "Sekhar" Ramakrishnan. This system is what I am currently using in MAX to move forward with this project.
Changed lines 109-111 from:
to:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/ZAxisGraph.jpg

This graph shows 2 versions: averaged and non-averaged values. The MAX patch I created to produce the 'averaged' graph includes a code that calculates the average of every 10 bytes received. I think this may have been an overkill averaging scheme as it produced somewhat 'choppy' values. However, the averaging still helps in trimming down data and makes the values easier to work with.
Added lines 87-88:
'''A. Reading the WiTilt Values'''
Changed lines 105-108 from:
to:
'''B. Using MAX to view the Sensor's Behavior Over Time'''

Using the multislider object, I was able to graph the sensor's value changes over Time.
Changed lines 101-106 from:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, [[http://ccrma.stanford.edu/~woony/software/w2o/instructions.html | Woon Seung Yeo]] from Stanford has figured this out, by creating [[http://ccrma.stanford.edu/~woony/software/w2o/ | W2O]] to configure the WiTilt to work with a group of MAX objects called , 'Open Sound Control.' This is what I am currently using.
to:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, [[http://ccrma.stanford.edu/~woony/software/w2o/instructions.html | Woon Seung Yeo]] from Stanford has figured this out, by creating [[http://ccrma.stanford.edu/~woony/software/w2o/ | W2O]] to configure the WiTilt to work with a group of MAX objects called , 'Open Sound Control' created by Chandrasekhar "Sekhar" Ramakrishnan. This system is what I am currently using in MAX to move forward with this project.
Changed lines 101-106 from:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, [[http://ccrma.stanford.edu/~woony/software/w2o/instructions.html | Woon Seung Yeo]] from Stanford has figured this out, configuring the WiTilt to open with a group of MAX objects called , 'Open Sound Control.' This is what I am currently using.
to:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, [[http://ccrma.stanford.edu/~woony/software/w2o/instructions.html | Woon Seung Yeo]] from Stanford has figured this out, by creating [[http://ccrma.stanford.edu/~woony/software/w2o/ | W2O]] to configure the WiTilt to work with a group of MAX objects called , 'Open Sound Control.' This is what I am currently using.
Changed lines 101-106 from:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, Woon Seung Yeo from Stanford has figured this out.
to:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, [[http://ccrma.stanford.edu/~woony/software/w2o/instructions.html | Woon Seung Yeo]] from Stanford has figured this out, configuring the WiTilt to open with a group of MAX objects called , 'Open Sound Control.' This is what I am currently using.
Changed lines 101-106 from:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, someone from Stanford has figured this out.
to:
Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, Woon Seung Yeo from Stanford has figured this out.
Changed lines 97-102 from:
Instead of, 'Z=587.' This is because of how the WiTilt was programmed by the wise guys. Now, if you were to build your own circuit, you could program the PIC chip differently: serout2...[adcVar], instead of serout2...[DEC adcVar].

To reprogram
the PIC chip on the WiTilt, you will need to spend extra bucks to purchase.
to:
Instead of, 'Z=587.' This is because of how the WiTilt was programmed by the wise guys. Now, if you were to build your own circuit, you could program the PIC chip differently: serout2...[adcVar], instead of serout2...[DEC adcVar]. Then, I assume, the values would be more readable in MAX.

**To reprogram the PIC chip on the WiTilt, you will need to spend extra bucks to
purchase the [[http://www.sparkfun.com/commerce/product_info.php?products_id=194 | Adapter Board for SFE ICSP connections]]. I have not tried to this just yet.

Going back to using WiTilt with MAX, I am still in the process of tweaking my own patcher that will straighten out the linefed values, put them together horizontally and finally reading them as numerical values instead of 'characters.' Meanwhile, someone from Stanford has figured this out.
Changed lines 89-90 from:
Using the WiTilt to work with MAX/MSP is not an easy task, either. First of all, the output coming from the WiTilt is in ASCII. MAX serial, by default, presents each incoming byte as a single value, so it comes out one byte at a time in a LINEFEED fashion.
to:
Using the WiTilt to work with MAX/MSP is not an easy task, either. First of all, the output coming from the WiTilt is in ASCII. MAX serial, by default, presents each incoming byte as a single value, so it comes out one byte at a time in a LINEFEED fashion,
Changed lines 97-99 from:
to:
Instead of, 'Z=587.' This is because of how the WiTilt was programmed by the wise guys. Now, if you were to build your own circuit, you could program the PIC chip differently: serout2...[adcVar], instead of serout2...[DEC adcVar].

To reprogram the PIC chip on the WiTilt, you will need to spend extra bucks to purchase.
Changed lines 73-74 from:
3. Open Terminal. Type the following command: ''ls /dev/tty.*'' -- This should show you which serial ports are available. \\
-> @@ /dev/tty.BlueRadios-COM0-1 /dev/tty.Bluetooth-PDA-Sync@@ \\
to:
3. Open Terminal. Type the following command: ''ls /dev/tty.*'' -- This should show you which serial ports are available.
-> @@ /dev/tty.BlueRadios-COM0-1 /dev/tty.Bluetooth-PDA-Sync@@
Changed lines 94-99 from:
-< @@8@@ \\
-<
@@7@@ \\
to:
-> @@8@@
-> @@7@@
Changed lines 91-93 from:
-< @@Z@@ \\
-< @@=@@ \\
-< @@5@@ \\
to:
-> @@Z@@
-> @@=@@
-> @@5@@
Deleted lines 87-89:

Using the WiTilt to work with MAX/MSP is not an easy task, either. First of all, the output coming from the WiTilt is ASCII. MAX, by default, receives each serial byte
Changed lines 89-90 from:
to:
Using the WiTilt to work with MAX/MSP is not an easy task, either. First of all, the output coming from the WiTilt is in ASCII. MAX serial, by default, presents each incoming byte as a single value, so it comes out one byte at a time in a LINEFEED fashion.

-< @@Z@@ \\
-< @@=@@ \\
-< @@5@@ \\
-< @@8@@ \\
-< @@7@@ \\

Changed lines 103-108 from:
to:


Changed lines 85-86 from:
to:
WORKING WITH MAX/MSP

** In case you are wondering why I am not using processing, it is because I simply can not get the WiTilt to connect with Processing. Reason: Beats me. I have done various computer restarts, Witilt resets, Witilt-MAC re-'pairing,' but with no positive results.

Using the WiTilt to work with MAX/MSP is not an easy task, either. First of all, the output coming from the WiTilt is ASCII. MAX, by default, receives each serial byte
Added lines 37-38:
[[http://www.sparkfun.com/datasheets/Sensors/WiTilt_V2_5.pdf | The WiTilt Datasheet]]
Changed line 44 from:
2. Debug / RF switch - switches PIC UART between bluetooth and hardline connections. \\
to:
2. Debug / RF switch - switches PIC UART between bluetooth and hardline serial connections. \\
Added lines 59-60:
Working with the menu is a pretty straightforward experience. Each option gives you specific instructions to manipulate the setup.
Changed lines 79-82 from:
6. If you have any problems establishing connection, I suggest disconnecting bluetooth, restarting computer, delete bluetooth pairing from the setup, re-establish pairing, then re-open Terminal and, finally, try reconnecting.
to:
7. If you have any problems establishing connection, I suggest the following steps in order of execution: disconnect bluetooth, restart computer, delete bluetooth pairing from the setup, re-establish pairing, then re-open Terminal and, finally, try reconnecting.
Changed line 69 from:
3. Open Terminal. Type the following command: ls /dev/tty.* -- This should show you which serial ports are available. \\
to:
3. Open Terminal. Type the following command: ''ls /dev/tty.*'' -- This should show you which serial ports are available. \\
Changed lines 73-76 from:
to:
4. Then, 'screen' the bluetooth port, using the following command: ''screen /dev/tty.BlueRadios-COM0-1 9600'' where '9600' is the baud rate.

5. You should then see the configurate menu above.

6. To disconnect from Terminal, use: 'Command' + 'a', followed by 'Command' + '\'

6. If you have any problems establishing connection, I suggest disconnecting bluetooth, restarting computer, delete bluetooth pairing from the setup, re-establish pairing, then re-open Terminal and, finally, try reconnecting.
Changed lines 5-7 from:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.00]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
to:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.95]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
Changed lines 65-71 from:
For preliminary testing, I suggest using Terminal or [[http://www.download.com/ZTerm/3000-2274_4-5656715.html | Zterm]] in MAC. I hadn't tried opening this from a PC, but I think there shouldn't be any problem (?) using this with Hyperterm.

2. Before opening Terminal, make sure that no other program (Processing or MAX) is open.
to:
2. For preliminary testing, I suggest using Terminal or [[http://www.download.com/ZTerm/3000-2274_4-5656715.html | Zterm]] in MAC. I hadn't tried opening this from a PC, but I think there shouldn't be any problem (?) using this with Hyperterm.

2. Before opening Terminal, make sure that no other program (Processing or MAX) is open. Turn ON WiTilt.

3. Open Terminal. Type the following command: ls /dev/tty.* -- This should show you which serial ports are available. \\
-> @@ /dev/tty.BlueRadios-COM0-1 /dev/tty.Bluetooth-PDA-Sync@@ \\
-> @@ /dev/tty.Bluetooth-Modem /dev/tty.modem@@
Changed lines 57-60 from:
to:
[[<<]]

NOTES ON STARTING BLUETOOTH CONNECTION WITH WITILT

During my interlude with this device, I realized that a degree of problem solving needs to be done. It is not as simple as opening terminal and, 'voila,' you have connection. These are the steps that I religiously follow to get connected quickly (Not fail-proof, though):

1. In MAC OSX 10.4, setup bluetooth connection (passkey input involved). Remember that in 10.3, the bluetooth setup interface is different as it doesn't allow you passkey options. OSX 10.3 only accepts numerical passkey input. Therefore, you can not type 'default' as passkey, unlike in 10.4. If you have 10.3, you will need to find someone with 10.4 just to get through. Then, in Terminal, manipulate the 'passkey' (turn it into numbers) using the AT command setup. Refer to [[http://itp.nyu.edu/~rm1039/Sensors/BlueRadios_AT_Commands_Rev_21.8.1.0.0.pdf | BlueRAdios AT Command datasheet]].

For preliminary testing, I suggest using Terminal or [[http://www.download.com/ZTerm/3000-2274_4-5656715.html | Zterm]] in MAC. I hadn't tried opening this from a PC, but I think there shouldn't be any problem (?) using this with Hyperterm.

2. Before opening Terminal, make sure that no other program (Processing or MAX) is open.
Changed lines 55-59 from:
%center% http://itp.nyu.edu/~rm1039/Sensors/AccelConfigMenu.jpg | WiTilt Configuration Menu
to:
%left% http://itp.nyu.edu/~rm1039/Sensors/AccelConfigMenu.jpg | WiTilt Configuration Menu
Changed lines 55-59 from:
to:
%center% http://itp.nyu.edu/~rm1039/Sensors/AccelConfigMenu.jpg | WiTilt Configuration Menu


Changed lines 53-55 from:
This whole circuit has been pre-programmed for output values to be read quite easily with the use of Terminal or Zterm in MAC, or hyperterm in PC. The WiTilt comes with a programmed configuration menu which allows you to control data flow with the Bluetooth interface.
to:
This whole circuit has been pre-programmed for output values to be read quite easily with the use of Terminal or Zterm in MAC, or hyperterm in PC. The WiTilt comes with an inherent configuration menu which allows you to control data flow with the Bluetooth interface. As soon as bluetooth connection is established, the following menu comes up:
Changed lines 42-55 from:
2. Debug / RF switch - switches PIC UART between bluetooth and hardline connections.

3.
Debug Header

4.
uC reset button

5.
Power connector (4 to 6 V)

6.
Status LED

7.
Bluetooth connection indicator LED

8.
Bluetooth pulse, mode indicator LED
to:
2. Debug / RF switch - switches PIC UART between bluetooth and hardline connections. \\
3.
Debug Header \\
4.
uC reset button \\
5.
Power connector (4 to 6 V) \\
6.
Status LED \\
7.
Bluetooth connection indicator LED \\
8.
Bluetooth pulse, mode indicator LED \\
Changed lines 41-42 from:
1. Power Switch
to:
1. Power Switch \\
Changed lines 41-60 from:
to:
1. Power Switch

2. Debug / RF switch - switches PIC UART between bluetooth and hardline connections.

3. Debug Header

4. uC reset button

5. Power connector (4 to 6 V)

6. Status LED

7. Bluetooth connection indicator LED

8. Bluetooth pulse, mode indicator LED

9. Reverse-polarized SMA antenna connector

[[<<]]
Changed lines 39-41 from:
%cframe% http://itp.nyu.edu/~rm1039/Sensors/HardwareLayout.jpg | WiTilt Hardware Layout
to:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/HardwareLayout.jpg | WiTilt Hardware Layout
Changed lines 39-41 from:
to:
%cframe% http://itp.nyu.edu/~rm1039/Sensors/HardwareLayout.jpg | WiTilt Hardware Layout
Changed lines 37-39 from:
As mentioned above, this is Sparkfun's 'plug-and-play' version of a wireless accelerometer. Aside from Freescale's triple axis accelerometer and BlueRadios' bluetooth module, the board also contains a PIC 16LF88-SSOP. This whole circuit has been pre-programmed for output values to be read quite easily with the use of Terminal or Zterm in MAC, or hyperterm in PC. The WiTilt comes with a programmed configuration menu which allows you to control data flow with the
to:
As mentioned above, this is Sparkfun's 'plug-and-play' version of a wireless accelerometer. Aside from Freescale's triple axis accelerometer and BlueRadios' bluetooth module, the board also contains a PIC 16LF88-SSOP. The hardware layout is as follows:




This whole circuit has been pre-programmed for output values to be read quite easily with the use of Terminal
or Zterm in MAC, or hyperterm in PC. The WiTilt comes with a programmed configuration menu which allows you to control data flow with the Bluetooth interface.
Changed lines 18-22 from:
This change in capacitance is then converted into voltage outputs which reflect movement changes along the X, Y, Z axes. This accelerometer also features a 4-level sensitivity scale (1.5g, 2g, 4g, 6g), with 1.5g setting being the most sensitive. It measures both (+) and (-) acceleration. It has 16 pins, only 8 of which are connected with functions.

%lframe%%width=210px%%height=230px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe%%width=210px%%height=230px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
This change in capacitance is then converted into voltage outputs which reflect movement changes along the X, Y, Z axes. This accelerometer also features a 4-level sensitivity scale (1.5g, 2g, 4g, 6g), with 1.5g setting being the most sensitive. It measures both (+) and (-) acceleration. It has 16 pins, only 8 of which are connected with functions. [[<<]]

%lframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%cframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 20-22 from:
%lframe%%width=230px%%height=230px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe%%width=230px%%height=230px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%lframe%%width=210px%%height=230px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe%%width=210px%%height=230px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 20-22 from:
%lframe%%width=220px%%height=220px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe%%width=220px%%height=220px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%lframe%%width=230px%%height=230px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe%%width=230px%%height=230px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 20-22 from:
%lframe% %width=220px% %height=220px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe% %width=220px% %height=220px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%lframe%%width=220px%%height=220px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe%%width=220px%%height=220px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 20-22 from:
%lframe% %width=220px% or %height=220px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe% %width=220px% or %height=220px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%lframe% %width=220px% %height=220px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe% %width=220px% %height=220px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 20-22 from:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%cframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%lframe% %width=220px% or %height=220px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe% %width=220px% or %height=220px%http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Deleted lines 19-20:
[[<<]]
Changed lines 22-24 from:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%center% %frame% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%cframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 23-24 from:
%cframe% %width=250px% %height=250px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%center% %frame% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 23-24 from:
%cframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%cframe% %width=250px% %height=250px% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 23-24 from:
%center% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%cframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg

[[<<]]
Added lines 20-21:
[[<<]]
Changed lines 23-24 from:
%rframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%center% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Deleted lines 22-23:
[[<<]]
Deleted lines 17-18:
[[<<]]
Added lines 18-19:
[[<<]]
Changed lines 23-24 from:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%rframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Changed lines 21-22 from:
%rframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
to:
%lframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg
Added lines 23-24:
[[<<]]
Deleted lines 22-23:
[[<<]]
Changed lines 33-34 from:
It allows for long distance communication due to its high sensitivity, UART, and PCM interfaces available to various applications. It runs on a 3.3V power supply, with an operating temperature range is at - 40~+70C . Without an antenna, it operates through a +200 meter (660 feet) distance, with software adjustable transmitter power.
to:
It allows for long distance communication due to its high sensitivity, UART, and PCM interfaces available to various applications. It runs on a 3.3V power supply, with an operating temperature range is at - 40~+70C . Without an antenna, it operates through a +200 meter (660 feet) distance, with software adjustable transmitter power.
Changed lines 37-40 from:
As mentioned above, this is Sparkfun's 'plug-and-play' version of a wireless accelerometer. Aside from Freescale's triple axis accelerometer and BlueRadios' bluetooth module, the board also contains a PIC 16LF88-SSOP. This whole circuit has been pre-programmed for output values to be read quite easily with the use of Terminal or Zterm in MAC, or hyperterm in PC.
to:
As mentioned above, this is Sparkfun's 'plug-and-play' version of a wireless accelerometer. Aside from Freescale's triple axis accelerometer and BlueRadios' bluetooth module, the board also contains a PIC 16LF88-SSOP. This whole circuit has been pre-programmed for output values to be read quite easily with the use of Terminal or Zterm in MAC, or hyperterm in PC. The WiTilt comes with a programmed configuration menu which allows you to control data flow with the
Changed lines 43-48 from:
to:


Changed lines 35-38 from:
to:
!!! The WiTilt v2.5, with RP-SMA

As mentioned above, this is Sparkfun's 'plug-and-play' version of a wireless accelerometer. Aside from Freescale's triple axis accelerometer and BlueRadios' bluetooth module, the board also contains a PIC 16LF88-SSOP. This whole circuit has been pre-programmed for output values to be read quite easily with the use of Terminal or Zterm in MAC, or hyperterm in PC.
Changed lines 31-34 from:
The bluetooth module included in the sparkfun board is a BlueRadios serial radio modem with an RP-SMA antenna reverse female connector for external antenna options to increase transmission range. Sparkfun does not specify exactly which BlueRadio bluetooth model they used in this breakout board. Although on the package, it reads C30 AH. Assuming that most, if not all, BlueRadios bluetooth modules have the same setup / pin connections, see above for datasheet. It allows for long distance communication due to its high sensitivity, UART, and PCM interfaces available to various applications. Operating temperature range is at - 40~+70C . Without an antenna, it operates through a +200 meter (660 feet) distance, with software adjustable transmitter power.
to:
The bluetooth module included in the sparkfun board is a BlueRadios serial radio modem with an RP-SMA antenna reverse female connector for external antenna options to increase transmission range. Sparkfun does not specify exactly which BlueRadio bluetooth model they used in this breakout board. Although on the package, it reads C30 AH. Assuming that most, if not all, BlueRadios bluetooth modules have the same setup / pin connections, see above for datasheet.

It allows for long distance communication due to its high sensitivity, UART, and PCM interfaces available to various applications. It runs on a 3.3V power supply, with an operating temperature range is at - 40~+70C . Without an antenna, it operates through a +200 meter (660 feet) distance, with software adjustable transmitter power.
Deleted lines 26-27:

%rframe% http://itp.nyu.edu/~rm1039/Sensors/witiltSMA_img.jpg
Changed lines 29-30 from:
[[<<]]
to:
%rframe% http://itp.nyu.edu/~rm1039/Sensors/witiltSMA_img.jpg
Added lines 27-28:

%rframe% http://itp.nyu.edu/~rm1039/Sensors/witiltSMA_img.jpg
Added lines 35-36:
Changed lines 31-39 from:
The bluetooth module included in the sparkfun board is a BlueRadios serial radio modem with an RP-SMA antenna reverse female connector for external antenna options to increase transmission range. Sparkfun does not specify exactly which BlueRadio bluetooth model they used in this breakout board. Although on the package, it reads C30 AH. Assuming that most, if not all, BlueRadios bluetooth modules have the same setup / pin connections, see above for datasheet. It allows for long distance communication due to its high sensitivity, UART, and PCM interfaces available to various applications. Operating temperature range is at - 40~+70C .
to:
The bluetooth module included in the sparkfun board is a BlueRadios serial radio modem with an RP-SMA antenna reverse female connector for external antenna options to increase transmission range. Sparkfun does not specify exactly which BlueRadio bluetooth model they used in this breakout board. Although on the package, it reads C30 AH. Assuming that most, if not all, BlueRadios bluetooth modules have the same setup / pin connections, see above for datasheet. It allows for long distance communication due to its high sensitivity, UART, and PCM interfaces available to various applications. Operating temperature range is at - 40~+70C . Without an antenna, it operates through a +200 meter (660 feet) distance, with software adjustable transmitter power.

Changed lines 27-28 from:
[[http://www.blueradios.com/BR-SC30A_Rev2.0.pdf | BlueTooth Module DIP datasheet]]
to:
[[http://www.blueradios.com/BR-SC30A_Rev2.0.pdf | BlueTooth Module DIP version datasheet]]
Changed lines 31-38 from:
This a BlueRadios serial radio modem with an RP-SMA antenna reverse female connector for increased transmission range. Sparkfun does not specify exactly which BlueRadio bluetooth model they used in this breakout board. Although on the package, it reads C30 AH. Assuming that most, if not all, BlueRadios bluetooth modules have the same setup / pin connections, see above for datasheet.
to:
The bluetooth module included in the sparkfun board is a BlueRadios serial radio modem with an RP-SMA antenna reverse female connector for external antenna options to increase transmission range. Sparkfun does not specify exactly which BlueRadio bluetooth model they used in this breakout board. Although on the package, it reads C30 AH. Assuming that most, if not all, BlueRadios bluetooth modules have the same setup / pin connections, see above for datasheet. It allows for long distance communication due to its high sensitivity, UART, and PCM interfaces available to various applications. Operating temperature range is at - 40~+70C .
Changed lines 27-28 from:
[[http://www.blueradios.com/BR-SC30A_Rev2.0.pdf | BlueTooth Module DIP datasheet]]\\
to:
[[http://www.blueradios.com/BR-SC30A_Rev2.0.pdf | BlueTooth Module DIP datasheet]]

[[<<]]
Added lines 7-9:

!!! The Triple Axis Accelerometer
Deleted lines 11-15:
[[http://www.blueradios.com/BR-SC30A_Rev2.0.pdf | BlueTooth Module DIP datasheet]]\\


!!! The Triple Axis Accelerometer
Added lines 27-28:
[[http://www.blueradios.com/BR-SC30A_Rev2.0.pdf | BlueTooth Module DIP datasheet]]\\
Changed lines 27-34 from:
to:
!!! The Bluetooth module

This a BlueRadios serial radio modem with an RP-SMA antenna reverse female connector for increased transmission range. Sparkfun does not specify exactly which BlueRadio bluetooth model they used in this breakout board. Although on the package, it reads C30 AH. Assuming that most, if not all, BlueRadios bluetooth modules have the same setup / pin connections, see above for datasheet.
Changed lines 5-6 from:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.00]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
to:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.00]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
Changed lines 5-6 from:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. This unit costs $99.00. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
to:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. The particular unit that I got is an RP-SMA version, which has a female connector for an [[http://www.blueradios.com/BR-SMA-ANT.pdf | RP-SMA antenna]. This unit costs [[http://www.sparkfun.com/commerce/product_info.php?products_id=640 | $99.00]]. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
Changed lines 5-6 from:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]].
to:
The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]]. This unit costs $99.00. It may be a good enough value considering the plug-and-play nature of this board. Pros and Cons will be discussed later in the report.
Added lines 1-34:
!!! by Pinky Magbanua

%rframe% http://itp.nyu.edu/~rm1039/Sensors/3AxisAccelPic.jpg

The WiTilt v2.5 is a 2.4GHz Wireless 3-axis Tilt Sensor from [[http://www.sparkfun.com | Sparkfun]]. It employs a FreeScale MMA7260Q triple-axis accelerometer and a class 1 Bluetooth link from [[http://www.blueradios.com | BlueRadios]].

[[http://www.sparkfun.com/datasheets/Accelerometers/MMA7260Q-Rev1.pdf | MMA7260Q datasheet]]

[[http://www.blueradios.com/BR-SC30A_Rev2.0.pdf | BlueTooth Module DIP datasheet]]\\


!!! The Triple Axis Accelerometer

[[http://itp.nyu.edu/physcomp/sensors/Reports/MMA7260Q | Here]] is a link to Tom Igoe's original sensor report summary.

This is a surface mount integrated circuit accelerometer that runs on low voltage (2.2V - 3.6V). It measures a change in capacitance through 2 g-cell beams that serve as back to back capacitors reacting to a movable beam located in between them. The illustration below demonstrates this mechanism.

%lframe% http://itp.nyu.edu/~rm1039/Sensors/3AxisAccelModel.jpg

This change in capacitance is then converted into voltage outputs which reflect movement changes along the X, Y, Z axes. This accelerometer also features a 4-level sensitivity scale (1.5g, 2g, 4g, 6g), with 1.5g setting being the most sensitive. It measures both (+) and (-) acceleration. It has 16 pins, only 8 of which are connected with functions.

%lframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinOutDesc.jpg
%rframe% http://itp.nyu.edu/~rm1039/Sensors/AccelPinDiag.jpg

[[<<]]