×

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: 257
  • Thank you received: 66
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.
The following user(s) said Thank You: Jim
1 year 4 months ago #88865

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

  • Posts: 5
  • Thank you received: 0
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
1 year 3 months ago #89444

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

  • Posts: 257
  • Thank you received: 66

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
The following user(s) said Thank You: Ferran
Last edit: 1 year 3 months ago by Aaron Morris.
1 year 3 months ago #89451

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

  • Posts: 5
  • Thank you received: 0
Hi Aaron and thanks.

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



Thx

Regards

Ferran
Last edit: 1 year 3 months ago by Ferran.
1 year 3 months ago #89454
Attachments:

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

  • Posts: 5
  • Thank you received: 0
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
1 year 3 months ago #89456

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

  • Posts: 396
  • Thank you received: 17
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.
1 year 3 months ago #89461

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

  • Posts: 257
  • Thank you received: 66

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.
The following user(s) said Thank You: Ferran
1 year 3 months ago #89462

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

  • Posts: 257
  • Thank you received: 66

If I had a way of measuring seeing, I would certainly try to implement something. I have had done some exploration with others about trying to measure the apparent/absolute magnitude of the sky (like a proper SQM). It is extremely difficult. Measuring magnitude would require controlling for 2 variables that are unique to almost every allsky camera: QE/frequency response of the sensor and the lens.

I would love some help in getting even a close approximation of magnitude converting an ADU value to a magnitude. It would almost certainly require some local offset for every camera/lens combination, I just do not quite understand the math involved.
1 year 3 months ago #89465

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

  • Posts: 5
  • Thank you received: 0
Yes, I try it, but when uses remote INDI server the telescope mount, filter wheel and other cameras are missing, only ZWO ASI and Telescope simulator appear.

Regards

Ferran
1 year 3 months ago #89470

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

  • Posts: 257
  • Thank you received: 66

You can add the additional servers/drivers in ~/.config/systemd/user/indiserver.service and restart (and reboot) so that the indiserver has all of the drivers. I just merged a change that would allow you to specify the camera name in the config in case you have multiple cameras attached. indi-allsky normally just selects the first available camera it detects.

There are also ways to daisy chain indiservers together. Let me know if you are interested in that.
1 year 3 months ago #89515

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

  • Posts: 2255
  • Thank you received: 223
Found the following error:
./setup.sh: line 1267: /home/heidenrod/GitHubstuff/indi-allsky/virtualenv/indi-allsky/bin/activate: No such file or directory

heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$ ll /home/heidenrod/GitHubstuff/indi-allsky/virtualenv/indi-allsky/bin/activate
ls: cannot access '/home/heidenrod/GitHubstuff/indi-allsky/virtualenv/indi-allsky/bin/activate': No such file or directory
heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$ ll /home/heidenrod/GitHubstuff/indi-allsky/virtualenv/indi-allsky/
.gitignore lib/ local/ pyvenv.cfg
heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$ ll /home/heidenrod/GitHubstuff/indi-allsky/virtualenv/indi-allsky/local/bin/activate
-rw-rw-r-- 1 heidenrod heidenrod 2187 Feb 6 14:53 /home/heidenrod/GitHubstuff/indi-allsky/virtualenv/indi-allsky/local/bin/activate
heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$


RESOLVED:
edited the wrong path in setup.sh
Last edit: 1 year 2 months ago by Gonzothegreat.
1 year 2 months ago #90235

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

  • Posts: 2255
  • Thank you received: 223
Also this one:
Failed to connect to bus: Operation not permitted (consider using --machine=<user>@.host --user to connect to bus of other user)

Resolved from a previous post of mine in this thread:
export XDG_RUNTIME_DIR=/run/user/$(id -u)
Last edit: 1 year 2 months ago by Gonzothegreat.
1 year 2 months ago #90236

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

Time to create page: 1.490 seconds