×

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

Bi-monthly release with minor bug fixes and improvements

Capture & Solve -> Slew to Target...

  • Posts: 200
  • Thank you received: 57
You are right. The AUX port needs level converter and just *looks* like serial port (and communication is over standard serial protocol). If you connect it with serial port you are indeed likely to fry at least one and possibly both ends of the connection. The HC serial socket is much better but it is not clean passthrough - you send commands with a prefix and you only get responses - so you cannot listen for broadcasts on the AUX bus - that limits possible functions a bit.
I have no AUX adaptor thus the HC variant will be implemented first, but the difference is essentially the prefix, so it will be simple switch.
I've also seen a nice hack with RPi0w mounted *inside* the HC providing the INDI interface to the HC.
The following user(s) said Thank You: Derek, Stephen
6 years 7 months ago #18671

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

  • Posts: 333
  • Thank you received: 24
Well, some time final became available and I am working on getting the Aux mc_slow goto working with the Slew to Target. I am also looking to add in the Backlash and PEC controls for the CGEM.

Please know there is nothing radical here, I am just adding functionality to the current celestron_gps driver.

Currently i am compile the celestron_gps_driver on my Mac via command line on using make within the libindi folder from git.

I would like to create a folder that would compile in 3rdparty driver directly on its own, creating the proper xml folders and such.

Is there a template folder that will do this that I can copy and move my current cpp files into?

I have tried to compile a single 3rdparty driver such as the indi-nexstarevo driver in its folder and I get errors -canot find INDI and such. Unfortunately, I have been spoiled with iOS development and the IDE, so make/cmake and such as new to me.

Any ideas? Thank you.
6 years 5 months ago #19907

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

  • Posts: 200
  • Thank you received: 57
You can use the scheme developed for CI of single drivers. Look at .travis.yml in main dir and build-3rdparty.sh in travis-ci subdir. I am using this scheme for my development of nexstarevo. It is based on my local scripts for single driver compilation. I'll include these scripts in next post. It is definitely possible to have selected drivers compiled in separate subdirs.
The following user(s) said Thank You: Stephen
6 years 5 months ago #19933

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

  • Posts: 200
  • Thank you received: 57
Here are my scripts for single driver compile. You need to have in your build directory two build directories and links to following places:
  1. src_master --> branch you are using
  2. src_<driver-name> --> branch with the driver development. It may be the same branch but not need to be
  3. libindi (build directory for the core library)
  4. 3rdparty (build directory for the drivers)
The links point to the top of the tree - not to the driver directory. The driver name is the suffix of the driver dir without "indi-" prefix.
Here are the scripts (build_core.sh):
#!/bin/bash
 
SRC="`pwd`/../master/"
 
( cd libindi
    cmake -DCMAKE_INSTALL_PREFIX=/usr/local . ${SRC}/libindi
    make
)

and build_3rd.sh:
#!/bin/bash
 
SRC="`pwd`/src_"
drv="gpsd nexstarevo"
 
for d in $drv ; do
( cd 3rdparty
    (
    mkdir -p $d
    cd $d
    if [ -e ${SRC}${d} ]; then
        SRC_DIR=${SRC}${d}
    else
        SRC_DIR=${SRC}master
    fi
    cmake -DCMAKE_INSTALL_PREFIX=/usr/local . ${SRC_DIR}/3rdparty/indi-${d}
    make
    )
)
done
 

I hope it helps.
The following user(s) said Thank You: Stephen
6 years 5 months ago #19934

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

  • Posts: 333
  • Thank you received: 24
Thank you Jochym. I will update you on how it goes. The Backlash settings may actually be working now, and will share as soon as done.

The nudging concept I have seen a few approaches in code so far:
- using the MC_SLOW Aux Commands
- using the 'r' precise command verse the 'R' used by celestron_gps

In your opinion, is using the MC_SLOW effectively the same as the precise command?

I am considering testing the distance to target and if it is with 1-2' then switching to the precise command. If this is known to already not improve things I will focus more on a pulse/nudge routine - assuming I can get there :)

Cheers!
6 years 5 months ago #19938

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

  • Posts: 200
  • Thank you received: 57
In my experience the slow approach tends to be more precise and gentle. The Celestron software uses it. But I suspect the accuracy increase is mostly due to the constant approach *direction* consistent with the one used at calibration. For the less precise mount that could be the crucial factor.
The following user(s) said Thank You: Stephen
6 years 5 months ago #19939

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

  • Posts: 333
  • Thank you received: 24
I see. I will try to add and test the precise slew first when under 2' and see if it can make Slew to Target more repeatable, and report back. It can be a week and a bit before I getting a chance to do this. If I can get below 200px the cropping can be less that it is useful.

Thank you for the help.
6 years 5 months ago #19953

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

  • Posts: 333
  • Thank you received: 24
Jasem,

I have some code for the indi_celestron_gps - allows the changing of the backlash settings for the mount. Tested tonight and it works well. It has helped improve the guiding, by tweaking with PHD2.

If this is of interest, please let me know the best way to send the code to you for evaluation/review/or...

I also have some test code for a more precise slew. This is still in testing.

Cheers!
6 years 5 months ago #20123

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

Sure, submit it as PR on Github.
6 years 5 months ago #20128

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

  • Posts: 333
  • Thank you received: 24
I will clean up the Backlash code, and once done I will attempt a Pull Request as soon as I figure it out in GitHub (I am assuming I need to fork or something.)

Moving on to the Nudging precise slewing...

Question: Does anyone have any ideas to determine from the RA/DEC coordinates to determine which N/E/S/W button to press to increase or decrease the RA/DEC position?

Any help, pointers or such would be welcomed.
Last edit: 6 years 5 months ago by Stephen.
6 years 5 months ago #20154

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

  • Posts: 333
  • Thank you received: 24
Jochym,

I have been working on celestron_gps driver for the AUX commands through the serial->USB celestron connection, through the handcontrol:
- backlash settings work
- got an unsync command from Celestron too (not done yet)

Perhaps you can help me out with the MC_SLOW_GOTO command. I can issue the command; however, I am am having trouble interpreting how to manage the MC_SLEW_DONE.

The Symptom is that once the command is issued, the mount continues in the one direction - i.e. I am testing the ALT command first,
e.g. hc_pass_aux_cmd(PortFD, MESSAGE_LENGTH, ALT, MC_GOTO_SLOW, result[0], result[1], result[2], RESPONSE_LENGTH, response )

Once issued the mount does not stop the slow move and just continues. It is clear I do not understand, and would appreciate any pointers.
6 years 4 months ago #21252

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

  • Posts: 456
  • Thank you received: 76
This symptom can happen if you send commands (such as query slew done) to the mount too quickly.
I wrote a mount controller that uses AUX commands through the handset. I wait 1second between 'query slew done' commands.
See line 169 here github.com/dokeeffe/auxremote/blob/maste...nt/MountService.java
Derek.
6 years 4 months ago #21259

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

Time to create page: 0.850 seconds