×

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
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.

  • Posts: 275
  • Thank you received: 69
Can you check your filesystems to see if you are out of space anywhere? indi-allsky is checking the disk usage using the psutil module and it is getting an permission denied error. If not, that is fine. I have merged an update to catch this exception. This will also fix the System menu (which is making the same disk check).

For the exposure, try setting the default exposure to something like 0.01 and see if that helps get things going.

And color balance... were you using using JPEG mode with libcamera? If so, that enables the auto white balance mode which corrects the colors (but also causes other problems). indi_pylibcamera returns RAW data which does not have the auto-white balance enabled. I will research to see if it possible to re-enable that.
Last edit: 1 year 6 days ago by Aaron Morris.
1 year 6 days ago #92747

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

  • Posts: 83
  • Thank you received: 4
you got it right, /tmp was full. I deleted dozens of tmp*.fit files created by indi-allsky and it should have enough space again. The exposure error went away with the sunset happening right now. Yes, I have used/tested libcamera with JPEG mode. It provided excellent pictures. Would be nice if the same quality could be achieved with raw. The secret sauce of the PiHQ camera firmware should not be a well hidden enigma.
After the git pull and restart the System menu is working now, but the May 10 20:58:32 localhost [ERROR] ImageWorker001 image.processImage() #655: PermissionError: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay' is still there.
With default exposure 0.01 it works now again.

CS, Markus
1 year 6 days ago #92748

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

  • Posts: 275
  • Thank you received: 69
I have implemented subtracting the offset from the image from indi_pylibcamera. I had already implemented from the libcamera-still side (it was automatically subtracted in JPEG mode).

I do not know why libcamera implemented this crazy offset... the standard offset for most of their camera modules is 4096 (in a 16-bit space). This basically means the image has a minimum RGB color of #101010, a light gray. It gives the image a hazy look. If you take dark frames, this would be eliminated, but the offset is so high, it needs to be subtracted if you do not have them.

I am not a big fan of the auto white balance from libcamera. It does give proper color balance, but it has a very nasty side effect at night. During the day, there is enough light, libcamera can give proper color offsets on the first exposure. However, at night, there is so little light, it has to repeat the exposure internally 3-6 times to return proper balance. This means a 30s exposure can take 120 seconds to complete. This is one of the reasons I implemented SCNR (from the PixInsight docs) to reduce the green bias from the camera.

Edit: I also increased the max gain for imx477 and imx378 to 22.
The following user(s) said Thank You: Markus Kempf
Last edit: 1 year 6 days ago by Aaron Morris.
1 year 6 days ago #92753

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

Time to create page: 1.394 seconds