×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Unable to connect

  • Posts: 6
  • Thank you received: 0

Unable to connect was created by dario

Hi everybody.
I was trying to use Indi-kstars with my eq6 with eqmod and a notebook.
If I connect eqmod via usb it goes well. The second peripherical I try to connect whatever it is, isn't recognized.
I think the problem could be that a notebook usually have 3 or 4 usb ports but only a bus...
I tried with a usb hub...same result.

Does Anybody know a way to use notebooks?

Best regards
Dario
3 years 9 months ago #56299

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

  • Posts: 315
  • Thank you received: 42

Replied by wotalota on topic Unable to connect

Dario,
You should provide more information. What operating system and version, the version of KStars. What is the second peripheral and to which USB port is it connected. Is there a corresponding INDI driver loaded and if so which port is it using. Then someone familiar with the operating system might be able to make a suggestions.
3 years 9 months ago #56325

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

  • Posts: 6
  • Thank you received: 0

Replied by dario on topic Unable to connect

Hi and Thanks.
well... eq6 with eqmod via usb
Qhy8l ccd via usb
Lodestar to guide via usb
Focuser via usb
Pc has Ubuntu 20.04 and 3 usb.
I used a desktop computer before without any problems...Now the desktop has died...So I tried to use a notebook.
On the notebook Eqmod is on usb0 and it works well.
If I connect the hub on another usb port kstars and Ekos give me an error message because they find no port....

I have loaded drivers for eqmod, cameras and focuser. I found them on Indi site.

Best regards
Dario
I use an usb Hub connected to DC for the cameras
3 years 9 months ago #56326

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

  • Posts: 315
  • Thank you received: 42

Replied by wotalota on topic Unable to connect

would start off with just the eq6 and qhy connected directly to usb slots without the hub, can you establish the qhy connection that way.
If not what does the indi control panel for the qhy look like, do you have some of the tabs showing?
If qhy is connected then connect and disconnect the hub to the other usb port can you identify it coming and going using the lsusb command.
If the hub show up try connecting the focuser to it and using lsusb or listing the /dev dir see if you can establish the port number it is using.
Last edit: 3 years 9 months ago by wotalota.
3 years 9 months ago #56343
Attachments:

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

  • Posts: 6
  • Thank you received: 0

Replied by dario on topic Unable to connect

Thanks for the answer.
I connect the eq6 and it works. When I connect the qhy (or the lodestar) to another usb port kstar panel says unable to find free port....but I have 2 ports still free....
3 years 9 months ago #56346

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

  • Posts: 1957
  • Thank you received: 420

Replied by Wouter van Reeven on topic Unable to connect

Dario,

Can you please try the following: open a command line terminal without any of your equipment attached and without KStars started and type

dmesg -w

You will see a lot of info scroll by which are the kernel messages of Linux that you can ignore. Once it has stopped scrolling it will wait for more kernel messages to appear (which is what the -w switch does) so please plug in the eqmod cable. You will see a few messages appear. Then please plug in the qhy camera. Copy and paste the messages that have appeared in your terminal when you plugged in the eqmod and the qhy in the forum here. This will allow us to help you resolve your issue.

By the way, press CTRL-C to exit dmesg and then simply type exit to quit the command line terminal.


Wouter
3 years 9 months ago #56347

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

  • Posts: 6
  • Thank you received: 0

Replied by dario on topic Unable to connect

Thanks,
ASAP I will do it. Maybe it will take some days because the dome it's far from my home....

Best regards
Dario
3 years 9 months ago #56354

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

  • Posts: 315
  • Thank you received: 42

Replied by wotalota on topic Unable to connect

In the meantime if your notebook is local and you have some device that works in usb slot 0. Considering all usb ports are the same usb2/3. Confirm the usb 1 and 2 are working at the OS level without INDI by using the same device in those slots. If they do not work, boot into the UEFI or BIOS and look for USB related configuration options that might enable them. A stellamate or Raspberry pi 4 would look nice in a dome.
3 years 9 months ago #56361

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

  • Posts: 6
  • Thank you received: 0

Replied by dario on topic Unable to connect

