×

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: 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.
  • Posts: 67
  • Thank you received: 0

I have 4 distros I'm using on separate SD cards...

NOOBS Raspbian
Astroberry (KStars 3.4.2 included)
Stellarmate OS
Raspbian 64-bit Beta

I don't use the Hot Spot either. I connect VNC thru my wireless router.

It looks like booting into AstroBerry starts the INDI Server automatically.

It doesn't see the camera when I start Ekos.

The Status Box at the bottom shows the following...

<strong>2020-08-18T08:05:38 Unable to establish remote device:
+ SV305 CCD
Please ensure remote device name corresponds to actual device name.
2020-08-18T08:05:24 INDI services started. Connection to remote INDI server is successful. Waiting for devices...
2020-08-18T08:05:24 Connecting to remote INDI server at localhost on port 7624 ...
2020-08-18T08:05:24 Warning: INDI Web Manager is not online.
2020-08-18T08:05:20 Establishing communication with remote INDI Web Manager...
</strong>

The camera is plugged into one of the RPi USB 2.0 ports.

lsusb shows an empty slot.

I'm controlling my NexStar SE8 GoTo mount with the RPi plugged into the Hand Controller via USB and ser2net software on the RPi and SkyQLinkPC software on the PC.
Works perfectly with Stellarium PC.

Thanks.
Last edit: 3 years 7 months ago by Doug MacGregor. Reason: Added an attachment
3 years 7 months ago #58352
The topic has been locked.
  • Posts: 67
  • Thank you received: 0
Just out of curiosity what does your "lsusb" show?

What I find strange is that when booted into StellarMate OS the Control Panel app shows in the following attachment...

I also noticed that the Windows driver file is called CkCameraDevice64.sys

Now maybe the name of the Linux driver doesn't matter but that Status Output from Ekos saying...

"Please ensure remote device name corresponds to actual device name"

refers to the actual device name as CkCamera.

I don't know if that means anything.
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58356
Attachments:
The topic has been locked.
  • Posts: 8
  • Thank you received: 1
This is the camera plugged into my Ubuntu laptop:

Bus 002 Device 002: ID 0bda:57d6 Realtek Semiconductor Corp. HP Truevision HD
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 005: ID f266:9a0a CKCamera CKCamera
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is plugged into the RPI Ubuntu Mate x64:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 007: ID f266:9a0a
Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
3 years 7 months ago #58358
The topic has been locked.
  • Posts: 67
  • Thank you received: 0

So the SV305 camera is MIA on your RPI as well. How does it find it then for KStars/Ekos?
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58361
The topic has been locked.
  • Posts: 8
  • Thank you received: 1
It is there, it is just not named. If you read through this thread kengs said "That's not a big issue. There is a file that translates the USB VID/PID to a description. That file needs to be updated.
wiki.debian.org/HowToIdentifyADevice/USB".

So it really has nothing to do with the driver or the library finding the camera.

Are you still having an issue? What os flavor are you using? I was able to get it going on Ubuntu mate x64. You may need to do a fresh os and start over.
3 years 7 months ago #58364
The topic has been locked.
  • Posts: 67
  • Thank you received: 0

I am trying to run it on a fresh download of Stellarmate 1.5.3 and/or a fresh download of AstroBerry.
I don't know specifically which OS/version they use but I am assuming they are both Raspbian or something similar.
What are you running on your RPi?
Are you saying that you are running Ububtu mate on an x64 conputer?
If you are, I have no problems running the SV305 on my Windows 7 laptop.

Could you please verify the size of your indi_sv305_ccd driver file compared to mine?
If it's different would you be willing to e-mail me a copy of your driver file?
You lost me a bit with the VID/PID stuff.
I did a listing if the /sys/kernel/debug/usb/devices file and the Manufacturer=CKCamera and the Product=CKCamera. (4th group down).
So you are saying that these names don't matter OR is that the file that needs to be updated?
Last edit: 3 years 7 months ago by Doug MacGregor.
3 years 7 months ago #58371
Attachments:
The topic has been locked.
Time to create page: 0.734 seconds