×

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

Bi-monthly release with minor bug fixes and improvements

Kstars on Rockpi works great except for Touptek Indi ccd driver.

  • Posts: 69
  • Thank you received: 5
Being experimenting with a Rockpi4b with M.2NVME memory. It works very fast with read/write speeds over 1.5GB/sec.  Running Twister OS which is based on Ubuntu.     KStars 3.5.4 works great as well except for one issue.

The only issue I have is trying to get my Toupcam (Touptek) ccd to work using Indi  as a guide cam in Ekos.  It just seems to be ignored. No errors just nothing.
All my other kit works fine in ekos.  ZWO cam and ZWO  EFW, Sesto Senso focusser, Mount all great.

I realise I am out on a bit of a limb here but anyone else using a Rockpi as their astro computer?
The extra speed and performance above the Raspberry Pi4 is so tempting.

For reference. I also have a Raspberry Pi 4 and everything works perfectly on that the Touptek is recognised and works.


 
Last edit: 2 years 8 months ago by David Thompson.
2 years 8 months ago #73434

Please Log in or Create an account to join the conversation.

USB issue? what does lsusb shows? dmesg perhaps when you plugin the camera?
2 years 8 months ago #73438

Please Log in or Create an account to join the conversation.

  • Posts: 69
  • Thank you received: 5
lsusb. shows the camera when it is attached.  See below. 

 



Kstars says unable to connect.


 

Not sure whats happening.

 
2 years 8 months ago #73446
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 69
  • Thank you received: 5
I have tried apt-get install trhe latest driver but it says its already installed.



This is the dmesg output showing the Toupcam is being recognised when connected.
I have reached the limit of my Linux skills.

Is there an easy way to see if I can get another application to use the camera?