Hi everybody,
I'm not in dome these days so I tried dmesg -w command using a smathphone, a mouse and a mass storage hdd. Aybe it won't be the same ...but the notebook recognize every periphericals. During the week I will try with the scope and the ccd.
Do you think that the hub could be difficult to recognize by kstars and ekos?

[ 1844.977406] logitech-hidpp-device 0003:046D:4054.0003: HID++ 4.5 device connected.
[ 2097.451310] usb 2-3: new full-speed USB device number 3 using xhci_hcd
[ 2097.651004] usb 2-3: New USB device found, idVendor=04d8, idProduct=fc8c, bcdDevice= 0.01
[ 2097.651009] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2097.651012] usb 2-3: Product: USB nFOCUS v1.0 RigelSys
[ 2097.651015] usb 2-3: Manufacturer: Astrogene1000_stuff
[ 2097.651016] usb 2-3: SerialNumber: 000000003D
[ 2097.695856] cdc_acm 2-3:1.0: ttyACM0: USB ACM device
[ 2097.700473] usbcore: registered new interface driver cdc_acm
[ 2097.700475] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2541.329211] usb 2-3: USB disconnect, device number 3
[ 2559.915340] usb 2-3: new high-speed USB device number 4 using xhci_hcd
[ 2559.938067] usb 2-3: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 2559.938073] usb 2-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2559.938076] usb 2-3: Product: USB 2.0 Hub
[ 2559.942554] hub 2-3:1.0: USB hub found
[ 2559.942931] hub 2-3:1.0: 4 ports detected
[ 2560.351296] usb 2-3.4: new full-speed USB device number 5 using xhci_hcd
[ 2560.591698] usb 2-3.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 2560.591702] usb 2-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2560.591705] usb 2-3.4: Product: TTL232R-5V
[ 2560.591706] usb 2-3.4: Manufacturer: FTDI
[ 2560.591708] usb 2-3.4: SerialNumber: AH01DEVI
[ 2560.629125] usbcore: registered new interface driver usbserial_generic
[ 2560.630032] usbserial: USB Serial support registered for generic
[ 2560.634673] usbcore: registered new interface driver ftdi_sio
[ 2560.635604] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 2560.635954] ftdi_sio 2-3.4:1.0: FTDI USB Serial Device converter detected
[ 2560.636208] usb 2-3.4: Detected FT232RL
[ 2560.638604] usb 2-3.4: FTDI USB Serial Device converter now attached to ttyUSB0
[ 3364.605496] usb 1-1.1: USB disconnect, device number 3
[ 3369.439278] usb 1-1.1: new high-speed USB device number 5 using ehci-pci
[ 3369.467845] usb 1-1.1: New USB device found, idVendor=1618, idProduct=6004, bcdDevice= 0.00
[ 3369.467871] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3370.236872] usb 1-1.1: USB disconnect, device number 5
[ 3371.995104] usb 1-1.1: new high-speed USB device number 6 using ehci-pci
[ 3372.024130] usb 1-1.1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[ 3372.024135] usb 1-1.1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[ 3372.024877] usb 1-1.1: New USB device found, idVendor=1618, idProduct=6005, bcdDevice= 0.00
[ 3372.024880] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3372.024883] usb 1-1.1: Product: QHY-8L
[ 3372.024884] usb 1-1.1: Manufacturer: QHY-CCD
[ 3486.479508] ACPI Error: No handler for Region [RCM0] (00000000c67a53ed) [SystemCMOS] (20190703/evregion-132)
[ 3486.479523] ACPI Error: Region SystemCMOS (ID=5) has no handler (20190703/exfldio-265)
[ 3486.479538] No Local Variables are initialized for Method [ESDT]
[ 3486.479541] No Arguments are initialized for method [ESDT]
[ 3486.479545] ACPI Error: Aborting method \_SB.WMID.ESDT due to previous error (AE_NOT_EXIST) (20190703/psparse-531)
[ 3486.479559] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190703/psparse-531)
[ 3511.034263] PM: suspend entry (deep)
[ 3511.039531] Filesystems sync: 0.005 seconds
[ 3511.039869] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 3511.042134] OOM killer disabled.
[ 3511.042135] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 3511.043629] printk: Suspending console(s) (use no_console_suspend to debug)
[ 3511.063344] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 3511.064241] sd 0:0:0:0: [sda] Stopping disk
[ 3511.192155] ACPI: EC: interrupt blocked
[ 3511.231349] ACPI: Preparing to enter system sleep state S3
[ 3511.234282] ACPI: EC: event blocked
[ 3511.234283] ACPI: EC: EC stopped
[ 3511.234284] PM: Saving platform NVS memory
[ 3511.234350] Disabling non-boot CPUs ...
[ 3511.234703] IRQ 28: no longer affine to CPU1
[ 3511.234712] IRQ 35: no longer affine to CPU1
[ 3511.234715] IRQ 36: no longer affine to CPU1
[ 3511.235816] smpboot: CPU 1 is now offline
[ 3511.236555] ACPI: Low-level resume complete
[ 3511.236602] ACPI: EC: EC started
[ 3511.236603] PM: Restoring platform NVS memory
[ 3511.236681] LVT offset 0 assigned for vector 0x400
[ 3511.236963] Enabling non-boot CPUs ...
[ 3511.237030] x86: Booting SMP configuration:
[ 3511.237030] smpboot: Booting Node 0 Processor 1 APIC 0x11
[ 3511.237217] microcode: CPU1: patch_level=0x06006705
[ 3511.239764] CPU1 is up
[ 3511.240146] ACPI: Waking up from system sleep state S3
[ 3511.269916] ACPI: EC: interrupt unblocked
[ 3511.308565] ACPI: EC: event unblocked
[ 3511.309190] [drm] PCIE GART of 1024M enabled (table at 0x000000F400000000).
[ 3511.309205] smu version 26.17.00
[ 3511.333415] sd 0:0:0:0: [sda] Starting disk
[ 3511.364902] [drm] UVD initialized successfully.
[ 3511.465135] [drm] VCE initialized successfully.
[ 3511.551915] usb 1-1.4: reset full-speed USB device number 4 using ehci-pci
[ 3512.035896] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 3512.035919] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 3512.039152] ata1.00: configured for UDMA/100
[ 3512.043936] ata2.00: configured for UDMA/133
[ 3512.180578] psmouse serio1: synaptics: queried max coordinates: x [..5648], y [..4826]
[ 3512.210989] psmouse serio1: synaptics: queried min coordinates: x [1292..], y [1026..]
[ 3514.238165] acpi LNXPOWER:05: Turning OFF
[ 3514.238279] OOM killer enabled.
[ 3514.238279] Restarting tasks ...
[ 3514.244771] usb 2-3: USB disconnect, device number 4
[ 3514.244778] usb 2-3.4: USB disconnect, device number 5
[ 3514.253895] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 3514.253928] ftdi_sio 2-3.4:1.0: device disconnected
[ 3514.256864] usb 1-1.1: USB disconnect, device number 6
[ 3514.263305] done.
[ 3514.276739] Bluetooth: hci0: RTL: rtl: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821

