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

362 Excellent

About AngryDonkey

  • Rank
    Star Forming

Profile Information

  • Gender
  • Location
  1. Have you tried reversing the focusing direction i.e. focus out instead of in?
  2. Although the comms protocols might be similar, the fundamental philosophies behind each framework are quite different which will reduce compatibility e.g. ASCOM implements a fairly strict interface whereas INDI is a lot more free form. Also the way messages flow push/poll is different. I'm sure it could be done somehow (the now retired wIndi server did expose ASCOM devices to INDI I believe) but I'm not sure the benefits would outweigh the potential issues of working across two frameworks. Drivers need to be written for a specific system (Windows/Linux) so the Vendor will still need to write two drivers if targeting both Windows and Linux. For Windows however the 'normal' ASCOM driver can be exposed over Alpaca so it doesn't need a separate 'Windows Alpaca' driver. Not sure if Vendors will buy into this but there is certainly a market for RPi based devices at the scope end.
  3. You only need the 'remote server'/'ASCOM remote' part if you want to use an existing Windows client (running on normal ASCOM) to connect to an Alpaca device driver (over the Alpaca API) or if you want an Alpaca client to connect to a regular ASCOM driver on a Windows machine. So it really only comes into play if you want to include some component running under the 'old style' ASCOM framework. I think the arrows in the diagram are a bit misleading, you can remove the entire left hand side of the diagram and it will still work i.e. you could have an Alpaca client running on Linux connect to an Alpaca driver running on the Raspberry Pi. Not sure what the rules are on posting links to other forums but if you look on cloudy nights and search for a recent thread called 'Raspberry Pi and Alpaca' there is a guy who has just done that i.e. developed a Linux client and RPi drivers via the Alpaca API. I don't think it is released yet but it shows what can be done. The problem at the moment of course is that there are very few (if any) Alpaca drivers and clients available at the moment. It's a bit of a chicken and egg situation and time will tell if it finds any traction... As has been said above, if you need something now (and you don't want to write your own drivers etc.) then its better to stick with the other suggestions. I also find the INDIGO framework to work quite well.
  4. This is not quite correct. ASCOM Alpaca does not require Windows nor does it need the original ASCOM framework to work. As a protocol I think it has a lot of potential, there is however very little support for it at present in terms of drivers and clients. Hopefully this will change...
  5. Personally I think the soon to be released QHY268 Mono would be a great camera for this scope.
  6. I have an Avalon LFR and it has been superb. I currently use it with my mobile dual scope imaging setup which weighs around 18kg and it doesn't seem to cause it any issues. It has been reliable and tracking is good, it needs to be guided though (due to its design). I would definitely call it portable in size and weight. The only slight negative I have noticed is that it is susceptible to wind. Hope this helps!
  7. Don't misinterpret me, I'm not disparaging the software, nor am I a free software zealot. I was just putting forward my own experience with free software, and musing about the subscription model. I do actually have a subscription to APP for image processing, the pricing model is slightly different - you can opt to buy, with the threat that v2 will not be available to you, or rent and have free upgrades for the term of the subscription. I opted to rent for one year, and buy later if I dont feel v2 is going to (a) happen anytime soon and (b) will improve my results significantly. I only wrote this because you suggested that they are not trying to compete (and rely on the fact that people don't want to invest time in learning a new system). I don't think that is the case, on the contrary I think they do want to compete which is what all this is about I guess.
  8. I think that is a bit unkind. I love open source software (and contribute) but it is not the only way. Often in smaller projects there is a large user community but most of the actual work is done by very few people who either are happy to give their time for free or have some other revenue stream derived from the open source offering (e.g. Stellarmate). Sometimes they drop out or have to shift priorities and projects can also dry up. Not saying that that is the case with Ekos or NINA (on the contrary) but it can happen. If you have a good product and you support it well then there is nothing wrong with charging for it. I think SGP has been suffering a lot because it didn't have a steady income stream (one update that had to be paid for in 10 years) which meant that support was sometimes poor and features very slow to emerge. With the new subscription model you are paying for updates but more importantly a new kind of 'Premium Support' which was not available before. I think this will be welcome by many, especially in this game where most of the problems are combinations of many things, not easily disentangled. Personally I think SGP is a good product and if it comes with steady development and good support then I am happy to pay for it. Of course this is not for everyone, but that's absolutely fine. I tried Kstars/Ekos and it didn't work well for me at the time but that doesn't mean that its not a good product. I think its great that we have a choice.
  9. Great images! I just had a look and managed to spot Neowise on my all sky images as well (just about). Thanks for reminding me!
  10. Hi Adam, yes the ASI 120 is generally supported in AllSkEye. If it is an older version ASI 120 though it can sometimes be problematic because the driver for these cameras was never really fixed and seems to fail a lot with some setups. It is really dependent on your computer and USB cable though so still worth a try if you want to go down that route. Mike
  11. Application settings are usually stored in folders associated to user accounts (where the logged in user can make changes). So disappearing settings could be related to that. For example if you run an app with elevated (admin) privileges, the user changes and different folders / settings are used.
  12. That's looks great! Hmm might have to get one for testing.
  13. Great stuff! Are there any sample all sky images taken with that camera?
  • Create New...

Important Information

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