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.

Gina

Thoughts on which imaging rigs to concentrate on

Recommended Posts

Flame and Horse's Head in Orion with 200mm f4 lens and 400mm f5 Esprit 80ED scope.

1407715606_Screenshotfrom2020-01-3116-20-40.png.4fc9e6a11e93657806678cf2b985ae6d.png

1870010342_Screenshotfrom2020-01-3116-18-23.png.7e2357d71fd683d53bdd59fab402494c.png

Edited by Gina

Share this post


Link to post
Share on other sites

M42 will fit nicely in the FoV of the Esprit.

1467026639_Screenshotfrom2020-01-3116-26-29.png.0eb7264129cb87f4458fddfea2d9b85f.png

Share this post


Link to post
Share on other sites

Returning to the Heart and Soul, while these didn't fare well as a pair with the dual lenses, they do work as separate objects in the 200mm lens and Esprit 400mm scope.  The Esprit can be "twinned" with an ST80 for a dual imaging rig.

2062568931_Screenshotfrom2020-01-3116-36-30.png.48d4b9163c97800821fd43cd4b2c1fd0.png

406221255_Screenshotfrom2020-01-3116-37-54.png.61f5c6ec3a0b1ab8c95fabd27abe7bc4.png

Edited by Gina

Share this post


Link to post
Share on other sites

With the camera turned 70° rather than 90° the framing for the Heart Nebula is much better.

1038553239_Screenshotfrom2020-01-3116-46-16.png.8140f4877439ab8a01a1788a2f660be4.png

Share this post


Link to post
Share on other sites

Now I want to sort out how to arrange dual imaging rigs and guiding.

With telescopes it's clear - one on each mount of the dual mounting bar.  Though I have just the one Esprit 80ED, the humble ST80 is same focal length and an achromatic scope is alright for NB with the very narrow wavebands, so an ST80 is adequate second imager.  I also have a pair of Evostar ED80s both with focal reducer/flattener.  The FL becomes 510mm and f6.37.  In either case one scope can have an OAG for guiding.

Edited by Gina

Share this post


Link to post
Share on other sites

With widefield imaging rigs it's not so clear-cut.  My earlier thought was to make a double bracket to take two cameras side by side but now I have the dual mounting bar there's a simpler option.  Copy the current WF imaging rig and put one on each mount.  One can use the 8 position ZWO filter wheel and the other the ZWO EFWmini with 5 positions. 

There then remains the question of guiding.  Seems an OAG is not practical with lenses.  Reason is that the back-focus of these vintage film SLR lenses is 45mm whereas that of the FF is 55mm.  This means the distance from OAG prism to sensor is only 30mm rather than 40mm and the guide camera can't be got close enough to focus.

Edited by Gina

Share this post


Link to post
Share on other sites

Gina I think a triple rig would be ideal 😉

Watch as moths fly out of Gina's purse

image.png

Edited by Mick H
  • Haha 1

Share this post


Link to post
Share on other sites

Another rethink on arrangement for dual imaging with guiding, resulting from a suggestion from Wim, for which I'm grateful.

I now plan to use a 15" Losmandy-style dovetail bar at 90 degrees to normal with an imaging rig at each ends and guider in the middle.  This photo shows the arrangement though with just one imaging rig ATM.

1973226716_GuidingNewSetup01.JPG.7aed2abdf3d08cba04ccd06ba3081a25.JPG

Edited by Gina

Share this post


Link to post
Share on other sites

Had similar but larger scale on the iEQ45 once, helps with balancing as  you can slide the bar sideways.

Dave

iEQ45-Triple.thumb.png.3957d8303ad16f57f9bb5185c5e4650c.png

 

  • Like 1

Share this post


Link to post
Share on other sites

Since Ekos can only handle one imaging system currently, separate instances of KStars/Ekos are needed to handle dual imaging.  It does handle a separate camera for guiding.  Each imaging camera will have it's own RPi for capture and focussing the lens.  These will have different Computer Names for identification from KStars/Ekos.  Each will have it's own Ethernet connection from an Ethernet switch on the pier.  One RPi unit will just connect to camera and focuser whilst the other will also connect to the mount and guide camera.  It isn't considered necessary to provide remote focussing for the guide system.

