×

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

Bi-monthly release with minor bug fixes and improvements

Stellarmate 1.7 Beta

  • Posts: 245
  • Thank you received: 56
I thought it maybe better to have a channel for Beta testing (or is there already one?) questions.
I have setup my gear with 1.7 and everything works (QHY, GEM45, SestoSenso, UPB) except my ZWO guide Cam.
I get "Unable to establish: ZWO CCD"
It shows up in the Stellarmate Dashboard under hardware correctly:

Is there a know issue with ZWO on the beta?
Just found the JSON option so added that. 
 

File Attachment:

File Name: ZWO.txt
File Size:1 KB
Last edit: 2 years 2 months ago by Rishi Garrod.
2 years 2 months ago #79494
Attachments:

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

  • Posts: 20
  • Thank you received: 1

Replied by Kemal YILDIRIM on topic Stellarmate 1.7 Beta

I've tested ZWO 178MC with no issue at all.
better to check USB 3.0 port and cable.
I am not using the stock ribbon cable, too long and not looking good for USB 3.0 transfer.
2 years 2 months ago #79698

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

  • Posts: 245
  • Thank you received: 56

Replied by Rishi Garrod on topic Stellarmate 1.7 Beta

I was running the most up to date code that was published on Sunday. When I swapped back to my 1.6.1 boot the camera works fine. Nothings changed in my setup only the version of software I was running. I have seen a number of updates in the meantime. When the weather clears up I will try again.

Those ZWO ribbon cables really are the pits. I use short quality cables.
Last edit: 2 years 2 months ago by Rishi Garrod.
2 years 2 months ago #79699

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

Replied by Jasem Mutlaq on topic Stellarmate 1.7 Beta

Kemal, are you using the ZWO on the 1.7.0 Beta?
2 years 2 months ago #79719

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

  • Posts: 245
  • Thank you received: 56

Replied by Rishi Garrod on topic Stellarmate 1.7 Beta

I just tried again with all the latest updates. Everything start except the ZWO 174 guide camera.
With 1.6.1 on the identical setup it works fine.
2 years 2 months ago #79723

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

  • Posts: 245
  • Thank you received: 56

Replied by Rishi Garrod on topic Stellarmate 1.7 Beta

So I just connect my ZWO 294MC Pro and it was recognised so it seems it is not all ZWO just my 174 guidecam.
I will now try some different cables and USB ports on the 174.
2 years 2 months ago #79724

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

Replied by Jasem Mutlaq on topic Stellarmate 1.7 Beta

I just tested with ASI178MC-Cool on the 64bit OS and it worked right away

2 years 2 months ago #79725
Attachments:

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

  • Posts: 245
  • Thank you received: 56

Replied by Rishi Garrod on topic Stellarmate 1.7 Beta

It's odd that it shows up on the Hardware tab on the Stellarmate dashboard.

I have tried different cables and different USB ports.

I checked lsusb first as "stellarmate" and then with sudo. Maybe this is normal?

stellarmate@stellarmate:~ $ lsusb
Bus 002 Device 003: ID 174c:1156 ASMedia Technology Inc. Forty
Bus 002 Device 005: ID 03c3:294f ZWO ASI294MC Pro
Bus 002 Device 002: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
stellarmate@stellarmate:~ $ sudo lsusb
Bus 002 Device 003: ID 174c:1156 ASMedia Technology Inc. Forty
Bus 002 Device 005: ID 03c3:294f ZWO ASI294MC Pro
Bus 002 Device 002: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 012: ID 03c3:1749 ZWO ASI174MM Mini
Bus 001 Device 010: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 009: ID 1233:1455 Denver Electronics iOptron iPolar
Bus 001 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 011: ID 04b4:6572 Cypress Semiconductor Corp. Unprogrammed CY7C65642 hub
Bus 001 Device 004: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 001 Device 003: ID 0424:2807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Could it be a permission issue?

Here is the verbose version:
Bus 001 Device 012: ID 03c3:1749 ZWO ASI174MM Mini
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x03c3 
  idProduct          0x1749 
  bcdDevice            0.00
  iManufacturer           1 ZWO
  iProduct                2 ASI174MM Mini
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0019
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              300mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)

 
Last edit: 2 years 2 months ago by Rishi Garrod.
2 years 2 months ago #79726

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

  • Posts: 20
  • Thank you received: 1

Replied by Kemal YILDIRIM on topic Stellarmate 1.7 Beta

Hi Jasem,
Yes I am using SM1.7
I have ZWO ASI178MC  and ASI120MM-S
both are working fine.

Dolookup and clear skies,
Kemal
2 years 2 months ago #79727

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

  • Posts: 245
  • Thank you received: 56

Replied by Rishi Garrod on topic Stellarmate 1.7 Beta

It is some sort of USB issue. I brought everything inside to start a real debug session, plugged the 174 directly into the Rpi and it works!
On 1.6.1 32 bit I have the camera attached to the hub in my mount (which is attached to the Pegasus UPB v2) and it has always worked fine.
On 1.7.0 64 bit I had also tried plugging it into my Pegasus UPB v2 but that didn't work either.
2 years 2 months ago #79728

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

  • Posts: 60
  • Thank you received: 2
Zwo asi 294mc pro  is recognised and works
2 years 2 months ago #79730

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

  • Posts: 48
  • Thank you received: 3
Hi,

I am also on the 1.7 beta.

I have no issues with the 1.7 beta when I image it. ZWO camera's work fine.

But as soon as I update the image my camera's keep crashing ZWO1600/294mc and it keeps reloading the asi driver.

I don't know if its relevant. But also note this when i try to update.

stellarmate@stellarmate:~ $ sudo apt-get update
Hit:1 deb.debian.org/debian bullseye InRelease
Hit:2 security.debian.org/debian-security bullseye-security InRelease
Hit:3 archive.raspberrypi.org/debian bullseye InRelease
Hit:4 deb.debian.org/debian bullseye-updates InRelease
Hit:5 ppa.stellarmate.com/repos/apt/stable bullseye InRelease
Reading package lists... Done                         
N: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'ppa.stellarmate.com/repos/apt/stable bullseye InRelease' doesn't support architecture 'armhf'
stellarmate@stellarmate:~ $ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  indi-bin kstars-bleeding kstars-bleeding-dbg libindi1
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.


This also means I am stuck with the kstars build dated 31-12-2021, I actually wanted to update because of a fix for the flat calibration issue I posted a few days ago.

What can I do? This issue is easy to reproduce. I have tried 3 times now.

Thanks!

Marco
2 years 2 months ago #79865

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

Time to create page: 1.532 seconds