I don´t know.
I installed 3 different versions of Ubuntu today.
None of them were able to connect to PHD2 .
I even get more problems in kstars to get the lodestar looping...
Not even in bin 2x2 anymore.
I totally give up now.
The only explanation to me is a hardware-damage of the laptop.
I close this topic here, it makes no sense anymore. Thanks all for your help...
Found this when starting phd2 in konsole...
Is this normal or relevant
Thanks DMSUMMERS for this input. I definitally will have a try on this when the very bad and rainy wheather has gone. Thats why i am testing inside.
I will get new cables to get this issue out of the count but atm ASCOM under windows works well so i will see if i have to change.
Right now i am too annoyed of permanent problems and think i will choose the more problem free system...
Back to taking pictures again, not spending my time with software issues...
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?
Seems you were too fast. Its on now
Thanks for the video.
After a complete new installation of Kubuntu (yes i googled that and installed it as a dualboot system for testing purposes) i managed, not without problems with picture size, to get the cam looping in bin 1X1.
Saved this configuration now, but can not test tonight because of bad weather.
Managed to keep the cam working in KStars, but no way to connect stable to PHD2 unfortunately.
There must be something i am doing wrong all the time...
Restarted all the software. Going to camera Tab, looping. No response. Its frustrating...
Found out that in this cases i have to delete the camera settings with the clear camera configuration button. This way i manage to loop in KStars again...
Found out that this does NOT help all the time... only sometimes...
I´m giving up now. There is no way to work for me like this...
I´ll provide a log here, i set up for the last minutes. No idea whats the problem.
I have no idea, what the problem is now
Any suggestions? Maybe Hardware-related?
I have no idea. But i will install a new version of Linux as dualboot maybe this helps.
Can you provide a link for an up-to-date version of the Kubuntu you are using?
I think the OS is not relevant. Works OK anywhere...
The telescopes you show here all are not very light-sensitive imho. But i don´t know them so maybe they all are ok...
Yes it used to be my "Kubuntu" Laptop as you say. I´m still no Linux-Crack so i do not really know if its Kubuntu or whatever.
I deleted the System Anyway, for getting a Dualboot-System with Windows/Linux for testing purposes.
ATM i have a new Win10 installation running with SGP-Trial Version and this is where i testet the Lodestar with running OK on bin 1x1.
What i believe is that is must have something to do with the usb connection.
I have problems all the time with connecting my gear and getting messages similar to " this port is allready used by another device"
This happens random and is most of the time solved by switching of and back on devices...
I did not yet find out how this could be solved...
Funny, because i ussually never change the wireing of my devices since i am working stationary.
Maybe its a hardware-related problem with my laptop in connection to Linux?
Maybe i should try another Linuxversion? Would you recommend one?
Problems keep staying with my Lodestar C2. Only way to use it was binning 2x2.
Since this can not be the last word, i tried different cables, ports, even bypassing the USB-Hub without success.
So i made a real hard test by deleting the linux system and installed windows 10 an Sequence Generator pro.
This to find out if its camera-related.
What can i say? The Lodestar runs flawless without binning under SGP with ASCOM Drivers.
Ja someone an idea what he problem could be?
I have ONE thing that catched my eye i on startups of the windows system about some pci-thing. Maybe this has got to do something with it?
See the screenshot.
I saw your thread here an have a question.
I use a Lodestar X2 too for guiding, and a Moravian G2 8300 colour for imaging.
I have the problem that the lodestar keeps timing out all of the time.
My only solution to this atm is to set the lodestar on binning 2x2, this way it works fine.
Could you explain a bit clearer for me, what exactly and where you changed the buffersize?
Maybe this would work for me too.