the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 3 days ago

Pligged in one after the other device. This way i was able to work, though there some strange behaviours of the system now, that i consider, has to do with mgen. I´ll have a try on your suggestions. Thanks for that. Tried another session today with mgen on scope. It works so great, that i think i will do it this way, and refrain from dithering... Hope that works for me.
Still hoping for full mgen support sometime :)

cheers
Niki

Read More...

the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 4 days ago

New tests yesterday. This time a comparison between internal guider and the MGen, mounted on the guiderscope. This was to exclude problems with the hardware or weighting issues.
Perfect round stars with MGen-guiding on the guidescope...
So it must be a settings-thing that the internal guider doesnt work satisfying.
Tried to use mgen in kstars yesterday too, to work from indoors, but always when i connected the mgen to usb, the mount did not connect to indi anymore...
Must be some kind of conflict at the usb ports.
I had to restart my whole system after this...

Nex try will be PHD2

cheers
Niki

Read More...

There is a new firmware release for MGen. Don´t know if you allready know...
here is the link to the APT-group, in which it was postet...

Don´t know if this could be of any helt for implementing the mgen into ekos...

cheers
Niki

Read More...

the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 6 days ago

TallFurryMan wrote: When and where exactly are you calibrating? Did you calibrate just before this target, or in another direction, possibly flipped? Having offsets on a side of the drift plot is not always a problem, but I haven't followed on changes to the internal guider lately.
If the drift plot is elongated to the right, it means that guiding corrections are slowing down the mount too much when it tracks too fast. Or, on the opposite, it means guiding corrections can't catch up on the mount tracking too slowly. It all depends on the root cause. Limiting pulse lengths can help to diagnose which is which.
If the drift plot is centered to the right, it means that you have an early offset that can't seem to be recovered. Early offsets are not a problem with guiding, as long as the initial capture doesn't contain the drift from the original center to the new one. However, this may cause some guiders to consider there is too much deviation and abort the capture.
But before tweaking guiding, as you mentioned, overweight or incorrect balance should be investigated: perhaps the weight of your setup is causing the mount to track too fast or too slow.

-Eric


Because i thought so, i calibrated new on every new testobject. What i saw from time to time, when doing so, was, that the mount seemed to "not be strong enough" to give the guiding pulses enough power. Please excuse this very "picturey" spoken words, but i think you know what i mean..
Like: Dec axis forward. . . ok, dec axis reverse. . . . . . . . . . . . . . . . . *nothing happens* or even one time i got an error containing "too much backlash"...
Unfortunately today, cloudfileds are disturbing my tests too...

I had a look on the guiding pulse lenghth. Could be coincidence.. There are lots of numbers there, and sometimes just zero...

Had a look on my weighting one more time, changed it a bit. Can it be that this is sooooo extremely sensitive?

On the other hand, considering all this problems, i have to say, that i never had so big problems with guiding when using my MGenII... This points out that it must be
a problem with the internal guider... Or the settings of it...

I changed the setting of the Pulse(?) now to 800. ATM its working ok.

Changed too much now, so i am not sure what caused the improvement...Letting a 600sec session run now on flame nebula, clouds are gone now, so maybe there will be some pictures usable. I have one 600sec image here, thats ok now.

Unoroicessed, only debeyered Screenshot of flame with 600secs here.

