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

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:

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

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.

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.

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

So the SV305 camera is MIA on your RPI as well. How does it find it then for KStars/Ekos?

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.

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?

In the lsusb output whre it says f266:9a0a
f266 is the Vendor ID (VID) which corresponds to CKcamera as the manufactuer of the device
9a0a is the Prodcut ID (PID) which corresponds to the SV305

The fact that there is no description showing simply means that the file that contains all the VID's and PIDs and their descriptions is missing the entry for f266:9a0a
It does not mean that the driver is missing.

From what I can see from that long device list, the SV305 is the only device listed that says "Driver=(none)" (second to last line for that device).

If you are using the same self-built driver as I am and you are using Astroberry/Stellarmate like I am, why is your setup working and mine isn't?

If you look at the contents of your /var/lib/usbutils/usb.ids file do you find either f266 or 9a0a?

I'm looking but I cannot find the command to update that file.
If I can make a guess. the Manufacturer sends the updated information to the repository at www.linux-usb.org/.

Regardless, that is a side issue.

Thanks.

It looks like Ekos is starting but the only problem is that it can't find the device.

Tryng to start indiserver manually gives an error.
I guess my driver is no good.
So I guess I just wasted 5 days of my time on this.
I guess I'll just have to wait for the official driver.
Thanks.

Hi folks,

I managed to get some time left to work on the driver again.

I Refreshed it with the last SVBony SDK, fixing (at least) two issues :
- armv6 support
- a buffered junk frame issue

<<
1. first time I connect it fails to, something about failed to set Gain.
>>

I informed SVBony about this issue. Still there...

<<
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.
>>

Should be fixed.

I can't help you for the RPi4 support. I only own RPi B+ and RPi 2.

You can build deb packages and share them for you tests.
Just use "make package" for libsv305 and indi-sv305, instead of "make install"

don't forget to use "sudo ldconfig" after the libsv305 install, to get the libraries up and indexed.

The driver works well on my amd64 and armv6 devices.

I just sent a pull request.

Best regards.

Blaise

your the driver failed to load as you did not install the libsv305, or installed it in your /usr/local/lib

there are several ways around it.

1.
2. run this to start your indiserveror
if that fails, go to your indi-3rdparty/libsv305 and do these