Enforce counter-weight up in eqmod

  • Posts: 4
  • Thank you received: 1

Enforce counter-weight up in eqmod was created by vnd

Hi,

Is anybody using the "Enforce counter-weight up" property in eqmod ?
It is supposed to control pier side but it is rather unreliable and hard to use, IMO. The client basically has to guess which pier side the driver would choose and eventually set this property to make the driver use the opposite side. But under certain conditions the driver may ignore this request, see this for details.

I want to change the behavior, but I don't want to break any functionality which is used. This is my idea:

Add new property "Target Pier Side" with values

"Auto" - current behavior, with counterweight down
"West", "East". - enforce given pier side, abort goto if the target is outside of safe range

maybe also rename "Enforce counter-weight up" to "Allow counter-weight up" and use it to extend the safe range 1 hour across meridian. Alternatively this can be given as numeric property.


Any opinions?

References:
https://github.com/indilib/indi/issues/798
https://github.com/indilib/indi/pull/550
2 weeks 2 days ago #33386

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

  • Posts: 136
  • Karma: 5
  • Thank you received: 52

Replied by jpaana on topic Enforce counter-weight up in eqmod

I use this functionality quite a lot as I have a remote observatory and my HEQ5 is balanced slightly biased towards imaging to the west of meridian (east heavy). So I slew to targets still a bit to the east with this on so the mount is on the "wrong" side, guiding works better and I can image longer. It mostly works, but occasionally near the meridian the scope does extra meridian flips before alignment usually fixes it. Forced pier side property would work perfectly for my use, preferably with controllable limit on how far the mount is allowed to go.
2 weeks 2 days ago #33388

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

  • Posts: 402
  • Karma: 1
  • Thank you received: 62

Replied by Ihoujin on topic Enforce counter-weight up in eqmod

I have not used this feature yet, but certainly will give it a go next time the need arises. I like the idea proposed on the git forum to pop-up a warning, but if I may expand on the idea. Suppose if the setting was saved in configuration with a condition for # of hours before meridian, then a popup could be implemented as a manual confirmation for safety. Automatic function could be made available but does pose some risk at the user's discretion.
INDI/KStars on Raspberry Pi 3B+
Lubuntu 16.04
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG @280mm Guide Scope
PHD2
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.
2 weeks 1 hour ago #33497

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

  • Posts: 4
  • Thank you received: 1

Replied by vnd on topic Enforce counter-weight up in eqmod

jpaana: I have more or less the same experience.

JFYI: I have created experimental pull request which replaces "Enforce counter-weight up" with "Target Pier Side". The safe limit is still hardcoded to 1 hour across meridian.
The following user(s) said Thank You: jpaana
1 week 6 days ago #33508

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

  • Posts: 136
  • Karma: 5
  • Thank you received: 52

Replied by jpaana on topic Enforce counter-weight up in eqmod

Thanks, I'll give this a go, on Friday weather permitting.
1 week 6 days ago #33519

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

  • Posts: 136
  • Karma: 5
  • Thank you received: 52

Replied by jpaana on topic Enforce counter-weight up in eqmod

From fairly light testing it seems to work well, I set target pier side to east (pointing west) and selected a target around 40 minutes east of meridian to schedule and everything worked perfectly through a few alignment steps, scope stayed on the east side without flipping back and forth.
1 week 4 days ago #33582

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

Time to create page: 1.315 seconds