Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.



  • Content Count

  • Joined

  • Last visited

Community Reputation

14 Good


About Robd

  • Rank
    Star Forming

Contact Methods

  • Website URL

Profile Information

  • Gender
  1. Eqmosaic is used to osition the mount to build you mosaic. From memory set fov details and overlap required. Start at center of grid and select no of panels required, assumes that you are already pointing to target. Take no of required frames for each panel. Stack each panel as normal then create mosaic. Exact method of mosaic will depend on your software, pixinsight - mosaic linear data. I recently used Hugin on a set of non linear images which worked a treat. Other software may also incorporate mosaic functionality. Rob
  2. Large rings are again just visible, is this from set that created the master or second set? Vlaiv has just beaten me to it, the filter is slightly out of position on second set compared to first. The large rings are on the filter whereas the smaller corrected rings are on the sensor. The latter don't move and are therfore corrected. The former compound the problem since the aberrations are slightly offset. Very careful cleaning of filters may help. However if filter is contributing to the vignetting then incorrect application will still happen. As a OSC user I, fortunately, don't have this problem. Rob
  3. Very odd. The large rings are just visible in the master flat. Is there any sign of them in either set of individual images? Rob
  4. Rather than an error (my earlier reply) or thread problem it sounds more like a timing issue, OK yes a problem with a thread. Solving completes, and results are shown. A separate thread is kicked off to create the 'solved' image, since this is 'interactive' it takes a while to create hence the problems if user is to quick with the mouse. Rob
  5. Not at home at present so going from memory. I assume that the error occurs when you hit the 'Browse solved image' button. The only thing that I can think of is that an error has occurred prior to creation of the solved image but after the display of the results. Make sure that auto syncing boxes are not checked. Grasping at straws I'm afraid. Rob
  6. We have, in the past, briefly considered a society Observatory, one member even looked at a possible plot, the eventual cost of which would have taken several years membership fees. Needless to say, we don't have one. Most considerations have already been covered - security, power, water, insurance. Also consider access/parking, can be problematic just for members but more so when expanding to outreach. Apart from the physical aspects of the build you will also have to manage access to the Observatory. The members will have paid for it so should have access to it, but who has the keys? Must an authorised member be on site to supervise? Will set up be for visual only or will imaging be allowed? If the latter do you allow members to bring own cameras to attach or does the society provide. Having spent many thousands on the build then it should be used, ideally, on every clear night which means that an authorised member must be also available. None of this is insurmountable, but will need a dedicated team to manage the observatory. Rob
  7. If you do not need bet access when imaging and your disk is big enough you could split into 2 or 3 partitions. Win 7 Linux Data. Then as you suggest, kill net access on win 7 and enable on Linux. Free up more space by removing all applications no longer required on win 7, as well as moving all documents to Linux or data. When imaging save to data or folder on Linux, don't use home folders due to security issues. Rob
  8. No problem. Should they not be able to help you then contact us either through the our web site or better still come to an 'Observing' meeting on the 1st Monday of the month. We don't do much observing due to weather but it is a good chance to chat. Rob
  9. Hi Neil, in principle yes we would. To get an idea see our 'Outreach Report' at http://www.broms-astro.org.uk/society-outreach/ If you can make it to the open evening this evening then we will certainly be able to discuss with you. Redditch does have an Astro society so it might also be worth contacting them. http://www.redditchastro.org.uk/ Rob ( Membership Sec. )
  10. Lukebl, in DSS have you tried stacking on comet and stars? In simple terms it stacks the comet throwing away the stars, then stacks stars throwing away comet, then puts results together giving comet on static star fields. Doubles stacking time but does give a nice result. Having said that I've never stacked a comet moving this fast.
  11. I use a Canon 1000d, hence a friend passed me the following links regarding best iso to use http://dslr-astrophotography.com There's an interesting article on the techy side of how setting the ISO affects astrophotography images... http://dslr-astrophotography.com/iso-dslr-astrophotography but if you just want the bottom line you can look up your Canon DSLR model and find the optimum ISO setting for astrophotography... http://dslr-astrophotography.com/iso-values-canon-cameras I hope that they are of some help. Rob
  12. My understanding is as follows- 1) Your mount does not have dual encoders, therefore when re-starting Eqmod has no way of determining where the scope is pointing. 2) I suspect that EQ will update files to indicate parked or not. It may continually update with current RA/DEC, but I would have thought that this was unlikely - unnecessary overhead replacing a file every second. 3) EQ depends on starting in a known position, hence Park before power off. 4) A power cut is very unlikely to corrupt a file unless a write was in progress in which case EQ possibly is frequently updating or you were very unlucky. I agree with Steppenwolf, however I think that you will first have to clear your pointing model since existing 'corrections' will be drastically different to the new position and now wrong. Actually that raises a possible downside to this solution. Usually we initially start at the default position of pointing north. Corrections are then fairly small, let's say 1degree. If after the power cut, restart and sync the error is now 90 degrees, I suspect that this might make ' mapping ' less reliable. I am not totally convinced that mathematically I am correct but gut feeling says that the smaller the correction the better. Either way unfortunately there is no magic button to put everything right again. Rob
  13. Our original observatory was a lift off roof. We then went conventional dome and finally to a double octagonal turret. See http://www.dipplestars.org.uk/Galleries/Observatory.html for details of the development and reasons for the changes. Not very mobile friendly I'm afraid. Rob
  14. We have overhead electric cables crossing the garden, 1 support post 2m south of observatory, 4 cables running approx. east west. I get similar spiking when cables are in field of view. Right pain because I rarely think to check.
  15. Hmm just managed to repost. I used the arduino and adafruit driver for mine. The latter will drive two steppers. My plan was to use one for the guide scope and the other for the imaging scope. It all worked fine switching between the two motors via software. Unfortunately one driver no longer works - think I blew something up on the board. Fortunately the other side still works and the guide scope doesn't need re-focusing very often.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.