UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
Hello again,
when testing a new filter I got very strange integration results, as if the flats / the MF is overcorrecting. For comparison I re-integrated different (older) images with a different filter, where I had good results with before. Same result: "tunnel vision".
21 x 300s Antlia DNB with 25 F, MD, MB:
only Lights:
(yes, some egg-stars - I was also testing / correcting for tilt)
by the way:
analysing the FITS headers revealed a ZWO ASI camera driver issue (in my case ASI 2600 MC): one cannot set the offset anymore. It´s "-1" when it should be 50....
but this can´t be the reason for my actual problem (and never had before with earlier versions of APP).
Any ideas?
thanks in advance
Peter
It´s "-1" when it should be 50....
Are you using KStars by any chance? I noticed th9s as well. Setting the value manually in Ekos (not the config but where you set up the image sequence) solves that.
Regarding the flats: What telescope are you using? What exposure time for the flats? What temperature of the sensor? What does the image look like if you only leave out the flats (so use the MD and MB)? What does the image look like if you only use the flats and MB?
Hi Wouter,
- no I don´t youse KStars. I use APT, APP & PI. I blinked every L / F / DF frame as well as the Masters.
- as far as I know: actually one cannot change the offset due to a ZWO camera driver issue when using the actual driver. I didnt test with the older driver. I could redo the calibration frames but not the Lights 🙂
- it´s a 250/1000 Newton, Antlia DNB Filter, T [sensor]: - 5 C
L exp: 300s, F exp: 0,53 s with a flatfieldbox,
The integration without Flats / MasterFlat, with or without MB MD look pretty similar to the second image (above). The second image (only L) can easily be LP corrected.
What does the image look like if you only use the flats and MB?
- I´ll have to do that.....
This is not a new setup, until now the APP integrations were fine...
Peter
@peter-s Hi Peter,
Thanks for the detailed answer.
This is not a new setup, until now the APP integrations were fine...
So, what changed? Did you install a newer version of APP? If yes, do you get a good result with the version of APP previously used by you? What version were you using before and what version do you use now?
Thanks, Wouter
Hi Wouter,
thanks for your time...!
APP changed, as mentioned above I now use APP 2.0.0.beta 8
I have to check which version was the latest before updating. I think it was 1.083-beta2.
On the other hand I am checking the new filter (Antlia DNB) vs the L-eXtreme but have same results with already taken images (with the L-eXtreme) when integrating them now.
and it seems the ZWO drivers behave strange -
update 1:
checking different ZWO camera drivers resulted in:
- the ZWO native driver supports offset
- the ASCOM driver doesnt support offset (in my setup), it returns "offset -1"
For the Lights I had to take the ASCOM driver.
I´ll double check the rest ...
Peter
update:
1. ZWO answered that they will fix that ASCOM driver issue
2. some tests:
What does the image look like if you only use the flats and MB?
L+F+MB
What does the image look like if you only leave out the flats (so use the MD and MB)?
L+MD+MB
L + new made F + new made DF + MB + MD:
So I think there was something wrong with the flats: offset? dew? (which I checked...)
Even though it doesnt look like other integrations it can be processed:
after quick de-vign.+ de-lp
I´ll redo a new set of images as soon as possible.
cs Peter
Hello again,
just wanted to post this update - maybe it helps others:
I was getting this ring issue again and again with my Newton, sometimes more, sometimes less, until I found the answer in this thread:
Until now I made the Flats with the flatfield panel laying directly on the tube. Now I
- placed the flatfield panel on the dew shield, ca. 40 cm away
- did the Flats in the dark
- closed the back / mirror side
Now already the integration stack is as it should be.
cs Peter
