×

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

Bi-monthly release with minor bug fixes and improvements

Multiple identical CCD cameras interfacing with Ekos via INDI

  • Posts: 2
  • Thank you received: 0
I have two ZWO ASI 120MM Mini cameras, one used for auto guiding and the other (for now) for photographs until I get a deep sky camera. Ekos can interface perfectly over INDI to my mount, GPS and either one of the cameras, but cannot differentiate between the two identical cameras when both are connected.

I can see from the Indi_asi_ccd driver logs that the 3rd party ZWO ASI CCD driver can see that there are two cameras presumably using the USB identifiers. The ASI function ASIGetNumOfConnectedCameras() returns 2 cameras and the driver XML lists both. However, both of the cameras are assigned device="ZWO CCD ASI120MM Mini".

Ekos Logs however show:
- ZWO CCD ASI120MM Mini is connected.
- 1 devices connected out of 1
- All INDI devices are now connected.

I assume if I had two different cameras as is more normal configuration, I would have a different device name, and viola. As I am new to Ekos and Indi, can anyone tell me if there is some configuration settings in Ekos, Indi, driver etc that I have not done that would allow me to use two identical cameras and allow me to make one my auto guider and the other the main photography camera?

Thanks in advance.
Rod
5 years 4 months ago #31278
Attachments:

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

  • Posts: 1029
  • Thank you received: 301
I'm not sure how zwo drivers work, but shouldn't you be instantiating two indi_asi_ccd drivers instead of one? If that works and you see two (different) devices, in a second step you should be able to assign your driver instances a different name with a command line option.

-Eric
The following user(s) said Thank You: Rodney Whitford
5 years 4 months ago #31279

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

I just fixed this in GIT. It will rename the 2nd one to XXX 2..etc. Please wait for nightly or compile from GIT and report back.
The following user(s) said Thank You: Eric, Rodney Whitford
5 years 4 months ago #31281

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

  • Posts: 220
  • Thank you received: 27
The cameras normally can be distinguised by their serian number, unless the USB2 versions dont report a serial number. (Can someone check that?)


Regards,

Paul
The following user(s) said Thank You: Rodney Whitford
5 years 4 months ago #31304
Attachments:

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

  • Posts: 2
  • Thank you received: 0
I downloaded the v1.7.5 code from GitHub and rebuilt. Test was as follows:
- Two ZWO ASI 120MM Mini cameras plugged into to Indi server.
- Both cameras were detected and displayed now on the Ekos Window. Two tabs were shown.
- Tab 1 was named "ZWO CCD ASI120MM Mini"
- Tab 2 was named "ZWO CCD ASI120MM Mini 2"

Observed the following:
- Order of the tabs on Ekos was different. Eg. first tab on Camera "ZWO CCD ASI120MM Mini" is "Main Control". However on "ZWO CCD ASI120MM Mini 2" first tab is "Options"
- RadioButtons for "Debug Levels", "Logging Levels" and "Log Output" is only on Mini 2 camera
- Observed numerical data such as temperature is updating and of different values as would be expected.
- Took a photo and confirmed that each camera can be commanded individually.

I will test the code changes more tomorrow as it is a bit late now, but it all looks great.

Thankyou so much for such an incredibly responsive fix to my problem exp. since my setup was probably a bit of a fringe use case.

I have attached screenshots of the Ekos client presenting both cameras and so you can see the behaviour I mentioned above.

Regards,
Rod Whitford
5 years 4 months ago #31337
Attachments:

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

This is normal even if two different ZWO cameras, you'll see the same behavior.
5 years 4 months ago #31340

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

Time to create page: 0.404 seconds