×

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

Bi-monthly release with minor bug fixes and improvements

New All Sky camera management software: indi-allsky

  • Posts: 2
  • Thank you received: 0
Using a Pi 4 8gb - installed indi-allsky.
I have a QHY678C i'm trying to connect to it but can't.
I did the fxload for usb 3.0 support but do not see an .img file for the qhy5iii678
Tried to do it with the 486 image file and didn't seem to work.

I'm going to try to reinstall everything.

Can you tell me if the 678 is supported?
.
1 year 3 weeks ago #92330

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

  • Posts: 275
  • Thank you received: 69

There is a QHY5III678.img that was just added one month ago, probably for the indi 2.0.1 release. It will not be in the astroberry repo which is still at indi 1.9.7.

You can follow these instructions to remove the astroberry repo: github.com/aaronwmorris/indi-allsky/wiki...tall-indi-repository

Then you can run ./misc/build_indi.sh to compile indi from source. I believe it will take 30-40 minutes on a Pi4.
The following user(s) said Thank You: Pete
1 year 3 weeks ago #92335

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

  • Posts: 403
  • Thank you received: 41
Any update/progress for the planetarium overlay? I think you’ve already tried with VirtualSky correct?
1 year 3 weeks ago #92336

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

  • Posts: 2
  • Thank you received: 0
Disregard - all working - Driver problem.
Last edit: 1 year 3 weeks ago by Pete.
1 year 3 weeks ago #92341

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

  • Posts: 275
  • Thank you received: 69

I did make an attempt with VirtualSky. I could not get the VirtualSky [HTML5] canvas to overlay on top of the indi-allsky image canvas. TJ's allsky overlays the VirtualSky canvas on top of a plain <img> element, which is the primary difference.

I tried, but it is above my skill level with HTML.
The following user(s) said Thank You: Euripides
1 year 3 weeks ago #92343

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

  • Posts: 275
  • Thank you received: 69
Creating exif metadata is proving to be considerably more difficult than I thought it would be. Reading exif data is fairly well documented, but creating exif data is much less obvious. There are a lot of projects that appear to be unmaintained as well.
1 year 3 weeks ago #92344

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

  • Posts: 275
  • Thank you received: 69
I just merged a change that adds EXIF tags for the created JPEG files. All (well, most) of the image reading and writing has been replaced with Pillow.
The following user(s) said Thank You: Jim
1 year 3 weeks ago #92406

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

  • Posts: 535
  • Thank you received: 109
I switched over to using Pillow today, seems to work well. I also switch the lens out with a different one, and notched the sensor board so that I could re-adjust the center of the sensor. That was its own story, and the camera is now sensitive to the tightness of the screws holding the board down. I wanted to use the lens right away, so I found this print very helpful: www.thingiverse.com/thing:4810077 - it allows the M12x0.5 threaded CCTV lenses to be mounted into the T2 threads of the camera. Surprisingly, the printed threads are very good. The lens focus is a bit too tight yet, but once set, it should not move. I am still messing with the focus. It almost feels like putting the dome back on changes the focus, which would be unfortunate. This is the lens in case anyone is interested: www.amazon.com/gp/product/B07DJZJD8V/ref...03_s00?ie=UTF8&psc=1

Here is a sample picture in full sun. The FOV is much better.



The following user(s) said Thank You: Aaron Morris
1 year 2 weeks ago #92445
Attachments:

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

  • Posts: 535
  • Thank you received: 109
I was having too many problems with the 290MC, and will chalk it up to being an early model. I purchased a 662MC, and so far, this is a keeper. It is able to pull out the Milky Way in our terrible Bortle 5/6 type skies with the right settings and a good focus. It would probably make an excellent guide camera.

Jim

1 year 1 week ago #92623
Attachments:

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

  • Posts: 275
  • Thank you received: 69
That looks fantasic! You have your focus really dialed in.

I recently added the ability to "stretch" images. I might provide some additional contrast enhancement with the milky way.
1 year 1 week ago #92641

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

  • Posts: 535
  • Thank you received: 109
I updated and see the options. It has been cloudy ever since, of course
1 year 1 week ago #92709

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

  • Posts: 83
  • Thank you received: 4
I got indi-allsky running with a remote indi_pylibcamera (PiHQ with RPI Zero W) for about two weeks now. Today I did an update (git pull) of indi-allsky. Since this time, the program no longer adjusts the exposure time. It stays at the minimum time.
further bugs:
- System menu does not work, I get Internal Server Error. All other menus do work.
- the image white balance is again quite bad. It was perfect with indi-allsky using libcamera directly. Might be a problem of indi_pylibcamera
- there is an error message in the log about a write attempt to /var/lib/containers/storage/overlay but indi-allsky is not running in a container...
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception: 
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception: PermissionError: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay'
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:     st = os.statvfs(path)
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:   File "/home/admin/indi-allsky/virtualenv/indi-allsky/lib/python3.9/site-packages/psutil/_psposix.py", line 175, in disk_usage
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:     return _psplatform.disk_usage(path)
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:   File "/home/admin/indi-allsky/virtualenv/indi-allsky/lib/python3.9/site-packages/psutil/__init__.py", line 2000, in disk_usage
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:     disk_usage = psutil.disk_usage(fs.mountpoint)
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:   File "/home/admin/indi-allsky/indi_allsky/image.py", line 652, in processImage
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:     self.processImage(i_dict)
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:   File "/home/admin/indi-allsky/indi_allsky/image.py", line 258, in saferun
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:     self.saferun()
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception:   File "/home/admin/indi-allsky/indi_allsky/image.py", line 229, in run
May 10 20:09:51 localhost [ERROR] MainProcess allsky._startImageWorker() #768: Image worker exception: Traceback (most recent call last):

CS, Markus
1 year 6 days ago #92746

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

Time to create page: 1.212 seconds