[ 3514.278611] Bluetooth: hci0: RTL: rom_version status=0 version=1

[ 3514.278615] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8821c_fw.bin

[ 3514.278640] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8821c_config.bin

[ 3514.278662] Bluetooth: hci0: RTL: cfg_sz 10, total sz 21678

[ 3514.304432] PM: suspend exit
[ 3514.335753] usb 1-1.1: new full-speed USB device number 7 using ehci-pci
[ 3514.447342] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
[ 3514.447346] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3514.447347] usb 1-1.1: Product: USB Receiver
[ 3514.447349] usb 1-1.1: Manufacturer: Logitech
[ 3514.452354] logitech-djreceiver 0003:046D:C534.0004: hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:12.0-1.1/input0
[ 3514.514324] Generic Realtek PHY r8169-200:00: attached PHY driver [Generic Realtek PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
[ 3514.521484] logitech-djreceiver 0003:046D:C534.0005: hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:12.0-1.1/input1
[ 3514.581947] logitech-djreceiver 0003:046D:C534.0005: device of type eQUAD nano Lite (0x0a) connected on slot 2
[ 3514.592028] input: Logitech Wireless Mouse as /devices/pci0000:00/0000:00:12.0/usb1/1-1/1-1.1/1-1.1:1.1/0003:046D:C534.0005/0003:046D:4054.0006/input/input24
[ 3514.592309] logitech-hidpp-device 0003:046D:4054.0006: input,hidraw2: USB HID v1.11 Mouse [Logitech Wireless Mouse] on usb-0000:00:12.0-1.1/input1:2
[ 3514.626011] r8169 0000:02:00.0 enp2s0: Link is Down
[ 3515.249895] logitech-hidpp-device 0003:046D:4054.0006: HID++ 4.5 device connected.
[ 3516.824104] ACPI Error: No handler for Region [RCM0] (00000000c67a53ed) [SystemCMOS] (20190703/evregion-132)
[ 3516.824118] ACPI Error: Region SystemCMOS (ID=5) has no handler (20190703/exfldio-265)
[ 3516.824130] No Local Variables are initialized for Method [ESDT]
[ 3516.824132] No Arguments are initialized for method [ESDT]
[ 3516.824135] ACPI Error: Aborting method \_SB.WMID.ESDT due to previous error (AE_NOT_EXIST) (20190703/psparse-531)
[ 3516.824146] ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to previous error (AE_NOT_EXIST) (20190703/psparse-531)
[ 3519.778319] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[ 3755.998077] audit: type=1400 audit(1593951407.121:49): apparmor="DENIED" operation="open" profile="snap.canonical-livepatch.canonical-livepatch" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=3299 comm="canonical-livep" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 3756.105748] audit: type=1400 audit(1593951407.229:50): apparmor="DENIED" operation="open" profile="snap.canonical-livepatch.canonical-livepatch" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=3343 comm="canonical-livep" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 3756.207529] audit: type=1400 audit(1593951407.329:51): apparmor="DENIED" operation="open" profile="snap.canonical-livepatch.canonical-livepatch" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=3388 comm="canonical-livep" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 3756.303826] audit: type=1400 audit(1593951407.425:52): apparmor="DENIED" operation="open" profile="snap.canonical-livepatch.canonical-livepatch" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=3432 comm="canonical-livep" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 3793.296933] usb 3-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 3793.320774] usb 3-2: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
[ 3793.320780] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3793.320783] usb 3-2: Product: DataTraveler 3.0
[ 3793.320786] usb 3-2: Manufacturer: Kingston
[ 3793.320788] usb 3-2: SerialNumber: 60A44C3FAC2DE391E914113D
[ 3793.357807] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 3793.364532] scsi host2: usb-storage 3-2:1.0
[ 3793.364694] usbcore: registered new interface driver usb-storage
[ 3793.367942] usbcore: registered new interface driver uas
[ 3794.373784] scsi 2:0:0:0: Direct-Access Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
[ 3794.374481] sd 2:0:0:0: [sdb] 121110528 512-byte logical blocks: (62.0 GB/57.8 GiB)
[ 3794.374743] sd 2:0:0:0: [sdb] Write Protect is off
[ 3794.374748] sd 2:0:0:0: [sdb] Mode Sense: 45 00 00 00
[ 3794.375791] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 3794.376394] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3794.558578] sdb: sdb1
[ 3794.560086] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 3817.374023] usb 2-3: new high-speed USB device number 6 using xhci_hcd
[ 3817.403798] usb 2-3: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 4.14
[ 3817.403804] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3817.403807] usb 2-3: Product: Mi Note 10 Pro
[ 3817.403809] usb 2-3: Manufacturer:
[ 3817.403811] usb 2-3: SerialNumber: dfhsfgsyj
3 years 9 months ago #56455

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

  • Posts: 6
  • Thank you received: 0

Replied by dario on topic Unable to connect

I found a problem. One of the three usb ports doesn't mount anything i connect to it. It works because If I connect the smarphone it charge itself.
Any suggestions?
3 years 9 months ago #56519

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

Time to create page: 1.225 seconds