Following is a quick-start guide for configuring Wasatch.PY on a brand-new or freshly imaged Raspberry Pi.
If desired, flash a fresh MicroSD card with a clean copy of Raspbian OS from:
Test log:
- This process was tested with 2019-09-26-raspbian-buster-full.zip
- This process was re-tested on 2020-08-04 using Raspberry Pi OS Imager 1.4 for MacOS
- This process was most recently tested on 2022-06-24 using Raspberry Pi OS Imager 1.7.2 for MacOS
- PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
- uname -a = Linux mzieg-rpi 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux
$ python3 --version
Python 3.9.2
$ sudo lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 24aa:1000 Wasatch Photonics Stroker FX2
Bus 001 Device 004: ID 17ef:602e Lenovo USB Optical Mouse
Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd KU-0833 Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(The 2nd device is a WP-785...all WP USB devices use the VID 0x24aa.)
$ mkdir -p work/code
$ cd work/code
$ git clone https://github.com/WasatchPhotonics/Wasatch.PY.git
$ cd ~/work/code/Wasatch.PY
$ sudo cp udev/10-wasatch.rules /etc/udev/rules.d
$ sudo shutdown -r now
You can do this using either Anaconda3 or pip3. I normally use Anaconda on Windows, MacOS and Ubuntu, and it does work for Wasatch.PY on Raspbian.
However, a full ENLIGHTEN development environment on Raspbian apparently can't be done from Anaconda at writing (needs some apt-get packages for PySide2), so you might just use pip3 for ARM at this time.
$ pip3 install numpy py six psutil future pygtail pyusb requests pexpect seabreeze bleak
Run demo.py with "--help" for command-line options. Note that you need to run "source activate wasatch3" each time you reboot (or open a new Terminal window, depending on how your shell is configured), in order to tell Linux and Miniconda "which version" of Python, and which set of package dependencies, you want to use.
$ python3 -u demo.py
2019-05-06 14:25:32,498 MainProcess root WARNING Top level log configuration (1 handlers)
2019-05-06 14:25:32,799 MainProcess __main__ INFO Wasatch.PY 1.0.25 Demo
2019-05-06 14:25:32,804 MainProcess wasatch.FeatureIdentificationDevice ERROR unable to control TEC: EEPROM reports no cooling
Reading: 1 Detector: 0.00 degC Min: 755.00 Max: 1067.00 Avg: 785.72 Memory: 22913024
Reading: 2 Detector: 0.00 degC Min: 757.00 Max: 1042.00 Avg: 785.75 Memory: 22913024
Reading: 3 Detector: 0.00 degC Min: 757.00 Max: 1048.00 Avg: 785.67 Memory: 22913024
Reading: 4 Detector: 0.00 degC Min: 755.00 Max: 1063.00 Avg: 785.64 Memory: 22913024
Reading: 5 Detector: 0.00 degC Min: 755.00 Max: 1050.00 Avg: 785.78 Memory: 22913024
Reading: 6 Detector: 0.00 degC Min: 755.00 Max: 1027.00 Avg: 785.51 Memory: 22913024
Reading: 7 Detector: 0.00 degC Min: 755.00 Max: 1057.00 Avg: 785.64 Memory: 22913024
Interrupted by Ctrl-C...shutting down
See WasatchShell README for documentation, or type "help" at the "wp>" prompt.
$ cd ~/work/code/Wasatch.PY
$ export PYTHONPATH=$PWD
$ cd WasatchShell
WasatchShell $ python3 -u wasatch-shell.py
--------------------------------------------------------------------------------
wasatch-shell version 2.2.1 invoked (Wasatch.PY 1.0.25)
wp> open
1
wp> set_laser_enable on
1
wp> set_integration_time_ms 100
1
wp> get_spectrum_pretty
| *
| *
| *
| *
| *
| *
| *
| *
| *
| * *
| * *
| * *
| * *
| * *
| * * *
| * * *
| * ** *
| * * ** * *
| * * ** * *
| ** * *** * **
| ** ** * *** * **
| **** *** ** *** * * * ** **
| ******************************* *************** * ** ** ***
| ********************************************************************************
+---------------------------------------------------------------------------------
Min: 886.00 Max: 3679.00 Mean: 1032.14 (range 799.39, 930.76nm)
wp> set_laser_enable off
1
wp> quit
If you get something like this:
libcblas.so.3: cannot open shared object file: No such file or directory
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
We recommend following the advice here:
In our case, this was sufficient to fix the issue:
$ sudo apt-get install libatlas-base-dev
