Thanks, Aaron.

I installed Bullseye 64-bit, used the build_indi script and connected the HQ camera via libcamera (I installed on raspy 4, that's much faster compared to raspi3). This seems to work on raspy 3 & 4 , both services are now running.
I now want to get some experience and might com back with questions if needed.

Thanks
Kurt

Thanks a lot! It's just what I needed. I had to install a few libs:

<code>sudo apt-get install libindi-dev libcamera-dev libcamera-apps libboost-program-options-dev</code>

Unfortunately, I get build errors on buster complaining about "addFitsKeyWords" being unknown and I had to copy the /usr/include/libcamera/libcamera/* files to the parent dir.

Fixing those and starting the driver works, but I can't see images and the size is 0,0, likewise the pixel size.

Any help here would be appreciated!

We shouldn't hijack this thread, I'll create another topic for this driver: indilib.org/forum/ccds-dslrs/12177-indi-libcamera-driver.html

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