software
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
software [2025/01/22 22:29] – holtz | software [2025/05/10 18:09] (current) – holtz | ||
---|---|---|---|
Line 32: | Line 32: | ||
This will also provide instantiations of all of the Alpaca devices: Telescope as T, Dome as D, Safetymonitor as S, Cameras as C[], Switches as SW[], Focussers as F[]. | This will also provide instantiations of all of the Alpaca devices: Telescope as T, Dome as D, Safetymonitor as S, Cameras as C[], Switches as SW[], Focussers as F[]. | ||
- | Documentation is also available at http:// | + | Documentation is available at http:// |
===== Robotic software ===== | ===== Robotic software ===== | ||
Line 38: | Line 38: | ||
Alternatively, | Alternatively, | ||
+ | For SONG operation, robotic operations will be conducted through Postgres database syncs from Aarhus, details TBD when this is implemented ... | ||
+ | |||
+ | ===== song1m computer ===== | ||
+ | |||
+ | This is the main computer interface. It is a virtual machine running on a box in the APO server room. Use the song account to log in. Once all remote software is started (see pwi1m, spec1m, and dome1m): | ||
+ | < | ||
+ | cd APOsong | ||
+ | ipython | ||
+ | > from aposong import * | ||
+ | </ | ||
+ | |||
+ | This should show you a list of commands (which you can see again with the commands() function), and a list of connected devices. | ||
===== pwi1m computer ===== | ===== pwi1m computer ===== | ||
Line 47: | Line 59: | ||
* several ASCOM drivers for telescope, port 1 focuser, and mirror cover control | * several ASCOM drivers for telescope, port 1 focuser, and mirror cover control | ||
* a custom PlaneWave API interface | * a custom PlaneWave API interface | ||
- | * ASCOM remote | + | * ASCOM remote |
+ | * PWI-4 interface | ||
+ | * PlaneWave Focuser (via PWI4) | ||
+ | * PlaneWave Mirror Cover (via PWI4) | ||
+ | * Atik guide camera | ||
+ | * Atik eShel camera | ||
+ | * QSI camera (for PlanWave port 1) | ||
+ | * QSI FilterWheel | ||
* A custom Alpaca server which supports Alpaca drivers for: | * A custom Alpaca server which supports Alpaca drivers for: | ||
- | *the Zaber focusing stage (Zaber XX) through an ASCOM Focuser device, | + | * the Zaber focusing stage (Zaber XX) through an ASCOM Focuser device, |
- | *the iodine stage (Thorlabs TLS 150 stage), commanded through an ASCOM Focuser device, | + | * the calibration stage (Thorlabs LTS 150 stage), commanded through an ASCOM Focuser device |
+ | * the iodine stage (Thorlabs TLS 150 stage), commanded through an ASCOM Focuser device, | ||
* the iodine cell temperature controller (Thorlabs TC300 controller), | * the iodine cell temperature controller (Thorlabs TC300 controller), | ||
| | ||
+ | |||
+ | PlaneWave interface 4 is started from a desktop icon. It will open (after a minute or two) a graphical window (more details below). Need to ensure that telescope is connected and all motors/ | ||
+ | |||
+ | ASCOM remote is stated from a desktop icon. It may need to be restarted if power is cycled to any of the devices that it interfaces to. It takes a minute or two to start and should show connections to all of the devices listed above. | ||
+ | |||
+ | The Alypca server is started from an Anaconda Python shell (start using Windows input). Once the terminal window comes up: | ||
+ | < | ||
+ | cd APOalpyca/ | ||
+ | python fpu_app.py | ||
+ | </ | ||
+ | |||
+ | The system should then be ready for remote usage. | ||
+ | |||
=== Planewave software === | === Planewave software === | ||
+ | |||
+ | The PlaneWave software is not normally used for regular operation, as we just use the ASCOM and direct PWI interface. However, more detailed information and more command functionality is available through the PWI graphical interface, e.g., for pointing models and telescope troubleshooting. Hence we provide some information here. | ||
On pwi1m, the telescope is controlled through the PWI4 software. This also has the capability to control an ASCOM camera, necessary when using PWI4 to construct a pointing model. | On pwi1m, the telescope is controlled through the PWI4 software. This also has the capability to control an ASCOM camera, necessary when using PWI4 to construct a pointing model. | ||
Line 101: | Line 136: | ||
Documentation of the Alpaca drivers can be found at [[https:// | Documentation of the Alpaca drivers can be found at [[https:// | ||
- | ===== Dome software | + | ===== spec1m computer ===== |
+ | |||
+ | spec1m is the SONG spectrograph computer. It controls the spectrograph QHY detector and the Esatto focuser. It also controls two thermocouples that monitor the body temperature of the QHY and a relay that resets a watchdog timer if the body temperature is under a limit; otherwise the watchdog is not reset and the QHY camera power will be cut after 2-3 minutes. | ||
+ | |||
+ | Run ASCOM remote for QHY interface and Esatto focuser interface. | ||
+ | |||
+ | Run Alpyca server for thermocouple interface from an Anaconda terminal shell: | ||
+ | < | ||
+ | cd APOalpyca/ | ||
+ | python spectro_app.py | ||
+ | </ | ||
+ | |||
+ | Since the QHY power is controlled by the thermocouple interface, the ASCOM remote interface won't connect until this is run: it will prompt you to connect the ASCOM device within 10 seconds. | ||
+ | |||
+ | ===== dome1m | ||
Dome control is implemented through software running on a Raspberry Pi, dome1m. | Dome control is implemented through software running on a Raspberry Pi, dome1m. | ||
Line 128: | Line 177: | ||
< | < | ||
cd APOalpyca/ | cd APOalpyca/ | ||
- | python | + | python |
</ | </ | ||
Line 180: | Line 229: | ||
===== Linux installation ===== | ===== Linux installation ===== | ||
+ | |||
+ | < | ||
+ | dnf install tcsh emacs git gnome-tweaks tigervnc-server gcc g++ strongswan | ||
+ | </ | ||
+ | |||
+ | change selinux to Permissive and reboot | ||
+ | |||
+ | < | ||
+ | useradd --uid 1013 -d /home/song song | ||
+ | passwd song | ||
+ | add song user into / | ||
+ | systemctl enable --now vncserver@: | ||
+ | firewall-cmd --permanent --add-service=vnc-server | ||
+ | firewall-cmd --reload | ||
+ | |||
+ | </ | ||
+ | |||
+ | set up ipsec.secrets, | ||
+ | < | ||
+ | systemctl enable --now strongswan | ||
+ | </ | ||
anaconda | anaconda | ||
+ | install | ||
+ | | ||
+ | add ssh-key | ||
+ | < | ||
+ | git clone APOsong.git | ||
+ | cd APOsong | ||
+ | pip install -e . | ||
+ | </ | ||
alpyca, tkthread, importlib_resources, | alpyca, tkthread, importlib_resources, | ||
| | ||
postgres 13 | postgres 13 | ||
< | < | ||
- | dnf install postgresql | + | dnf install postgresql |
</ | </ | ||
+ | |||
+ | pgadmin4 | ||
+ | < | ||
+ | dnf install https:// | ||
+ | dnf install -y https:// | ||
+ | dnf install pgadmin4 | ||
+ | </ | ||
+ | |||
+ | |||
+ | Need to set up correct password authetication in pg_hba.conf and postgresql.conf | ||
influxdb | influxdb | ||
Line 253: | Line 341: | ||
</ | </ | ||
- | dnf install tigervnc-server | + | Copy existing grafana.db |
software.1737584993.txt.gz · Last modified: 2025/01/22 22:29 by holtz