Jump to content

NLCbanner2024.jpg.2478be509670e60c2d6efd04834b8b47.jpg

Anonymous Astronomer

Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by Anonymous Astronomer

  1. Hello everyone! 


    Image processed in PI:

    - Decon and Denoise on each channel
    - DBE
    - Histogram stretch
    - Channel combination with PixelMath
    - Applying Ha as Luminance with LRGB Combination 
    - ACDNR
    - Curves transformation
    - Saturation boost

    - Reducing Star Sizes with Morphological Transformation
    -Dark Structure Enhance

    Clear skies,
    Vlad


    1372955893_CaveNebula.thumb.png.2426c0d2340d4414b19aed2b160b0cad.png

    • Like 4
  2. Hello everyone! 


    Image processed in PI:

    -LRGBCombination (RGB combine)
    -DBE
    -BackgroundNeutralization
    -EZ Denoise
    -ColorCalibration
    -DBE on Lum
    -Stretching using HistogramTransformation
    -Applying Luminance Image with LRGBCombination (adjust saturation and check off chrominance noise reduction)
    -SCNR
    -MultiscaleLinearTransform
    -CurvesTransformation
    -Reducing Star Sizes with MorphologicalTransformation
    -Dark Structure Enhance

    1562916066_IrisNebula.thumb.png.d297d0cb73453faaed29dc9419ee9eb8.png

    • Like 2
  3. First time when I process something in PixInsight. Hard to learn but very useful tool.

    Had big issues integrating Ha in RGB (tried for a week to process and combine Ha but without any satisfying results) so the image is without Ha.

    Main steps (these steps were not performed in this order, they are written as I remember):

    -Cropping with DynamicCrop
    -DynamicBackgroundExtraction
    -MultiscaleLinearTransform
    -Matching the Images with LinearFit
    -Stretching using HistogramTransformation
    -Colour-Combining with ChannelCombination
    -Performing the Colour Calibration with PhotometricColorCalibration
    -Removing the Green Colour Cast with SCNR
    -Applying Luminance Image with LRGBCombination
    -BackgroundNeutralization
    -ACDNR
    -Deconvolution with DynamicPSF
    -HDRMultiscaleTransform
    -CurvesTransformation
    -Reducing Star Sizes with MorphologicalTransformation
    -Saturation Enhancements and Hue Shifts with CurvesTransformation

     

    M33.thumb.png.58dca35a448d6ddfaf048ffd4d9ace03.png

  4. On 27/03/2021 at 00:25, discardedastro said:

    To add to this, run the star-cross test in PHD2. This is a basic test, but will show you if you have any PHD2-driven mount motion issues. It's quick and easy to do and will rule out any obvious configuration (i.e. rate mismatches etc) or mechanical issues.

    I will definitely try that.

    Thank you!

    21 hours ago, michael8554 said:

    Old PHD2 Logs should be in the same folder as recent ones - unless you've deleted PHD2 at some point ?

     Yes, I've deleted phd2...good to know that I can just rerun the installer.

    Thank you!

  5. 15 hours ago, KP82 said:

    You will need a serial to USB adapter

    I've bought today a serial to USB cable. I intend to use it tonight.

    Thank you for the advice!

    3 hours ago, michael8554 said:

    I think your GuideLog from 2 weeks ago would be useful to have too, for comparison purposes.

    Unfortunately I don't have that logs...idk why..

     

    3 hours ago, michael8554 said:

    Upload both logs from the good and bad sessions to the PHD2 Help site, instructions in the Help menu (get the dates right !)

    https://groups.google.com/g/open-phd-guiding

    Some incidentals from the log:

    This Cal was at Dec = 19, not a game changer, but hence the suggestion from PHD2 to Cal at Dec = 0.

    RA Guide Speed = 6.0 a-s/s, Dec Guide Speed = 6.0 a-s/s.

    A little low, 8 to 15 is normally used, try 10 / 66% / 0.66X, a setting in your mount.

    Guidescope focus could be better, HFD = 4.35 px, use the Star Profile window in PHD2 to get that to its lowest reading.

    First of all, thank you so much for your time and for all the technical analysis.

    I'll make all the recommended adjustments and also post the logs to the PHD2 Help group.

    Hopefully I will be able to guide tonight with those adjustments and the USB-serial connection to the mount.

     

    Cheers,
    Vlad

  6. Hello everyone

    I've started astrophotography in September last year with the following setup: 

    Telescope: WO ZS 61
    Mount: EXOS-2 PMC8 (wireless connection to the laptop)
    Camera: ASI1600MM Pro
    Software: APT/N.I.N.A

    Had no problem with this equipment, taking mostly 60s subs (rarely 90s with round stars) without guiding.

    So...heading to the problem...

    Recently bought an ASI120mm camera with an Artesky guidescope. On the first night with this setup, I've managed to take approx. 5x300s in N.I.N.A. After that my mount got suddenly disconnected and then PHD2 never worked properly.

    I'm struggling for more than 2 weeks...

    Having the following issues on different nights:

    1. PHD2 error messages:
    - pulse guide command to mount has failed
    - RA calibration failed star did not move enough
    - PHD2 is not able to make sufficient corrections in RA
    - PulseGuide command to mount has failed - guiding is likely to be ineffective
    - Although I start calibration within +/- 10 degrees of celestial equator I get the following message: "Calibration this far from the celestial equator will be error prone. For best results calibrate at a declination of -20 to +20."

     2. The most recent one that happened 2 nights in a row without any error messages is that PHD2 loops infinitely when I start calibration. 

    Tried the following "fixes":
    - increasing calibration steps in PHD2
    - using another USB Type-C cable (tried connecting guide camera to imaging camera and also tried connecting guide camera directly to the laptop)
    - tried different USB slots
    - rebalancing
    - reinstalling all the software (ASCOM drivers, PHD2, N.I.N.A, APT, ZWO drivers)

    I'm hopeless...

    You can find my last PHD2 logs in the attachment.

    I'm opened to any ideas, suggestions (buying a more capable mount is not an option at the moment)

    Thank you in advance!

    Cheers,
    Vlad 

    PHD2_DebugLog_2021-03-25_214115.txt PHD2_GuideLog_2021-03-25_214115.txt

  7. 1 hour ago, tooth_dr said:

    1. The size of the filter does impact the image but not in the sense that the 2" is better than the 1.25" version.  It is related to the size of your sensor and the speed of your telescope.  If your sensor is small and the telescope is say F5 or slower, then you can likely just use 1.25" filter - cheaper and no impact on quality. If the sensor is larger or you have a fast telescope then you will need the 2" filters, as the smaller ones will cause excessive vignetting.

    2. 35nm would not be suitable for good deep sky imaging, 7nm will give nice contrast and  is what I use.

    3. You often get what you pay for with filters, Baader would be decent.  I have some Optolong Ha Oiii Sii filters that I like also, and seem very comparable to Baader.

     

    All of that makes sense. I really appreciate your input.

    Thank you,
    Vlad

    • Like 1
  8. Hello everyone,

    I'm looking to buy some NB filters and wanna make the best decision.

    1. Does the size of the filter impacts the quality of the image? (is it a big impact?)

    2. I know that lower HBW is best, but... for example: does the difference between 35nm and 7nm is worth the price?

    3.Can you recommend some H-alpha, OIII, SII?

    Thank you in advance!

    Cheers,
    Vlad

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.