Astrophotography with the DWARF 3 – Settings and Calibration Guide

If you just need a number to punch into the app tonight, my Dwarf 3 Settings Quick Start covers that in about a minute. This page is for the questions that come after: why 60 seconds and not 90, why gain 50 works for one galaxy and gain 80 works for one nebula, and what to actually do when a session goes wrong instead of right.

One dark frame, contaminated by stray light most likely from a passing car, once put horizontal bands across all 561 stacked frames of the M13 Hercules Cluster before I caught it, which is the kind of thing a spec sheet will not warn you about and a real session will. Every number and rule below traces back to a session(s) actually run and logged on this site, not a manufacturer’s datasheet. Where a setting is the standard case, it is presented as the standard case. Where a setting is a documented exception, like the one gain value below that breaks the usual range, it is called out as an exception rather than folded quietly into the rule.

None of this is a fixed formula. Sky conditions, target brightness, ambient temperature, and how long the unit has been running all move the correct configuration for a given night. Treat every number below as a starting point to adjust from, not a setting to copy blindly.

---

Table of Contents

1. Quick Reference Settings
2. Exposure Time
3. Gain
4. Filter Selection: Emission vs Reflection and Broadband Targets
5. Focus and Atmospheric Seeing
6. Sensor Acclimatization
7. Dark Frame Calibration
8. EQ Mode Setup
9. Solar Imaging
10. Posts in This Section
11. Frequently Asked Questions

---

Quick Reference Settings

Target Type	Exposure	Gain	Filter	Mode
Emission Nebulae	60s	80 to 90	Duo-Band	EQ
Reflection or broadband nebulae	60s	50 to 60	Astro	EQ
Galaxies	30 to 60s	50 to 60	Astro	EQ
Star Clusters	15s (Alt-Az) or up to 30s (EQ)	50 to 60	Astro	Alt-Az or EQ
Moonlit sky nebulae	60s	80 to 90	Duo-Band	EQ
High light pollution nebulae	60s	80 to 90	Duo-Band	EQ
Solar (sunspots)	Manual bracket, roughly 1/500s to 1/1000s	0	Front solar filter, internal VIS or Astro, Sun Track mode	Sun Track

Exposure Time

Exposure time determines how long the sensor collects photons for each individual sub frame. In Alt-Az mode the practical ceiling is 15 seconds, past that field rotation starts trailing stars toward the frame corners. In Guided EQ mode the app supports exposures up to 120 seconds, but 60 seconds is the recommended working maximum. A 60 second sub collects four times the signal of a 15 second sub, which is the entire reason EQ mode is worth setting up.

The floor sits around 30 seconds. Below that, read noise from the sensor starts to dominate the per frame signal rather than the target itself. For most deep sky targets in EQ mode, 60 seconds is the right call.

Gain

Gain amplifies the signal from the sensor before it converts to a digital value. Higher gain means more sensitivity, but also more amplified noise and less dynamic range. The Sony IMX678 sensor in the DWARF 3 performs best between gain 50 and gain 90, depending on the target. Gain 100 and above degrades dynamic range faster than it improves signal and should be avoided for deep sky work.

For galaxies, gain 50 gives the cleanest background with enough sensitivity to hold detail. The M101 Pinwheel Galaxy session on this site, 60 second subs and 6 hours 18 minutes of total integration, was shot at gain 50. For faint emission nebulae with the Duo-Band filter engaged, gain 80 to 90 is the right call, since the filter is already suppressing the sky background and the cost of the higher gain is smaller than it would be without the filter.

One documented exception is worth naming rather than folding into the standard range. The M13 Hercules Cluster session used gain 40 with 30 second subs and the Astro filter, and produced a clean result across 9 hours 37 minutes of total integration. That number sits below the 50 to 60 range in the table above. It worked because M13 is bright and high surface brightness by cluster standards, not because gain 40 is a better default. Treat it as a case worth knowing about, not a new recommendation.

Filter Selection: Emission vs Reflection and Broadband Targets

Every emission nebula setting in this guide leans on the same trick. Emission nebulae glow because ultraviolet radiation from nearby hot stars ionizes surrounding hydrogen gas, which re-emits light at specific, narrow wavelengths, H-alpha and OIII. The Duo-Band filter isolates exactly those two lines, which is what lets it cut through a Bortle 7 to 9 sky or a bright moon: it simply is not passing most of the wavelengths that light pollution is made of.

