I know it´s not really the place for this but i have to aks what the problem could be that the cam almost won´t connect to PHD2

See video...

dead youtube video

Seems you were too fast. Its on now

I've on occasion experienced issues connecting from PHD2 using the method you're using, but I came to find it's easier and more reliable to just bring PHD2 up and make sure the profile is right (but don't connect from inside PHD2). Connect from Ekos (using guide tab controls). Depending on any out-of-sync state condition between Ekos & PHD2, you might need to forcibly disconnect and then reconnect, but generally, I no longer experience connection problems when coming from Ekos. Just a thought for something different to try. I could make myself believe a prior connection that has not "let go" could cause follow-on connect attempt issues. Cheers, Doug

I understand what you say.

The problem is that i am at the point "creating" the profile in PHD, and eveen here the problem allready occurs.

I have phd as guider in EKOS. I start PHD. I start KStars and the system connects automaitc immideately.
Ending up in the state you see on the vid...

I have to explain the situation in detail.

Got an ASUS Vivobook running some KDE-Neon-Plasma whatever...
Problems with the Lodestar X2 running on BIN 2x2 only. Bin 1x1 gives me timeouts. (ordered special cables to maybe get rid of that)
For testing purposes i erased the complete system and installed windows to have a clou how ASCOM behaves. (Under ASCOM everything runs fine)
So i installed the newest version of KUBUNTU how Jasem told me. Because on his Kubuntu System the same Cam has no issues at all.
So now i have a dualboot System running Win10 on one, and Kubuntu 20.-something on the other.
And THERE this problem started to happen.
I do not even have it on an old Stellarmate running 1.5.4 nor on my macbook air.
So it must have something to do with the Kubuntu, doesn´t it?
Can one somhow find out whats wrong?
Or "debug" something? Or just update kubuntu?

Niki

Well....not sure I can help with the dual boot config part of this issue. One thought might be to set your default profile in the OS environment you DONT want to test to use only simulators (mount, cam, guider). Connect and disconnect that profile to be sure it's the active default, and then exit. Next, set the profile in the OS you DO want to test to the actual HW. My guess is that somehow, you're managing to establish a connection to HW when not intended, so that when you are ready and try to intentionally connect, the equipment is already connected or the connection didn't clean up correctly (and then you can't get the socket/port when you want/need it for the config you're testing). It's not the first time I've seen the state machine from PHD2 to Ekos show incorrect state, so it can definitely be confused (and confusing to debug). Anyway, maybe something else to try. Good luck...

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

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