Quote:
Originally Posted by bojan
Hi Steve,
I noticed on your picture you marked serial mouse encoders... Are you using mouse driver or David Ek's box?
I use mouse driver (Gmouse.com), but I have a problem here, it seems the mouse interrupt handling does not work properly and very often the position is not updated while tracking and/or slewing.
Currently, when I want to move the scope, I have to stop tracking, to avoid problems - automatic returning to a position that scope thinks is current and correct and which is not because of missing interrupts.
So I plan to mount the David Ek's box (which keeps current scope position in its own controller's memory and sends it to main computer on request), but since I can live with the workaround, ans since I am lazy, the box is still on my table, waiting..
Yes, it is a work in progress :-)
|
Bojan,
When Mel first introduced mouse encoders years ago, I added it to the
DEC axis only.
Later I added it to the RA axis too although I turn it on and off
depending on what I'm using the scope for.
I use a mouse driver without accelleration (the floppy you see sticking
out the laptop is the backup mouse driver).
I searched for ages to find a mouse driver that was glitch free.
Basically, once I setup the mouse increments in Config.dat, turn on encoders, I can track and slew with the DEC readout giving me an
update on screen.
If I stay the driven side of my backlash, I'm ok.
If I go backwards and introduce some backlash take-up, I get positioning
errors.
So to keep it simple it is only mostly used as a 'push to' goto function.
I set on a known star in stars.dat.
Do an equatorial co-ordinates reset.
Then push the scope until I am at my desired GOTO location.
(I can drive there with the handpad, but it all depends what side
of the backlash I am on).