×

INDI Library v1.9.8 Released (29 Sep 2022)

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

Astroberry Server 2.0.1 is available now!

  • Posts: 30
  • Thank you received: 3
I just did apt update now and after reboot INDI won't start. The syslog is full of the following failures:
systemd[1]: Started INDI Web Manager.
indi-web[2689]: Traceback (most recent call last):
indi-web[2689]:   File "/usr/local/bin/indi-web", line 10, in <module>
indi-web[2689]:     sys.exit(main())
indi-web[2689]:   File "/usr/local/lib/python3.7/dist-packages/indiweb/main.py", line 315, in main
indi-web[2689]:     start_profile(profile['name'])
indi-web[2689]:   File "/usr/local/lib/python3.7/dist-packages/indiweb/main.py", line 99, in start_profile
indi-web[2689]:     indi_server.start(info['port'], all_drivers)
indi-web[2689]:   File "/usr/local/lib/python3.7/dist-packages/indiweb/indi_server.py", line 74, in start
indi-web[2689]:     self.start_driver(driver)
indi-web[2689]:   File "/usr/local/lib/python3.7/dist-packages/indiweb/indi_server.py", line 37, in start_driver
indi-web[2689]:     cmd = 'start %s' % driver.binary
indi-web[2689]: AttributeError: 'NoneType' object has no attribute 'binary'
systemd[1]: indiwebmanager.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: indiwebmanager.service: Failed with result 'exit-code'.
indiwebmanager.log contains repeated failures
WARNING: terminating indiserver failed code 1
2 years 6 months ago #51340

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

  • Posts: 30
  • Thank you received: 3
Oh, it looks like the problematic update was indi-astroberry-diy 2.5. The indi web manager wasn't able to change the profile, but after I manually removed the "Astroberry Board" driver from .indi/profiles.db, everything seems to work again.
2 years 6 months ago #51341

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

  • Posts: 7
  • Thank you received: 1
Hello !.
I'm trying to connect my QHY367C to an astroberry.

Astroberry server 2.0.1 just installed on RPI 3B+
I have made an upgrade (apt-get upgrade). Always the same error with Ekos: "No QHY camera connected. Power on ? "
My QHY367C is well powered and connected with the original cable to the RPI (The camera is new, never used).
Is it normal? Have you an idea ?
Thank you !
Regards,
Jonathan
2 years 6 months ago #51369

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

  • Posts: 344
  • Thank you received: 68

Did you "sudo apt-get update" before the "sudo apt-get upgrade" command?

The "Power on ?" query is an INDI debug line, so INDI is not detecting your QHY camera, although it appears that INDI is starting correctly (Just saying that this looks INDI related, rather than directly Astroberry related).
__
I blog my progress: www.coochey.net
2 years 6 months ago #51381

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

  • Posts: 7
  • Thank you received: 1
Oups, no i didn't.
I'll try tomorrow asap !
Thanks for the quick reply !
The following user(s) said Thank You: Giles
2 years 6 months ago #51386

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

  • Posts: 7
  • Thank you received: 1
Ok so i did an update then an upgrade, no differences.
I have again the "No QHY camera detected. Power on ? "
The astroberry server is fresh, newly installed on my RPI3B+. So is the QHY367C.

Any thoughts ?
2 years 6 months ago #51393

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

  • Posts: 344
  • Thank you received: 68

Does the QHY show up if you run lsusb ?
__
I blog my progress: www.coochey.net
2 years 6 months ago #51402

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

  • Posts: 7
  • Thank you received: 1
Nope... No sign of QHY camera after a lsusb.
Do i need to install something else ?
2 years 6 months ago #51418

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

  • Posts: 344
  • Thank you received: 68

If you can't see any QHY device in the output then its just not seeing the camera via the USB port. (or any difference with the output of lsusb when the camera is connected compared to when it is not)

Perhaps try a different USB cable, check connections and power.

Does the camera work on another system?
__
I blog my progress: www.coochey.net
Last edit: 2 years 6 months ago by Giles.
2 years 6 months ago #51419

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

  • Posts: 344
  • Thank you received: 68

No, you shouldn't have to, although I only have ZWO cameras not QHY, but should be the same.
__
I blog my progress: www.coochey.net
2 years 6 months ago #51420

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

  • Posts: 155
  • Thank you received: 22
Try sudo apt-get dist-upgrade. That may help.
2 years 6 months ago #51424

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

  • Posts: 7
  • Thank you received: 1
Ok so i have did some tests. Here the message i have posted on QHYCCD forum :

I have a QHY367 and i''m trying to use it on my RPi astroberry server (indi). The camera is not recognize.
So i have tried to connect it to my mac, with EZCAP, without success.
After that i've installed native driver on my bootcamp, with EZCAP for windows. The camera is well recognized.
Because i want to use it on my astroberry server, which uses indi driver, do you have an idea about the issue here ?
Do you think is usb cable correlated ? Do i need to powered it ?
Thank you for the reply. "

So the cable works for windows. But impossible for me to run the camera on astroberry or mac.
I'll tried with sudo apt-get dist-upgrade
2 years 6 months ago #51456

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

Moderators: Radek Kaczorek
Time to create page: 1.195 seconds