pi@rockpi-4b:~$ sudo dmesg | grep usb
[ 0.000000] Kernel command line: root=UUID=f43869ab-391c-4c4b-98c0-2663c796d171 rootwait rootfstype=ext4 bootsplash.bootfile=bootsplash.armbian console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart= usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x1058:0x25a2:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[ 1.256435] usbcore: registered new interface driver usbfs
[ 1.256482] usbcore: registered new interface driver hub
[ 1.256531] usbcore: registered new device driver usb
[ 2.703561] ehci-platform fe380000.usb: EHCI Host Controller
[ 2.703589] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 1
[ 2.703746] ehci-platform fe380000.usb: irq 39, io mem 0xfe380000
[ 2.719508] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00
[ 2.719763] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.719774] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.719783] usb usb1: Product: EHCI Host Controller
[ 2.719792] usb usb1: Manufacturer: Linux 5.10.43-rockchip64 ehci_hcd
[ 2.719800] usb usb1: SerialNumber: fe380000.usb
[ 2.723270] ehci-platform fe3c0000.usb: EHCI Host Controller
[ 2.723294] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 2
[ 2.723432] ehci-platform fe3c0000.usb: irq 41, io mem 0xfe3c0000
[ 2.735507] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00
[ 2.735746] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.735756] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.735764] usb usb2: Product: EHCI Host Controller
[ 2.735773] usb usb2: Manufacturer: Linux 5.10.43-rockchip64 ehci_hcd
[ 2.735781] usb usb2: SerialNumber: fe3c0000.usb
[ 2.737572] ohci-platform fe3a0000.usb: Generic Platform OHCI controller
[ 2.737594] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 3
[ 2.737748] ohci-platform fe3a0000.usb: irq 40, io mem 0xfe3a0000
[ 2.799707] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[ 2.799718] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.799727] usb usb3: Product: Generic Platform OHCI controller
[ 2.799736] usb usb3: Manufacturer: Linux 5.10.43-rockchip64 ohci_hcd
[ 2.799744] usb usb3: SerialNumber: fe3a0000.usb
[ 2.801059] ohci-platform fe3e0000.usb: Generic Platform OHCI controller
[ 2.801081] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 4
[ 2.801210] ohci-platform fe3e0000.usb: irq 42, io mem 0xfe3e0000
[ 2.863706] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[ 2.863716] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.863726] usb usb4: Product: Generic Platform OHCI controller
[ 2.863734] usb usb4: Manufacturer: Linux 5.10.43-rockchip64 ohci_hcd
[ 2.863742] usb usb4: SerialNumber: fe3e0000.usb
[ 2.866513] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.866524] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.866533] usb usb5: Product: xHCI Host Controller
[ 2.866541] usb usb5: Manufacturer: Linux 5.10.43-rockchip64 xhci-hcd
[ 2.866550] usb usb5: SerialNumber: xhci-hcd.0.auto
[ 2.867645] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.867794] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[ 2.867804] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.867813] usb usb6: Product: xHCI Host Controller
[ 2.867821] usb usb6: Manufacturer: Linux 5.10.43-rockchip64 xhci-hcd
[ 2.867829] usb usb6: SerialNumber: xhci-hcd.0.auto
[ 2.869644] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.869654] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.869662] usb usb7: Product: xHCI Host Controller
[ 2.869671] usb usb7: Manufacturer: Linux 5.10.43-rockchip64 xhci-hcd
[ 2.869678] usb usb7: SerialNumber: xhci-hcd.1.auto
[ 2.870667] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.870826] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[ 2.870836] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.870844] usb usb8: Product: xHCI Host Controller
[ 2.870853] usb usb8: Manufacturer: Linux 5.10.43-rockchip64 xhci-hcd
[ 2.870861] usb usb8: SerialNumber: xhci-hcd.1.auto
[ 2.872119] usbcore: registered new interface driver usb-storage
[ 2.922748] usbcore: registered new interface driver usbhid
[ 2.922755] usbhid: USB HID core driver
[ 7.114319] usbcore: registered new interface driver brcmfmac
[ 138.316943] usb 2-1: new high-speed USB device number 2 using ehci-platform
[ 138.486495] usb 2-1: New USB device found, idVendor=0547, idProduct=b134, bcdDevice= 0.00
[ 138.486522] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 138.486538] usb 2-1: Product: USB2.0 Camera
[ 138.486554] usb 2-1: Manufacturer: TT
[ 236.120697] usb 2-1: USB disconnect, device number 2
[ 255.742759] usb 2-1: new high-speed USB device number 3 using ehci-platform
[ 256.219979] usb 2-1: New USB device found, idVendor=0547, idProduct=b134, bcdDevice= 0.00
[ 256.219993] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 256.219998] usb 2-1: Product: USB2.0 Camera
[ 256.220002] usb 2-1: Manufacturer: TT
[ 279.644461] usb 2-1: USB disconnect, device number 3
[ 295.190009] usb 2-1: new high-speed USB device number 4 using ehci-platform
[ 295.671048] usb 2-1: New USB device found, idVendor=0547, idProduct=b134, bcdDevice= 0.00
[ 295.671060] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 295.671066] usb 2-1: Product: USB2.0 Camera
[ 295.671070] usb 2-1: Manufacturer: TT
pi@rockpi-4b:~$
2 years 8 months ago #73493

Please Log in or Create an account to join the conversation.

  • Posts: 69
  • Thank you received: 5
The potential of the Rock Pi with M.2 NVME storage is what's driving me.

I decided to compare:-

Raspberry Pi 4 with USB3 attached SSD storage, Cost less than £100 all in including case.

with a

Rock Pi 4B with M.2. NVME storage cost around £130 all in.
(costs vary by country)

II have now given up on trying to use VNC over a WiFi connection to my Mac in the house as it is just so slow unless you are within a few feet of the internet router. Put a brick wall in the path and the speed just drops to unusable.

So I decided to fall back on ethernet with a Cat 5 cable to run the 40 Metres (131ft) from my warm study to the mount in the garden.


Transfer speeds for a 1GB test file between remote mount (40 Meters) and base iMac over ethernet

Raspberry Pi4 with very fast SD card .............. Forever! ( not worth doing)
Raspberry Pi4 with USB3 SSD........................... 6.9 MB/s. (Bytes not Bits)
Rock Pi4B with M.2 NVME storage.................... 11.1 MB/s

I was initially impressed with the Raspberry Pi results until I tried the Rock Pi with M.2 NVME.
Using VNC over an ethernet connection to the Rock Pi blows out my Windows laptop in performance!

BUT - there is an issue:-

My guide cam is a Toupcam and when I use Kstars/Ekos it works perfectly on my Raspberry Pi4 , as does everything else.

However, on the Rock Pi I have run into what I think is a USB problem in that the Toupcam is not connecting under Indi although everything else works under KStars/Ekos. ZWO camera and EFW. Mount and Sesto Sense focusser.

