Sorry to butt in.
but i did something similar last week and so started reading the thread. Interesting discussions.
Since you are using raspberry pi4, have you though about using astroberry-diy focuser? I have not used this module, but from what i can gather going over the code, if requires one to hook up a motor driver to the pi, and use the indi-astroberry-focuser to control it. This driver allows you to select which GPIOs the motor driver is connected to. so i imagine it is a matter of getting a DRV8834/DRV8834/A4988/A4988 and hocking up the cables properly.
I did it somewhat differently, in that I had the motor driver, drv8825 in my case, connected and fpga and connected that to the indi by using a indi_fpga_focuser derived from the above-mentioned indi module. Please see the screenshot.
"I should probably mention that I run Linux Ubuntu everywhere I can, including the Pi, laptop and desktops."
i wish more would ditch windows and apple for linux. it is so much better compared to 10/20 years ago.
thx8411 wrote: Hello,
Thanks for your help Sarwar. I didn't notice this behavior.
It's great !
I will look deeply at your patch and do some testing this week-end.
Does it work for all targets (amd64, arm, etc.) ?
yes, i have it running.
you would need to recompile the code. if you are unsure how to do it, i recommend doing it manually for the time being - till they update the indi repository.
Whilst the OEM is working on their SDK, this workaround may be useful to mitigate the issue:
dlwmacgregor wrote: Interesting.
I'm using a Raspberry Pi 4B with the latest release of Astroberry.
All other settings have no errors.
Yes. multiple power resets of both camera and Pi.
Probably best to wait until SVBONY replies to thx_8411.
Sarwar wrote: Gain control works just fine.. probably just needs a few millisecond of sleep. I say so because it happens only when the camera is connected for the first time, i.e. from a power cycle or powering it up for the first time.
diff --git a/indi-sv305/sv305_ccd.cpp b/indi-sv305/sv305_ccd.cpp index 457db530..fd51d4d9 100644 --- a/indi-sv305/sv305_ccd.cpp +++ b/indi-sv305/sv305_ccd.cpp @@ -340,6 +340,7 @@ bool Sv305CCD::Connect() pthread_mutex_unlock(&cameraID_mutex); return false; } + usleep(0.1 * 1e6); // get camera properties status = SVBGetCameraProperty(cameraID, &cameraProperty);
Gain control works just fine.. probably just needs a few millisecond of sleep.
without knowing which version of indi-sv305 is installed in your system, it will not be easy to say. What we can do is do a reinstall of sv305 and take it from there.
can you check what you see when you run this command
also do this:
sudo apt install cmake-gui
I am hoping you will see something like what you see in the attached screenshot, if not type them in, click Tools > Configure
sorry my mistake, you did install it after i told you. Apologies
it seems you have not installed indiserver, can you confirm indiserver is installed?
what is stellamate? does it come with indi-dev stuff? Why are you not using astroberry?
sudo apt install indi-full
if you started a fresh, you need to run the apt again.
I though you already install this
sudo apt-get -y install libnova-dev libcfitsio-dev libusb-1.0-0-dev zlib1g-dev libgsl-dev build-essential cmake git libjpeg-dev libcurl4-gnutls-dev libtiff-dev libfftw3-dev libftdi-dev libgps-dev libraw-dev libdc1394-22-dev libgphoto2-dev libboost-dev libboost-regex-dev librtlsdr-dev liblimesuite-dev libftdi1-dev libavcodec-dev libavdevice-dev
if it does not work, give a screenshot of the output after running the above command.
once done, go to
rm build -r
cmake ../ -DCMAKE_INSTALL_PREFIX=/usr
sudo make install
sudo apt update sudo apt install git git init git clone https://github.com/thx8411/indi-3rdparty thx8841_sv305 cd thx8841_sv305 git checkout thx8411_sv305_2 cd libsv305/ mkdir build cd build cmake ../ -DCMAKE_INSTALL_PREFIX=/usr make sudo make install sudo ldconfig
cd ../../indi-sv305/ mkdir build cd build cmake ../ -DCMAKE_INSTALL_PREFIX=/usr make sudo make install sudo ldconfig
left tje sv305 guiding in the backyard. getting 15-minute subs on a DIY tracker on EQ5+72ED. pretty cool. RMS of 0.41
had a little issue with the sv305. about 250 hot pixels and sensitivity is not awsome. only found 3 usable stars whilst pointing at north american nebula - that should have been an easy target. however, using 4x4 binning improved things massively. settled on 2x2 bin in the end. will try pointing it towards something mire near the horizon and outside the milky way region to see how well it works.
I am testing the sv305 now, so may not be prompt.
no it does not mean that, it just means in the most likely case, that /usr/local/lib is not one of the places that is listed in the LD_LIBRARY_PATH. so you can use one of the three solutions i posted to solve it.