Difference between revisions of "McScope"
(Tag: Visual edit) |
|||
Line 1: | Line 1: | ||
This page is about a reference DIY microscpoe control system similar to those used by John McMaster. Its intended to be a good starting place for what options might be for adding automated image capture to a microscope. | This page is about a reference DIY microscpoe control system similar to those used by John McMaster. Its intended to be a good starting place for what options might be for adding automated image capture to a microscope. | ||
+ | <br /> | ||
+ | [[File:Mcscope overview thumb.png|center|thumb]] | ||
+ | |||
+ | |||
+ | Above: high level sample architecture. In this example one axis uses an MDrive17 and a second axis uses a generic stepper motor without integrated driver. However, in a real system you probably want X and Y to use the same motor/drive | ||
+ | |||
Useful links: | Useful links: | ||
− | * https://github.com/SiliconAnalysis/pyuscope | + | |
− | * https://microwiki.org/media/scopetek/0001-scopetek-directly-control-RGB-gain.patch | + | *https://github.com/SiliconAnalysis/pyuscope |
− | * https://microwiki.org/wiki/index.php/Stepper_Motor | + | *https://microwiki.org/media/scopetek/0001-scopetek-directly-control-RGB-gain.patch |
− | * https://www.machinekit.io | + | *https://microwiki.org/wiki/index.php/Stepper_Motor |
− | * https://beagleboard.org/black | + | *https://www.machinekit.io |
+ | *https://beagleboard.org/black | ||
Reference system, focusing on critical components | Reference system, focusing on critical components | ||
− | * Microscope | + | |
− | ** AmScope MU800 camera | + | *Microscope |
− | ** MDrive17 stepper motors on XY stage | + | **AmScope MU800 camera |
− | * BBB indexer | + | **MDrive17 stepper motors on XY stage |
− | ** BBB | + | *BBB indexer |
− | ** Machinekit | + | **BBB |
− | ** B3I cape (breaks out step/direction to RJ45) | + | **Machinekit |
− | * T61p laptop | + | **B3I cape (breaks out step/direction to RJ45) |
− | ** Ubuntu 16.04LTS | + | *T61p laptop |
− | ** pyuscope (microscope control software) | + | **Ubuntu 16.04LTS |
− | ** touptek.ko modified for direct RGB control | + | **pyuscope (microscope control software) |
+ | **touptek.ko modified for direct RGB control | ||
Reference workflow: | Reference workflow: | ||
− | * Connect BBB over USB to host laptop | + | |
− | * Host laptop: static config IP to 192.168.7.1 | + | *Connect BBB over USB to host laptop |
− | * SSH -X from T61p to BBB (192.168.7.2) | + | *Host laptop: static config IP to 192.168.7.1 |
− | ** Launch LinuxCNC software over X | + | *SSH -X from T61p to BBB (192.168.7.2) |
− | ** Launch server.py RPC client (TODO: bring back automatic launch) | + | **Launch LinuxCNC software over X |
− | ** Use LinuxCNC GUI for all setup movement, not pyuscope | + | **Launch server.py RPC client (TODO: bring back automatic launch) |
− | * Optional: white balance camera using cal.py. Write values to microscope.json | + | **Use LinuxCNC GUI for all setup movement, not pyuscope |
− | * Start pyuscope software | + | *Optional: white balance camera using cal.py. Write values to microscope.json |
− | * Select current objective (ie 20x) | + | *Start pyuscope software |
− | * Use LinuxCNC GUI to navigate around stage and make adjustments to level out | + | *Select current objective (ie 20x) |
− | ** TODO: add link / suggestions how to do this | + | *Use LinuxCNC GUI to navigate around stage and make adjustments to level out |
− | * Use LinuxCNC GUI to navigate to upper left corner of die and in pyuscope hit "set upper left" | + | **TODO: add link / suggestions how to do this |
− | * Use LinuxCNC GUI to navigate to lower right corner of die and pyuscope hit "set lower right" | + | *Use LinuxCNC GUI to navigate to upper left corner of die and in pyuscope hit "set upper left" |
+ | *Use LinuxCNC GUI to navigate to lower right corner of die and pyuscope hit "set lower right" | ||
+ | |||
+ | <br /> |
Revision as of 07:54, 19 August 2019
This page is about a reference DIY microscpoe control system similar to those used by John McMaster. Its intended to be a good starting place for what options might be for adding automated image capture to a microscope.
Above: high level sample architecture. In this example one axis uses an MDrive17 and a second axis uses a generic stepper motor without integrated driver. However, in a real system you probably want X and Y to use the same motor/drive
Useful links:
- https://github.com/SiliconAnalysis/pyuscope
- https://microwiki.org/media/scopetek/0001-scopetek-directly-control-RGB-gain.patch
- https://microwiki.org/wiki/index.php/Stepper_Motor
- https://www.machinekit.io
- https://beagleboard.org/black
Reference system, focusing on critical components
- Microscope
- AmScope MU800 camera
- MDrive17 stepper motors on XY stage
- BBB indexer
- BBB
- Machinekit
- B3I cape (breaks out step/direction to RJ45)
- T61p laptop
- Ubuntu 16.04LTS
- pyuscope (microscope control software)
- touptek.ko modified for direct RGB control
Reference workflow:
- Connect BBB over USB to host laptop
- Host laptop: static config IP to 192.168.7.1
- SSH -X from T61p to BBB (192.168.7.2)
- Launch LinuxCNC software over X
- Launch server.py RPC client (TODO: bring back automatic launch)
- Use LinuxCNC GUI for all setup movement, not pyuscope
- Optional: white balance camera using cal.py. Write values to microscope.json
- Start pyuscope software
- Select current objective (ie 20x)
- Use LinuxCNC GUI to navigate around stage and make adjustments to level out
- TODO: add link / suggestions how to do this
- Use LinuxCNC GUI to navigate to upper left corner of die and in pyuscope hit "set upper left"
- Use LinuxCNC GUI to navigate to lower right corner of die and pyuscope hit "set lower right"