That trick does not work on every nebula. Reflection nebulae do not emit their own light. They scatter the light of a nearby star off dust grains, the same physical process that makes Earth’s sky blue, and scattered starlight is broadband, carrying the full spectrum of the illuminating star rather than a narrow spike a filter can isolate. The Iris Nebula (NGC 7023) and M78 are both reflection nebulae documented on this site, and both were shot with the Astro filter rather than Duo-Band. Running Duo-Band on a reflection nebula would technically still pass some light, but it would throw away most of the signal for no benefit, since there is no light-pollution-specific emission line to reject in favor of.

The practical consequence is integration time. A reflection nebula under Bortle 6 skies has to out-collect the sky glow the hard way, since there is no narrowband shortcut buying signal to noise ratio back for free. The Iris Nebula session ran 6 hours 1 minute with the Astro filter and resolved the bright core with real color and structure, while the fainter outer dust halo was still emerging rather than fully resolved at that integration depth. The path forward for that kind of target is not a different filter, it is more hours on the same filter and settings, stacked onto the existing data.

Rule of thumb: if the target glows from ionized gas (nebulae cataloged as emission or planetary nebulae, most of the bright Messier and Sharpless nebulae imaged for their H-alpha structure), reach for Duo-Band, especially under light pollution or moonlight. If the target shines by reflected or scattered starlight (reflection nebulae, most star clusters, all galaxies), use the Astro filter and plan for longer integration under a light-polluted sky, since the Duo-Band shortcut simply is not available for that kind of light.

Focus and Atmospheric Seeing

A slightly missed focus does not always announce itself. The target still appears, the stars still look round, the stack still completes. It shows up later, after stretching, as galaxy cores that look smeared rather than compact, nebula edges that never quite sharpen, or a soft look across the whole frame. Check focus carefully before an important session, and check again if the temperature has dropped significantly partway through the night, since the best focus point can drift as the device and optics cool.

Target altitude affects sharpness as much as focus does. Light from a target low in the sky passes through more atmosphere, which usually means softer, noisier data. Light from a target higher up passes through less atmosphere, and both sharpness and contrast tend to improve. It is generally worth waiting until a target has climbed to a reasonable altitude before starting a session rather than starting the moment it clears the horizon.

Tracking accuracy and stacking quality compound with both of the above. Stacking reduces random noise and reveals faint signal, but it cannot remove blur that was already present in the individual frames. A long stack built from soft, low altitude, or poorly focused frames will process worse than a shorter stack built from tight, well focused, high altitude frames, even at the same total integration time.

Sensor Acclimatization

The DWARF 3 sensor is uncooled, so its operating temperature tracks ambient air temperature plus whatever heat the unit generates internally while running. A practical rule of thumb: sensor temperature runs about 32 to 35 degrees Fahrenheit above ambient once the unit has been running for a while. That gap is why a summer session and a winter session at identical settings do not produce comparable noise, and it lines up with what shows up in the data directly: sessions run in the 20s Fahrenheit produce a visibly cleaner background than summer sessions at the same settings.

Power the DWARF 3 on 15 to 20 minutes before your first exposure and let it sit at that stage rather than starting to shoot immediately. That window is long enough for the sensor to climb from a cold start to a stable operating temperature, which keeps you from drifting through the first frames of the session and also helps focus stability, since the best focus point can shift while the unit is still warming up.

The warm up direction matters. Starting from a cold device and letting it climb to operating temperature over that 15 to 20 minute window is straightforward, the unit is heading toward equilibrium the whole time. Starting from a device that ran hot earlier in the day and trying to bring it back down before a session is a slower, less predictable process, since you are now waiting on ambient air to pull heat back out rather than letting internal operation carry it up, and it will generally take longer than the 15 to 20 minutes a cold start needs. If you have run the DWARF 3 earlier in the day, whether for solar imaging or just testing, give it more recovery time before a deep sky session than you would coming from cold, and avoid power cycling mid session, since that resets the thermal curve you were just letting settle.

Dark Frame Calibration

Dark frames must match the exposure length, gain setting, and sensor temperature of your light frames. Because the DWARF 3 sensor temperature is driven by ambient air temperature and internal heat generation, dark frames taken in summer are not valid for a winter session. A seasonal master dark library, updated every two to three months, covers most conditions.

The minimum recommended dark frame count is 20. Thirty or more produces a more accurate master dark and better calibration of the fixed pattern noise the sensor generates on its own.

Inspecting Darks Before Use

