×

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

Bi-monthly release with minor bug fixes and improvements

Driver for old Meade DSi 1 Pro

  • Posts: 52
  • Thank you received: 0
I have installed " Mint distro", installed kstars,
installed MeadeDsi driver from indi lib/individual/devices/cameras,
restarted PC,
started kstarsekos,
entered meade dsi into profile and saved profile,
tried to connect,
2020-09-11T10:26:57: [INFO] Unable to find DSI. Has the firmware been loaded?
3 years 6 months ago #59730

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

  • Posts: 52
  • Thank you received: 0
removed kstars,
then installed using terminal:
sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding

Same result: 2020-09-11T10:45:05: [INFO] Unable to find DSI. Has the firmware been loaded?
3 years 6 months ago #59731

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

  • Posts: 52
  • Thank you received: 0
lsusb in terminal gives:

Bus 001 Device 013: ID 156c:0101
so does this mean linux sees the dsi but kstars does not?
3 years 6 months ago #59732

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

  • Posts: 153
  • Thank you received: 29
Hi Bruce,
These were all great debug steps.

The fact that you see "156c:0101" on the USB means that linux detects the DSI and loads the firmware properly. This is good.

I expect that they way you should be installing indi and the dsi driver is as follows:
sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding

Can you describe what you meant by this: " installed MeadeDsi driver from indi lib/individual/devices/cameras"? Are you manually building something? The indi-dsi driver will automatically be installed via the indi-full metapackage.

Thanks,
Ben
3 years 6 months ago #59739

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

  • Posts: 52
  • Thank you received: 0
Hi Ben,
I think i used that install method.
But,...can i run those commands again? ie. can i re install over the top of my existing kstars?
3 years 6 months ago #59767

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

  • Posts: 52
  • Thank you received: 0
"Can you describe what you meant by this: " installed MeadeDsi driver from indi lib/individual/devices/cameras"? Are you manually building something? The indi-dsi driver will automatically be installed via the indi-full metapackage."

After i install ktars bleeding edge, the meade dsi does not appear in the CCD dropdown list. i therefore install the driver(?) as stated above.

2020-09-12T00:19:40: [INFO] Unable to find DSI. Has the firmware been loaded?
(i have tried connecting the dsi on a friends linux pc running kstars and the same error is produced)

(Thanks Ben for your persistence.)
Last edit: 3 years 6 months ago by Bruce Nye.
3 years 6 months ago #59768

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

  • Posts: 52
  • Thank you received: 0
Hi Ben,
I have tried everything you have suggested and all i can think of doing, updates....upgrades....etc. etc...
and still the same issue persists.

020-09-12T00:42:12: [INFO] Unable to find DSI. Has the firmware been loaded?
i think kstars does not like my DSI. A shame as i reelly would like to get it working thru Kstars.
3 years 6 months ago #59770

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

  • Posts: 153
  • Thank you received: 29
Hi Bruce,

I re-read all of the posts scratching my head and notice that the error message that I was originally fixated on (driver crash) is no longer occurring. That's definitely an improvement.

The error message that you're seeing now is simpler to figure out, I think. What I would suggest doing is running lsusb, like you've already done before. You'll need to note the bus and device number of the DSI (it was bus 001 and device 013 when you did it earlier, but that will change as devices are plugged/unplugged). Once you have the bus and device number, run the following command:
ls -l /dev/bus/usb/BUS_NUMBER_HERE/DEVICE_NUMBER_HERE

Using the example that you posted earlier, it would've been
ls -l /dev/bus/usb/001/013

You'll see something like the following:
ben@vela:~$ ls -l /dev/bus/usb/001/002
crw-rw-r-- 1 root root 189, 1 Sep 10 20:29 /dev/bus/usb/001/002

This will show you the permissions for the DSI USB device.

Thanks,
Ben
3 years 6 months ago #59772

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

  • Posts: 52
  • Thank you received: 0
bruce@bruce-HP-ProBook-6460b:~$ lsusb
Bus 002 Device 003: ID 1bcf:2805 Sunplus Innovation Technology Inc.
Bus 002 Device 005: ID 156c:0101
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
bruce@bruce-HP-ProBook-6460b:~$ ls -l /dev/bus/usb/002/005
crw-rw-rw- 1 root root 189, 132 Sep 12 11:58 /dev/bus/usb/002/005
bruce@bruce-HP-ProBook-6460b:~$
3 years 6 months ago #59773

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

  • Posts: 153
  • Thank you received: 29
The permissions look good. Could you run:
touch /dev/bus/usb/002/005

and also:
fuser /dev/bus/usb/002/005

and:
dmesg | tail
3 years 6 months ago #59774

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

  • Posts: 52
  • Thank you received: 0
bruce@bruce-HP-ProBook-6460b:~$ touch /dev/bus/usb/002/005
bruce@bruce-HP-ProBook-6460b:~$ fuser /dev/bus/usb/002/005
bruce@bruce-HP-ProBook-6460b:~$ dmesg | tail
[ 1735.499809] usb 2-1.2: New USB device found, idVendor=156c, idProduct=0100, bcdDevice= 0.00
[ 1735.499816] usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1735.686670] usb 2-1.2: USB disconnect, device number 4
[ 1737.471170] usb 2-1.2: new high-speed USB device number 5 using ehci-pci
[ 1737.499728] usb 2-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[ 1737.499736] usb 2-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[ 1737.500429] usb 2-1.2: New USB device found, idVendor=156c, idProduct=0101, bcdDevice= 0.00
[ 1737.500435] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1737.500439] usb 2-1.2: Product: EZ-USB FX2
[ 1737.500443] usb 2-1.2: Manufacturer: Cypress
3 years 6 months ago #59775

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

  • Posts: 153
  • Thank you received: 29
Can you run this (close kstars/ekos first):

export LIBUSB_DEBUG=3
indiserver -v indi_dsi_ccd
3 years 6 months ago #59776

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

Time to create page: 0.442 seconds