I'm helping a friend to implement an INDI/Ekos/kstars environment in his observatory.
Everything is ok except for the motion in the DEC axis when commanded from the "Mount Control" window.
Goto's motions, however, works great in RA and DEC.

The INDI/Ekos/kstars runs on ubuntu 20.04 (was tested before on 18.04).
The TSX runs in windows 7 (Home Premium) in a virtual machine (ubuntu is the host).
The latest indilib was tested as well as previous versions (compiled) back to 2019.
We also tested to run TSX on wine.
In all scenarios the problem is the same: no DEC movement from the "Mount Control" window.

There is also another strangeness in the "Mount Control" window: the slew speed options jump from 256x to 9x which is indeed faster than the 256x.

In the attached log we moved the mount first in RA with success then in DEC with no success.

Thanks in advance.


The amount of RAM allocated by the indi_webcam driver increases until the system becomes unstable.
This is affecting this driver in Ubuntu 18.04 and raspberry PI's 3 and 4.
First noted in RP4 and reported here ( indilib.org/forum/ccds-dslrs/7199-indi-w...-making-it-slow.html ) some days ago.
The webcam I use is the SPC900nc (no LX mod, standard).
The amount of allocated RAM increases merely by letting the "Loop", in Guide Module, run.
After about 2 hours in RP4 the RAM allocated surpasses the 2 Gb and the CPU usage reaches for 100% making the system unresponsive and unstable.
The message "Buffer Cleared of 3 stale frames." repeats for every frame grabbed from the webcam (the exact number may vary).

Any help is appreciated.

File Attachment:

File Name: indi_webcam_ccd_235806.zip
File Size: 1 KB


For some months I've used indi-webcam driver with Phillips SPC900nc on Ubuntu (kstars/ekos) with no problems .
Recently, however, I begin try to use Raspberry PI to control the same equipment.
First tried RP 3 B+ with astroberry up to date (kstars/ekos) for a couple of days and realized the RAM was not enough.
Then I changed to RP 4 (4 Gb).
In RP 4 with astroberry up to date the webcam did not connect immediately but after updating the USB firmware VL805 from release 0137ad (shipped with astroberry) to 0138a1 ( www.raspberrypi.org/forums/viewtopic.php?t=273027 ) everything went on track again.
Besides the cheap webcam my setup includes AZEQ5 (EQMod driver) and a Nikon d750 (Nikon DSLR driver).
Oh! After the USB firmware update my wireless keyboard and mouse dongle is disconnected immediately after indi drivers are started by ekos. Tried wired mouse with same result. Others users report the same problems with other USB equipment after the firmware update. By now I can live with the remote desktop (VNC).
The guiding goes fine for some minutes with captures from Nikon happening as expected.
After about 1 h the system becomes slower and depending on the demand the system ends up freezing (sometimes not).
The first day with PI4 I let the system guiding and acquiring frames for 2 hours without opening other programs or anything and noticed by the first time the system was slower.
The second day, noticed the same and found what was happening, the process indi_webcam_ccd was using more than 1 Gb of RAM after about 1 or 2 hours. Not a problem for PI4 but it clearly indicates the process is dealing with a task much bigger than necessary. In fact I noticed the guiding was not performing ok anymore. More frequent resets of the autoguiding position begun to occur.
Yesterday night I managed to accompany the problem occurring and saw as the amount of RAM used by indi_webcam grew with time.
The log from the session is attached as well as some screenshots showing the system monitor and the use of RAM climbing.

Is this a problem uniquely related to SPC900nc or is there any other users experiencing the same hunger for RAM by indi-webcam?
Thanks in advance for any help.


Tomasz, I tried phd2 but to no success. PHD2 refuses to connect to the indi v4l2 camera instance. The mount connects flawlessly. Can you send me prints of your indi configuration panels?
In the indi control panel I can stream the video from the camera but when I close that window and tell PHD2 to connect it fails.


I'll definitely try guiding with PHD2. Thank you for the idea.

Anyway, I keep puzzled about the fact that the camera's first test in ekos guiding module worked. The next night (three nights after), it stopped working. There was only one different thing I did: I connected my DSLR in INDI by the first time. When I tried to obtain a capture to test the connection (still using the INDI control panel controls), the capture went ok but the download of the frame crashed kstars. When I restarted kstars, I did not connected the DSLR anymore and tried guiding as three nights before but to no success as already mentioned. Maybe this crash had something to do with the webcam not guiding, maybe not. Already reinstalled kstars to no success. Maybe I did not removed some defective configuration file... I'll investigate more in the weekend and is nothing works, i'll go for PHD2.

Thanks again.


I plan to use webcam SPC900nc as a guide camera to a Az-Eq5 mount (EQmod) using Ekos internal guiding capabilities. Both devices were nicely configured and connected by INDI. From the INDI control panel in kstars, I can successfully stream video with the webcam but when I try to capture (Capture or Loop) a frame to choose the guiding star, Ekos/INDI fail in capturing the image.
The funnny thing is that 3 night before, when I first tried this, the guiding images appeared and I could even try some guiding.
I'm sending the prints of the INDI control panel (the relevant ones, I think) and the Ekos guiding panel.

Any help will be welcome.