Difference between revisions of "Experimental PC"

Latest revision as of 15:31, 28 February 2023

Extra stuff for all the experimental hardware that might need setting up. The information contained here will also be useful if you want to install any of these bits of hardware on any other Linux PC.

2023 Update

Experimental PC Kubuntu 22.04 supersedes most of this page.

2022 Update

Much of the information in the Experimental PC old page is now out-dated and/or refers to hardware that is no longer in use. This new page attempts to build a modern version, please contribute by adding instructions for software they use regularly.

Back to Linux How-tos

Pre-install

Scenario 1: inherited PC with working hardware, updating Linux

1. Make a list of all the hardware you have (or likely to have) attached to the PC
2. From this list, work out which programs/utilities you use
   • Most of these will already be installed in /usr/local/bin/
3. Work out how to recompile (and re-install) all these programs
   • Most will have their source code in /home/scan/source/hardware/
4. Save all the configuration files you think you might need
   • Most of these will be in /etc/

Scenario 2: Adding new hardware to an already up-to-date PC

1. Use this wiki, find the instructions for the relevant hardware
2. Any extra configuration files you need (e.g. /etc/stages/IW_stage_origin) - copy off a PC that already has this hardware installed (or you may find a copy in /home/share/backup_system_files/<name of PC> )

ThorLabs APT control components

See ThorLabs apt stages.

Scope (and AFG) utilities

These are the standard command-line utilities to grab traces, save setups etc

vxi11

(Used by Agilent and Tek utilities, and a low-level diagnostic tool in its own right)

• cd /home/scan/source/hardware/vxi11/
• make clean; make; sudo make install
• Installs:
  • vxi11_cmd
  • vxi11 user library

Agilent scope

• cd /home/scan/source/hardware/agilent_scope/
• make clean; make; sudo make install
• Installs:
  • agetwf
  • agilent_load_setup
  • agilent_save_setup

Tek scope/AFG

• cd /home/scan/source/hardware/tek/
• make clean; make; sudo make install
• Installs:
  • tgetwf
  • tek_load_setup
  • tek_save_setup
  • tek_afg_upload_arb
  • tek user library

LeCroy scope

• cd /home/scan/source/hardware/lecroy/
• make clean; make; sudo make install
• Installs:
• lgetwf

PI pci stages*

Experimental PC Old instructions on this cover up to driver_2.6. Below are updated instructions for driver_3.xx_v1.0, but are sios specific! sios install may need to be ported from L4, or sios may need to painfully upgrade to latest os/kernel.

• cd /home/scan/source/dev/pi_pci/driver_3.xx_v1.0/library/
• make clean; make; sudo make install;
• // for new PC may need to double check that g++ is installed, and possibly libncurses5-dev
• cd /home/scan/source/hardware/pi_pci_stage/
• // for kernel versions 5.4 and older certain headers don't have consistent filepaths wrt /usr/src/*headers* and /usr/include/linux/. so below is mainly specific to outdated kernels in sios at the moment.
• // cp /usr/local/include/pi_stage.h from ejectorseat to your local experimental pc (last stable version for sios on ejectorseat)
• make clean; make; sudo make install;
• cd /home/scan/source/dev/pi_pci/driver_3.xx_v1.0/driver/
• // permissions for this directory are wild, root and scan users don't seem to be able to write/access certain files during "make" so temporary work around right now is to cp -r the entire /driver directory onto the local disk (e.g. in /tmp/something) where the local user for sure has full permissions on every file and sub-directory
• make
• // if there are errors about /etc/pi_stage/position not existing cp or mv position_um to it. if there are errors complaining about things at the kernel level, then you might need to install source files: sudo apt-get install linux-source
• sudo ./install_pi_stage

PI USB stage driver

I think the format of udev rules has changed since the scripts were first written and the SYSFS should be replaced with ATTRS. This should fix the problem of the device not being recognised automatically when plugged in.

• cd /home/scan/source/hardware/pi_usb_stage/utils/cmd_line_utils/
• make clean; make all; sudo make install;
• sudo ./actually_install_pi_usb
• check if /etc/udev/rules.d/98-pi-usb.rules exists and change SYSFS to ATTRS (the remove rules should still be okay).
• cd /home/scan/source/hardware/pi_usb_stage/utils/manual_usb_stage/
• make clean; make all; sudo make install;
• look at /etc/pi_stage/usb_installed_stages, change stage_model_here to whatever model file you need to use... (axis 0 m-062.pd)

Newport mirrors

Control of the capacitive feedback newport CONEX mirror. Separate scripts for Newport Agilis exisit.

• cd /home/scan/source/hardware/newport_CONEX
• sudo make; sudo make install;
• Installs:
  • newport_control

and copies the appropriate udev rule to the local machine.

c-scan

• cd /home/scan/source/hardware/scanner/
• edit or create the Makefile for your machine - i.e. Makefile.swing you need to comment in the modules you want to install here
• make clean; make; sudo make install
• sudo cp ~sds/bin/cscan /usr/local/bin/
• Installs:
  • c_scan
  • c_scan man pages
  • cscan: this performs a "touch" on the con-file that you're running with c_scan, so you can see the time at which you started the scan, and - by the time stamp on the data file - the time at which you finished the scan.

d-scan

Modern version of c-scan with greater flexibility etc.

• cd /home/scan/source/d_scan/d_scan
• edit or create the Makefile for your machine - i.e. Makefile.swing you need to comment in the modules you want to install here
• make clean; make; sudo make install
• Find errors and debug

• Fair chance you'll run into problems with the OpenCV version, you'll need to get an older version from the git repository ~good luck~.