@@ -27,7 +27,7 @@ camera.
27
27
28
28
## Requirements and installation
29
29
Some packages need to be installed with apt-get:
30
- - ` libcamera ` (if not already installed). You can test libcamera and the support
30
+ - ` libcamera ` and ` libcamera-apps ` (if not already installed). You can test libcamera and the support
31
31
for your camera with:
32
32
``` commandline
33
33
libcamera-hello --list-cameras
@@ -52,36 +52,42 @@ for your camera with:
52
52
by yourself. Instructions can be found here: https://github.com/indilib/indi . A Raspberry Pi Zero does not
53
53
have enough RAM to compile with 4 threads in parallel: you need to do ` make -j1 ` instead of ` make -j4 ` .
54
54
Finally, after installation, you need to have a working INDI server: ` indiserver -v indi_simulator_telescope `
55
- - The Python packages ` picamera2 ` , ` numpy ` , ` lxml ` and ` astropy ` . Theoretically these packages can be installed with ` pip ` .
56
- But at least the version of ` picamera2 ` must fit to the ` libcamera ` you installed with ` apt-get ` . Therefore it is
57
- safer to install these Python packages with ` apt-get ` too.
58
-
59
- The command line to install all is:
55
+ - The Python packages ` PyQt5 ` , ` picamera2 ` and ` numpy ` must be installed with ` apt-get ` . Typically they are already
56
+ installed. If not you can install them with:
60
57
``` commandline
61
- sudo apt-get install libcamera-apps indi-bin python3-picamera2 python3-lxml python3-astropy python3-numpy
58
+ sudo apt-get install python3-picamera2 python3-pyqt5 python3-numpy
62
59
```
63
60
64
- The ` indi_pylibcamera ` driver package is available on PyPi. Please install with:
61
+ The Raspberry PI OS requires a virtual environment to install non-system Python packages. Trying to install
62
+ ` indi_pylibcamera ` without a virtual environment will fail with ` error: externally-managed-environment ` .
63
+
64
+ Run the following on a command line to install ` indi_pylibcamera ` in a virtual environment called ` venv_indi_pylibcamera ` :
65
65
``` commandline
66
- sudo pip3 install indi_pylibcamera
67
- sudo indi_pylibcamera_postinstall
66
+ python3 -m venv --system-site-packages ~/venv_indi_pylibcamera
67
+ source ~/venv_indi_pylibcamera/bin/activate
68
+ pip install --upgrade pip
69
+ pip install indi_pylibcamera
68
70
```
69
71
70
- The ` indi_pylibcamera_postinstall ` script creates in ` /usr/share/indi ` a symbolic link to the driver XML. That makes
71
- the driver available in the KStars/EKOS profile editor in "CCD"->"OTHERS". Not all versions ov KStars/ECOS support this
72
- (for instance it works with KStars 3.6.5 but not with KStars 3.4.3).
73
-
74
72
## Uninstall
75
73
For uninstalling the driver do:
76
74
``` commandline
77
75
sudo rm -f /usr/share/indi/indi_pylibcamera.xml
78
- sudo pip3 uninstall indi_pylibcamera
76
+ rm -rf ~/venv_indi_pylibcamera
79
77
```
80
78
81
79
## Running
82
- You can start the INDI server with ` indiserver -v indi_pylibcamera ` . When the server is running you can connect to
83
- the server from another computer with an INDI client (for instance KStars/EKOS). The camera name is the one
84
- you configure in ` indi_pylibcamera.ini ` .
80
+ At the moment there is no support to start the driver from the EKOS profile editor.
81
+ The driver and the indi server must be started in shell with activated virtual environment:
82
+ ``` commandline
83
+ source ~/venv_indi_pylibcamera/bin/activate
84
+ ```
85
+
86
+ In the same shell you can start the INDI server with ` indiserver -v indi_pylibcamera ` . When the server is running
87
+ you can connect to the server from another computer with an INDI client (for instance KStars/EKOS). The camera name
88
+ is the one you configure in ` indi_pylibcamera.ini ` .
89
+
90
+ I recommend you to make a wrapper script to activate the environment and start the driver.
85
91
86
92
## Global Configuration
87
93
The driver uses a hierarchy of configuration files to set global parameter. These configuration files are loaded in the
0 commit comments