Has nobody an idea? Nobody has got a problem with that?
I am wondering, if there is a way to keep the checkboxes in the capture-module fixed. I mean so that i do not have to check them each time i start the system.
Is this able?
Oh my... Accidently managed to insert a <space> after the foldername...
After almost 2 Months of rain, i managed to get some lights last night.
As usual i wanted to do a fast check with "Blink" in Pix Insight.
Unfortunately PixInsight is not able to open the pictures anymore. None of them.
Did there something change that could make problems? I´m on KDE-Neon and KStars Version 3.3.0
For testing, i downloaded a fast Fits-Viewer. This program WAS able to open the files. So i believe it must have got something to do with the Fitsheader somehow?
Thanx for this interresting discussion. Since i am suffering on bad guiding (internal) from time to time too, i´ll have a go on this settings you mentioned.
Ron Kramer wrote:
Then wanted to do an object and guide through phd. The calibration this time was ok, but i got the immediate information that the alignment may not be very accurate. i don´t get why...
Are you performing calibration with PHD near the celestial equator/Meridian? if not it will give you this error.
You can check the calibration (in the options) and you should see a nice RED and BLUE L shaped graphic.
If it's not orthogonally correct you will get that error. They should be at a true 90' angle. (orthogonal)
IT should not matter, but does. - try and make sure you ROTATE your guide camera so that North is aligned upward. (West will likely be flipped) that's okay. It is supposed to correct for this but I've experienced that it calibrates better and without error if North is up when you review the calibration data.
I have been using the internal guider as well - and I do find it to be less than consistent. = (
I'm about to swap my 6" APO for my 11" RASA which should be more forgiving... Spring time swap.
I performed my calibration on my object which indeed was standing quite high. But this should not make a difference, does it?
Have to stop testing due to bad weather for some time now.
rotating the guidecam is a bit of a problem for me, since i had to tinker the connection by myself, but i will give it a try.
Yesterday i did the following:
Checked my Polaralignement via the Polarscope. Again. (I am not doing this often because i am not moving my stuff anyway.
Did a "Polar-Drift-Align" in PHD after i got that information elsewhere. Did this 3 times for at least 20 minutes. So i am pretty sure Polaralignment is NOT the problem.
Then wanted to do an object and guide through phd. The calibration this time was ok, but i got the immidiate information that the alignment may not be very accurate. i don´t get why...
Tried some more times where the calibration suddenly stops without bigger reason. Finally decided to use the calibration though i got the info that it would not be accurate.
Unfortunately the guiding was way off.
Then i changed to the internal guider. This worked very well. So i started my session and went to bed.
I decided to make it a real challenge for the system and made 1200sec frames.
The first 3 frames were totally OK, but then something strange happened... But see yourself..
Thinking about it, and bout the constellation and the telescopes orientation in the morning, i think it just hit the tripod, can you confirm?
This brings me to the often discussed problem i also have. I would have had the mount to slew to this object from the other side, but i unfortunately can not controll that.
Or would there be a way?
My conclution now is, that the guiding would have been very good now, without this fault. I just do not understand why PHD does not work good for me, but i can life with that, as long as the internal guider works good.
knro wrote: So I checked PHD2 code and it is indeed different way of calculating RMS from our method. So it could be the same performance, but the RMS is different.
Does that mean that its working one as good as the other, and only the „drawing“ is different?
That would explain the still good stars though RMS of 2,0
Gesendet von iPhone mit Tapatalk
Testing yesterday again.
Installed latest nightly.
Changed gain of the asi120 from 28 upto 80.
Iterations in settings to three like it is default on new version.
Checked Paralignment through polarscope which was abit off, and fixed that.
First calibration running flawless.
Rms still at max 2,0 but 70% about 1,2 or so
Next i will test with phd. Maybe tonight, weather looks good.
I am not on remote atm. All tests are on a linux laptop with direct connection to the hardware. This to except delay problems between two computers, which i definitally have due to week wifi.
Gesendet von iPhone mit Tapatalk
Unfortunately not. PHD2 DID work, what was a big step for me since it did NOT, the last time i tried.
But i initially got a failure about "Backlash Problem" right at calibration...
I think i will today:
Update to the latest nightly (if i not allready am running it)
correct my polar-alignment since i did not check that for quite some time
maybe run a polaralignment in Kstars or PHD2
And then try again.
Yesterday things got worse.
Most of the frames are lost due to guiding loosingnthe guidestar.
What changed was the gain of the asi 120 to 28, because on the guideframes it was hard to see the guidestar due to strong noise. Maybe this was the wrong decision...
Should i try to raise the gain?
As you can see in the screenshot, the system keeps using very faint stars for guiding. I do not get why it does not choose a bright one...
Can i adjust this somewhere?
As mentoned above, is it better to guide through asi, or through mount?
You can see the last guidegraph from last night in the second picture.
I will post last nights log later, as i am in my work now...
I have to say that the kstars version i am using atm works GREAT! The only problem is my guiding.
No more camera issues since the short usb cables.
Offline-Platesolving runs within seconds.
Very satisfying system.
Gesendet von iPhone mit Tapatalk
Tried changing the iterations down to 3 with no effect. Decided to use this absolutely clear night to capture pictures and not to test around.
Maybe i can use the frames, also with not so good guiding...
Tried differend algorithms, but this made it not better too...
Tried PHD2 again, but this gives me peakes of 8+ arcsecs...
I´m a bit confused, what could be the problem...
One more thing that happenend today was that from one minute to the other, kstars crashed, and all my profiles where gone. I could not make new profiles.
I had this issue some time ago if you remember and was able to solve this issue with renaming the .indi folder and the .kstars folder in my home dir.
Tried both, seems a bit better this way... But i do not know...
Hi! I am using my setup like in the signature. I guide via the internal guider, what works quite "well" but could be a bit more accurate.
i am most of the time between 2 arcsecs but there are some "overshooters" that go up to 4 arcsecs.
Now my problem is the calibration. It happens that the system keeps losing the guidestar when calibrating. it looks like this happens because of a bit "diffuse" frames. there is a big gradient in the guideframes from left bottom to right top. And the system keeps using guidestars that are not so bright, don´t know why...
When i choose a guidingstar manually, i take a bright one, and then calibration ends OK. But when i let KStars choose, the stars runs out of the box quite often.
What could be the solution for that?
Please don´t refer to PHD, since this does not work ATM...