×

INDI Library v1.8.9 Released (01 Mar 2021)

INDI monthly update. In addition to driver improvements, major code refactoring is in progress by @pawel-soja to modernize and improve INDI aging code.

New forum users, please go here first: indilib.org/forum/new-forum-users.html

How to set up Ekos for 2 scopes and 2 cameras on the same mount

  • Posts: 480
  • Thank you received: 53
Hi!

I've been using a side-by-side setup for a while, and would want to utilize it better. This is the current situation:

One Losmandy G11 (mount)
One refractor with a Moonlight focuser (scope 1)
A guidescope with Lodestar (guidescope)
One C8 with a Moonlight focuser (scope 2)
One R-Pi4 (Stellarmate)

What I do now, is to manually switch between the scopes. That is, for swithcing from scope 1 to scope 2, I shut down Ekos and Indi, attach the relevant USB-cables and disconnect the one's I don't want. (if both moonlights are connected, there are strange things happening).

What I would want:
To be able to set up a Scheduler sequence, where I first execute a job on Scope 1, and then a job on Scope 2. (I am currently not using them in parallell, they are not that well aligned either).

My idea has been to attach a second R-Pi to control Scope 2. But if I do, how on earth could I set up a Scheduler sequence that uses Scope 2 (attached to R-Pi number 2) AND control the mount and the guiding (attached to R-Pi number 1)?

Or else - if I could just attach all things (Scope 1, Scope 2, including both focusers, and the guidescope, and the mount) to just one R-Pi and run in the same Ekos session - how then, could I tell scheduler/capture model which scope and focuser to use? Currently, neither Sequencer nor Capture module seems to have a way to switch main scopes, so to speak. They use whatever I have set up in the beginning.

I'd be grateful for any advice and your experiences on this. I am probably missing some easy solutions and overseeing possibilities... so any advice is very welcome.

Magnus

Celestron C8, Skywatcher 100 ED Pro
Losmandy G11
Atik 383L+, ASI294
6 months 4 weeks ago #60325

Please Log in or Create an account to join the conversation.

  • Posts: 113
  • Thank you received: 14
You can run indi on 2 RPis. I think this tutorial might help.

Indi on multiple devices
When you run RPi 2, that does not have the mount connected to it, you use the procedure described in the link. Otherwise, you have everything on the same RPi.
Run ekos for scope/camera 1 on RPi 1, and for scope/camera 2 on RPi 2. Two instances of Ekos, but you only use one at a time of course.
Wim

Opticron Oregon 15*70, Skywatcher 150PDS + ST80, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI174MM-Cool + Pentax K20D (retired) + ZWO ASI120MM, homemade ditherbox, PixInsight, Rock64 x 2 with INDI & PHD2, cloud cover

www.astrobin.com/users/wimvb/
The following user(s) said Thank You: mlarsson, glundby
Last edit: 6 months 3 weeks ago by wimvb.
6 months 3 weeks ago #60355

Please Log in or Create an account to join the conversation.

  • Posts: 480
  • Thank you received: 53
Hi!

Thanks! This works nicely this far. And I realized I set the camera in the Capture module, meaning that each job has a dedicated camera, and now it switches nicely between them! SO far so godd!!

Only problem left is the focuser. How do I make sure the correct camera/focuser combination is used in the Focuser module? States differently: how do the Focuser modul know which camera and which focuser to use?

Connected to that: both focusers are now called Moonlight. How can I give them different names?

Magnus

Celestron C8, Skywatcher 100 ED Pro
Losmandy G11
Atik 383L+, ASI294
6 months 3 weeks ago #60462

Please Log in or Create an account to join the conversation.

  • Posts: 1902
  • Thank you received: 410
Also be careful with dithering ;-)
Wouter van Reeven

ASI6200 and 7 slot 2" filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and 5 slot 1.25" filter wheel with an 8" TS Ritchey-Chrétien on a SkyWatcher EQ6-R
The following user(s) said Thank You: glundby
6 months 3 weeks ago #60464

Please Log in or Create an account to join the conversation.

  • Posts: 480
  • Thank you received: 53
Hi!
Yes, my plan is to use one camera at the time.... then dithering would work, right?

But I need to solve the focuser issue - how to make sure the right camera and right focuser do the focusing... I don't get that.

Magnus

Celestron C8, Skywatcher 100 ED Pro
Losmandy G11
Atik 383L+, ASI294
6 months 3 weeks ago #60467

Please Log in or Create an account to join the conversation.

  • Posts: 1902
  • Thank you received: 410
Yes, one camera at a time should be fine.
Regarding the focuser issue: how about creating aliases and using those? If you search on this forum then you should find several posts in which Jasem explains how to do that.
Wouter van Reeven

