×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

[ANSWERED] Multiple ZWO Devices Components throught USB

  • Posts: 106
  • Thank you received: 11
Components: I will soon be using a ZWO ASI1600MM-Cooled, a ZWO EFW Filter Wheel and a ZWO ASI120MM Guide Camera ALL of which are connected via a single USB cable from the ASI1600MM-C to a Raspberry Pi 3.

For the indiserver do I need to start two instances of indi_asi_ccd driver?

Example: indiserver -m 100 -v indi_asi_ccd indi_asi_wheel indi_asi_ccd

Should I connect the ASI cameras to the Rpi3 separately to first create their individual config files and only then start two instances of the driver?
Skywatcher 190MN - EQ6 Pro (with Belt Mod) - ASI1600MM-Cooled - ASI EFW7 - ASI120MM - WO f4 Guide Scope - Rigel nStep - KStars/Ekos - KDE - PixInsight
Last edit: 6 years 11 months ago by Keith Cobby. Reason: Updated
6 years 11 months ago #16218

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

Just this:

indiserver -v indi_asi_ccd indi_asi_wheel
6 years 11 months ago #16220

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

  • Posts: 106
  • Thank you received: 11
Ok great thanks. What does the -m 100 mean? Is it concurrently connection?
Skywatcher 190MN - EQ6 Pro (with Belt Mod) - ASI1600MM-Cooled - ASI EFW7 - ASI120MM - WO f4 Guide Scope - Rigel nStep - KStars/Ekos - KDE - PixInsight
6 years 11 months ago #16221

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

It's how many MBs behind the driver can lag before it disconnects, by default it's 128MB now so putting -m 100 is actually worse. Just do not use that option unless you want to use a larger value for some reason.
The following user(s) said Thank You: Keith Cobby
6 years 11 months ago #16223

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

Time to create page: 0.228 seconds