Recent Changes - Search:

Main

Robotics I Fall 2007

Robotics II Spring 2007

Robotics I Fall 2006

Vision Servoing Laboratories

FPGA-Based Vision

VDSP

LabVIEW Embedded

Code

Site Admin

edit SideBar

LabNotes

RoboticsIFall2007.LabNotes History

Hide minor edits - Show changes to output

Changed line 53 from:
# In the "File" menu, select "Load Program" and specify the DXE file.  The DXE file will be in a subfolder named @@VDK_Application@@ inside a subfolder named @@BF537@@ in your project folder.
to:
# %item value=5% In the "File" menu, select "Load Program" and specify the DXE file.  The DXE file will be in a subfolder named @@VDK_Application@@ inside a subfolder named @@BF537@@ in your project folder.
Changed lines 37-38 from:
# If that fails, quit VDSP.  Turn the Handy Board off, wait a few seconds, and then turn it on.  (This gives Windows a chance to reload the low-level USB driver).  Then relaunch VDSP and try to connect again.
# If it still fails, your emulator driver may need to be re-established using the Analog Devices Configurator Tool.  Instructions for doing this still needs to be written.
to:
** If that fails, quit VDSP.  Turn the Handy Board off, wait a few seconds, and then turn it on.  (This gives Windows a chance to reload the low-level USB driver).  Then relaunch VDSP and try to connect again.
** If it still fails, your emulator driver may need to be re-established using the Analog Devices Configurator Tool.  Instructions for doing this still needs to be written.
Changed line 35 from:
# Click on icon in upper left of screen.  This should connect to your board: \\
to:
# Click on “Connect to Target” icon in upper left of screen.  This should connect to your board: \\
Changed lines 37-40 from:
# If that fails, try rebooting the PC and return to here.
# If it still fails
, your emulator driver may need to be re-established.  Instructions for doing this are ''this still needs to be written.''
# If
VDSP ''does'' connect to your board, quit it and try LabVIEW again.
to:
# If that fails, quit VDSP.  Turn the Handy Board off, wait a few seconds, and then turn it on.  (This gives Windows a chance to reload the low-level USB driver).  Then relaunch VDSP and try to connect again.
# If
it still fails, your emulator driver may need to be re-established using the Analog Devices Configurator Tool.  Instructions for doing this still needs to be written.
# If VDSP ''does'' connect to your board, quit VDSP, and then
try LabVIEW again.
Changed line 43 from:
# Build your code in LabVIEW.  This will result in a DXE (DSP Executable) file in your project.  Navigate into the @@VDK Application@@ folder and find it there.
to:
# Build your code in LabVIEW.  This will result in a DXE (DSP Executable) file in your project.
Changed lines 53-54 from:
# Choose "Load File" and specify the DXE file.
# Choose
"Run" to run your code.  Your code should now run.
to:
# In the "File" menu, select "Load Program" and specify the DXE file.  The DXE file will be in a subfolder named @@VDK_Application@@ inside a subfolder named @@BF537@@ in your project folder.
# From the "Debug" menu, choose
"Run" to run your code.  Your code should now run.
Changed line 48 from:
In the lower left, there are three choices "On emulator exit":
to:
In the lower left, there are three choices for "On Emulator Exit":
Changed line 48 from:
There are three choices for what to do when the emulator disconnects:
to:
In the lower left, there are three choices "On emulator exit":
Changed line 52 from:
->->Set it to “Run from current PC.”  Note:  You only have to do this once, and the setting will be remembered.
to:
->Set it to “Run from current PC.”  Note:  You only have to do this once, and the setting will be remembered.
Changed lines 1-2 from:
 Here is an assortment of important safety and community notes.
to:
Here is an assortment of important safety and community notes.
Changed line 36 from:
->Attach:connect-to-board.png
to:
Attach:connect-to-board.png
Changed lines 47-52 from:
->Attach:target-options.png\\
->There are three choices for what to do when the emulator disconnects:
## Halt the PC.
## Reset the PC.
## Continue running from current address.
-> Set it to “Continue running from current address.”  Note:  You only have to do this once, and the setting will be remembered.
to:
Attach:target-options.png\\
There are three choices for what to do when the emulator disconnects:
## Reset DSP and run.
## Run from current PC.
## Stall the DSP.
->->Set it to “Run from current PC.”  Note:  You only have to do this once, and the setting will be remembered.
Changed lines 1-2 from:
Here is an assortment of important safety and community notes.
to:
 Here is an assortment of important safety and community notes.