ASI6200 and 7 slot 2" filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and 5 slot 1.25" filter wheel with an 8" TS Ritchey-Chrétien on a SkyWatcher EQ6-R
The following user(s) said Thank You: mlarsson
6 months 3 weeks ago #60475

Please Log in or Create an account to join the conversation.

  • Posts: 480
  • Thank you received: 53
Hi!

Yes, I'll solve that, creating aliases (I guess).

But then: maybe not a problem and I haven't tested it, but how would the focuser module know which camera to focus with at a particular time, and even more, which focuser? I realize that the capture sequence specifies the camera - is that "carried over" to the focuser, or does the focuser use the last camera used (in which case it will be the wrong camera when shifting)? But nowhere do I specify which focuser is to be linked to which camera....?

Magnus

Celestron C8, Skywatcher 100 ED Pro
Losmandy G11
Atik 383L+, ASI294
Last edit: 6 months 3 weeks ago by mlarsson.
6 months 3 weeks ago #60483

Please Log in or Create an account to join the conversation.

  • Posts: 113
  • Thank you received: 14
If you go into the details of the lsusb command, you can extract info on each focuser which makes it unique, sometimes a serial nr. You can then use that to identify each focuser. But I must admit, I have never had to use that. Usually, vendor id and device id are enough to identify a device uniquely. The info you need should be in the tutorial.
I believe (but am not sure) that the combination of port mapping/binding and aliases solves your problem.
Wim

Opticron Oregon 15*70, Skywatcher 150PDS + ST80, AZ-EQ6 GT + EQ3-2 Goto, ZWO ASI174MM-Cool + Pentax K20D (retired) + ZWO ASI120MM, homemade ditherbox, PixInsight, Rock64 x 2 with INDI & PHD2, cloud cover

www.astrobin.com/users/wimvb/
Last edit: 6 months 3 weeks ago by wimvb.
6 months 3 weeks ago #60491

Please Log in or Create an account to join the conversation.

  • Posts: 480
  • Thank you received: 53
Hi!

Thanks for you advice.

But... :)

First, the persistent port mapping: It turns out my two Moonlight controllers (MyFocuserPro, actually, version 1, but running on the Moonlight protocol) has exactly the same serial header:

udevadm info -a -n /dev/ttyUSB0 | grep '{serial}' | head -n1
ATTRS{serial}=="0000000A0005"

and

udevadm info -a -n /dev/ttyUSB1 | grep '{serial}' | head -n1
ATTRS{serial}=="0000000A0005"

So how can I do a persistant port mapping now.....?

Secondly, I still do not see how this solves the Ekos challenge of Focuser module knowing which of them to use. All the cases I have seen here, only use one focuser, but someone must use two.....? (there was a discussion of N-camera setup in an earlier thread but as I saw it, no real solution)

Magnus

Celestron C8, Skywatcher 100 ED Pro
Losmandy G11
Atik 383L+, ASI294
6 months 3 weeks ago #60500

Please Log in or Create an account to join the conversation.

  • Posts: 1073
  • Thank you received: 187

mlarsson wrote: Hi!
What I would want:
To be able to set up a Scheduler sequence, where I first execute a job on Scope 1, and then a job on Scope 2. (I am currently not using them in parallell, they are not that well aligned either).


I'm not an expert with the scheduler. But I believe when creating jobs you can choose a specific equipment profile for it. So I would try creating separate profiles for scope 1 and scope 2 and assign them to their respective jobs in the queue.
You will still have to resolve the identity of your moonlight focusers. But one trick may involve using the Custom Drivers feature under Tools>Devices to create a uniquely named driver for the second scope. You should then be able to save its own configuration, such as unique serial port mapping for the custom INDI Driver.

I think it is doable. At least when not used at the same time.
INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
PHD2
Waveshare Stepper Motor Board - DIY Focuser
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.
6 months 3 weeks ago #60504

Please Log in or Create an account to join the conversation.

  • Posts: 480
  • Thank you received: 53
Hi!

Thanks! That makes sense. The profiles then would only include one camera and one focuser, so matching focuser and camera would be solved :) Great, a step forward. I had not noticed this possibilty!

Remains then how to persistently match focusers to drivers - when their serial headers are identical... hrm... work around that? :)

Magnus

Celestron C8, Skywatcher 100 ED Pro
Losmandy G11
Atik 383L+, ASI294
6 months 3 weeks ago #60508

Please Log in or Create an account to join the conversation.

  • Posts: 1073
  • Thank you received: 187
When you run lsusb. Do they also have the same Vender ID and Product ID?
I expect they do, but it's not a guarantee if they made revisions.
INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
PHD2
Waveshare Stepper Motor Board - DIY Focuser
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.
6 months 3 weeks ago #60526

Please Log in or Create an account to join the conversation.

Time to create page: 1.090 seconds