My experience with dew heaters has shown that (at least in winter) I never run with the dew heater turned off so I see no need to have remote dew heater control.  If I don't want dew heater control, it will simplify both hardware and software.  The current WF rig does have this control but the second RPi and HAT can do without it.  I can just ignore the dew heater control on the current RPi control unit and connect the dew heater directly to the 13.8v supply.  In other words all three dew heater would be connected to the main supply via a fuse and maybe a toggle switch (or I could simply remove the fuse if dew heaters are not needed).

The photos below show the RPi plus HAT (Hardware Attached on Top) which was originally designed for use with the Esprit 80ED Pro telescope but now used with the WF rig.

Electronics.JPG

270987098_Screenshotfrom2020-02-0411-46-10.png.f6b5ef498c0d8cf1354632f71893248a.png

Share this post


Link to post
Share on other sites

Since Ekos can only handle one imaging system currently, separate instances of KStars/Ekos are needed to handle dual imaging.  It does handle a separate camera for guiding.  Each imaging camera will have it's own RPi for capture and focussing the lens.  These will have different Computer Names for identification from KStars/Ekos.  Each will have it's own Ethernet connection from an Ethernet switch on the pier.  One RPi unit will just connect to camera and focuser whilst the other will also connect to the mount and guide camera.  It isn't considered necessary to provide remote focussing for the guide system.

My experience with dew heaters has shown that (at least in winter) I never run with the dew heater turned off so I see no need to have remote dew heater control.  If I don't want dew heater control, it will simplify both hardware and software.  The current WF rig does have this control but the second RPi and HAT can do without it.  I can just ignore the dew heater control on the current RPi control unit and connect the dew heater directly to the 13.8v supply.  In other words all three dew heater would be connected to the main supply via a fuse and maybe a toggle switch (or I could simply remove the fuse if dew heaters are not needed).

The photos below show the RPi plus HAT (Hardware Attached on Top) which was originally designed for use with the Esprit 80ED Pro telescope but now used with the WF rig.

Electronics.JPG

270987098_Screenshotfrom2020-02-0411-46-10.png.f6b5ef498c0d8cf1354632f71893248a.png

Edited by Gina

Share this post


Link to post
Share on other sites

Seems to be an intermittent problem with the ASI120MC-S that I'm using for guiding.  It shows as changing between a normal image and this

1472493298_Screenshotfrom2020-02-0413-29-43.png.7f3a911deda059dd0a32ef4e100c4404.png

The rig is pointing southwards to a far hill with trees and the wiggly line is where the land/trees meet the sky.

Edited by Gina

Share this post


Link to post
Share on other sites
1 hour ago, Gina said:

Since Ekos can only handle one imaging system currently, separate instances of KStars/Ekos are needed to handle dual imaging.  It does handle a separate camera for guiding.

Do you run ekos on the Pi, or on a laptop/pc? Whatever you use, you can control the other camera from pixinsight. Just connect to the remote pi, and use the ccd process. It's fairly straightforward. 

Share this post


Link to post
Share on other sites
1 hour ago, Gina said:

Seems to be an intermittent problem with the ASI120MC-S that I'm using for guiding.  It shows as changing between a normal image and this

1472493298_Screenshotfrom2020-02-0413-29-43.png.7f3a911deda059dd0a32ef4e100c4404.png

The rig is pointing southwards to a far hill with trees and the wiggly line is where the land/trees meet the sky.

Strange. Could it be thrown off by the overall brightness? How does it perform when it's darker? 

Share this post


Link to post
Share on other sites
3 minutes ago, wimvb said:

Do you run ekos on the Pi, or on a laptop/pc? Whatever you use, you can control the other camera from pixinsight. Just connect to the remote pi, and use the ccd process. It's fairly straightforward. 

I run Ekos on my Linux Mint tower indoors.  I have been on the INDI forum and got info direct from the author.  I want to use Ekos for autofocus and plate solving etc. 

