Difference between revisions of "Experimental PC"

From Applied Optics Wiki
Jump to: navigation, search
(comedi kernel drivers)
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
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.
 +
 +
==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]]
 
Back to [[Linux How-tos]]
  
<big>Extra stuff for all the experimental hardware that might need setting up, for instance in PCs like '''blanket''', '''carpet''', '''pouffe''' etc.</big>
 
 
The information contained here will also be useful if you want to install any of these bits of hardware on any other Linux PC.
 
  
Includes a bit of information about c-scan too.
+
__TOC__
  
 
== Pre-install ==
 
== Pre-install ==
Line 19: Line 21:
 
#* Most of these will be in /etc/
 
#* Most of these will be in /etc/
  
Example: swapping the increasingly doddery blanket (running Suse 11.2, kernel 2.6.31.14-0.6) for carpet (running Suse 11.4, kernel 2.6.37.6-0.7):
 
 
I tarballed /etc/ and /usr/local/bin/ from the old PC, and stuck the files in my home directory where they would be recoverable if the old PC died. This is advisable if you're updating the OS on the same PC, in case you accidentally wipe the old partition or something goes wrong during the installation (eg in resizing partitions). /etc/ for configuration files (including our own, for the stages, the SLM etc) and /usr/local/bin/ just as a reminder of the extra stuff (mainly our own) that we installed.
 
  
 
=== Scenario 2: Adding new hardware to an already up-to-date PC ===
 
=== Scenario 2: Adding new hardware to an already up-to-date PC ===
Line 28: Line 27:
 
# 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> )
 
# 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 ==
 
== Scope (and AFG) utilities ==
  
These are the standard command line utilities to grab traces, save setups etc
+
These are the standard command-line utilities to grab traces, save setups etc
  
 
=== vxi11 ===
 
=== vxi11 ===
Line 61: Line 64:
 
**tek_afg_upload_arb
 
**tek_afg_upload_arb
 
**tek user library
 
**tek user library
 +
 
=== LeCroy scope ===
 
=== LeCroy scope ===
 
==== VXI11-compatible LeCroy scopes ====
 