so long, i`ll keep you updated...

Read More...

the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 6 days ago

pentaxian23 wrote: I noticed your guiding pulse lengths are 0. Something wrong there. Check guide options, configuration - two axis and auto star

and you have corrections for the graph turned off. Good to turn that on to see what's happening.


Two axis was on, autostar was off...




Gesendet von iPhone mit Tapatalk

Read More...

the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 6 days ago

Atm testruns with guiding, without dithering. Funny that, on an object very deep near horizon in the south, my guiding hits run out of the cross to the right. Same setup working good on cassiopaia region. How come? Suggestions? Weighting problems? I even had a failure when calibrating...

Taking testshots atm on hpersei

Cheers, Niki


Gesendet von iPhone mit Tapatalk

Read More...

the.cakemaker replied to the topic 'Session recap - guiding Problems?' in the forum. 7 days ago

OK. Good points you are talking bout.

Especially the camera download time could be the key, since it was the first time i used the g2 cam.
And what i know bout it now is that it takes some time to get the pictures from the cam.
Last time i was using guiding via kstars, it was my dslr. there is not such a long download-time.

I´ll definetly have a look on that.

Read More...

the.cakemaker replied to the topic 'Session recap - guiding Problems?' in the forum. 7 days ago

How would i know if autoguiding stops and tracking continous? And why should tracking NOT continou? What does re-acquire mean? My english is not so good, sorry?

What is interesting maybe is, that the egg-form of the stars always points in the same direction. And in the bginning, i recognized that the "guiding marks" where all left of the center.

Read More...

the.cakemaker thanked Jasem Mutlaq in topic How to use PHD2 7 days ago
the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 7 days ago

So that is what i‘ll do next session.




Gesendet von iPhone mit Tapatalk

Read More...

the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 7 days ago

TallFurryMan wrote: Fast idea: do it again without dithering :)

-Eric


I will. The thing is that i can not see what was wrong with dithering...


Gesendet von iPhone mit Tapatalk

Read More...

the.cakemaker replied to the topic 'Re:Session recap - guiding Problems?' in the forum. 7 days ago

Oh its not as bad Eric :)

I dic not take the time to exactly control which picture corresponds to which part of the log. I know that the first pic is the best and that its getting worse, the longer it takes. I thought maybe some of you guys have a fast idea by checking the screenshots. If not so, i‘m going check that more accurate. But would it help?


Gesendet von iPhone mit Tapatalk

Read More...

the.cakemaker created a new topic ' How to use PHD2' in the forum. 7 days ago

If i lime to try phd2 guiding, where do i habe to install it, if i want to use it on my remote-imac? Local? Client? Both?

And is it able to start it then via webmanager?

Cheers, niki


Gesendet von iPhone mit Tapatalk

Read More...

the.cakemaker created a new topic ' Session recap - guiding Problems?' in the forum. 7 days ago

Hey there!

This is a recap of last nights session with KStars.
It also was my first night with the Moravian G2 8300 color cam.

So for the beginning: Everything (almost) worked like a charm :)
It´s just... the results are... useless...

So what i did is was a session on the wizard-nebula.
From the beginning i started to solve both cams (guiding cam ASI 120 and the G2) in park position to make sure "they know where they are" AND to test Platesolving.
I knew it worked great outdoors, but since i found out that its a difference to run on mac remotely or to work on my linux notebook direct, it was the first time i was trying to solve on the mac. No problems, solved in seconds. Thats mostly because i now wrote to the main scope 1100mm instead of 1000mm like in the Tipps i got here in the forum. Thanx for that.
After that i went to capella for focusing, solved in the second iteration, great! Thats really fun!
Then i went for the wizard nebula, solved on third iteration, GREAT too, because i rember solving action taking minutes before :)
Set up guiding,dithering, cooling main cam, start when -10° is received just EVERYTHING was working flawless.
The guiding graph did not exceed 1arcsec, thought that looks good for me...

BUT: As you see, none of the pictures is usable, because of lines instead of stars....

And i consider that the problem of the guiding has something to do with dithering... Because almost EVERY Dither-iteration endet with a dithering-error.
You can see that on the screenshots. I took lots of screenshots because i thought its running so flawless, something must be wrong :)

I have all the stuff attached, and also the logfile for that session. Had to cut out the second half of the log, because it was too big for the forum with 33mb...

As you can see on the last picture, the stars became more and more out of control the later it got.

So please guys, tell me what the fault could be. Any suggestion will help!

cheers
Niki

Read More...

the.cakemaker replied to the topic 'Re:*new* Plate solving tip!' in the forum. 7 days ago

Tried 1100mm instead of 1000mm
GREAT!

Platesolving now takes 5secs !

BIG THANX for that Tipp!


Gesendet von iPhone mit Tapatalk

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!