New ASCOM driver for test V1.0.1.10: Page 2

New ASCOM driver for test V1.0.1.10

purdyd

Sam wrote:
Purdyd wrote:So here are two dark image panels at temperatures of 2C and 28C and stretched hard in photoshop like what you might do with a deep sky image

significant decrease in hot pixels and noise but the fixed pattern bands are starting to rear up and they are hard to get rid of when they are close to the values for the faint objects

yes, the right down side is not a good area to image DSO expecially for narrowband

here is a NGC6888 raw file

174.rar

Thanks for sharing that. I assume that is the ASI174mm cooled judging from the lack of thermal noise and hot pixels in the 120 second exposures.

Sam@ZWO

Space Cowboy wrote:
Sam wrote:
Space Cowboy wrote:Ive installed the new ascom driver for my 224mc but can't find the new high and low gain settings in firecapture?

you can set the value you see in ASCOM when you click high gain or low gain

Thanks Sam, do I use ascom alongside firecapture or instead of? I've never used ascom before and the asi manual only refers to guiding.

ASCOM driver is recommended for DSO imaging

so you can use many professional DSO imaging software such like maxim-dl

Sam@ZWO

Purdyd wrote:
Sam wrote:
Purdyd wrote:So here are two dark image panels at temperatures of 2C and 28C and stretched hard in photoshop like what you might do with a deep sky image

significant decrease in hot pixels and noise but the fixed pattern bands are starting to rear up and they are hard to get rid of when they are close to the values for the faint objects

yes, the right down side is not a good area to image DSO expecially for narrowband

here is a NGC6888 raw file

174.rar

Thanks for sharing that. I assume that is the ASI174mm cooled judging from the lack of thermal noise and hot pixels in the 120 second exposures.

yes in high gain mode 1e/ADU

space cowboy

you can set the value you see in ASCOM when you click high gain or low gain

Thanks Sam, do I use ascom alongside firecapture or instead of? I've never used ascom before and the asi manual only refers to guiding.

ASCOM driver is recommended for DSO imaging

so you can use many professional DSO imaging software such like maxim-dl

Thanks Sam so firecapture does not use the new ascom driver gain settings they can only be accessed through ascom or maxim as stand alone capture platforms?

space cowboy

After some trial and error I've got the new 224mc high and low gain settings running on the ascom platform v6.1 alongside sharpcap. Firecapture will not run with the ascom platform and crashes as soon as the camera properties are selected in ascom.

purdyd

Sam wrote:

ASCOM driver is recommended for DSO imaging

so you can use many professional DSO imaging software such like maxim-dl

Why would you use the ascom camera interface vice going directly through the .dll?

For instance, I just copied the .dll file in the ascom driver download into the firecapture directory and that appears to work fine,

space cowboy

Purdyd wrote:
Sam wrote:

ASCOM driver is recommended for DSO imaging

so you can use many professional DSO imaging software such like maxim-dl

Why would you use the ascom camera interface vice going directly through the .dll?

For instance, I just copied the .dll file in the ascom driver download into the firecapture directory and that appears to work fine,

I just tried copying the .dll ascom driver into FC directory and its made no difference to FC. Still can't see any high and low gain sliders like there are in the ascom platform and FC still crashes when ascom platform cam settings are activated for the asi224mc.

purdyd

Space Cowboy wrote:
Purdyd wrote:
Sam wrote:

ASCOM driver is recommended for DSO imaging

so you can use many professional DSO imaging software such like maxim-dl

Why would you use the ascom camera interface vice going directly through the .dll?

For instance, I just copied the .dll file in the ascom driver download into the firecapture directory and that appears to work fine,

I just tried copying the .dll ascom driver into FC directory and its made no difference to FC. Still can't see any high and low gain sliders like there are in the ascom platform and FC still crashes when ascom platform cam settings are activated for the asi224mc.

As far as I can tell high gain and low gain are just presets of the gain. Since you can set the gain via a slider in firecapture, I don't see why that is necessary.

I don't have the asi224mc and have not tried to set the gain by using the ascom driver and then running firecapture.

But then again, I don't see any reason to do that.

I did notice that in Maxim dl that when I access the camera properties that the zwo camera setup window has a l gain and high gain button which set the gain to 0 and 179 respectively

However I can easily do that in firecapture

So I'm not sure why using the ascom interface is the way to use the camera for deep space.

Sam@ZWO

Space Cowboy wrote:
Purdyd wrote:
Sam wrote:

ASCOM driver is recommended for DSO imaging

so you can use many professional DSO imaging software such like maxim-dl

Why would you use the ascom camera interface vice going directly through the .dll?

For instance, I just copied the .dll file in the ascom driver download into the firecapture directory and that appears to work fine,

I just tried copying the .dll ascom driver into FC directory and its made no difference to FC. Still can't see any high and low gain sliders like there are in the ascom platform and FC still crashes when ascom platform cam settings are activated for the asi224mc.

just like Purdyd said, you don't need the ASCOM in FC

you can just set the parameters the same under FC

these buttons is just set the gain and offset to a resonable value for you

you can set everything under FC

space cowboy

Thanks Purdyd for your explanation! Sam completely confused me!

Sam your cameras are brilliant but please give clearer instructions and answers as not all of us are software experts.

Sam@ZWO

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

bigol

Hello, Sam.

Why your ASCOM driver doesn't report version? How we could check it?

Why I can't select binning in driver settings?

It's all about ascom 1.0.1.17

Thanks.

Sam@ZWO

bigol wrote:
Hello, Sam.

Why your ASCOM driver doesn't report version? How we could check it?

Why I can't select binning in driver settings?

It's all about ascom 1.0.1.17

Thanks.

we will show the version on the UI of the dialog in our next build version

the binning method is choose from the Control software

this is because ASCOM has this interface

the driver setting only show these cannot control through ASCOM

« Previous Page