Courious transparent ampglow issue with my 294 MC Pro and Astropixelprocessor: Page 2

Courious transparent ampglow issue with my 294 MC Pro and Astropixelprocessor

wvreeven

Tobi294MCPro Can you indicate in my image where you see it?

Tobi294MCPro

wvreeven

Tobi294MCPro It depends. If you leave the camera and filter on the telescope then there is no need.

Tobi294MCPro

wvreeven no, I take off the camera after every session.

wvreeven

Tobi294MCPro Honestly I don't see anything there at all. If there is something it is such a little bit that you can suppress that in post-processing.

Regarding the flats, in that case you should take flats every night. I didn't do an exhaustive inspection but it looks like this time it wasn't necessary.

wvreeven

Tobi294MCPro I loaded the FITS that APP produced for me in PI and did three things:

crop
background neutralization
stretch via HistogramTransformation using the ScreenTrnasferFunction settings

The result looks great and no amp glow at all. For some reason I cannot upload any images so the resulting FITS is in the same https://wvreeven.stackstorage.com/s/NGC7000_BBS_ZWO folder.

Tobi294MCPro

wvreeven in both it is visible when you zoom in.

Tobi294MCPro

Tech@ZWO is there anything new yet?

Tobi294MCPro

Hello guys I have a good news on my issue. I found out through the APP forum, that my BadPixelMap was false or bad. So I have decativate the BPM and here is the new result.

Tobi294MCPro

Hm, I can´t accept the way only deactivate the bpm in app. Because a friend of mine has the same camera and stack too with app and had the bpm at autoamtic and he has nothing an issue like mine.

I show you the bpm of him and my again.

The only difference between him and me is the temp of the sensor. He use -10° and I have used -15°.

Tech@ZWO

Tobi294MCPro Thank you for your patience, i calibrated these images in our software ASIStudio-ASIDeepstack.
The ampglow can be calibrated well. https://drive.google.com/file/d/1pp3PFYBFOiaLyJu_5Jxk32JsDYIrLFXW/view?usp=sharing
If the problem only appears in APP when BPM is enable, is it possible some parameter settings in this function or program affect that?
I'm not fimilar in APP, sorry if i said something wrong.

Tobi294MCPro

Tech@ZWO yes that´s the point, in AsiStack I had no issues, so it seems it´s a issue in APP maybe. But when I deactivate the BPM it´s no problem, because the hot pixels where remove too without the BPS. So ist seems this function is more or less useless in my opinion.

« Previous Page Next Page »