×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

Losmandy Gemini Slew Fails

2 months 5 days ago 2 months 5 days ago by jnowat.
jnowat
Senior Boarder
Senior Boarder
Posts: 54
Karma: 1
More
Topic Author
Losmandy Gemini Slew Fails #55104
I can park and unpark the mount all day. Every now and then I get the slew failed error.

I've tried the following:
1) reset Astroberry
2) reset Gemini
3) reset both Astroberry and Gemini
4) reset everything connected (2x ASI CCD, Pegasus UPB, ASI EFW, and of course Astroberry and Gemini)
5) run a scheduler- ran into wild happenings like slew failing seeral times before working.
6) slew with mount control in ekos, start guiding procedure, take frames..... this works. xD hahaha not ideal


I was taking multiple 300sec frames a few nights ago. Given there have been clouds lately, but I could definitely be having much more scope time is EKOS/INDI would stop being so foolish with the Gemini driver.


I'm really not in the mood to reinstall everything because without any updates since, this workflow and INDI profile were working fantastically.


Who enjoys seeing such:

2020-06-05T05:29:29: [ERROR] Slew failed.
2020-06-05T05:29:29: [ERROR] Error Slewing to JNow RA 17:52:53 - DEC 53:23:39
2020-06-05T05:29:26: [ERROR] Slew failed.
2020-06-05T05:29:26: [ERROR] Error Slewing to JNow RA 17:52:53 - DEC 53:23:39
2020-06-05T05:29:24: [ERROR] Slew failed.
2020-06-05T05:29:24: [ERROR] Error Slewing to JNow RA 17:52:53 - DEC 53:23:39
2020-06-05T05:29:21: [ERROR] Slew failed.
2020-06-05T05:29:21: [ERROR] Error Slewing to JNow RA 17:52:53 - DEC 53:23:39
2020-06-05T05:29:05: [INFO] Synchronization successful.
2020-06-05T05:28:46: [INFO] Slew is complete. Tracking...
2020-06-05T05:28:40: [INFO] Slew is complete. Tracking...
2020-06-05T05:28:14: [ERROR] Slew failed.
2020-06-05T05:28:14: [ERROR] Error Slewing to JNow RA 17:52:00 - DEC 53:23:37
2020-06-05T05:28:14: [ERROR] Slew failed.
2020-06-05T05:28:14: [ERROR] Error Slewing to JNow RA 17:52:00 - DEC 53:23:37
2020-06-05T05:28:13: [ERROR] Slew failed.
2020-06-05T05:28:13: [ERROR] Error Slewing to JNow RA 17:52:00 - DEC 53:23:37
2020-06-05T05:28:13: [INFO] Synchronization successful.
2020-06-05T05:27:58: [INFO] Slew is complete. Tracking...
2020-06-05T05:27:41: [INFO] Slew is complete. Tracking...
2020-06-05T05:27:33: [INFO] Slew is complete. Tracking...
2020-06-05T05:26:40: [ERROR] Slew failed.


I've attached logs... can I do better?

KStars 3.4.2 (Build: 2020-04-26T07:39:54Z) on Win10, connected remotely (5GHz WiFi) to RPi4/4GB running Astroberry (Linux astroberry 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux)

Losmandy G11, Gemini II, 10" f/3.8 Newt (Ostahowski Optics),
TV Paracorr-2, 2" Starlight FT, HSM20, Pegasus UPBv2,
ASI1600MM Pro, ASI174MM Mini, ZWO LRGB, EFW, & OAG,
StellarMate on RPi3 and/or Astroberry on RPi4
KStars 3.4.1 Build 2020-02-24T07:38:50Z on Win10 (updated 20200506)
Indi ver....
Attachments:

Please Log in or Create an account to join the conversation.

2 months 5 days ago
ChrisRowland
Platinum Boarder
Platinum Boarder
Posts: 516
Karma: 9
More
Losmandy Gemini Slew Fails #55106
What's happening is that the mount seems to be rejecting the slew command with code 6. The reason could be that there is something about the position that the mount doesn't like, perhaps it is to a position that is out of range. The mount manual may have more information about what causes the mount to fail to slew and maybe even what the code 6 reply means.

Please Log in or Create an account to join the conversation.

2 months 5 days ago
jnowat
Senior Boarder
Senior Boarder
Posts: 54
Karma: 1
More
Topic Author
Losmandy Gemini Slew Fails #55108
Thanks Chris. Gemini Hand Controller reports target unreachable... But it's plenty reachable. I grabbed the laptop, went out there, got the same error on EKOS and this on controller, reset Gemini, reconnected, slews fine.

Thing is, I'd already tried this and it didn't do the trick. What would force the Gemini to think that the target wasn't reachable if I'd plate solved at that area and it "knew" that it was okay to slew? It wouldn't even slew to a spot close to the pole!

