Hi!
Good to hear you are making progress!! However, I do not have a build environment on my Raspberry - just a standard Stellarmate image. However, if you are able to give me instructions - if not too complicated - on how to set it up, I could try the next few days.
(the other issue with scope information keeps pestering me - guess I should open a separate thread on it)
Best,
Magnus
Read More...
Hi!
Here's a screen-shot of the filter config:
I use the V-filter for alignment and for focus. This problem has occurred when I do a series of Miras where for each, I take VRI-band images, in that order. So that first shot is same filter as alignment.
Best,
Magnus
Read More...
Hi again,
John, I seem to have had the issue with system hanging on changing focus offset at filter change. This was clearly an intermittent issue. I ran a series of variables last night (it is a very long list from which the greedy scheduler picks what is observable that night). It seemed to work nicely at first, then one time hanging (before midnight, while I was watching) toggling exposure and filter change in the capture module made it work again without interrupting the scheduler. Then I went to sleep. According to the log, it seems to have been hanging in the latter part of the night, though, for instance around 02:13, finally closing down at 2:43 when dawn began.
Log attached.
Magnus
Read More...
Hi!
Thanks. That did it.
Is this a new feature, simulate daytime? In summer, here, I guess we have "daytime" the whole night.....
Magnus
Read More...
Hi!
I just upgraded one of my Stellarmates and got a new version of Kstars. And the color scheme is flat out terrible. See here:
No matter how I change color schemes or themes, this quite useless blue color stays on the sky. Anyone can help me get back to a black or white sky? (Star chart color scheme is slightly better but far from what I want)
Magnus
Read More...
Hi!
I keep having problems with FOCALLEN and APTDIA in my fits headers. Indi persists in wanting my scope focal length to be 500 and aperture to be 30 - and THIS (and not the info from the optical train!) is what is entered in the fits headers. I have manually set the correct values, clicked set, then Save, but next time I start Ekos, the 500 / 30 values are back again.
Anyone knows what is going on here?
Wrong fits keywords makes plate-solving needed for photometry impossible (I have to manually correct later).
Magnus
Read More...
Hi!
So I had another clear night and turned on the logs as you said. However, now it worked flawlessly with filter change!! I have not changed anything so I do not understand what happened - but it did work nicely....
Magnus
Read More...
Hi!
I just reinstalled Stellarmate on one of my SD-cards and updated to latest version, 1.8.2. And now I run into some issues:
First, I get some odd values in my FITS-headers. I have set up the optical train to use my C11, apterture 279 mm, focal length 2000 mm (f=7.2) and make sure the this primary train is used for capturing. But in the fits header was apterture 30 mm, f = 500 mm. These values I now found in the Indi panel settings for the camera (QHY268m). Does anyone have any clue, first, why these values are used in FITS header and not the ones from the optical train, secondly, where on earth did these values come from? I for sure did not set them.
Secondly, I usually have some filter offsets for focus when doing photometry (R and I filters need some offset). But when I do that in this new version, the capture model gets stuck saying "Focus offset for filter" (or something simular). No time out, no nothing. So I hit pause in the capture module, the Start again, and now the capture starts. However, I can not do this a´manually for a scheduler run for the whole night. Anyone recognize this? I did not find anything relating to this in the log so I did not include a log file. Not sure which log I would need.
Any help warmly welcome.
Magnus
Read More...
Hi!
Yes, well, this was a new profile 
But I'll follow your advice and try again later today.
I just was baffled by Ekos not getting any frame info when it so clearly was there in the Indi window..
Then, later at night, I changed back to my much more complex configuration with 2 imaging cameras and one guiding camera and a filter wheel. NOW the ASI 183 worked flawlessly.....
Magnus
Read More...
Hi!
Unfortunately, no stack trace. In this setup I had only one camera - definitely the right one in the Primary train, but again, I'll test more later today. And there is no filter wheel in this configuration - just the mount and one camera.
Magnus
Read More...
Hi!
I just ran into a strange situation: I changed my setup to only having a single ZWO camera and the mount - to do some experiments. But now suddenly I can not capture with Ekos - Ekos crashes when I try. This seems related to the fact that there are no frame dimensions in Ekos. However, they are identified in the Indi Control window. And I can capture with Indi control window. And if I hit "reload configuration" in Ekos, Ekos crashes.
See here:
What's happening here? Oh, and I just upgraded Stellarmate to see if that helped. Did not. And I deleted the ZWO CCD config file and rebooted. Same thing again.
Ideas?
Magnus
Read More...
Hi!
I had some more serious problems with my ASI EFW resulting in buying a new one. And in the process there I upgraded to latest stable. Since then, this happens. Running Kstars 3.6.9 now.
Magnus
Read More...
Hi!
I also get the error about updating filters every time I connect. Seems not to matter but odd.
Magnus
Read More...