×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

INDI Driver for SVBONY cameras

  • Posts: 67
  • Thank you received: 0

Thanks for the info on the SV305 Pro.

I get "cmake command not found".
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58193
The topic has been locked.
  • Posts: 48
  • Thank you received: 0
Here is a crash course on how to build it.
github.com/thx8411/indi-3rdparty#install-pre-requisites

you need to run

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
3 years 7 months ago #58194
The topic has been locked.
  • Posts: 67
  • Thank you received: 0
Well, I tried your commands on NOOBS 32-bit and I made it almost all the way to the end but I got a CMake Error on cmake ../

Where do I go from here?

Your help is much appreciated. This isn't critical. The driver will be out sooner or later. I just wanted to try my hand at this.

OK. I think I fixed it. I needed to run...

sudo apt-get install libindi-dev

No CMake errors.

make -j4 worked.

Last line worked. (sudo make install</code>)

Great!

Now, which one is the driver? If I understand it correctly, it was installed?
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58196
Attachments:
The topic has been locked.
Is this driver ready to be merged to INDI 3rdparty repo? what's pending at this stage?
3 years 7 months ago #58209
The topic has been locked.
  • Posts: 10
  • Thank you received: 0
@Sarwar
Using your method, I used:
git clone github.com/thx8411/indi-3rdparty (*omitted "thx8841_sv305")
cd indi-3rdparty (*no "thx8841_sv305" dir to change to)
then, was able to successfully:
git checkout thx8411_sv305_2

then:
cd libsv305-build (*dir prev. created)
cmake ~/sv305project/indi-3rdparty/libsv305 (*seemed successful, no errors)
make (*seemed successful)
sudo make install (*seemed successful)

