ASI120MM / what computer?
Posted 04 December 2012 - 03:09 AM
the pro guys in this forum convinced me to get a ASI120MM camera,
but I desperate need to upgrade my computer to be able to handle the data.
Any suggestions what performance should I aim for with a moderate budget? Should I have a separate laptop for the data acquisition and a desktop for processing?
Posted 04 December 2012 - 03:43 PM
my experience with a PC with an AMD chip has been mixed to be honest.
With a DMK it baulked and gave me such grief that I sold the DMK. I tried an ASI 120MM, and it didn't fare too much better.
Right now I am running a Flea2 with firewire and it is singing along.
The PC for capture is a desktop quad core.
The ASI 120MM is a good camera and Sam is a great guy to deal with, perhaps see what he says, I found him to be very honest and forthcoming with his communications.
Posted 04 December 2012 - 04:12 PM
Posted 04 December 2012 - 07:08 PM
I thinking of a "split" set-up
buying a modest laptop for portability and portable hard-drives, complemented by a more spec desktop for processing.
Posted 04 December 2012 - 11:39 PM
the most important thing is that its should be a intel computer. I found that all intel computers can use the full bandwidth of USB2.0 and ASI120MM can run to 30fps at full resolution without any problem.
when USB is fine then you need to consider CPU and harddisk.
if you want to use FC then with a CPU 2.0G and 2GRAM is suggested.Harddisk biger better. you may got 50-100G data one night
Posted 04 December 2012 - 11:41 PM
I am sorry about the AMD system
Posted 05 December 2012 - 02:51 AM
Posted 06 December 2012 - 10:27 PM
Posted 06 December 2012 - 11:52 PM
how can I tell if a bunch of USB is on one or more host?
Posted 07 December 2012 - 10:10 AM
Posted 08 December 2012 - 03:18 PM
For example, my flea cameras can take exposures up to 60 minutes long.
Posted 08 December 2012 - 03:21 PM
Exposure Range: 64µs-1000s
Ive ordered an ASI120MC, and I am hoping to use it as a guide camera. Will also try to to some short deep space stuff with it also. We'll see how it goes when it arrives.
Posted 08 January 2013 - 06:09 PM
I try to avoid Win8 ... and I have to use the Laptop for processing as well to save money....
The one I find in my price range is Asus A54C-SX327V Notebook.... it's a Intel core3-2.2GHz with 4G ddr3 500Gb
Once I've got the Laptop, need to start from scratch re software...
So, what software I need to download for the ASI120MM camera, and to make RGB planetary pics?
Is it expensive software(s)?
Posted 08 January 2013 - 10:41 PM
For Combining the RGB file I think MaxIm-DL does it well.
PS can do it too.
Posted 08 January 2013 - 11:05 PM
a "work-flow" chart for planetary beginners would be so nice
I'm sure many people would benefit from it. I personally feel a bit overwhelmed by the complexity of so may software and process... missed out a lot in the past, trying to catch up with learning.
tnx in advance
Posted 09 January 2013 - 09:16 AM
you are correct about the complexity of astronomy imaging.
but this is the same reason why we love it
Posted 09 January 2013 - 09:22 AM
For a couple of $$ you can add another 4Gb DDR module
Makes a lot of difference when running W7!!
Posted 09 January 2013 - 09:52 AM
1. Move scope from garage to yard, engage fans, several hours previous to imaging. It's best to set up on grass or dirt - but not concrete or asphalt. It's best to set up so that you'll not image over a bunch of houses (although, this is very difficult - I live in a neighborhood with other houses, drat it).
2. Double check all the cables (to computer, Servo Cat, Argo Navis, focuser, etc.) are secure and connected properly.
3. Collimate as carefully as possible (I have a truss-Dob and simply moving it from the garage to the yard throws it off - if you have an SCT it may well need less collimating (but longer cooling)). But careful and accurate collimation is essential as most learn the hard way (I know I did).
4. Acquire planet in the eyepiece. Use a reticle eyepiece to first center without a Barlow. Then I add whatever Barlow I'm going to use and double check centering with the reticle. A lot of folks find the planet with the camera. In fact, many collimate with the camera (which is undoubtedly the "best" way to do it, though sort of a pain with my system.)
5. Attach camera and filter wheel.
6. Bring up FireCapture. Hope that I still see the planet in the frame. Usually, I do. Rough focus.
7. Run through each channel I plan to use finding settings at which the histogram is between 60-80% (for Jupiter, lower for Saturn).
8. Focus carefully (and re-focus as needed).
9. Begin acquiring. I typically acquire 40s per Red and Blue, then 60s for blue. I've gone shorter and gone longer (60s per R and G, 80s blue). There is debate about how long is too long. Some is personal preference. But, as a general rule, the longer you run, the more rotational drift you get. (all the numbers above are for Jupiter). If you have a fast camera, you can get away with shorter avis. If you have a slow camera, the rotational blurring is probably a necessary price to pay for lower noise in the final image. If you shoot at shorter focal lengths, you can go longer. Don't be afraid to play with it (that goes for every aspect - use mediocre or bad nights to play with settings so that you have a good routine when the great seeing comes).
10. Break down. I can usually just wheel the scope into the garage and pack everything away later. An observatory would be nice but would need to be in my front yard.
11. Align and stack each avi in AutoStakkert!2. How many frames you will stack depends on how good the seeing was, how many frames you collected, etc. At the gain settings I use with the Flea3, I try to stack around 2000 frames per channel - corresponds to 40-60% of the frames, depending on what focal length I used and which channel. Again, how many frames and where you set alignpoints is something to play around a lot with.
12. Sharpen each stacked tif. I usually use Registax 6 and have a "stock" wavelet setting. But I try to play with that some - some tifs can take more and others less. I know a lot of people use deconvolution in AstraImage. You'll find that most images, while looking largely the same in total, bear a good deal of personal character.
13. Look at all the tifs and select the "good ones".
(Note: 14-15a are optional. If you don't do RGB, skip. If you don't want to bother with derotation, skip).
14. Make image measurements in WinJupos of the good ones.
15. Derotate and stack the R,G and B channels in WinJupos. Again, I run 40s R and G, then 60s B. Derotated and stacked the total span of time is about 3 minutes.
15a. Occasionally, I make an image measurement for the RGB from 15 and then derotate and stack several RGBs that are within 5-20 minutes of each other. This often works very well.
16. Take the stacked RGB into Photoshop, adjust levels, curves, denoise, high pass filter, etc. until the image looks best (to me). Again, play with it.
17. Occasionally I will go back to an image and re-align/stack in AS!2 more carefully or with different numbers of frames. I typically only do this if I think the final image came out worse than I expected from the video or channels.
18. Post to CN and ALPO.
You should play around as much as possible with all of that. I wouldn't take anyone's method and apply it unthinkingly but, if you are to do so, there are better folks than me. But that is, I think, pretty close to what everyone does, although details will vary considerably. But, like I say, the important thing is to experiment and try new things. Each setup is different, each night is different, etc.
Also, while it looks on paper fairly complicated, once you get the routine down, it isn't all that bad. An evening moves pretty smoothly once you start acquiring. And the processing is unbreakable, assuming you don't throw the raw data away. Can't tell you how many "final" images I've tossed in the bin. But you just start over with the avi and all is well. Good luck.
Posted 09 January 2013 - 12:49 PM
It also makes you system more responsive overall. I can easily do capturing with FireCapture AND quickly processing in AS!2 and Photoshop to see what the recordings look like, without dropping frames. RAM memory is also relatively cheap.
Below you'll find a small graph showing the performance of AS!2 using relatively few alignment points, under several conditions (and for version 184.108.40.206 and a beta 220.127.116.11). The recording was one of Saturn, about 2 GB in size, containing 6085 frames. I also simulated a low ram condition, where there was not enough memory available for AS!2 (or windows) to buffer a recording.
Posted 09 January 2013 - 03:10 PM
I just learned yesterday that to find a laptop with WIN7 and not W8 is difficult, but not impossible .
Hardware related question, if I use external HD on the laptop and dumping the data, the USB port is shared with the camera true the hub. Would this slow it down a bit?
Or some laptop has USB3 for the HD and USB2 for the cam.
Thanks for the advice and the work-flow Paul