Jump to content



  • Posts

  • Joined

  • Last visited

Everything posted by AstroMuni

  1. I like your keen nature to deal with challenges There is a lot to learn so I didnt take that route when I started a year ago. I went for the bright DSOs (see my journey in the link attached to my signature). With small exposures you can get a lot of detail from these brighter objects and then comes the challenge of learning to process them. I have just recently purchased a guide scope and hoping to get longer exposures when clouds clear....a long wait in this country it looks like.
  2. Hi @alacant, Nice shot. I notice there is some haze around the stars. Not sure if this is due to image convertion due to upload or just my screen
  3. Looking at the FLO page for this https://www.firstlightoptics.com/telescopes-in-stock/skywatcher-explorer-130.html you can see their comparison of 130 vs 130P. Choose between the two depending on your plans going forward. As others have already said, if you can get a sturdier mount then go for it. And also look at Dobsonions. Skywatcher/Orion do have several good ones with similar apertures. And as budget is a concern, look out for second hand ones too
  4. hi, Welcome to SGL. It would help us if you let us know more details about your new telescope - model, lenses used etc.
  5. Its all the wonderful gulf stream that runs past our island
  6. I have the ASI224mc as main camera and recently purchased the ASI120mm mini for guiding. These are connected to the RPi and I remotely access these from my laptop running Ekos. The connection to these seems to a bit of hit and miss. There are times when they launch beautifully and there are others when only one of them or none will connect. I have tried with the ZWO CCD driver and using the ZWO Camera 1, 2 drivers I have ALSO tried using Kstars on RPi and connecting with a local connection and with same results. As the ASI224 supports USB3 and ASI120 mini only works on USB2, I tried connecting these to various USB ports on the RPi 4b with similar results. RPi is using Astroberry v2.0.4 build so has the INDI drivers from v1.9.3 is my understanding. My laptop is running Kstars/Ekos 3.5.6. Any help is appreciated!
  7. You should be able to get near focus in daylight. If thats not working then it will be quite challenging at night. Thats my experience. During daytime use a very low exposure less than a sec.
  8. This is tutorial for SIRIL a free software. I know you are trying to use PS but this gives you an idea of sequence of operations. https://siril.org/tutorials/tuto-scripts/ Several folk here use SIRIL to do the initial stretching etc and then do the final processing in PS.
  9. Take a look at Skeye app which has a Push-To capability. Using this you should be able to get your scope close to where you wish to be. Final steps would need to be done using your finder scope or red dot finder. Its not as bad as it looks though, you should be able to capture atleast the brighter galaxies using short exposures (even as low as 5sec) without tracking. Once you have cracked that bit, you can then send those images to stacking software. Good luck.
  10. What I was suggesting is just an extension of this wherein you have a hub to which the cameras are connected and a cable running from hub to your laptop (albeit a long one ). This to me is the simplest solution as there is no introduction of additional software in the middle. You could connect the mount to the hub as well, but as you've pointed out, you are able to use Wifi connectivity for that. The RPi solution using INDIGO/ ALPACA seems to be viable. So good luck with that. My reason for asking what RPi is used for was because with the RPi running INDIGO it would seem that all the grunt work is still being done on laptop and RPi just becomes a mediator between INDIGO & ASCOM.
  11. Perhaps I havent understood this fully. How do you connect laptop to cameras now?
  12. What are you planning to use the RPi for? In your case it sounds like a powered USB hub that is located outside connected by USB cable to laptop would do the trick. I dont have a solution off hand on how to bypass the USB cable to laptop (ie wireless), but I am sure there are ways around this.
  13. My suggestion is try the INDI/INDIGO drivers. If you have trouble then try ASCOM route. As INDI/INDIGO is running on RPi, as per my understanding, all that ALPACA will do is create a bridge to ASCOM drivers running on a Windows box. That sounds like additional traffic back & forth RPi. Happy to be corrected on ALPACA. What agents are you referring to? All that runs for me on RPi is INDI server and it will initiate loading of relevant drivers. Nothing else is running there at the moment. Now that I have a guidescope, I may consider using PHD2 to run from RPi at some point (as that will be closer to. mount, guidecam) Ekos internal guider works just fine for the moment.
  14. I am viewing my laptop screen so it works fine. The more your resolution the slower it would get to screen grab
  15. @vlaiv as you are using RPi, INDIGO or INDI seem to be the way to go. As to what software you use on laptop you have a choice of CCD Ciel, etc. EDIT: And if INDIGO drivers dont work you have the fallback of using INDI drivers as INDIGO is meant to be compatible with INDI
  16. I use Team viewer to see my laptop screen on my phone while I am focusing. Ekos has a polar alignment assistant which you can use in same way.
  17. I use Kstars/Ekos on laptop connected to INDI server on RPi. With Ekos there is option to test platesolving using an older image so you can test the whole kit inside. Caveat: It will slew the scope but its attempt to platesolve again to check if object in centred will fail PS: I did evaluate INDIGO but the Kstars/Ekos combo just ticked all the boxes for me. Its stellarium + capture + platesolve + control of mount etc.
  18. I have been consistently told by my colleagues in my local society that IR/UV cut filter is essential to get clearer images for both planetary and DSO when using my camera (ASI224mc) as its highly sensitive to IR & UV. I have recently bought one but dont have any comparisons to show you as its been cloudy since
  19. Hi Brendan, I have a scope with similar focal length/aperture (650/130) and I bought the Astro Essentials 32mm guidescope just last week to go with it. Works well ( I tried guiding & platesolving) during the one night that I managed to get with clear skies. I use the ASI224mc on main scope & ASI120mm mini on guider. The suggested ratio (based on lots of reading up ) is 5:1 FL between main & guide, hence went for a guidescope of around 130mm FL.
  20. @velis dont be too disheartened by the bird-jones comments. I have the 130eq which is a slightly bigger version of what you have. It has a slightly better reputation I guess but not too far off I got mine collimated with help from a friend and its worked well for me. Do NOT expect to view with high magnifications but it should do a lovely job for viewing DSO and star clusters. As others have said the mount is its weakest point so I used to attach sandbags/milk bottles filled with water etc. to stablise it. I decided to take the plunge into astrophotography after I upgraded my mount and was pleasantly surprised with the results (see link in my signature). Good luck.
  21. I am thinking a dormer with an opening on the flat roof would work perhaps?
  22. I have acquired my first guide scope and managed to attach it to the screw thread provided for attaching camera to top of tube rings. Had a few discussions with FLO who were very helpful. Also my local astro society were equally helpful in choosing the right scope etc. Now to practice taking images with guiding. Fingers crossed.
  23. Its works perfectly if I connect both to the the USB3 ports on RPi. I cant use the ASCOM drivers as I am Linux based. And for completeness the ZWO CCD driver supports multiple cameras at same time. The ZWO Camera 1, 2, 3 are for users who have issues with that driver and these support only a single device each.
  24. Hi, I updated my RPi 4 to latest version of astroberry v2.0.4 today and been trying to connect my main ASI224mc and ASI120mm mini guide cameras in Ekos. When I connect both the cameras on the USB2 ports only one of them i.e. ASI120mm connects. If I connect the ASI224mc on the USB3 and ASI120mm to USB2 again its only the ASI120 that connects. But if I connect both on the USB3 ports on the RPi it connects successfully. I have tried with the ZWO CCD driver and using a combination of ZWO Camera 1, ZWO Camera 2 drivers. In both cases the behaviour is the same. It works fine on my Linux Mint laptop using direct connection to the cameras even though the USB ports are USB2 only. Both RPi and Linux are running Kstars 3.5.5 stable. Any ideas what is the cause of this?
  25. Find out the light pollution at your location using https://www.lightpollutionmap.info. Then in stellarium you can set the bortle level for your location and that should help give an idea of the kind of skies you can see. Its not always very accurate but you atleast get some idea. I am sure skysafari has similar feature.
  • 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.