×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

[SOLVED] eqmod does not remember scope position.

  • Posts: 226
  • Thank you received: 88

Ok, that explains why encoder positions are lost when you restart the indiserver. Is'nt there a jumper on your board to disable this behavior ? If I understand it is used for firmware loading purpose. Otherwise you would have to park/unpark on every connection, not only when you power off your mount.
9 years 4 weeks ago #3372

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

  • Posts: 2247
  • Thank you received: 223

I'll come up with a script to do that, I have an idea. Will post the script once finished.
It would be nice to have an option called something like "read encoder position".
9 years 3 weeks ago #3374

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

  • Posts: 2247
  • Thank you received: 223


There is no switch for that, the firmware upgrade is one via a software.
If I can't come up with a suitable script, I will have to make sure that the mount is parked after each use and hope for the best that the Odroid doesn't reboot half through a session....
9 years 3 weeks ago #3375

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

  • Posts: 2247
  • Thank you received: 223
I've found the following post:
www.indilib.org/forum/general/522-parkda...or-indi-sx.html#2569




Is there a way to pass such values to the Eqmod on start, as in reading a file if possible, similar to ParkData.xml ? Or set it by command line with indi_setprop?
Or maybe, after each completed slew, the RA/DEC is written to a file which can be read on restart of the Eqmod, that would a cool feature to have.
You could choose to reload the previous location on restart if needed (in my case, after a power cut).


EDIT:
edited to avoid confusion, this is an example to show the lines "Setting default Init steps"
Last edit: 9 years 3 weeks ago by Gonzothegreat.
9 years 3 weeks ago #3376

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

Please change <device name="EQMod"> to <device name="EQMod Mount">
9 years 3 weeks ago #3377

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

  • Posts: 2247
  • Thank you received: 223


This is not my post, I took it as an example to show the following lines only:
[b]2014-12-31T16:19:10: Init() : Setting default Init steps -- RAInit=8388608 DEInit = 8388608
2014-12-31T16:19:10: Init() : Motors already initialized[/b]
9 years 3 weeks ago #3378

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

  • Posts: 2247
  • Thank you received: 223
I've been testing a few new firmwares for the AstroEQ but it still doesn't work.

Could someone guide me on how to re-inject the "default Init steps -- RAInit=8388608 DEInit = 8388608" back into Eqmod (Ekos) please?
8388608 is an example, I believe they are the default values.
9 years 3 weeks ago #3388

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

  • Posts: 226
  • Thank you received: 88
You just have to create a ~/.indi/ParkData.xml file like this one:
<parkdata>
    <device name="EQMod Mount">
        <parkstatus>
true
        </parkstatus>
        <parkposition>
            <raencoder>
8388608
            </raencoder>
            <deencoder>
10644608
            </deencoder>
        </parkposition>
    </device>
</parkdata>
Use your saved encoder values in your case. Those values will be used on startup to set the encoder values.

Another solution would be to modify the /usr/share/indi/indi_eqmod_sk.xml file and set the CURRENTSTEPPERS property as read/write instead of read-only: that way you may directly modify it by hand.

I attach a small simple script to monitor the ra/de stepper values (add -h option to the indi_getprop command for remote host). There is also a -m option in indi_getprop to monitior values but I did not test yet.
The following user(s) said Thank You: Gonzothegreat
9 years 3 weeks ago #3391
Attachments:

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

  • Posts: 2247
  • Thank you received: 223
Thank you so much, I will try it this evening.

In the worse case scenario, if that doesn't work or become too much of a pain the back side.... I might get myself a HEQ5 syntrek mount with a "HitecAstro EQDIR adapter for EQMOD" to replace my EQ3-2 / AstroEQ setup.
9 years 3 weeks ago #3395

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

  • Posts: 2247
  • Thank you received: 223

I have enabled this option in /usr/share/indi/indi_eqmod_sk.xml
<defNumberVector device="EQMod Mount" name="CURRENTSTEPPERS" label="Stepper Position" group="Motor Status" state="Idle" perm="[b]rw[/b]">
<defNumber name="RAStepsCurrent" label="RA Steps" format="%.0f" min="0.0" max="16777215.0" step="1.0">
1.0
</defNumber>
<defNumber name="DEStepsCurrent" label="DE Steps" format="%.0f" min="0.0" max="16777215.0" step="1.0">
1.0
</defNumber>
</defNumberVector>

Now you do have a new box in the Motor Status tab, you can enter the values there, but the RA/DEC Steps are not changing.
Last edit: 9 years 3 weeks ago by Gonzothegreat.
9 years 3 weeks ago #3398

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

  • Posts: 2247
  • Thank you received: 223


That above actually does work, the CURRENTSTEPPERS are set to the value from ~/.indi/ParkData.xml .
That gives me a work around which is a great step forward.
Off to write another bash script now.


Thanks for the help, I will let you know how I get on.
9 years 3 weeks ago #3399

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

  • Posts: 2247
  • Thank you received: 223
so far SO good, your script has helped me a LOT!!!!!

I have made the following modification to it:
#echo "$0: rastep=$rastep destep=$destep"
cat << EOF > /root/.indi/ParkData.xml
<parkdata>
    <device name="EQMod Mount">
        <parkstatus>
true
        </parkstatus>
        <parkposition>
            <raencoder>
$rastep
            </raencoder>
            <deencoder>
$destep
            </deencoder>
        </parkposition>
    </device>
</parkdata>
EOF


It will write the ParkData file automatically.
It's still a work in progress, it's in the right direction.
9 years 3 weeks ago #3403

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

Time to create page: 0.410 seconds