Jump to content

sgl_imaging_challenge_banner_31.thumb.jpg.b7a41d6a0fa4e315f57ea3e240acf140.jpg

jusasi

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

5 Neutral

About jusasi

  • Rank
    Nebula

Profile Information

  • Location
    Lahti

Recent Profile Visitors

573 profile views
  1. Thanks for the analysis! Yeah, the Dec backlash seems bad - I might just go ahead and return it on that basis alone. If the skies stay clear enough I'll definitely try your tips. Also I didn't mention my gear, I totally forgot: - The scope is a 70mm refractor with 420mm focal length, reduced to 336mm with a reducer. - The guide scope is a 50mm / 162mm focal length basic scope. - The main camera is ASI1600MM, guide camera is ASI224MC. - ASI filter wheel. - Total weight of that setup is 3.8kg. I bought the mount intending to use it as a trave
  2. Ok, please bear with me as this is may be a bit long and highly illustrated. I've tried to record my struggles as detailed as I could in the hopes of getting some help from you guys, so I beg you to read this carefully if you have experience with guiding issues and/or with the EQ3 Pro (SynScan) mount - I only got this mount about a week ago and I'm still wondering whether these issues is something that can be solved or to be expected, or whether I'm dealing with damaged goods. So here we go. Bottom line, what is your judgement: is this correctable, is there something very wrong with the m
  3. The information is there, but I have to admit it's pretty well buried under a wall of text. I should restructure the readme and categorize the documentation into the repository Wiki. To answer your questions: 1) Correct. It's mentioned in the readme if you can find it 2) Yep, Win10 with Linux Subsystem. 3) Not supported out of the box. I suppose it could run, given that it's executed inside cygwin. And correct, this is for the needs where the API is required. With Win10 Linux Subsystem or cygwin you could natively run the solver as well - but if your software cannot us
  4. It's very similar to ansvr by its concept, although I've never used it but judging by the instructions it's very much the same. The same basic idea of providing an offline API for the solver. Not many differences, apart from Astrometry-api-lite being multi-platform solution and open source. In Windows Ansvr runs on top of cygwin, while Astrometry-api-lite runs on top of Windows 10 Subsystem for Linux.
  5. Basically, yes. If your control laptop is a Windows laptop, you could now install the Astrometry-api-lite to the control laptop, go set the Kstars/Ekos solver settings to use http://localhost:3000 instead of http://nova.astrometry.net and that's it. And yes, you wouldn't need an internet connection - that's the idea . In fact, this is how I roll, I run Windows 10 with Kstars on my control machine while my INDI slave is a Raspberry Pi, and run the Astrometry-api-lite as my solver on the Windows machine.
  6. Well if you're already running your Kstars on Linux, you'd just be adding an extra layer with this API - just download the astrometry.net solver (if running Ubuntu or similar, sudo apt-get install astrometry.net) and configure it to use your catalogue files (/etc/astrometry.cfg, add_path) and you're good to go. You can set up Kstars to use the solver directly, you don't need Nova or Astrometry-api-lite at all. Edit: to clarify, if on the other hand you were running Kstars/Ekos in Windows, this is what you would need. On Linux however Ekos can use the solver directly. Also if you wa
  7. Hi folks, I just finished work on a new release of the Astrometry-api-lite application and I'm happy to announce that it's now easily installable on Windows 10 with Subsystem for Linux installed. The new Windows installer lets you install and configure the whole shebang with just a few mouse clicks and installs a desktop shortcut to run the service. The only manual install requirement that is left is the Linux Subsystem, which you can install from the Windows Store. You can get the Astrometry-api-lite installer from here: https://github.com/Jusas/astrometry-api-lite/releases In addit
  8. The API runs on Raspberry Pi just fine - however performance/speed might not be very high for completely blind solves. The API itself does not eat much resources, so it just depends on how well the solver can perform with the Raspberry Pi ARM CPU (and probably the SD card read speeds affect it as well). But yeah, it'll run, at least runs on my Pi 3B.
  9. I've not used ansvr, but if it does use the same API endpoints as with nova.astrometry.net (I suspect it does) then yes, it can. And yes, I've personally used this with Kstars/Ekos myself, I've installed the Linux subsystem to my Windows 10 (you can get it from the Microsoft Store, easy installation instructions) and I run the astrometry-api-lite there. My setup is basically a Raspberry Pi running indi server, then connecting to it with my Windows 10 laptop and running the the solver api on the laptop.
  10. Hi there folks, I just wanted to let you know that I've just released a "lite" version of the astrometry.net API. The aim of this little project was to create a simpler solution for those that need the API (but not the fluff on top of it that Nova provides) and perhaps have the need or desire to run it locally, or to set up a copy of the solver service. I know some people may have trouble running the solver on their own machines (Windows), or the software they use simply need to use the interface the API provides - this is designed to tackle that problem. Personally I already found a use
  11. Thanks! Although I'm suspecting there's not much that can be done. I suspect the light areas are a reflection of some light. I'm not sure what you mean by unstretched masters - these are the master frames, calibrated with biases, darks and flats. What do you need?
  12. I'm practicing this fine art of processing at the moment and yesterday I captured a sample set of frames from my balcony, inside light polluted city center. Took them with 2x2 binning since I wanted to get some decent amount of material to work with in the tight time window I had. The result was a bit disappointing but I'd still like to see what can be salvaged of this little endeavor. I'm hoping to get some processing tips with PixInsight. Here's a quick peek of what I've got: This is after combining the LRGB masters and the output of STF. As you can see there's a lot of w
  13. A bit of a late reply but since I've been in the same situation here's my 2 cents. I started out with a Canon 1100D that I already owned for general purpose photography. A few months back after a long consideration I bought a C9.25 SCT, my first telescope, mostly for eyeballing but with the idea of maybe getting into astrophotography later, so I also bought the T2 thread for Canon cameras and a T2 adapter (like this one http://www.astroshop.eu/projection-adapter/omegon-camera-adapter-1-25-/p,1250) that allowed me to place eyepieces inside the adapter and then connect it to the camera & OTA
  14. I've been looking at the options now and I'll probably go with the TS INED 70mm scope Chris linked. Also I've decided to get the Atik 414EX as it's 60% more sensitive than the 314L+ and the price difference isn't that big. Now I just need to figure out which set of filters to get but things are locking into place now. The FOV calculator gives a pleasant field of view. F ratio: Focal Length: Field of view: Resolution: f6 420mm 1.22° x 0.92° 3.17"/pixel Unless someone comes and tells me I'm making a terrible mistake I'll probably go with this
  15. Forgot to mention, it's a CCD camera I'm planning to get, Atik 414EX Mono to be precise.
×
×
  • 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.