Problem with ZWO ASI6200MM camera coexisting with ASI290MM

[pleiades-coram]

SUMMARY
Raspberry (Native Raspbian version)
KStar 3.5.5 beta
KStar Build: 2021-07-28T15:01:33Z

My ZWO ASI6200MM doesn't seem to coexist with my ZWO ASI290MM guide camera. I plugged my guide camera to the camera USB hub or to the Raspberry USB ports but nothing. However, both cameras are connecting well when plugged at the same time in using ekos but the main camera is unable to produce image. Connecting each camera one by one is working well. The problem only happen to my main camera (ASI6200MM) and I needed to power it down to regain control if it. I can say for sure that both cameras can be connected and working altogether when using Windows 7. It seems that's a driver conflict.

Regards,
Yves

[knro]

It appears there is some limitation when the SDK is invoked with multiple cameras. If a single executable does this like what we do in INDI then multiple camera operation may not work fully. The only solution to this issue is to run individual driver per camera. The current ZWO INDI driver architecture does not work like this.

So it would take some work to convert the multi-camera single-driver architecture to single-camera single-driver.

[pleiades-coram]

Hi Jasem,Why asking me to send my problem report here if you are the same person who already responded to me on the other forum? Is someone going to do something about this in a near future?Regards,YvesLe 23 août 2021 13 h 47, Jasem Mutlaq ***@***.***> a écrit : It appears there is some limitation when the SDK is invoked with multiple cameras. If a single executable does this like what we do in INDI then multiple camera operation may not work fully. The only solution to this issue is to run individual driver per camera. The current ZWO INDI driver architecture does not work like this. So it would take some work to convert the multi-camera single-driver architecture to single-camera single-driver. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[knro]

Because this is the correct place to report this issue. It's not a KStars issue. Let's see if any of the INDI developers, perhaps @jpaana can suggest a proper solution for this.

[pleiades-coram]

Okay Jasem, I'm going to wait for his response.Regards,YvesLe 23 août 2021 17 h 03, Jasem Mutlaq ***@***.***> a écrit : Because this is the correct place to report this issue. It's not a KStars issue. Let's see if any of the INDI developers, perhaps @jpaana can suggest a proper solution for this. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[jpaana]

Unfortunately I haven't actually even tried running multiple ASI cameras on one machine as currently one of the two I have is in my allsky camera (120MM-S) and the other (178MC) is in my remote observatory. Both have small sensors and neither of them have hubs either so it's quite different from your equipment in any case.

Running one driver per camera would sound quite logical thing to try as that would minimize the influence they have on each other. But if the other camera doesn't show up at all even with lsusb command, then that wouldn't help. Running things off the Pi directly is often power sensitive and running under powered does cause all sorts of weird issues. Then again running the other camera off the other's (hopefully powered when the 12V is connected?) should also eliminate that...

[pleiades-coram]

Hi Jarno, Both cameras are able to connect at the same time with ekos. I can use the guide camera but not the main camera. In using the main camera, the guide camera no longer worked. Below is the listing when using lsusb command. As you can see, Device 007: ID 03c3:290f and Device 005: ID 03c3:620b have no labels but are related to ZWO cameras. ***@***.***:~ $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 04ca:0022 Lite-On Technology Corp. Bus 001 Device 007: ID 03c3:290f Bus 001 Device 005: ID 03c3:620b Bus 001 Device 003: ID 04b4:6572 Cypress Semiconductor Corp. Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Is there a way to run one driver for each camera? I also tried to connect my main camera with a short USB 2.0 cable. The one provided by them is a flat USB 3.0 cable and it seems fragile. However it didn't help ! Another thing, both cameras use their power from the USB, The only 12V DC port (optionnal) on the ASI6200 is to power the cooling system. Regards, Yves Le 24/08/21 17:01, Jarno Paananen ***@***.***> a écrit :

…

Unfortunately I haven't actually even tried running multiple ASI cameras on one machine as currently one of the two I have is in my allsky camera (120MM-S) and the other (178MC) is in my remote observatory. Both have small sensors and neither of them have hubs either so it's quite different from your equipment in any case. Running one driver per camera would sound quite logical thing to try as that would minimize the influence they have on each other. But if the other camera doesn't show up at all even with lsusb command, then that wouldn't help. Running things off the Pi directly is often power sensitive and running under powered does cause all sorts of weird issues. Then again running the other camera off the other's (hopefully powered when the 12V is connected?) should also eliminate that... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub(#437 (comment) ), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ATGQHFFBNU7EDUJD4Q2Q2WDT6QCBLANCNFSM5CU4ZJBA ). Triage notifications on the go with GitHub Mobile for iOS(https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 ) or Android(https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email ).

[knro]

I submitted PR #438 that could fix this issue.

[pleiades-coram]

Ok thanks !  I will wait...Regards,YvesLe 25 août 2021 12 h 49, Jasem Mutlaq ***@***.***> a écrit : I submitted PR #438 that could fix this issue. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[knro]

Ok MR merged. Please test from GIT or the nightlies and report back. You need to select "ZWO Camera 1" and "ZWO Camera 2" in your profile.

[pleiades-coram]

