×

INDI Library v1.9.8 Released (29 Sep 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Trouble with the EQ6R-Pro USB Port and EQMOD

  • Posts: 56
  • Thank you received: 7
Connection tab in indi-eqmod driver: Try baudrate: 115200
Edgar
1 year 11 months ago #64645

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

  • Posts: 20
  • Thank you received: 3
Hi Jürgen,

Any chance we could see the output of `dmesg` and `lsusb` from your astroberry? I'd be interested in knowing if you have the same serial controller I do.

I have a suspicion that there might have been a hardware change. Knowing what you have would answer that question.
1 year 11 months ago #64648

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

  • Posts: 20
  • Thank you received: 3
Hi Hades,

Unfortunately, I don't have a windows machine to test with. I'll try on my Mac later tonight.

I was pretty excited to have the USB port, and to get away from the EQMod cables. Thankfully they are still an option if I can't get the USB port working.
1 year 11 months ago #64649

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

  • Posts: 128
  • Thank you received: 11
Hi Androgena,
here you see the lsusb from my EQ6-R:


As already worte by Seescho it is important to set the Baud rate to 115200, otherwise ist doesn't work.

Once the mount is seen by EKOS I have the following informations in the INDI mount tab "firmware": Firmware 0307, mount code 0x23.

Do you have tryed another USB cable? Hope you get your mount working!

Best regards


Jürgen
1 year 11 months ago #64656
Attachments:

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

  • Posts: 128
  • Thank you received: 11
I just saw, that you already posted your lsusb... I try to get the detailed lsusb output after work, just copied the one line output after my photo session last night.

My EQ6-R has at least a different product ID.
1 year 11 months ago #64657

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

  • Posts: 20
  • Thank you received: 3
Hi Wouter,

I tried the scan ports button. Also went through the device mapping process on the port 8624 page. No luck with either.

It looks like my mount has a different serial controller than other known working mounts. Jürgen reports he has the Prolific 2303, where mine has the 23d3. His is a pretty standard TTY device. Mine shows up as a human input device,

www.prolific.com.tw/US/ShowProduct.aspx?pcid=41

I should reach out to SkyWatcher to see what they have to say.
1 year 11 months ago #64661

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

  • Posts: 20
  • Thank you received: 3
Thank you, Jürgen. I suspected that might be the case.

The EQMod cable still works in the hand controller port. I'll be okay if we can't figure this out. :)
Last edit: 1 year 11 months ago by Chris Barbour.
1 year 11 months ago #64662

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

  • Posts: 20
  • Thank you received: 3
Hi Edgar,

The mount doesn't even show up as a com port. Unfortunately, it's not the bitrate setting.
1 year 11 months ago #64663

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

  • Posts: 20
  • Thank you received: 3
One other possible lead... It looks like the version of the Kernel I'm running may not have a driver for this serial controller.

I found this document suggesting that 23d3 support was added in Linux 5.5

cateee.net/lkddb/web-lkddb/USB_SERIAL_PL2303.html

It looks like 4.4 is the latest Kernel available for Raspbian.

en.wikipedia.org/wiki/Raspberry_Pi_OS

I might try compiling a newer kernel. I'm not sure how much of a pain that's going to end up being, though.
The following user(s) said Thank You: Tim
1 year 11 months ago #64664

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

  • Posts: 964
  • Thank you received: 128
Yes, I was sort-of suspecting it's a HID. Seems to get more and more common, and I don't like it too much. It's asking for trouble when it comes to firmware upgrades. The ZWO EAF is also such a 'problem child'. FW update software only for windows, but contrary to standard COM/USB ports where you usually can run that software in wine, the HID support in wine is not up to that :( Not even vmware worked.

So I'm afraid you will need a dedicated driver to use that USB port.

Then again - isn't eqmod supposed to use the HC port anyhow, and USB only if used through the HC? What would be the advantage using that USB port?
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 year 11 months ago #64665

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

  • Posts: 1942
  • Thank you received: 418
How about backing up the SD card and installing Ubuntu 20.04 with KStars on it? May be easier than compiling your own kernel.
Wouter van Reeven

ASI6200MM and 7 slot 2" filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and 5 slot 1.25" filter wheel with an 8" TS Ritchey-Chrétien on a SkyWatcher EQ6-R
1 year 11 months ago #64666

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

  • Posts: 20
  • Thank you received: 3
I can confirm the mount works with the latest Kernel releases.
[ 1100.656675] usb 1-1.3: new full-speed USB device number 11 using xhci_hcd
[ 1100.793704] usb 1-1.3: New USB device found, idVendor=067b, idProduct=23d3, bcdDevice= 4.05
[ 1100.793727] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1100.793746] usb 1-1.3: Product: USB-Serial Controller
[ 1100.793764] usb 1-1.3: Manufacturer: Prolific Technology Inc.
[ 1100.793781] usb 1-1.3: SerialNumber: AECOb19B616
[ 1100.899680] usbcore: registered new interface driver pl2303
[ 1100.899719] usbserial: USB Serial support registered for pl2303
[ 1100.899793] pl2303 1-1.3:1.0: pl2303 converter detected
[ 1100.900470] usb 1-1.3: pl2303 converter now attached to ttyUSB0

Current versions of Stellarmate and Raspberry Pi OS require an unsupported kernel upgrade to make the mount work. I'm sure we can expect official support eventually, but this is a Raspbian thing, and not a Stellarmate thing.

This process worked for me: www.raspberrypi.org/documentation/raspbi...ations/rpi-update.md

Here's my release information:
stellarmate@stellarmate:~ $ uname -a
Linux stellarmate 5.10.0-v7l+ #1382 SMP Tue Dec 15 18:23:34 GMT 2020 armv7l GNU/Linux
 
stellarmate@stellarmate:~ $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

The port needs to be set to 115200 as per the other comments.

Here's the output of lsusb:
stellarmate@stellarmate:~ $ lsusb
 
Bus 002 Device 002: ID 0424:5807 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 011: ID 067b:23d3 Prolific Technology, Inc.
Bus 001 Device 006: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 005: ID 1546:01a7 U-Blox AG [u-blox 7]
Bus 001 Device 003: ID 0424:2807 Standard Microsystems Corp.
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 
stellarmate@stellarmate:~ $ lsusb -s 001:11 -v
 
Bus 001 Device 011: ID 067b:23d3 Prolific Technology, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x067b Prolific Technology, Inc.
  idProduct          0x23d3
  bcdDevice            4.05
  iManufacturer           1
  iProduct                2
  iSerial                 3
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0027
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a  1x 10 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
1 year 11 months ago #64667

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

Time to create page: 1.099 seconds