Share this post


Link to post
Share on other sites
6 minutes ago, wimvb said:

Strange. Could it be thrown off by the overall brightness? How does it perform when it's darker? 

I don't know how it performs when it's darker as I've only been testing for an hour or so.  Exposure does seem to be very critical.

Edited by Gina

Share this post


Link to post
Share on other sites

Ok. Pixinsight can do platesolving of course, but not autofocus. It seems that development of the INDI modules in PI has stalled. 

Share this post


Link to post
Share on other sites

I have been investigating connections as these are a common cause of intermittent faults.  Compared the USB3 input port on the ASI16000 camera with that on the ASi120.

 

1670678203_USB301.JPG.d0cd77937ad30ce64f96d45d9ad73592.JPG

1831094575_USB302.JPG.542ee0a316d3fae4ecf14395e02d40f3.JPG

 

Share this post


Link to post
Share on other sites

As far as I am aware you can Virtual Linux on the same Mint Tower - subject to memory and processor speeds and run either Ekos/Kstars or CCDciel in the virtual set up. Will still need 2 RPI running Indiserver.

OR

YOU MIGHT just be able to run CCDCIEL + Ekos on the Tower (No virtualisation needed) and have 2 RPI running Indiserver.  One Indiserver would run Mount,guiding,platesolving,camera A,focusing while the other would just run Mount simulator , Camera B and Focusing.  You just point Ekos and CCDCIEL to different Indiserver IP addresses.  This should work as I think the Indiserver  config files are held on the Indiserver computer (i.e. not the tower).  Thats the theory 🙂

Share this post


Link to post
Share on other sites

Urk, that doesn't look good. I had problems with a SX FW some years ago that turned out to be a missing centre block, though the contacts were still there. Sent it off to SX for repair and everything was OK afterwards.

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, Gina said:

1831094575_USB302.JPG.542ee0a316d3fae4ecf14395e02d40f3.JPG

 

That doesn't look great :(

I wouldn't have thought it would be too hard to replace though?

James

  • Like 1

Share this post


Link to post
Share on other sites

I'll take a look tomorrow.

Share this post


Link to post
Share on other sites
3 hours ago, stash_old said:

Will still need 2 RPI running Indiserver.

 

3 hours ago, stash_old said:

One Indiserver would run Mount,guiding,platesolving,camera A,focusing while the other would just run Mount simulator , Camera B and Focusing

Is this really necessary? Indi is distributed, ie N x M solution with any number of servers and any number of clients. I haven't tested this, but I wouldn't be surprised if only one rpi is needed.

Also, check this link

https://indilib.org/develop/developer-manual/100-3rd-party-drivers.html

Edited by wimvb

Share this post


Link to post
Share on other sites
3 hours ago, wimvb said:

 

Is this really necessary? Indi is distributed, ie N x M solution with any number of servers and any number of clients. I haven't tested this, but I wouldn't be surprised if only one rpi is needed.

Also, check this link

https://indilib.org/develop/developer-manual/100-3rd-party-drivers.html

Gina said "Since Ekos can only handle one imaging system currently, separate instances of KStars/Ekos are needed to handle dual imaging.  It does handle a separate camera for guiding.  Each imaging camera will have it's own RPi for capture and focussing the lens." and I concur that if you want to run 2 concurrent imaging camera's (i.e. NOT 1 imaging and 1 guiding which is ok) it is my understanding that is not possible at the moment because of Ekos !- perhaps  @RadekK could confirm or deny this !

You can as you point out run many Indiservers in a "Chain" but there will be one master and the rest will be slaves as I understand it - I have done "chaining" using multiple PI's and this works. In effect Ekos thinks its talking to one Server as I understand the chaining process.

Ok the master server can contain many devices and Kstars/Ekos has a profile so the 2 Kstars/ekos would have different devices defined in the active profile.   The following mentions this and Gina was part of the discussion and I presume had further PM's with the Dev's.

https://indilib.org/forum/ccds-dslrs/4256-multiple-imaging-camera-s.html 

