I noticed Bressier Messier mount as one of the mount options, and when I tried it it seems to connect. When I bring up the mount control and press an arrow button I get an error saying the command only works when mount is tracking.
I have pressed "Stop" on the HC, and the display now shows Tracking ON. But no change in Ekos/Kstars.
I have not done a GOTO or alignment or anything. This mount is sitting on my patio and I'm just trying to see if I can control it. My plan is to polar align it and then use plate solving.
My wife's CG5 is a bit fiddly in that before it will talk she has to use previous alignment or something to that effect to bypass the alignment part. I don't see that on the HC.
So now what?
The clicked current and write is an Ekos thing (Indi control panel, mount, site management, park position "Current" "Default" "Write Data" "Purge Data". I presumed you can move the mount to a park position, click current, then write data and it should make that the park position. I *think* this is actually for custom park positions.
When I connect to the mount, it shows up at Polaris. But there is a feature under Eqmod where you can right click anywhere on the screen, select Eqmod mount, then Goto & Set as Park Position. When I did this, the mount would slew to some place way way away from Polaris. I don't know why.
The good news, apparently, is that I reprogrammed the AstroEQ controller to invert DEC, and the mount now appears to be slewing in the correct direction. I had assumed inverting DEC in Indi control panel would have done this, but apparently not. Hopefully, skies will be clear for real testing!
When Ekos comes up and connects to the scope, it shows it pointing basically at Polaris.
I told the scope to "Park" - it slewed where ever it was going, and when it stopped, I clicked "Current" and "Write Data". I've loosened the clutchs and realigned to the index marks. This should now be the park position.
But if I then right-clicked on Polaris and tell the mount to Goto and set park position, the mount slews quite a distance away.
I've tried power-cycling between tests, and it doesn't seem to make a difference.
FWIW, right now, it shows Pier side - West pointing East, but it still moves the wrong direction.
Surely this is some flaw in my powerup sequence? I need to purge data, write data, power cycle, etc. but in the right order?
Thanks Lupták. The EQ5 is indeed showing Pier side - East pointing West!
That's gotta be it!
I'll report back if and when I find how to change it.
Hi Nigel and thank you!
I don't think it irrelevant at all. In fact, I'm beginning to wonder if gps is the heart of the problem.
I do have a GPS dongle attached to the Pi, and *usually* it shows longitude as 248.x something or other. But it sometimes takes a long time to show a response, if at all. So, I thought I'd bypass it and tell Ekos I was in Mesa (which is where I am). I looked up the coordinates on my other mount (iOptron CEM25 w/gps), and it shows:
Lat - 33:26:56.8
Lon - -111:41:31.1
Which is what I used on the EQ5.
What's odd is after I removed the gps dongle from the configuration and restarted Ekos, the Lat/lon now show:
Lat - 33:26:56
Long - 248:18:29
Which are the values the gps dongle typically reports when it actually is working.
Unfortunately, when I attempted to slew to Dubhe, the mount still slewed the wrong direction.
I am using Astroberry with an EQ5-type mount with AstroEQ. I'm trying to figure out why it is slewing in the wrong direction. Currently, mount is on patio and it's still daylight, but it should at least slew in the right general direction I would think. I don't know if this is significant, but Ekos shows mount type as EQ6.
From what I've read, the most common cause is incorrect location. I have manually configured Kstars to use Mesa, AZ as my location, and as far as I can tell, it appears latitude and longitude are correct (33:24:53 and 248:10:19). UTC is correct (for now) at 2022-5-24T0:57:45, though I notice in INDI control panel, under mount "site management" this does not appear to update in real time?
In my testing, I
- purged all configuration.
- right-clicked on mount location (near Polaris) and told Ekos to goto that position and set it to park.
- slewed to Mizar, but the mount slewed West.
- Parked and unparked mount.
- enabled "Reverse DEC" in INDI control panel.
- Slewed to Mizar - mount slewed West again.
To help you help me, I should provide logs - what specifically? Ekos "INDI" and "Mount"? Should I also include "Mount" driver?
Trying to work out some bugs with my iOptron CEM25 mount, and someone pointed out in one of my logs that "Calibration guide speeds: RA = 0.9 a-s/s, Dec = 1.4 a-s/s" were very low, should be at least 7.5arcsec/sec, maybe the way EKOS reports?
I didn't know the answer so figured I'd ask here. Thx.
FWIW, I had recalibrate when mount moves checked, so when I moved to M51 it recalibrated.
How did my message get in here? Ugh - sorry.
Not dumb at all! And thanks for the quick reply!
I can try that.
I feel stupid for asking this, but how can I simulate night so I can test during the day? I tried setting time to 10pm, and I checked "Site management" and changed the time there to 10pm, but when I try to do a goto, at the bottom of the screen it says it's 18:42 or something and complains about horizon limits or that my target is below horizon (M42).
What am I overlooking?
It's been 30 years since I built anything in Linux, and even then I don't recall mucking about too much.
Is there no way to build just the driver? Or would this create a mismatch in dependencies, etc.?
I found the dsusb driver source online and feel confident I can make the changes. What do I need to install on my pi to compile the new driver? This thread: www.indilib.org/forum/astroberry/7751-libindi-compilation.html seems to suggest this is a huge undertaking. Does it have to be?
Shoot - that makes sense.
So, I'll see about modifying the existing dsusb driver.