Hi all,
When I started out with astrophotgraphy, I went with what looked like the prevailing guidance - that image capture doesn't need much computing power, and pretty much any computer will do. I bought a quite low-powered Windows laptop, thinking that would be good for running from batteries when away from base. But having used it for a while, and done some experimenting, reading and researching, I've come to feel that I really need more power.
So I am thinking of upgrading the laptop. But I wondered if anybody might have any thoughts on whether I am on the right track with this - and if I am, how powerful a laptop I ought to be looking for?
Current kit is :-
Dell Inspiron 17-5770 laptop with i3 CPU, 8GB RAM, 1TB hard disc, integrated graphics.
Sky-Watcher AZ-EQ6 mount
Canon EOS 600D imaging camera
ZWO ASI120MC-S guide camera
Windows 10
Stellarium & EQMOD running the mount
BackyardEOS handling image capture
PHD2 guiding
The system works, but the laptop feels rather overloaded. I can see signs that the CPU is running pretty much flat out, and when capturing images I get a delay of about 35 seconds between shots. This feels too long - especially when shooting short exposures on brighter targets! Comparing with a few friends, they seem to generaly get delays of around 8 seconds or less between frames. Their equipment setups are sufficiently different to mine that it is difficult to figure out much from further comparing with them. I have experimented with NINA in place of BackyardEOS, and got fairly similar results (with NINA controllong the mount too, in place of the Stellarium/EQMOD setup). Experiments suggest that the time taken to transfer data from camera to computer is around 10 seconds. The remaining 25 seconds appears to be taken up by processing activities on the computer - which I imagine mainly to be decompression, debayering and stretching of the image data so that the software can display the image on screen. If I have just a capture program running - nothing else - and just the DSLR connected, the data transfer time appears to fall to around 5 seconds, which I take to be a sign of the computer being overloaded when running everything.
Having thought around the subject a little, I realise that the computing workload will depend on the type of camera being used - how many pixels, whether a "consumer" or an "astro" camera, and whether colour or monochrome. I reckon that my kind of camera - i.e. a DSLR - probably imposes a higher workload than most "astro" cameras, as the RAW data from the camera needs to be decompressed and then debayered before it can be stretched and displayed. So perhaps a low-power laptop would be OK for an astro camera with a small sensor, but maybe not for a typical DSLR?
If anybody is running anything broadly similar to my setup - i.e. involving a Windows laptop and a DSLR - I'd be very interested in feedback on how well you get on. How short is the time gap between exposures when shooting an image sequence? Plus details of the kit used, etc. Any such feedback will be very gratefully received.
Many thanks for reading.
Regards,
Tim
When I started out with astrophotgraphy, I went with what looked like the prevailing guidance - that image capture doesn't need much computing power, and pretty much any computer will do. I bought a quite low-powered Windows laptop, thinking that would be good for running from batteries when away from base. But having used it for a while, and done some experimenting, reading and researching, I've come to feel that I really need more power.
So I am thinking of upgrading the laptop. But I wondered if anybody might have any thoughts on whether I am on the right track with this - and if I am, how powerful a laptop I ought to be looking for?
Current kit is :-
Dell Inspiron 17-5770 laptop with i3 CPU, 8GB RAM, 1TB hard disc, integrated graphics.
Sky-Watcher AZ-EQ6 mount
Canon EOS 600D imaging camera
ZWO ASI120MC-S guide camera
Windows 10
Stellarium & EQMOD running the mount
BackyardEOS handling image capture
PHD2 guiding
The system works, but the laptop feels rather overloaded. I can see signs that the CPU is running pretty much flat out, and when capturing images I get a delay of about 35 seconds between shots. This feels too long - especially when shooting short exposures on brighter targets! Comparing with a few friends, they seem to generaly get delays of around 8 seconds or less between frames. Their equipment setups are sufficiently different to mine that it is difficult to figure out much from further comparing with them. I have experimented with NINA in place of BackyardEOS, and got fairly similar results (with NINA controllong the mount too, in place of the Stellarium/EQMOD setup). Experiments suggest that the time taken to transfer data from camera to computer is around 10 seconds. The remaining 25 seconds appears to be taken up by processing activities on the computer - which I imagine mainly to be decompression, debayering and stretching of the image data so that the software can display the image on screen. If I have just a capture program running - nothing else - and just the DSLR connected, the data transfer time appears to fall to around 5 seconds, which I take to be a sign of the computer being overloaded when running everything.
Having thought around the subject a little, I realise that the computing workload will depend on the type of camera being used - how many pixels, whether a "consumer" or an "astro" camera, and whether colour or monochrome. I reckon that my kind of camera - i.e. a DSLR - probably imposes a higher workload than most "astro" cameras, as the RAW data from the camera needs to be decompressed and then debayered before it can be stretched and displayed. So perhaps a low-power laptop would be OK for an astro camera with a small sensor, but maybe not for a typical DSLR?
If anybody is running anything broadly similar to my setup - i.e. involving a Windows laptop and a DSLR - I'd be very interested in feedback on how well you get on. How short is the time gap between exposures when shooting an image sequence? Plus details of the kit used, etc. Any such feedback will be very gratefully received.
Many thanks for reading.
Regards,
Tim