Do I need to install the whole master release or just ithe ZWO Driver?  Thanks!YvesLe 26 août 2021 16 h 43, Jasem Mutlaq ***@***.***> a écrit : Ok MR merged. Please test from GIT or the nightlies and report back. You need to select "ZWO Camera 1" and "ZWO Camera 2" in your profile. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

[pleiades-coram]

Hi Jasem, I reinstalled the whole kit from the file "setupAstroRaspbianPi.sh". It's very time consuming. Maybe you can tell me the short way as I'm not a Linux guru. :-) Here are my observation... 1- I can connect both cameras in using ZWO Camera 1 and ZWO Camera 2. 2- I can image a light frame with both cameras (cameras covered) but it seems unstable sometime. 3- When both cameras are connected, the output of the main camera (ASI6200MM) has horizontal patterns. No problem detected for the moment with the guide camera. NOTE: GitHub didn't seem to accept attached file. I will send you it on request Attached is a compressed file containing two images (binning 4x4) output from my ASI6200MM with and without the guide camera connected. The same output pattern is there with binning 1x1. Hope this help! Regards, Yves Le 26/08/21 16:43, Jasem Mutlaq ***@***.***> a écrit :

…

Ok MR merged. Please test from GIT or the nightlies and report back. You need to select "ZWO Camera 1" and "ZWO Camera 2" in your profile. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub(#437 (comment) ), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ATGQHFDVOLT32YRF4B5XAYTT62RNTANCNFSM5CU4ZJBA ). Triage notifications on the go with GitHub Mobile for iOS(https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 ) or Android(https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub ).

[knro]

Is this pattern the same issue when using the original driver? Are you sure everything has sufficient power?

[pleiades-coram]

As a follow-up, my latest observations were related to a 3-ft USB 2.0 cable. I just did a test with my original 15-ft USB 3.0 flat cable and I cannot take an image at all. I also tried with a 15-ft USB 2.0 cable and the same problem. I went back with my 3-ft USB cable and noticed that if I take a shot with my guide camera only once, I cannot use my main camera anymore. It's probable a sort of voltage drop somewhere. Maybe the Raspberry is not able to deal with or the camera takes too much current. Regards, Yves Le 27/08/21 14:01, Yves Laroche ***@***.***> a écrit :

…

Hi Jasem, I reinstalled the whole kit from the file "setupAstroRaspbianPi.sh". It's very time consuming. Maybe you can tell me the short way as I'm not a Linux guru. :-) Here are my observation... 1- I can connect both cameras in using ZWO Camera 1 and ZWO Camera 2. 2- I can image a light frame with both cameras (cameras covered) but it seems unstable sometime. 3- When both cameras are connected, the output of the main camera (ASI6200MM) has horizontal patterns. No problem detected for the moment with the guide camera. NOTE: GitHub didn't seem to accept attached file. I will send you it on request Attached is a compressed file containing two images (binning 4x4) output from my ASI6200MM with and without the guide camera connected. The same output pattern is there with binning 1x1. Hope this help! Regards, Yves Le 26/08/21 16:43, Jasem Mutlaq ***@***.***> a écrit : > > > > Ok MR merged. Please test from GIT or the nightlies and report back. You need to select "ZWO Camera 1" and "ZWO Camera 2" in your profile. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub(#437 (comment) ), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ATGQHFDVOLT32YRF4B5XAYTT62RNTANCNFSM5CU4ZJBA ). > Triage notifications on the go with GitHub Mobile for iOS(https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 ) or Android(https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub ). > >

[pleiades-coram]

Hi Jasem, One thing for sure is that your new driver works well compared to the older one. Depending of what USB cable lenght and if it's USB 2.0 or 3.0 these behaviours varies. Plugging the guide camera directly to the main camera hub or directly to the Raspberry also cause problem. I found something very unusual. The guide camera can coexit well when a 12V is applied to my main camera. According to ZWO, the 12V input only serve to control the cooling system. It's really not the case with that camera. First, I thought the 12V also provide a source to the main camera hub but it's also not the case. Whatever where I plug the guide camera, the 12V seems necessary to both camera to work together. I was able to run in a loop both cameras during several minutes. However, the main camera was set to binning 4x4. Setting to binning 1x1 ask to much ressource and Kstar/Ekos vannished at each time after the second image attempt. I switched back several times from the new to the old driver and even if a 12V cooling source is applied, the old driver always fail. Also, when the 12V source is applied, all horizontal pattern lines disappeared. So for now, the only thing that can produce problem is downloading a full frame image during the time the guider is working. Is there a possiblity to stop the guider just before downloading a such big image to prevent a software crash. FYI, my testing were done in using a RaspBerry Pi 4 version B with 8GB of RAM with a SD card of 128 GB. Regards, Yves Le 27/08/21 14:04, Jasem Mutlaq ***@***.***> a écrit :

…

Is this pattern the same issue when using the original driver? Are you sure everything has sufficient power? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub(#437 (comment) ), or unsubscribe(https://github.com/notifications/unsubscribe-auth/ATGQHFHQVOK2XEDPPMHIRS3T67HT7ANCNFSM5CU4ZJBA ). Triage notifications on the go with GitHub Mobile for iOS(https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 ) or Android(https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub ).

[knro]

Can you test with "ZWO Camera 1" and "ZWO Camera 2" drivers?