Jump to content



  • Content Count

  • Joined

  • Last visited

Community Reputation

375 Excellent

About AngryDonkey

  • Rank
    Star Forming

Profile Information

  • Gender
  • Location

Recent Profile Visitors

2,783 profile views
  1. Hello! Yes you can install INDIGO server on a RPi and then use AllSkEye to connect to it via your network and use it as normal. Kind Regards, Mike
  2. I might be wrong but I think that the Thomas Jacquin all sky software only supports ASI cameras and the RPi hq camera.
  3. Personally I don't think there is anything that can be done unless you go through a dealer which I'm sure would make it too expensive. Even if you would get something in place (e.g. contract or similar), it would be very difficult to enforce. I have looked at escrow services (e.g. escrow.com) but there always seems to be someone at a disadvantage and in any case they would know nothing about astro gear and could not make an impartial decision. So I think that someone/both will have to take a leap of faith... I have sold and bought expensive equipment internationally but in all cases:
  4. If you can, then I would recommend wired. You will need a router to plug in the ethernet cable running to your NUC (or just use your existing router). The laptop can then join the same network either by also being connected to the router by a cable or via wifi.
  5. If the NUC needs 19V you can use a DC step up converter from 12 to 19V (that's what I use). They are fairly cheap.
  6. Just learned something new today! You can actually auto translate youtube subtitles into any language in the video settings, made watching it much more interesting!
  7. A real shame that you had such trouble with your two Avalon Fast Linears as it is a great mount (when working as it should). Do you think that the problems with the second mount were down to the seller or Avalon (or did you buy direct)? What problems did you have with SGP? I've never had any issues with SGP (with the StarGo version of the linear). Maybe third time lucky?
  8. I happily run my dual setup off one intel compute stick with no USB issues. Might be worth giving it a go first on the NUC to see if a second computer really is required... You could then spend the money saved on something else
  9. Not something I have heard of, can you elaborate? Thanks!
  10. And I got most of my images back! I hadn't logged in for a while, so that was a nice surprise!
  11. Have you tried reversing the focusing direction i.e. focus out instead of in?
  12. 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
  13. 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
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.