Excited about this update Aaron - even more-so if we can get the appropriate INDIlib driver sorted as I'm sure people using the library will have other applications where these cameras could be used.

This update was really more of an experiment for me to see if I could acquire images from other sources. The time lapse part of the code does not particularly care where the data comes from.

It was never my intention to push for a new driver in indi. I am not that subtle. Although, I can see how my post could be perceived that way.

Recently, I have been following the Allsky Camera group on facebook and there has been a lot of activity and interest in the new Waveshare IMX378-190 camera that has an integrated lens. It is a compelling product at $50 and is perfect for all sky cameras, although I think the view might be a bit too wide.

Hi all,
is there an easy way to change the web page's port?
I tried to edit /etc/apache2/ports.conf and virtual port on /etc/apache2/sites-enabled/allsky-indi.conf without success or the only option is to edit setup.sh and install again?
Best regards
Pierre

You can run setup.sh as many time as you need. It will not hurt your existing installation.

You can either edit setup.sh or just edit the /etc/apache2/sites-enabled/allsky-indi.conf file directly. You just need to restart the apache2 service when finished.

I believe the setup.sh script comments out the Listen directives in ports.conf, so the only file you need to edit is the site.

ok; thank you very much!

I am continuing to make improvements to indi-allsky.

I was able to implement an interesting enhancement. Since indi drives the underlying camera, I decided to integrate [virtual] telescope and GPS functionality from the respective servers. I used the Telescope Simulator and the GPSd servers to get information about where the camera is located as well as where it is pointed. The telescope simulator is [virtually] slewed to the zenith of the current location which is detected by GPS.

Since the Telescope Simulator is used, if the FITS files are exported, they are properly tagged with time, site latitude/longitude, and RA/dec of the sky for each image.

Hi fellas.
I'm new here and a Indi-allsky software user. I have some questions and issues:
1 - When I change EXPOSURE PERIOD in Allsky config, always change again to the default value (in number, to 15), and it corresponds (real and efective value) to MAX. EXPOSURE value.
2 - When the DAYTME CAPTURE options is enabled and DAYTIME TIMELAPSE is disabled, when the night period begins and the night timelapse and capture creation starts the camera's image freezes and I need to restart the Indi-allsky service. When I disable the DAYTIME CAPTURE option, the upload to Internet stop working.
I have a ZWO ASI 120 camera
Can you help me?

Thx
Ferran

I am not quite sure what you are talking about with the EXPOSURE PERIOD. I double checked the code and it seems to be doing the right thing (I do have typos sometimes). Make sure you have updated to the latest code. It is possible there was a bug at one time that I corrected.

For the ASI120, there is a known issue with this model. I have documented the workaround here:
github.com/aaronwmorris/indi-allsky/wiki...20MC-S-Camera-Issues

Hi Aaron and thanks.

I applied the workaround for the ASI 120, I give you feedback ASAP.
EXPOSURE PERIOD is this:



Thx

Regards

Ferran

Hi friends.

I have an Ubuntu Linux with Kstars and Indi AllSky.
Run AllSky at startup. When start Kstart say "another instance of INDI is running. Do you want to close the other ?,,,,,,," and close one Indi server, only run Kstars or Indi AllSky software is possible.
There are any way to run Kstars and INDI AllSky on the same server simultaneously???.

Thanks

Ferran

I know I was interested in your software when I first saw it, over a year ago, but I still am running the original "Instructables" software from Thomas. I should get back to updating to your program.

Did you ever look into incorporating an evaluation of "seeing" from the images? It would be useful for establishing exposure times for people who are imaging thru telescopes. Forgive me if I asked this before or if someone else has already asked, I did not read thru all the responses, this time.

In Kstars/EKOS, select Mode "Remote" instead of Local and use "localhost" for the address. indi-allsky starts its own indiserver service so you do not need to launch a second one.