Changed line 36 from:
Attach:connect-to-board.png
to:
->Attach:connect-to-board.png
Changed lines 46-48 from:
# Configure the emulator in the Tools menu.  There are three choices for what to do when the emulator disconnects:
to:
# From the "Settings" menu, choose "Target Options": \\
->Attach:target-options.png\\
->
There are three choices for what to do when the emulator disconnects:
Changed lines 35-36 from:
# Click on icon in upper left of screen.  This should connect to your board.
to:
# Click on icon in upper left of screen.  This should connect to your board: \\
Attach:connect-to-board.png
Changed line 26 from:
* Read Appendix B of my book for construction notes on how to wire stuff.  '''Neatness matters—improperly or badly wired stuff can fail or cause shorts on the board.'''
to:
* Read Appendix B of my book for construction notes on how to wire stuff.  '''Neatness matters—improperly or badly wired stuff can fail or cause shorts on the board.'''  This is also explained at http://handyboard.com/sensors/ .
Changed line 19 from:
* Read Section 4.5 of ''Robotic Explorations'' to understand how LEGO fits together.
to:
* Read Section 4.5 of ''Robotic Explorations'' to understand how LEGO parts fit together.
Added line 19:
* Read Section 4.5 of ''Robotic Explorations'' to understand how LEGO fits together.
September 17, 2007, at 05:12 PM by Fred Martin - added Wiki section
Added lines 3-9:
!Wiki
* You must post links to your [[Lab 1]] reports on the [[Lab 1]] page. The wiki password is posted to the [[http://groups.google.com/group/91450-f07 | class discussion board]].
* You must join the class discussion board in order to view the wiki password.
* Please join the class discussion board if you have not done so already.
* Please fill in the Author and Summary fields when you make changes to the wiki.
* The wiki is a class resource.  Please use it and add stuff.

Added lines 8-10:
!Parts
There is now a [[Parts Request]] wiki page.  Please use it to request parts that we should have.

Added lines 33-43:
# Boot up VDSP and connect to your board.
# Configure the emulator in the Tools menu.  There are three choices for what to do when the emulator disconnects:
## Halt the PC.
## Reset the PC.
## Continue running from current address.
-> Set it to “Continue running from current address.”  Note:  You only have to do this once, and the setting will be remembered.
# Choose "Load File" and specify the DXE file.
# Choose "Run" to run your code.  Your code should now run.
# Click on the upper-left icon to detach the emulator.  Your code should continue to run.
# Finally, unplug the USB cable from the Handy Board.
'''You must detach the emulator in software before unplugging the Handy Board—otherwise, you'll crash the software on the PC and you'll have to reboot it.'''
Changed lines 19-32 from:
*
to:

!Problems with LabVIEW Embedded
If you get a "Failed to Script Board Tools" error, it's likely a communication problem.  Fix this by:
# Quitting LabVIEW.
# Opening VisualDSP++ (VDSP).
# Click on icon in upper left of screen.  This should connect to your board.
# If that fails, try rebooting the PC and return to here.
# If it still fails, your emulator driver may need to be re-established.  Instructions for doing this are ''this still needs to be written.''
# If VDSP ''does'' connect to your board, quit it and try LabVIEW again.

!Detaching from the PC and Continuing to Run Your Code
The basic process is the following:
# Build your code in LabVIEW.  This will result in a DXE (DSP Executable) file in your project.  Navigate into the @@VDK Application@@ folder and find it there.
# Quit LabVIEW in order to detach from your board. (We are hoping there might be a way to detach without quitting, but we don't yet know of it.)
Changed line 15 from:
* Read Appendix B of my book for construction notes on how to wire stuff.  '''Neatness matters—improperly or badly wired stuff can fail or cause shorts on the board.''
to:
* Read Appendix B of my book for construction notes on how to wire stuff.  '''Neatness matters—improperly or badly wired stuff can fail or cause shorts on the board.'''
Changed lines 12-19 from:
* Violators will be penalized with a $5 cash fine ''per incident,'' which will go toward a LEGO replacement fund.
to:
* Violators will be penalized with a $5 cash fine ''per incident,'' which will go toward a LEGO replacement fund.

!Wiring Sensors and Motors
* Read Appendix B of my book for construction notes on how to wire stuff.  '''Neatness matters—improperly or badly wired stuff can fail or cause shorts on the board.''
* Ribbon cable has been ordered for using in wiring sensors.  This will work better than solid core wire because it is flexible.
* Do '''not''' leave exposed wires dangling around the Handy Board.  This can cause shorts which can damage the board. 
* Do '''not''' use the "Cricket Wires" (pre-cut stranded wires with a crimped metal end) with the Handy Board.  They are not intended for this.  These wires cost 50c each to purchase.  Violations will result in $1 fine per incident.
*
Changed lines 8-12 from:
!
to:
!Treatment of the LEGO Parts
* At most 3 pieces of LEGO may be glued to a motor or sensor, ''exclusively'' for the purpose of modularizing the element (co-called “LEGOizing” it).
* Gluing 3 beams together and tacking a touch sensor to them is '''not''' LEGOizing.
* Cutting or otherwise permanently changing the shape of rigid LEGO elements is prohibited.
* Violators will be penalized with a $5 cash fine ''per incident,'' which will go toward a LEGO replacement fund.
Added lines 1-8:
Here is an assortment of important safety and community notes.

!Battery Charging
* The BFHB only charges when it's powered off. LED Flashing= pre-charge, on steady=regular charge, off = no charge.
* The charge LED flashes if you try to charge when the board is powered on.  This does NOT mean the board is charging.  Indeed -- it is not.
* When you are finished using your board, turn it off and put it on charge.

!
Edit - History - Print - Recent Changes - Search
Page last modified on September 17, 2007, at 07:48 PM