then:
cd indi-sv305-build (*dir prev. created)
cmake ~/sv305project/indi-3rdparty/indi-sv305 (*successful/no errors)
make (*partially successful? some repeating error types of the form: /usr/bin/ld: //usr/local/lib/libSVBCameraSDK.so: invalid string offset 3931 >= 552 for section `.strtab' ) *last printline following make command: " [100%] Built target indi_sv305_ccd "
sudo make install (*seemed successful, no errors)

At that point, i tried running indi from sudo per your comments, but got an error that driver wasn't found (no details as this was last night).
Today, brought up kstars/ekos/indi panel, but no (new) driver was available in the dropdown. Closed and tried running indi via sudo again, same error.
Should I be running a command to update my local ekos indi, or point it to the driver? Is there a step I've missed that involved moving the (newly built) driver into a space where local ekos/indi can find it?
(re: prereq's mentioned in a post here are installed)
thanks
3 years 7 months ago #58226
The topic has been locked.
  • Posts: 48
  • Thank you received: 0
I did not get those linking errors in your screenshot.

My sv305 is in the mail somewhere, ill try when I get it. Should be with me in a couple of days I guess.

Does indiserver indi_sv305_ccd work?
3 years 7 months ago #58228
The topic has been locked.
  • Posts: 8
  • Thank you received: 1
@MG!IFOS!
I just went through your steps and was able to successfully build both the library and driver.

Did you get all the prerequisites that Sarwar pointed out? Pretty sure you need:

sudo apt-get install libindi-dev

You also need to get these items (zlib and cfitsio ) from this README:

github.com/thx8411/indi-3rdparty/blob/master/indi-sv305/README

sudo apt-get install zlib1g

sudo apt install libcfitsio-dev


I had no build errors in either the cmake or make:

walt@rpi-indi:~/sv305-indi$ cmake ~/sv305/indi-3rdparty/indi-sv305
-- The CXX compiler identification is GNU 9.3.0
-- The C compiler identification is GNU 9.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found CFITSIO 3.47: /usr/lib/aarch64-linux-gnu/libcfitsio.so
-- Found INDI: /usr/lib/aarch64-linux-gnu/libindidriver.so;/usr/lib/aarch64-linux-gnu/libindiAlignmentDriver.so (found version "1.8.6")
-- Found ZLIB: /usr/lib/aarch64-linux-gnu/libz.so (found version "1.2.11")
-- Found SV305 libraries : /usr/local/lib/libSVBCameraSDK.so
-- Performing Test COMPATIBLE_FORTIFY_SOURCE
-- Performing Test COMPATIBLE_FORTIFY_SOURCE - Success
Linux target
-- Configuring done
-- Generating done
-- Build files have been written to: /home/walt/sv305-indi
walt@rpi-indi:~/sv305-indi$ make
Scanning dependencies of target indi_sv305_ccd
[ 50%] Building CXX object CMakeFiles/indi_sv305_ccd.dir/sv305_ccd.cpp.o
[100%] Linking CXX executable indi_sv305_ccd
[100%] Built target indi_sv305_ccd
3 years 7 months ago #58233
The topic has been locked.
  • Posts: 48
  • Thank you received: 0
Got the camera this morning.

Installing on Rpi4 went smoothly. installed in /usr/lib.

and did get the linking error. I believe it is related to the binary that is provided by the OEM for rpi4. a couple of observations may have already been reported:
1. first time I connect it fails to, something about failed to set Gain.
2. the driver only appears when the remote mode is selected. I am guessing this will be fixed when it is absorbed into the master repo.

I cannot test it with stars, as I am still waiting on my guide scope and there are no clear skies in the coming week. but it takes pictures just fine. Live video seems to be working as well
3 years 7 months ago #58245
The topic has been locked.
  • Posts: 67
  • Thank you received: 0

What was the name of the driver file and where did you put it?
My install placed it in /usr/local/bin and seems to be called indi_sv305_ccd.
OK Ekos was able to find it when I selected Remote Mode.
But now I'm getting an error on the Remote Server.
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58247
Attachments:
The topic has been locked.
  • Posts: 48
  • Thank you received: 0
I installed in /usr/bin. But i don't think it matters

You need to run indiserver indi_xxxxx on the terminal before connecting with remote on kstars

3 years 7 months ago #58288
The topic has been locked.
  • Posts: 67
  • Thank you received: 0

Which OS are your running on your RPi? I did mine with NOOBS (Raspbian I guess).
And as far as needing to run "indiserver indi_xxxxx", I thought that KStars/Ekos handled starting the server itself. What is the "xxxxx" for?

I typed in indi-web -v to start the server and I did get one error. Is that the wrong command?
Maybe my problem is that I'm running KStars 3.0.0 and my Windows 10 PC is running 3.4.3

I'm rusty on Linux and CL input. My Linux days were in the 90's.

I appreciate the help.
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58339
Attachments:
The topic has been locked.
  • Posts: 48
  • Thank you received: 0

i am on astroberry. much more straightforward to set up all the dependencies. but i reckon you would be fine setting it up on raspbian if you followed all the steps:
github.com/rkaczorek/astroberry-server
wget -O - https://www.astroberry.io/repo/key | sudo apt-key add -
sudo su -c "echo 'deb https://www.astroberry.io/repo/ buster main' > /etc/apt/sources.list.d/astroberry.list"
sudo apt update
sudo apt upgrade
sudo apt install astroberry-server-full 

My remote PC is on ubuntu 20.04. (i hate the concept of software for money - especially considering all the degradation on performance with usage and "spyware". ironic since i am a software/hardware engineer by day)

Also i donot use the astroberry hotspot but get the rpi to connect to the home network.

i am running a diy hardware for tracking and triggering my old nikon d7000, which does not have bulb mode, which requires me to set up parms prior to starting indi. so i donot use indi-web. i ssh into the rpi4, run the application to control my fpga over SPI and run:
indiserver indi_eqmod_telescope indi_nikon_cc indi_sv305_ccd

in the remote machine, i start kstar (v3.4.3), set it as remote, provide IP, select the drivers, i.e. Nikon DSLR, EqMod Mount, and SV350 CCD. Guiding as PHD2 and set the ip.

finally, open a browser, go to <IP_PI4>/desktop, login and start phd2.


EDIT: Just tested the indi-web-manager from my browser, and it works flawlessly too. after i start my diy software bits. considering i am runing modified indi_eqmod and indi_nikon, i am surprised
Last edit: 3 years 7 months ago by Rashed.
3 years 7 months ago #58343
The topic has been locked.
Time to create page: 0.860 seconds