Losmandy G11, Gemini II, 10" f/3.8 Newt (Ostahowski Optics),
TV Paracorr-2, 2" Starlight FT, HSM20, Pegasus UPBv2,
ASI1600MM Pro, ASI174MM Mini, ZWO LRGB, EFW, & OAG,
StellarMate on RPi3 and/or Astroberry on RPi4
KStars 3.4.1 Build 2020-02-24T07:38:50Z on Win10 (updated 20200506)
Indi ver....

Please Log in or Create an account to join the conversation.

2 months 5 days ago
phomer60
Gold Boarder
Gold Boarder
Posts: 204
More
Losmandy Gemini Slew Fails #55112
Anon,
When something like that happens, I park the mount in the CWD position - this always works for me.
I then set the mount to coldstart on connect, disconnect the mount and then connect it.
I then slew to somewhere away from the pole and do a synch.
Paul

Please Log in or Create an account to join the conversation.

2 months 5 days ago
TallFurryMan
Platinum Boarder
Platinum Boarder
Posts: 900
Karma: 13
More
Losmandy Gemini Slew Fails #55117
I suppose there are geographical settings in the mount firmware? Are they still correct when the problem occurs?

-Eric

HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access

Please Log in or Create an account to join the conversation.

2 months 5 days ago
amendolajamie
Junior Boarder
Junior Boarder
Posts: 36
More
Losmandy Gemini Slew Fails #55125
I don't know if this is the same issue as mine, but it sounds similar and I have a fix in code. You can also work around it by making sure that you stop guiding before doing a slew. Here's the thread, I think you posted to that thread. indilib.org/forum/mounts/7065-losmandy-s...s-haywire.html#55124

Please Log in or Create an account to join the conversation.

2 months 4 days ago 2 months 4 days ago by mlarsson.
mlarsson
Platinum Boarder
Platinum Boarder
Posts: 419
Karma: 1
More
Losmandy Gemini Slew Fails #55144
Hi!

If I get the manual right, code 6 means "outside limits".

I've had similar issues at times. I would advise you to check the safety and GOTO limits. And if you've changed the limits, at least my Gemini 2 needs to be restarted (else errors such as these occur).

I also note in the log that the mount seems to use the location "Hollywood", that is the default location. Is it correct that your lat and long are these:

[2020-06-04T21:41:27.943 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[DEBUG] Mount Controller Latitude: 41.0333 Longitude: 235.9 "

If I read the logs correctly, you get a slew fails after connecting the mount, that is, you have not been able to do any successful slews first - correct? It seems that you connect, start scheduler, and then get a slew fails. Like in log_22-23-15.txt:
#703
[2020-06-04T22:24:02.892 Pacific Daylight Time INFO ][ org.kde.kstars.ekos.scheduler] - Scheduler is starting...
[2020-06-04T22:24:02.898 Pacific Daylight Time INFO ][ org.kde.kstars.ekos.scheduler] - "Scheduler started."

then #786:
[2020-06-04T22:24:10.929 Pacific Daylight Time DEBG ][ org.kde.kstars.ekos.mount] - Slewing to RA= "17h 52m 52s" DEC= " 53° 23' 38\""
[2020-06-04T22:24:10.938 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "17h 52m 52s" ( 17.8813 ) DE: " 53° 23' 38\"" ( 53.3941 )
[2020-06-04T22:24:10.944 Pacific Daylight Time INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'C/2017 K2 (PANSTARRS)' is slewing to target."
[2020-06-04T22:24:10.981 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] <setObjectRA> "
[2020-06-04T22:24:10.990 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:Sr 17:52:53#> "
[2020-06-04T22:24:10.996 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:Sr 17:52:53#> successful. "
[2020-06-04T22:24:11.003 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] <setObjectDEC> "
[2020-06-04T22:24:11.008 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:Sd +53:23:39#> "
[2020-06-04T22:24:11.013 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:Sd +53:23:39#> successful. "
[2020-06-04T22:24:11.019 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] <Slew> "
[2020-06-04T22:24:11.024 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] CMD <:MS#> "
[2020-06-04T22:24:11.030 Pacific Daylight Time DEBG ][ org.kde.kstars.indi] - Losmandy Gemini : "[SCOPE] RES <6> "
[2020-06-04T22:24:11.036 Pacific Daylight Time INFO ][ org.kde.kstars.indi] - Losmandy Gemini : "[ERROR] Error Slewing to JNow RA 17:52:53 - DEC 53:23:39 "

Did you try just start it and slew manually? Maybe in the other logs that I didn't catch...

I recognize that at times, the Gemini seems to be confused, as if the model and/or limits are changed. Cold starting would then reset to normal operation. This just might be related to power as well - might there be temporary power losses to you mount? Do you run it on 12V or higher?


Magnus


C8, Losmandy G11, Canon 1000D astromodified.
The following user(s) said Thank You TallFurryMan

Please Log in or Create an account to join the conversation.

Time to create page: 0.689 seconds