×

INDI Library v1.9.9 Released (30 Nov 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Losmandy Gemini Slew Fails

  • Posts: 61
  • Thank you received: 12
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 Gemini II, 250mm custom newt @ f/3.8, Parracorr,
ZWO OAG, ASI174MM Mini, Astrodon LRGBHa, ASI EFWx8,
[Rokinon 85mm f/1.4 AF, AstromechFoc, ASI EFWx5, ASI1600MM Pro (Piggy back)]
Astroberry latest on RPi4 && KStars 3.6.2 Build 2022-12-04T03:35:06Z on Win10
Last edit: 2 years 7 months ago by Jacob Nowatzke.
2 years 7 months ago #55104
Attachments:

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

  • Posts: 554
  • Thank you received: 138
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.
2 years 7 months ago #55106

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

  • Posts: 61
  • Thank you received: 12
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 Gemini II, 250mm custom newt @ f/3.8, Parracorr,
ZWO OAG, ASI174MM Mini, Astrodon LRGBHa, ASI EFWx8,
[Rokinon 85mm f/1.4 AF, AstromechFoc, ASI EFWx5, ASI1600MM Pro (Piggy back)]
Astroberry latest on RPi4 && KStars 3.6.2 Build 2022-12-04T03:35:06Z on Win10
2 years 7 months ago #55108

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

  • Posts: 412
  • Thank you received: 30

Replied by Paul on topic Losmandy Gemini Slew Fails

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
Losmandy G11 with Gemini 2 controller
QSI 583/683 monochrome cameras with filter wheel
Starlight Xpress Lodestar X2 guide camera
Microtouch Focuser controlled using Arduino UNO emulating Feathertouch controller
Raspberry Pi 2GB with Raspberry Pi OS 64bit Bullseye
2 years 7 months ago #55112

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

  • Posts: 1029
  • Thank you received: 301

Replied by Eric on topic Re:Losmandy Gemini Slew Fails

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
2 years 7 months ago #55117

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

  • Posts: 99
  • Thank you received: 3
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
2 years 7 months ago #55125

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

  • Posts: 565
  • Thank you received: 56
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

Losmandy G11, Celestron CGE-Pro
Celestron C11, C8
Skywatcher 100 ED Pro
QHY268m, Atik 383L+, ASI294
Lowspec, Star'Ex
The following user(s) said Thank You: Eric
Last edit: 2 years 7 months ago by Magnus Larsson.
2 years 7 months ago #55144

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

Time to create page: 0.878 seconds