I don't have the Linux skills to compile the Indi drivers (don't know how to get them) from source on my Rock Pi but was hoping for some guidance/ suggestions.
2 years 8 months ago #73505

Please Log in or Create an account to join the conversation.

  • Posts: 69
  • Thank you received: 5
Trying to Compile Toupcam drivers from source for my Rock Pi 4B.

Initially successfully compiled the libtoupcam file and installed no errors.

Then tried to compile the indi-toupbase driver. Keep getting the same error.



pi@rockpi-4b:~/Projects/build/indi-toupbase$ cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi-3rdparty/indi-toupbase
-- 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
CMake Error at /home/pi/Projects/indi-3rdparty/cmake_modules/FindINDI.cmake:285 (message):
Could not find INDI include directory
Call Stack (most recent call first):
CMakeLists.txt:11 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/pi/Projects/build/indi-toupbase/CMakeFiles/CMakeOutput.log".


What am I doing wrong? What is the INDI include directory?
2 years 8 months ago #73531

Please Log in or Create an account to join the conversation.

  • Posts: 421
  • Thank you received: 102
Try
sudo apt install libindi-dev
The following user(s) said Thank You: David Thompson
2 years 8 months ago #73532

Please Log in or Create an account to join the conversation.

  • Posts: 69
  • Thank you received: 5
Thanks for info. Having installed libindi-dev the compilation of indi-toupbase succeeded.
Did the install but still cant get it to work in ekos. Get "unable to establish message"

Back to square one.
2 years 8 months ago #73534

Please Log in or Create an account to join the conversation.

  • Posts: 69
  • Thank you received: 5
Tried some more suggestions from the cloudy night forum.

Here are the results.

Tried my ZWO ASI290MC and it works fine in both USB3 port and USB2 port on RockPi.

Tried using a powered hub for the Toupcam same problem unable to establish connection.

Don't have any file similar to toupcam.rules in /etc/udev/rules.d. on my Rock Pi.

On my Raspberry Pi there is a file called 99-toupcam.rules so copied that across to Rock Pi and rebooted rock pi. Still same error.

Tried to follow the steps for using the other software but ran into errors on this step.

sudo apt-get install -y libgstreamer-plugins-base1.0-dev

it couldn't find some files that are needed.

So it kind of looks like it is an issue with toupcam driver and not the USB ports on the rock pi.

Will struggle on with the last step to try some other software.
Last edit: 2 years 8 months ago by David Thompson.
2 years 8 months ago #73559

Please Log in or Create an account to join the conversation.

  • Posts: 421
  • Thank you received: 102
So your post got me intrigued with the Rock Pi. I ordered one from Ali Express, with 16GB eMMC storage. It's a speedy little guy, that's for sure! At least, compared to a Raspberry Pi.

I spent some time and ported my Waveshare Stepper Motor HAT INDI driver to work on the Rock Pi 4B. That was pretty straightforward.

So I got everything built and installed, and everything works! At least for a few captures of the ASI 1600MM Pro. And then it stops working until I reboot. :(

dmesg shows a bunch of errors about "Ring expansion failed". Are you getting anything like that in your dmesg?

Apparently that's been fixed in the kernel 4 years ago! The Rock Pi people are using an ancient 4.4 kernel.

I'm going to try pestering them and see if they will at least apply the fix to the 4.4 kernel, if they won't update to a newer kernel.

Otherwise I may have to build a kernel from source, with the patch applied. Not my first choice, however.

-- Kevin
2 years 7 months ago #74085

Please Log in or Create an account to join the conversation.

  • Posts: 421
  • Thank you received: 102
I see you also have an ASI1600MM Pro. Are you able to take more than a handful of images with it? I just tell Ekos to loop images on the autofocus tab, and it starts failing after just a few images.
2 years 7 months ago #74086

Please Log in or Create an account to join the conversation.

  • Posts: 69
  • Thank you received: 5
I haven't had the chance to have a long go with the ASI1600 yet, I got bogged down trying to find a solution for the toupcam. Hope you find a way to get the latest kernal. I thought of trying to build one from source but it's beyond my Linux skills at the moment.
2 years 7 months ago #74090

Please Log in or Create an account to join the conversation.

Time to create page: 0.518 seconds