Anything bought in 2010 onwards (generally black, though we've got one blue one)...
 
  
 
*cd /home/scan/source/hardware/lecroy/
 
*cd /home/scan/source/hardware/lecroy/
Line 71: Line 72:
 
*lgetwf
 
*lgetwf
  
==== VCIP-only LeCroy scopes ====
+
== PI pci stages* ==
The old (non-Windows) LT564L scope, and Teti's old Waverunner 6050 (the one that runs Windows 2000).
+
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/hardware/ethernet_scope/
 
*make clean; make; sudo make install
 
*Installs:
 
**eth_cmd
 
**/etc/lecroy_tcp/ (empty directory)
 
*cd /home/scan/source/egetwf/
 
*make clean; make; sudo make install
 
*Installs:
 
**egetwf
 
 
 
== PI PCI stage driver ==
 
*cd /home/scan/source/dev/pi_pci/driver_2.6/library/
 
*make clean; make; sudo make install
 
*Installs:
 
**pi_save_pos
 
**pi_recall_pos
 
**(pi_user library)
 
**/etc/pi_stage/stage_database/
 
  
 +
*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/
 
*cd /home/scan/source/hardware/pi_pci_stage/
*make clean; make; sudo make install
+
*// 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.
*Installs:
+
*// cp /usr/local/include/pi_stage.h from ejectorseat to your local experimental pc (last stable version for sios on ejectorseat)
**set_stages_safe
+
*make clean; make; sudo make install;
**manual_pci_stage (manual_stage)
+
*cd /home/scan/source/dev/pi_pci/driver_3.xx_v1.0/driver/
**/etc/pi_stage/position_um '''if''' it doesn't already exist (default stage position file, all axes at 0)
+
*// 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
**/etc/pi_stage/installed_stages - this is the default list of installed stages, '''which you may need to edit if yours are different:'''
+
*make  
axis 0  m-531.dd
+
*// 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
axis 1  m-531.dd
+
*sudo ./install_pi_stage
axis 2  m-605.2dd
 
axis 3  m-605.2dd
 
 
 
*cd /home/scan/source/dev/pi_pci/driver_2.6/driver/
 
*make
 
*sudo ./install_pi_stage_recall
 
*Installs:
 
**PI PCI stage device driver
 
 
 
'''Note:''' if you see something like the following after the last "make"....:
 
 
 
make -C /lib/modules/2.6.27.45-0.1-default/build M=/home/scan/source/dev/pi_pci/driver_2.6/driver modules
 
make[1]: Entering directory `/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default'
 
make[1]: *** No rule to make target `modules'.  Stop.
 
make[1]: Leaving directory `/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default'
 
make: *** [default] Error 2
 
 
 
... it means that you don't have the kernel-source package installed. To fix this:
 
*sudo zypper install kernel-source
 
then...
 
*cd /home/scan/source/dev/pi_pci/driver_2.6/driver/
 
*make
 
*sudo ./install_pi_stage_recall
 
 
 
For kernels newer than 2.6.36, I had to make changes to the driver to get it to compile, replacing ioctl with unblocked_ioctl (and also in the BNS driver).
 
 
 
 
 
== PI ISA stage ==
 
*cd /home/scan/source/hardware/stages
 
*make -f Makefile.osam clean; make -f Makefile.osam;  
 
*sudo make -f Makefile.osam install
 
*Installs:
 
**manual_stage
 
**/etc/stages/PI_stage_origin '''if''' it doesn't already exist (default stage position file, all axes at 0)
 
 
 
== Inchworm and IDAC stages ==
 
*cd /home/scan/source/hardware/IW_driver
 
*sudo make install
 
*Installs:
 
**/etc/stages/IW_stage_origin '''if''' it doesn't already exist (default stage position file, both axes at 0)
 
*cd /home/scan/source/hardware/IDAC_driver
 
*sudo make install
 
*Installs:
 
**/etc/stages/IDAC_stage_origin '''if''' it doesn't already exist (default stage position file, both axes at 0)
 
 
 
== BNS SLM ==
 
*cp -av [LOCATION_OF_OLD_CONFIG_FILES]/etc/slm /etc/
 
 
 
*cd /home/scan/source/dev/BNS/driver_2.6/
 
*make
 
To install use
 
*sudo ./install_slm_mtrr
 
OR
 
*sudo ./install_for_boot
 
The latter install the kernel driver in the system and will load it automatically at boot time for you.  If you
 
want it load right now without rebooting use the previous version as well - matt
 
 
 
*Installs:
 
**BNS SLM device driver
 
 
 
*cd /home/scan/source/dev/BNS/utils/
 
*make clean; make; sudo make install
 
*Installs:
 
**bns_change_frame (change_frame_bns)
 
**bns_laser_ab
 
**bns_power
 
**bns_power_off
 
**bns_power_on
 
**bns_upload_frame (upload1_bns)
 
 
 
*cd /home/scan/source/hardware/bns_slm/manual_bns/
 
*make clean; make; sudo make install
 
*Installs:
 
**manual_bns
 
 
 
*cd /home/scan/source/hardware/bns_slm/set_bns/
 
*make clean; make; sudo make install
 
*Installs:
 
**set_bns
 
 
 
== FFTW libraries ==
 
 
 
These are needed by the higher order correction algorithm when using the SLM in c-scan. I use the ''float'' version of the libraries (rather than the standard ''double'' version) for speed, and so an extra option must be set before compiling.
 
 
 
*cd /home/scan/source/fftw-3.3/
 
*make distclean; ./configure --enable-float; make; sudo make install
 
*Installs:
 
**(FFTW float libraries)
 
 
 
== Comedi ==
 
 
 
=== comedi kernel drivers ===
 
 
 
The comedi drivers are now included in the kernel sources but for now are in the "staging" area.  On SUSE these are not built by default and the way to get them is to install the kernel sources and remake the kernel with these staging drivers installed.
 
 
 
* cd /usr/src/linux
 
* su
 
* make cloneconfig
 
* make menuconfig or make xconfig
 
* select "Device drivers":"Staging drivers":"Data acquisition support (comedi)"
 
 
 
There should now be an "M" in the < > next to this. There should also now be loads of comedi related options, you might have to go in and out of the config to see this.  Select the relevant ones- you may have to descend the options tree to find yours.
 
 
 
* Change the kernel name so as to distinguish it from your current kernel ("general setup":"Local version") by adding .comedi to the end.
 
 
 
* Save the config, change the name to .config.comedi and exit
 
 
 
* make (this can take a long time)
 
* make modules_install
 
* make install
 
 
 
In theory on reboot there should be an option to boot to something XXXXX.comedi - this is the one with your drivers in it.  I suppose you could leave the name without the .comedi and it would boot automatically but then you'd find it difficult to boot if you screwed up the kernel build!
 
  
=== comedi kernel driver compilation the OLD way ===
 
  
The "current release" version of the comedi is 0.7.76, however this will not compile on modern kernels (it's more than 7 years old). The current comedi policy seems to be one of continuous code development, they seem to have given up on producing "releases." We need to create a directory on the local disk (there is a lot to compile) and download a "git snapshot".
+
== 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 /usr/local/src/
+
*cd /home/scan/source/hardware/pi_usb_stage/utils/cmd_line_utils/
*sudo mkdir comedi
+
*make clean; make all; sudo make install;
*sudo chown <your_username>: comedi
+
*sudo ./actually_install_pi_usb
*cd comedi
+
*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)
  
The following two lines are from the comedi download page (and it's worth checking they are still correct, as they occasionally change which version control software they use): http://www.comedi.org/download.html
+
== Newport mirrors ==
*git clone git://comedi.org/git/comedi/comedi.git
+
Control of the capacitive feedback newport CONEX mirror. Separate scripts for Newport Agilis exisit.  
*cd comedi
 
*./autogen.sh
 
The "./configure" script needs some extra arguments to work (ref Roger). "./configure -h" to see all options. These might change in the future.
 
 
 
For 32- or 64-bit (tested by Steve):
 
*./configure --with-linuxsrcdir=/usr/src/linux
 
 
 
*make
 
*sudo make install
 
*sudo /sbin/depmod -a
 
*sudo make dev
 
(probably don't need this anymore, see later)
 
  
 +
*cd /home/scan/source/hardware/newport_CONEX
 +
*sudo make; sudo make install;
 
*Installs:
 
*Installs:
**(comedi libraries)
+
**newport_control
**(device libraries)
 
**(comedi devices in /dev/)
 
 
 
*sudo echo 'KERNEL=="comedi*",                      MODE="0666"' > /etc/udev/rules.d/53-comedi.rules
 
**Sets the permissions of the DAQ to world-readable-and-writable during boot
 
 
 
==== Specific instructions for the Amplicon PCI230 ====
 
(See also Roger's Troubleshooting Tips below for other cards, and for getting comedi to cope with kernel updates)
 
 
 
===== Older versions of comedi =====
 
For old versions of comedi, you need to run comedi_config after you install your card's driver. For new versions of comedi, this is done automatically. If you've got more than one card in your PC, then I guess google it.
 
 
 
*sudo echo 'install amplc_pci230 PATH=/sbin:/usr/sbin:/usr/local/sbin:$PATH; comedi_config /dev/comedi0 amplc_pci230' >> /etc/modprobe.d/99-local.conf
 
**Means that when you use ''modprobe'' to load the amplc_pci230 module, it automatically runs ''comedi_config'' too.
 
**Unfortunately, ''udev'' ignores this, so we have to...
 
*sudo echo '/sbin/modprobe amplc_pci230' >> /etc/init.d/boot.local
 
*sudo echo '/usr/local/sbin/comedi_config /dev/comedi0 amplc_pci230' >> /etc/init.d/boot.local
 
**Makes the PCI230 modules get loaded automatically at boot time
 
 
 
===== Newer versions of comedi =====
 
As you no longer have to run comedi_config, then you don't need to tell modprobe about comedi_config, and all you need is the following line that will install your driver at boot time:
 
*sudo echo '/sbin/modprobe amplc_pci230' >> /etc/init.d/boot.local
 
 
 
==== Troubleshooting tips ====
 
 
 
Installing comedi onto different machines may require a slight modification to the approach above.
 
 
 
*Change the name of driver (amplc_pci230 above) depending on the DAQ card used (e.g. most PCI National instruments DAQ cards use ni_pcimio). A complete list can be viewed on [http://www.comedi.org/hardware.html comedi's hardware list].
 
*Some drivers may not compile using make. If this happens, put #if 0 and #endif at the top and bottom of the driver's code respectively. The drivers are located in ./comedi/drivers/, adv_pci1710.c and adv_pci_dio.c have been known to cause problems.
 
*Once installed, if the modules do not load into the kernal using modprobe (e.g. if comedi_test returns cannot find comedi0 or drivers), insmod may be required. The following needs to be placed in and at the end of /etc/init.d/boot.local (these are for National Instruments DAQ, change drivers as required)
 
**/sbin/insmod /lib/modules/comedi/comedi.ko
 
**/sbin/insmod /lib/modules/comedi/drivers/8255.ko
 
**/sbin/insmod /lib/modules/comedi/drivers/ni_pcimio.ko
 
**/usr/local/sbin/comedi_config /dev/comedi0 ni_pcimio (if this is not already there)
 
 
 
==== Dealing with kernel updates ====
 
 
 
Updates to the kernel mean that the comedi drivers need to be reinstalled. As the kernel updates are usually fairly minor, the comedi drivers usually don't need recompiling. It's annoying having to deal with this, so this solution helps to remove some of that annoyance. When you've installed comedi run the following as root:
 
 
 
cp -r /lib/modules/$(uname -r)/comedi /lib/modules/
 
 
 
This will copy your current comedi installation to /lib/modules/comedi.
 
 
 
Now add the following to /etc/init.d/boot.local (*before* any of the commands to load the comedi modules):
 
 
 
KERNEL=$(uname -r)
 
 
if [ ! -d /lib/modules/${KERNEL}/comedi/ ]; then
 
        cp -r /lib/modules/comedi /lib/modules/${KERNEL}/
 
        depmod -a
 
fi
 
 
 
This will check for the presence of the comedi directory in the modules directory for the current kernel and copy it over if it doesn't exist. ''depmod -a'' updates the module dependencies.
 
 
 
It is important that if you install a newer version of comedi that you remove /lib/modules/comedi and replace it with your updated version. Also note that some kernel updates may be incompatible with your compiled comedi drivers and so you'll have to recompile and reinstall using the instructions above.
 
 
 
=== comedilib ===
 
 
 
comedilib should now be installed automatically through Roger's openSUSE repository. Updates will also become available through the normal update procedure. If this doesn't work for any reason, see Roger or use the old method:
 
 
 
cd /home/scan/source/hardware/comedi/comedilib-0.8.1/
 
make distclean; ./configure; make; sudo make install
 
Installs:
 
 
* libcomedi
 
* comedi_test
 
* /usr/local/sbin/comedi_config
 
 
 
=== Comedi Settings for the NI PCI-6251 ===
 
 
 
If you want to use the PFI port as a digital output, you must do some extra configuration. This is possible using the demo tools in comedilib (which could also be copied across to your own code of course). So, to change channel 14 of subdevice 7 (ie. pin 1 on the connector) to be a digital output do the following in the comedilib/demo directory:
 
  
* ./choose_routing -s7 -c14 16  # NI_PFI_OUTPUT_DO == 16
+
and copies the appropriate udev rule to the local machine.
* ./dio -s7 -c14 1        # now its an output
 
* ./outp -s7 -c14 1  # test the output (or 0)
 
  
All these can be set up at boot. Putting /usr/local/bin/choose_rooting -s7 -c** 16 for all/any channels in /etc/rc.d/boot.local and copying (as root) choose_rooting from the demo folder in (compiled?) comedilib to /usr/local/bin/.
 
 
=== Comedi on openSUSE 11.4, Kernel 2.6.37.6-0.5-desktop  ===
 
I did a clean install of openSUSE 11.4 64bit on Settee. I had a few problems, so I thought I'd write down how I finally managed to get it working. This was June 2011, on Settee (Samuel).
 
 
After running ~share/suse_hacks/<suse version>/std_suse_hacks_<location>, make sure to run the install_eee_packages too. This will install comedilib automatically for you, amongst other things.
 
 
I tried to use the kernel tree to install comedi. From /usr/src/linux/ type: '''sudo make menuconfig''', and choose to install modules for comedi and the relevant drivers. Comedi may be found in the tree under Device Drivers >> Staging Drivers >> Data acquisition support (comedi). Use / for search if so desired. Use '''sudo make modules'''; '''sudo make install''' to install. Unfortunately, this method didn't work for me, and the modules for other devices like network cards got overwritten, so I had to rescue the system.
 
 
I thus downloaded the latest snapshot from the [http://www.comedi.org/downloads.html comedi download] page, untarred it to /usr/local/src/comedi, and used '''./autogen.sh''' then '''./configure --with-linuxdir=/usr/src/linux'''. It correctly detected the 64bit arch. Run '''make''' then '''sudo make install''' to install. Use the directions above to add the relevant lines to /etc/init.d/boot.local. Since I use the NI PCI6251, the lines in my boot.local file are :
 
 
KERNEL=$(uname -r)
 
if [ ! -d /lib/modules/${KERNEL}/comedi/ ]; then
 
  cp -r /lib/modules/comedi /lib/modules/${KERNEL}/
 
  depmod -a
 
fi
 
 
/usr/local/sbin/comedi_config /dev/comedi0 ni_pcimio
 
choose_routing -s7 -c0 16 # NI_PFI_OUTPUT_DO == 16
 
choose_routing -s7 -c1 16 # NI_PFI_OUTPUT_DO == 16
 
etc etc
 
choose_routing -s7 -c14 16 # NI_PFI_OUTPUT_DO == 16
 
choose_routing -s7 -c15 16 # NI_PFI_OUTPUT_DO == 16
 
 
choose_routing is available from comedilib/demo/.libs/. Copy using sudo to the /usr/local/bin/
 
 
Hopefully that helps.
 
  
 
== c-scan ==
 
== c-scan ==
I had to make a once-only change to blanket's c_scan Makefile, due to going from a 2.4 kernel to a 2.6 kernel (and subsequent change of BNS device driver).
 
  
 
*cd /home/scan/source/hardware/scanner/
 
*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  
 
*make clean; make; sudo make install  
 
*sudo cp ~sds/bin/cscan /usr/local/bin/
 
*sudo cp ~sds/bin/cscan /usr/local/bin/
Line 356: Line 122:
 
**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.
 
**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.
  
== Jai CCD camera ==
 
*sudo cp ~sds/bin/ccd* /usr/local/bin/
 
*Installs:
 
**ccd_set_serial
 
**ccd0
 
**ccd1
 
**..
 
**ccd7 (different shutter speeds)
 
  
== Andor iXon camera ==
 
You can find the latest driver here: /home/scan/source/hardware/andor_camera/andor you need to copy
 
this directory to a local disk to build and install the driver and libraries because the andor
 
supplied script borks if it isn't run as root and the permissions on the nfs disks prevent root
 
running the script directly.
 
  
The current driver is v2.82 install in December 2008 by Matt.  This is broken for kernel versions
+
== d-scan ==
2.6.23-2.6.27 and will cause hard kernel lock ups is you install it on these kernels. Under newer
+
Modern version of c-scan with greater flexibility etc.
kernels it may not compile because of an error in src/driver/fault.c - just just #define NOPFN_SIGBUS -1
+
*cd /home/scan/source/d_scan/d_scan
in the preamble of fault.c to fix this.  We are waiting for a revised driver.
+
*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
== Nanoscope lab / Andor iXon camera ==
+
*Find errors and debug
The Andor camera setup we use uses a client / server model to overcome some of the shortcomings of
 
the Andor driver / libraries.  All the code can be found in  /home/scan/source/hardware/andor_camera/camera.
 
You need to make the camera_driver and the camera_utils all application code should use and compile
 
in the camera_client code. Before you use anything the server needs to be running (camera_server).
 
Placing the following line in boot.local AFTER the Andor code will ensure it runs at boot time:
 
<pre>
 
echo Installing the camera_server
 
su matt -c /usr/local/bin/camera_server &
 
</pre>
 
 
 
Remember the meminfo thing! reserve at least 4Mb of RAM for the driver by adding this to the boot options in the grub boot
 
script (menu.1st) mem=1000M where 1000 is the size of the RAM in Mb - 4 (maybe 5?) as in:
 
 
 
<pre>
 
    kernel /boot/vmlinuz-2.6.25.18-0.2-default root=/dev/disk/by-id/scsi-SATA_ST340014A_3JX7N160-part2 resume=/dev/sda1 splash=silent showopts mem=1000M vga=0x31a
 
</pre>
 
 
 
The current driver 2.82-30003 on kernel 2.6.27.xx appears to be working, however, Andor seem to be ironing out a few bugs still so this could be volatile - if you have a working system I suggest leaving it alone.
 
  
2.78 works on pre 2.6.25 (or thereabouts) but not after because it causes hard kernel locks, it also requires a little hacking
+
*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~.
to compile on these newer kernels but since it crashes this is a little pointless. 2.82-30002 compiles and doesn't crash
 
but returns scrambled image data.  2.82-30003 compiles on 2.6.27 kernels but not older ones, it doesn't crash and the image
 
data seems ok.
 

Latest revision as of 09:46, 9 May 2022

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.

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~.