×

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

Bi-monthly release with minor bug fixes and improvements

New All Sky camera management software: indi-allsky

  • Posts: 2247
  • Thank you received: 223
My SUPER old QHY5 works with this tool, excellent.
I will test it and report as I have seen quite a few things could do with improvements.

Good tool so far. Thanks for creating it.
1 year 9 months ago #83688

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

  • Posts: 83
  • Thank you received: 9
Anybody got ideas?? To my earlier post

I appreciate all the hard work you have done to create this package! I just installed Indi AllSky on an Astroberry server running on a Raspberry PI 4. The installed seemed to go just fine. It was a clean install of Astroberry and Allsky. I started the service just as described in the install section of the readme file, no errors. Where things go off the rail is when I try to access the application with the Raspberry PI using raspberrypi.local/ I get the Astroberry log on page. what am I doing wrong??
Last edit: 1 year 9 months ago by Bruce Morrell.
1 year 9 months ago #83766

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

  • Posts: 348
  • Thank you received: 69
Not sure, but if you install on astroberry then all-sky relocates its services to another port. Accessing it requires putting a colon then the port number after the host name.

Think it is documented somewhere...
1 year 9 months ago #83767

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

  • Posts: 83
  • Thank you received: 9
Yes I saw that and tried port 80, 81 and 82 no luck....
1 year 9 months ago #83770

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

  • Posts: 348
  • Thank you received: 69
raspberrypi.local:444

Failing that, discover the actual IP of the Astroberry and use that instead of raspberrypi.local

The .local address relies on something called multicastDNS or mDNS to work, and not all systems support it.

You can always use netstat to discover what ports are listening on your system, it will be one of those.
1 year 9 months ago #83775

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

  • Posts: 255
  • Thank you received: 65

Just to restate what @Giles already mentioned. Astroberry is a special case since it already has nginx running on port 443. indi-allsky will setup an alternate listener using nginx on port 444.

You should be able to use astroberry.local:444/ or raspberrypi.local:444/
1 year 9 months ago #83784

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

  • Posts: 255
  • Thank you received: 65

I am glad you got it working after the troubles you had! Feel free to open an issue in GitHub related to any improvements.
1 year 9 months ago #83785

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

  • Posts: 83
  • Thank you received: 9
Thank you everybody for your input. Yes using astroberry.local:444/ does work.
I found more in depth discussion on cloudynights here www.cloudynights.com/topic/785514-new-al...oftware-indi-allsky/
Cant wait to try it out.... Bruce
1 year 9 months ago #83905

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

  • Posts: 255
  • Thank you received: 65
I have just released v4.0 of indi-allsky which includes meteor/line detection for the images.

All in all, the detection works very well. On the very first night of testing, I managed to capture a meteor and the line detection flagged the image. Detection works slightly better with a monochrome camera, but I have been surprised by how accurate the detection works across all of my cameras.

The only weak point in the detection is "clouds". Just like our imaginations can see objects in clouds, the edge detection can be thrown off when clouds are arranged certain ways.

The detection is also very fast, taking a mere 0.1s to analyze a 1920x1080 image on Raspberry Pi hardware.
Last edit: 1 year 8 months ago by Aaron Morris.
1 year 8 months ago #84218

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

  • Posts: 255
  • Thank you received: 65
I have created a timelapse video to show the star and line detection abilities in indi-allsky. Hopefully, this can demystify what is going on in the background.

I added a new option to highlight the detected stars (red circles) and lines detected (green lines) within the detection area. If you look carefully, you can see there are some false positives for both. Defraction/reflection artifacts from the dome can be detected as stars. Same for lines. Also, the edges of clouds can sometimes be detected as lines.



Startrails:


Note: There are some dark areas center left. This my oldest allsky camera (sv305) and a couple of years in the sun have caused some striations to develop in the plastic dome.
1 year 8 months ago #84450
Attachments:

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

  • Posts: 20
  • Thank you received: 2
I really like indi-allsky, and have been using it for several months now. As a minor issue, does anyone else have problems with the lunar and solar orbs positions? Mine seem to be out by 180 degrees, despite no image flipping. Times and locations are all correct, and I cannot see any way to adjust the positions. It makes no difference to the utility of indi-allsky, but it niggles my OCD! Any ideas how to correct it?
Regards
Tim
1 year 7 months ago #85043

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

  • Posts: 255
  • Thank you received: 65
Hello Tim, what is your configured latitude and longitude and where do you live? I just want to double check the logic.

Can you upload an image here so I can see what you are seeing?

The orbs are drawn on the image after any flipping is done, so that should not affect anything.
1 year 7 months ago #85044

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

Time to create page: 2.200 seconds