There are now SDKs for all flavours , arm included.Yes, and I can see that includes all arm variants (armhf, armel, arm64).
Perhaps that's the better way indeed.
Read More...
As I said: "Because the only ARM images are for RPi, I had to do the git-clone procedure to to install INDI core, indi 3rd party libraries and third party drivers. It took a while but it's done"
Read More...
Hello, I'm new here, and a total INDI beginner.
I'm sorry to ask, but I've looked around and I've failed to find any documentation or forum posts to help me solve this issue.
My objective is simple: I have a Toupcam USB 2.0 camera (specifically: this one), and an OrangePI PC Plus, which is an SBC similar to an RPi 3. My hope is to be able to capture images from this camera. It's manufacturer only has official SDKs for x86, but I've read here that INDI does support them, so I decided to give it a try.
(Parenthesis: ¿Why an OrangePi PC+ instead of an RPi? Well this H3 board has the same 1G memory of an RPi 3 and the same CPU performance -benchmarked with 7z-, but the OPi is much more battery friendly drawing half the power (under 1000mA), and the eMMC memory is faster than SD cards which might help for my end purpose of platesolving)
Because the only ARM images are for RPi, I had to do the git-clone proecdure to to install INDI core, indi 3rd party libraries and third party drivers. It took a while but it's done.
My camera is plugged in an USB port, and dmesg shows:
[ 146.188881] usb 5-1: new high-speed USB device number 2 using ehci-platform
[ 146.645777] usb 5-1: New USB device found, idVendor=0547, idProduct=1005, bcdDevice= 0.00
[ 146.645804] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 146.645820] usb 5-1: Product: USB2.0 Camera
[ 146.645842] usb 5-1: Manufacturer: TTI installed XFCE and Kstars. When I launch Kstars, it seems to launch fine:
Qt: XKEYBOARD extension not present on the X server.
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-vnc'
org.kde.kstars: Welcome to KStars 3.0.0
org.kde.kstars: Build: 2018-12-21T13:43:03Z
org.kde.kstars: OS: "debian"
org.kde.kstars: API: "arm-little_endian-ilp32-eabi-hardfloat"
org.kde.kstars: Arch: "arm"
org.kde.kstars: Kernel Type: "linux"
org.kde.kstars: Kernel Version: "5.10.21-sunxi"
org.kde.kstars: Qt Version: 5.11.2
org.kde.kstars: Processing "unnamedstars.dat" , HTMesh Level 3
org.kde.kstars: Sky Mesh Size: 512
org.kde.kstars: Loaded DSO catalog file: "unnamedstars.dat"
org.kde.kstars: "Star HD20794 not found."
org.kde.kstars: "Star HD98230 not found."
File opened: "/usr/share/kstars/ngcic.dat"
org.kde.kstars: Loading NGC/IC objects
File opened: "/usr/share/kstars/comets.dat"
org.kde.kstars: "Object named Pluto not found"
org.kde.kstars: "Object named NGC 6050A not found"
org.kde.kstars: "Object named Pluto not found"
... it also complains about Ceres, Pallas, Vesta and many others....
org.kde.kstars: "Object named Halley (1982 HG1) not found"
Icon theme "breeze-dark" not found.
glibc >= 2.1 detected. Using GNU extension sincos()Then I click on Tools->Devices->Device Manager -> Local/Server -> CCDs, and I scroll the list to find "ToupCam", which I select.
Then In Mode I leave "local" selected (no idea what that does), and click on "Run Service"
Then a new window pops up titles "Indi Control Panel - KStars", and it has a single tab titled: "Toupcam GPCMOS01200KPC".
Behind the Indi Control Panel that popped up, the "Device Manager" window is still open, and it has accumulated the following in its log space:
2021-05-21T22:39:35: startup: /usr/bin/indiserver -v -p 7624 -f /tmp/indififo40a95507
2021-05-21T22:39:35: listening to port 7624 on fd 3
FIFO: start indi_toupcam_ccd
FIFO: Starting driver indi_toupcam_ccd
2021-05-21T22:39:35: Driver indi_toupcam_ccd: pid=22924 rfd=4 wfd=7 efd=8
2021-05-21T22:39:35: Client 5: new arrival from 127.0.0.1:34126 - welcome!
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on Focuser Simulator.FOCUS_TEMPERATURE
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on CCD Simulator.FILTER_SLOT
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on CCD Simulator.FILTER_NAME
2021-05-21T22:39:36: Driver indi_toupcam_ccd: snooping on SQM.SKY_QUALITYThen, back to the "Indi Control Panel" that popped, it has a "Connect" button. If I click on it, the following appears on it's log:
2021-05-21T22:44:05: [ERROR] Failed to start camera pull mode. Unspecified failure
2021-05-21T22:44:05: [INFO] Maximum gain considering dual gain is 22500.
2021-05-21T22:44:05: [INFO] Video Mode RGB detected.
2021-05-21T22:44:05: [INFO] Toupcam GPCMOS01200KPC is online. Retrieving basic data.Meanwhile, back in the "Device Manager" Window, the following lines are appended to the log area after clicking the button:
2021-05-21T22:44:05: Client 6: new arrival from 127.0.0.1:34130 - welcome!
2021-05-21T22:44:06: Client 6: read EOF
2021-05-21T22:44:06: Client 6: shut down complete - bye!And that's it. the camera doesn't connect/work.
Is there something that I can do? It works fine on Windows with SharpCap.
Read More...