Help with new ASI120MC

edting

Hi everyone:

Nice to be here.

I bought a new ASI120MC from High Point. I am using two laptops with Windows 7 and am getting strange, pixelated images of Jupiter. I am using Registax 5 and 6.

I have owned half a dozen or so Imaging Source cameras with no problems, and I have an ASI120MM that works fine.

I updated the driver and it didn't solve the problem.

Can anyone help?

-Ed

riklaunim

Bad debayering? Try debayer.exe from FireCapture and check which color scheme will debayer it correctly.

edting

Hi:

Thanks for the suggestion. I located debayer from Fire Capture 2.3 and it opened up a screen (below.) Can anyone suggest a different setting? This is what FC defaulted to.

-Ed

riklaunim

Open avi and change the algorithm until you get proper colors on the preview. If more than one are correct - pick the one that looks the best :)

edting

Hi:

Thanks for the response. I should clarify here. The avi files look normal to me - they look like the files generated by my DBK and DFK units. I can even process the avi files in Registax. Everything looks normal until I get to the wavelets. Moving the sliders in wavelets will result in the image you see above.

Any help would be appreciated.

-Ed

dasilvor

I have the same problem with my 120mc. I thought it was my processing,but it seems not.

If anybody comes up with a solution, please share

Dave

Sam@ZWO

just choose the right debayer pattern when debayer

or you can debayer in FC and capture in color video

edting

Hi:

I did some more experimenting. It turns out the the longer your exposure times, and the lesser the number of stcakable frames, the higher the chance of getting this grid-effect on your final images. This ASI is not like my D*K, where I can go for long exposures and capture only a few frames.

Unfortunately, in "solving" this problem I came upon another. There are several rows of dead pixels running diagonally across the chip. I wound up returning the ASI120MC to High Point, and they're sending me another one.

-Ed

Sam@ZWO

maybe some dusts on the sensor.

pixel is more small than that