Easy test Gina could run 2 Ekos/Kstars Plus 1 Indiserver with all the devices set up  🙂 

Dont know if anyone has done it it yet

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By javaruba
      Hi folks,
      I've been seeing tear drop shape stars with the EdgeHd 8 and ZWO ASI294MC Pro camera, so I verified the collimation. I'm using a celestron x0.7 reducer.
      Does collimation needs to be checked  with an eyepiece or with the camera and with or without reducer? I'm asking since I verified my collimation yesterday and couldn't see the concentric rings with the complete imaging train (ASI294MC, OAG, and x0.7 reducer). It was only showing the inner shadow and outer circle. I than  replaced the AS294MC with my guide cam (ASI120) which has a much smaller sensor and could see many rings. While, to my view, it seems to be collimated, it's strange that I can't see the rings with the main imaging cam. Any thoughts? Here's how I left the collimation after some adjustments with the guide cam.

      Kind regards,
      Jairo
    • By ChrisBAgile
      I'm brand new to the forum and new to Astro. I've been loving it since January and learnt a huge amount by myself with the help of forums like these.
      I recently purchased an iOptron 10" RC truss. 3" focuser with a 2" compression. I have been using a WO FLT 132 before this which is little more forgiving. I have attached a couple of pictures from my first attempts. I am not using a field flattener at this point. (just getting used to collimating and setting up). Camera ZWO ASI 6200 MC cooled camera. The images below are composed of 50 x 5 minute subs stacked in pixinsight with basic image processing. I'm using PHD II and a WO guidestar 61 and ASI 120 for guiding on a CEM60EC mount. Drift alignment in PHD 2. Any ideas as to the main causes of egg shaped stars? Could this be sensor tilt? crappy guiding? Focus also looks off? Any help appreciated please
       


    • By Adaaam75
      Hi guys,
      So on Tuesday night I spent the evening imaging the moon with my Celestron 9.25 SCT and DSLR as shown below and am happy with the images I collated (I only took images as I did intend to take capture video but I got carried away and time was getting on).
      I have approx 350 jpeg (and the equivalent in raw) images and have used the Microsoft image composite editor to stitch the frames together without editing them first etc but I wonder if I'm going the images an injustice?
      I'm not ready to pay for editing software as I know there is a lot of very good free downloads out there and I'm asking for recommendations. Should I be processing the frames before/after stitching and what software would you recommend? Please offer any advice you have.
      I will post the resulting image once I'm happy with the outcome 😁
      Thanks in advance!
       
    • By Adaaam75
      Hi guys,
      So on Tuesday night I spent the evening imaging the moon with my Celestron 9.25 SCT and DSLR as shown below and am happy with the images I collated (I only took images as I did intend to take capture video but I got carried away and time was getting on).
      I have approx 350 jpeg (and the equivalent in raw) images and have used the Microsoft image composite editor to stitch the frames together without editing them first etc but I wonder if I'm going the images an injustice?
      I'm not ready to pay for editing software as I know there is a lot of very good free downloads out there and I'm asking for recommendations. Should I be processing the frames before/after stitching and what software would you recommend? Please offer any advice you have.
      I will post the resulting image once I'm happy with the outcome 😁
      Thanks in advance,
       

    • By jadcx
      Hi
      I feel as though I see a steady stream of images along the lines of “I just held my phone up to the eyepiece”.  Now either I’m absolutely missing something (which is definitely possible) or there is considerably more luck/effort in those images than inferred.
      I have an iPhone, and seem to have two significant problems using it to grab any kind of useful image. And no, I’m not expecting it to rival a dedicated imaging rig. Firstly, alignment is very difficult. And secondly, focus seems to be impossible. I have one of the Celestron NexYZ phone mounts, which is less steady than I expected but I can eventually get the camera aligned with the eyepiece. But I’ve never managed to get focus. I’ve tried the default camera app as well a dedicated one with more manual control. I’m failing.
      Overall this is not a significant impediment to my observing.  But it would be great to be able to get some reference shots to go with my observing notes. Does anyone have any tips?
×
×
  • Create New...

Important Information

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