Bug 441684 - ZWO Camera 1, 2 and 3 missing from KStars Windows version 3.5.4 stable
Summary: ZWO Camera 1, 2 and 3 missing from KStars Windows version 3.5.4 stable
Status: RESOLVED NOT A BUG
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.5.4
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-29 04:07 UTC by Yves
Modified: 2021-09-13 15:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-28215-0.html (1.71 KB, text/html)
2021-08-30 05:58 UTC, Yves
Details
attachment-27510-0.html (854 bytes, text/html)
2021-09-05 03:45 UTC, Yves
Details
attachment-29834-0.html (1.36 KB, text/html)
2021-09-13 15:19 UTC, Yves
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yves 2021-08-29 04:07:29 UTC
SUMMARY

The KStars/EKos Windows version 3.5.4 does not have the new ZWO Camera 1 and 2 drivers listed in the Profile Editor menu.  In using INDIWEBManagerApp I can select ZWO Camera 1 and ZWO Camera 2 but it cause connection issues.  I needed to select ZWO Camera only from INDIWEBM«anager to be able to connect successfully with KStars (Windows client) but got the same problem as reported to https://bugs.kde.org/show_bug.cgi?id=441399.



STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 7 x64
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

I want to setup my Raspberry as a server and control that server from a Raspberry and/or Windows client.  This way, it will  minimize all processes at the source.  I'm thinking about driving my two cameras with two Raspberry devices if I have no choice.  One camera for each Raspberry. It seems to be possible to choose PHD2 with a different ip address so it might be a working solution.

I also want to drive a Waveshare 2-CH RS-232 HAT and a Waveshare RPi Relay Board.  However, 2 of the 3 ports (relays) of the RPi Relay Board cause my connected COM ports to freeze with my 2-CH RS-232 HAT.  They seem to work well when plugged together (no boot problem) but when toggling relays it crashed COM ports when they are connected to devices.  I tried different scenarios to regain control of the COM ports but without success.  In my case, no need to purchase a new Raspberry...already got one 8GB and two 2GB (for testing).

Thanks a lot for your support !!!

Regards,
Yves
Comment 1 Jasem Mutlaq 2021-08-29 08:23:12 UTC
This is not released software yet. This is under preliminary testing. Does ZWO Camera 1, 2..etc even work with your setup? please report.
Comment 2 Yves 2021-08-30 05:58:27 UTC
Created attachment 141144 [details]
attachment-28215-0.html

Hi Jasem,

The ZWO Camera 1 and 2 work with my setup. Probably it's not the driver fault but when using my main camera (9576 x 6388) in binning 1, the KStars/EKos GUI vanished completely after the second shot. However, three processus still remain active in the background and needed to terminate them.

I tried different experimentation in installing Raspbian on a PC and in using different OS already installed on different microSD cards with Ubuntu Desktop, Ubuntu Mate and Manjaro. The only system that gave me some success was Ubuntu Desktop. 

After installing the Nightly PPA builds (not working with Raspbian) on my Ubuntu, I was able to shoot with both cameras in binning 1 at the same time in looping during at least 15 minutes. However, after booting the Raspberry, I was not able to get that working anymore. It's very weird !

Regards,
Yves

Le 29/08/21 04:23, Jasem Mutlaq  <bugzilla_noreply@kde.org> a écrit : 
> 
> https://bugs.kde.org/show_bug.cgi?id=441684
> 
> --- Comment #1 from Jasem Mutlaq <mutlaqja@ikarustech.com> ---
> This is not released software yet. This is under preliminary testing. Does ZWO
> Camera 1, 2..etc even work with your setup? please report.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
>
Comment 3 Jasem Mutlaq 2021-08-30 06:07:25 UTC
It's probably memory related issue. How much RAM do you have on the Pi?
Comment 4 Yves 2021-08-30 06:23:33 UTC
   8GB
   Le 30 août 2021 02 h 07, Jasem Mutlaq <bugzilla_noreply@kde.org> a
   écrit :

     https://bugs.kde.org/show_bug.cgi?id=441684

     --- Comment #3 from Jasem Mutlaq <mutlaqja@ikarustech.com> ---
     It's probably memory related issue. How much RAM do you have on
     the Pi?

     --
     You are receiving this mail because:
     You reported the bug.
Comment 5 Jasem Mutlaq 2021-08-30 09:55:51 UTC
Please run KStars via Ekos Debugger and share the backtrace of the crash.
Comment 6 Yves 2021-09-05 03:45:15 UTC
Created attachment 141304 [details]
attachment-27510-0.html

Hi Jasem,

Sorry for the delay... I will give a try with Ekos Debugger soon.

Yves


Le 30/08/21 05:55, Jasem Mutlaq  <bugzilla_noreply@kde.org> a écrit : 
> 
> https://bugs.kde.org/show_bug.cgi?id=441684
> 
> --- Comment #5 from Jasem Mutlaq <mutlaqja@ikarustech.com> ---
> Please run KStars via Ekos Debugger and share the backtrace of the crash.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
>
Comment 7 Yves 2021-09-13 15:19:58 UTC
Created attachment 141516 [details]
attachment-29834-0.html

Hi Jasem,

It,s not resolved yet. I have many other things to do since two weeks so sorry I didn't get involved much deeper...The main problem is I can't install Ekos Debugger with Raspbian. PPA are not allowed with Raspbian. I have to compile things but how? Would you mind giving me instructions to do so?

Regards,
Yves


Le 13/09/21 06:22, Jasem Mutlaq  <bugzilla_noreply@kde.org> a écrit : 
> 
> https://bugs.kde.org/show_bug.cgi?id=441684
> 
> Jasem Mutlaq <mutlaqja@ikarustech.com> changed:
> 
>  What |Removed |Added
> ----------------------------------------------------------------------------
>  Status|REPORTED |RESOLVED
>  Resolution|--- |NOT A BUG
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
>