A dark frame is supposed to record nothing but sensor noise, no target, no sky, no stray light. When one picks up light it should not have, the effect on your stack is not subtle, it is structural.

One session on this site captured 561 frames of the M13 Hercules Cluster overnight, only for the stacked result to come back with thick, precise horizontal bands running across the frame. The cause traced back to a single dark frame captured at 24 degrees Celsius that had picked up stray light, most likely from a car driving past during the dark capture sequence. Dark frames get subtracted from every light frame during calibration. When a dark frame has light in it, that light gets subtracted from the whole stack, printing a dark shape into data that was otherwise clean. Pulling the one bad file and restacking from the remaining 560 frames fully resolved it, the underlying 9 hours 37 minutes of data had been fine the entire time.

Before using a batch of darks, open them in a FITS viewer, apply a hard stretch, and look for anything that should not be there: gradients, banding, a bright patch in one corner. A clean dark frame looks like uniform noise under a hard stretch. If it looks like it has structure or a scene in it, do not use it. Capture your darks somewhere away from traffic, porch lights, or phone screens, with the lens fully covered. A dark frame captured with a car passing by is not a dark frame.

EQ Mode Setup

EQ mode requires a level surface and a polar alignment procedure through the app before each session. In the DWARFLAB app, go to Deep Sky, then Settings, then EQ Mode. The app walks you through a tilt and rotation alignment matched to your latitude and facing north. The whole process takes about 5 minutes.

The app accepts up to 4 degrees of deviation, but for 60 second subs, push for 1 degree or less. Deviations above 2 degrees start showing visible trailing at 60 seconds. After GoTo completes, wait 30 seconds before starting your capture sequence. That gap lets the tracking motor settle and clears the mild oscillation that sometimes follows a slew.

Solar Imaging

Solar imaging on the DWARF 3 is a different workflow from every other target on this page, and the settings above do not apply to it.

A front mounted white light solar filter is mandatory. The DWARF 3’s magnetic solar filter covers both lenses and snaps on before the app will let you track the Sun. Never point the telescope at the Sun without it, a camera ND filter or welding glass does not qualify, and check the filter for pinholes before every session. Without it the sensor is destroyed in seconds, and any eye in the optical path suffers permanent damage.

Gain stays at 0 for solar work. There is already more signal coming through the filter than you need, and any added gain just costs you dynamic range in the penumbra detail around each spot. Exposure is manual and filter dependent rather than fixed. One bracketed session shot 150 subs at three shutter speeds, 1/10000s, 1/1000s, and 1/500s, with 1/500s giving the best exposed disk that day, spot groups resolving down to individual umbral cores right in the live preview. Your own filter and sky brightness will move that number, so bracket a few shutter speeds and pick the one where the disk is clearly exposed without the brightest areas clipping.

The DWARF 3’s internal filters, VIS, Astro, and Duo-Band, exist for night imaging and do not add solar detail through the front solar filter, they only change the color the disk renders in. VIS gives a brown-orange disk, Astro shifts it deep red, and Duo-Band needs a much longer shutter and renders the Sun magenta. None of this is hydrogen-alpha solar imaging in the dedicated-scope sense, that requires an etalon with a passband hundreds of times narrower than anything the DWARF 3’s internal filters provide. It is a color experiment worth trying once, not a detail-recovery technique.

Sensor temperature runs hot during solar sessions since the unit is typically running at midday. One tracked session showed internal temperature climbing from 102°F to 127°F over about fifteen minutes of continuous solar tracking. Give the unit breaks between runs during a solar session, and see the Sensor Acclimatization section above for why recovering from a hot midday session before a deep sky session that night takes longer than starting from cold.

Posts in This Section

• How to Get Better Results with DWARF 3: Time, Thermal Stability, and Calibration – the three variables that determine data quality on the DWARF 3 and how to control them.
• DWARF 3 Guided EQ Mode: How to Capture 60-Second Exposures – step by step EQ mode setup and the quality difference it produces versus Alt-Az.
• Maximize Sharpness with DWARF 3 Techniques – image scale, focus, seeing, and processing choices that determine how sharp a DWARF 3 image looks.
• Iris Nebula NGC 7023: Six Hours of Blue Light With No Duo-Band Shortcut Available – why reflection and broadband nebulae need a different filter strategy than emission nebulae.
• DWARF 3 Settings Quick Start – the short version of this page: quick reference table, presets, and troubleshooting only.
• Shooting Sunspots with the DWARF 3 – the full sunspot session this page’s solar settings are drawn from.

---

Frequently Asked Questions