Been out a couple of times recently after a hiatus and noticed the meridian flip goes well up until the point of solving and can never find where it is.
That's when I stop things, download an image and solve it manually, only to find out the dec is out by around 20 degrees. RA is perfectly fine
I'm using a HEQ5 Pro running Stellarmate on an RPi 4, Kstars 3.6.0 stable (Thought it would with the package updater)
My current routine is simply: Polar align, reset to home position, slew to meridian to calibrate guiding, solve, slew to target and solve.
Do I need to have a better mount model perhaps and slew to targets further away to build it before slewing to intended target?
Read More...
Like many, I experience issues with backlash on their mounts and have to resort to only guiding in one direction to keep things stable
The issue is that when it comes to dithering since one direction is disabled when it's completed, if the backlash is on the other side, it can't be corrected and creates a runaway effect.
How possible would it be to implement a feature that switches to both North and South guiding for recentering and continues to guide in the opposite direction of the dither?
Read More...
Just checked the location and time settings, all seem correct.
I'm out tonight so I'll have a look when it comes to doing the meridian flip
Cheers,
Matt
Read More...
Spent these last few nights having to manually flip my mount since my HEQ5 doesn't want to switch pier sides even when it's almost an hour past the meridian.
EKOS works fine in the fact once it's over 0.2 hours, it'll issue a slew command but like I say, the mount just doesn't want to switch and thinks it's fine.
I had it last night where even when I flipped the mount manually and solved, it still thought it was on the other side and proceded to slew back. I put it into the home position, cleared the mount model, synced to Polaris but it still happened
Is there a way to fix this?
Matt
Read More...
I've just tested the latest nightly build after seeing the changes merged on GitHub and can confirm that the initial results are very promising.
I haven't done a lot of imaging recently due to having to throw away a lot of exposures due to the "backlash" issue. One of my problems was actually related to my PSU which I upgraded to 13.8v, and now that's fixed.
I was imaging a couple of nights ago on the latest stable update and that reported 6000ms of backlash, now with the fixed driver, I get 1500ms and the star cross test works but produces a lowercase t shape which I'm not sure about.
Matt
Read More...
Did you end up sorting the issue? I reckon it's the cable and comms issues with it. I'll see by connecting my hand controller usb instead of the eqdir cable
Read More...
I've just had a look and there's quite a few read errors on mine too. Sometimes just before the spike and some not. Communication error in the eqdirect wire? Could also be voltage drops from psu? What psu are you both using?
Read More...
I've been having to throw away half of my subs for the past 3 months because of this issue, so hopefully it doesn't budge and stays exactly like it is
Matt
Read More...
Update. I ended up changing the time and location updates in the INDI options from KStars to the mount and there's no spikes to be seen. Currently been over 30 minutes
Read More...
I do keep getting this error when they occur
EQMod Mount : "[COMM] read error, will retry again... "
Read More...
I found this rather odd. I'm currently out at the moment and it still keeps happening. My guide rate is at 0.8 hence the 12.0329 but why is the RA then deciding to go at 1.8x sidereal
[2020-11-30T19:32:46.640 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[DEBUG] Timed guide West 79 ms at rate 12.0329 "
[2020-11-30T19:32:46.640 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[DEBUG] StartRATracking() : trackspeed = 27.0739 arcsecs/s, computed rate = 1.8 "
[2020-11-30T19:32:46.641 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[DEBUG] SetRARate() : rate = 1.8 "
[2020-11-30T19:32:46.641 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[MOUNT] SetMotion() : Axis = 1 -- dir=forward mode=slew speedmode=lowspeed "
[2020-11-30T19:32:46.641 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[SCOPE] CheckMotorStatus() : Axis = 1 "
[2020-11-30T19:32:46.642 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[COMM] dispatch_command: \":f1\", 4 bytes written "
[2020-11-30T19:32:46.642 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[COMM] read_eqmod: \"=111\", 5 bytes read "
[2020-11-30T19:32:46.643 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[MOUNT] SetSpeed() : Axis = 1 -- period=344 "
[2020-11-30T19:32:46.644 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[COMM] dispatch_command: \":f1\", 4 bytes written "
[2020-11-30T19:32:46.645 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[COMM] read_eqmod: \"=111\", 5 bytes read "
[2020-11-30T19:32:46.646 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[COMM] dispatch_command: \":I1580100\", 10 bytes written "A few seconds later, it receives a command after the spike occurs and is told to do a 1776ms @ 0.8x when it then only does 0.2x
[2020-11-30T19:32:54.476 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[DEBUG] Timed guide East 1776 ms at rate 12.0329 "
[2020-11-30T19:32:54.476 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[DEBUG] StartRATracking() : trackspeed = 3.00821 arcsecs/s, computed rate = 0.2 "
[2020-11-30T19:32:54.476 GMT DEBG ][ org.kde.kstars.indi] - EQMod Mount : "[DEBUG] SetRARate() : rate = 0.2 "Read More...
