×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

indi_celestron_aux

  • Posts: 10
  • Thank you received: 1

Replied by Craig Oakley on topic indi_celestron_aux

I was able to get in some testing last night.

I tried the "Nearest Math Plugin" with no success. The default is "Inbuilt Math Plugin".

Just to verify my setup, I went back to the old Celestron CGEM driver (indi_celestron_gps) with the hand controller and RS 232 cable. Everything works with no issues.

Then I verified the SkyQ WiFi module without Ekos using the Celestron SkyPortal app. Again, everything worked as expected with no issues.

So back to testing the Celestron AUX driver. Before every test I reset the mount to the initial configuration: EQ North with RA/Dec set to the index marks. I also reset the driver (purge configuration).

I even tried the Celestron AUX driver using the serial interface. No matter what steps or math plugin I use, the mount does not know where it is pointing. I also tried both manual and plate-solving to sync.

For example: I reset my mount configuration and the driver. Power up with the hand controller connected. With the mount pointed towards Polaris, I use the hand controller to slew to a bright star and sync Ekos with the RA and Dec coordinates. I repeat this with at least 6 stars added to the alignment set size. Then I use Kstars to goto a new star close to where I was last pointing. The mount slews far in the opposite direction.

If you would like me to test any specific procedure, just let me know.

Thanks for the help...
2 years 5 months ago #77390
The topic has been locked.

Replied by Jasem Mutlaq on topic indi_celestron_aux

After the 1st step, slewing to a bright star and then syncing, does the mount crosshair jump to the new synced position?
2 years 5 months ago #77392
The topic has been locked.
  • Posts: 10
  • Thank you received: 1

Replied by Craig Oakley on topic indi_celestron_aux

Yes. In fact, after each slew and sync the crosshair hovers over the correct position in Kstars.

However, when performing a goto after the sync stage, the crosshair no longer matches the actual mount position.
2 years 5 months ago #77394
The topic has been locked.
  • Posts: 200
  • Thank you received: 57

Replied by Paweł on topic indi_celestron_aux

I do not understand what is happening here. This is quite different from anything I get on my AltAz mount. Unfortunately, I have no RaDec mount to test it on. I think that we will need to extend the simulator to be able to test RaDec as well. No we have to ask Fabrizio (or someone else) to test it on his equatorial mount to verify that the driver still works at least on *some* eq mounts. Craig: remember that you *cannot* (must not) use hand controller with the driver. Use android indi client instead. When you turn everything on after full reset of all components (did you switch the driver to Eq-mode?, Did you activate the alignment module?): What is the reported position of the mount on kstars before any sync operation? What about first sync? What is happening with the mount if you use motion control buttons in the driver (in which directions it is moving)?
2 years 5 months ago #77396
The topic has been locked.
  • Posts: 10
  • Thank you received: 1

Replied by Craig Oakley on topic indi_celestron_aux

1) The hand controller was originally disconnected as suggested in the AUX documentation. I only connected the hand controller for testing. The hand controller is also needed during testing using the serial/RS232 interface.

2) Yes. When I first connect the AUX driver, I select the "Mount Info" tab and change the "Mount Type" to "Equatorial". The default is AltAz.

3) Yes. The "Alignment Subsystem Active" button and the "Inbuilt Math Plugin" button is green and already active after first connecting. To confirm the alignment system is active, I tried toggling the button off and then back on. I also tried the "Nearest Math Plugin".

4) After first connecting and changing to Equatorial, the mount coordinates show as 00 00 00 RA and -00 00 00 DEC.

5) After the first sync, the RA and DEC show the correct values of the star selected. This is correct for both manual syncing and plate solving.

6) The motion control is correct. i.e. "Right" moves the RA counterclockwise and "Up" moves the Dec counterclockwise. This is the same as if I was using only the hand controller without Ekos. This motion is also the same if using the Celestron SkyPortal app.
2 years 5 months ago #77407
The topic has been locked.
  • Posts: 37
  • Thank you received: 0

Replied by Maciek on topic indi_celestron_aux

I've been trying today 4 sync sessions with my evolution mount (all started from alt:0;az:0 and based on plate solving) 3 first I was using "Nearest Alignment" and sorry to say, but was quite bad
first point error about ~20000 arcsec
second ~11000
third ~4000

While using "slew to target" It aborts after few tries at around 130 arcsec error.


Fourth session was using built-in plugging and It was:
first point error about ~20000 arcsec
second 3000 arcsec
third 600 arcsec

And while using "slew to target" It aborts after few tries at around 60 arcsec error.


My issue is still not resolved, You have to use this error prone method with first point directing alt0:az0. If you miss this point by a few degs, your whole calibration process is working bad
2 years 5 months ago #77440
The topic has been locked.
  • Posts: 37
  • Thank you received: 0

Replied by Maciek on topic indi_celestron_aux

And I just run into something odd - after writing last message, pressed again "slew to target" error jumped from 60 to 400arcsec (ok some time passed by) but it goes into loop moving to the same place and plate solving same place, but on kstars map it was moving to right place, and after plate solve jumped into real bad place.
2 years 5 months ago #77441
The topic has been locked.
  • Posts: 37
  • Thank you received: 0

Replied by Maciek on topic indi_celestron_aux

@Paweł, @Jasem I can provide access to my indi server over internet for you
2 years 5 months ago #77442
The topic has been locked.
  • Posts: 37
  • Thank you received: 0

Replied by Maciek on topic indi_celestron_aux

In daytime like today I can point the moon using my muscles, and tell SkyPortal that I am pointing it or just use my NexStar hand controller to do the same. Just one calibrating point with proper leveled mount is enough to follow the moon for hours. No North Alt 0 requirements not any, just point to the moon and follow it. Not a chance with Indi_celestron_aux :-(

I have a dream - to take out my gear, connect to it from my worm home (just like using astroberry with indi server) - press one button (auto align to sky using mount, camera artificial horizon and plate solve) and just enjoy the views....


Have a good day :-)
2 years 4 months ago #77968
The topic has been locked.
  • Posts: 10
  • Thank you received: 1

Replied by Craig Oakley on topic indi_celestron_aux

I started to debug my issues with the indi_celestron_aux driver and made a major breakthrough last evening.

Please forgive my coding methods, I have been familiarizing myself both with the INDI framework and development under Linux.

To summarize the issue, it appears the indi_celestron_aux driver never initializes the motor controllers using the MC_SET_POSITION command. Both the ALT and AZM controllers have no known values and thus no home position (i.e. the mystery slew limits in RA).

For example, I added a "zero" button to the indi_celestron_aux driver. This allows me to initialize the controllers with a home position after startup.

AUXCommand raCmd(MC_SET_POSITION, ANY, AZM);
raCmd.setPosition(STEPS_PER_REVOLUTION / 4);
sendAUXCommand(raCmd);

AUXCommand decCmd(MC_SET_POSITION, ANY, ALT);
decCmd.setPosition(STEPS_PER_REVOLUTION / 2);
sendAUXCommand(decCmd);

This immediately fixes my slew limit problems. The mount now knows I am positioned at the index marks. However, this is still a work in progress.

I would like to mention two very helpful resources: Rick Bassham's indi-celestron-cgx driver and the AUX protocol document by Andre Parquette (see below).
github.com/rickbassham/indi-celestron-cgx
www.paquettefamily.ca/nexstar/NexStar_AUX_Commands_10.pdf

In my early investigation, I found it easy to modify Rick Bassham's driver to support the SkyQ WiFi module without the need for a hand controller. Since my mount does not support automatic alignment (MC_LEVEL_START and MC_LEVEL_DONE), I also modified the code to manually zero the mount at startup.

Testing the mount indoors with the modified indi-celestron-cgx driver, all my primary issues are fixed. After the initial startup, I can fully control the mount through WiFi with no hand controller. I can also successfully goto any object using KStars.

I am hoping to test outdoors in the next few days; my local weather has not been cooperating.
The following user(s) said Thank You: Jasem Mutlaq
2 years 4 months ago #78051
The topic has been locked.
  • Posts: 78
  • Thank you received: 3

Replied by Gary McKenzie on topic indi_celestron_aux

Craig,
are you using a CPC mount or a cgx. I have a CPC wedge mounted and would like to use the aux driver, but found that the lack of a home starting position was a pain. Your mods seem to fix it....so wanted to confirm I could use it with my mount..
cheers
Gary
2 years 4 months ago #78052
The topic has been locked.
  • Posts: 10
  • Thank you received: 1

Replied by Craig Oakley on topic indi_celestron_aux

I am using the original Celestron CGEM with only the SkyQ WiFi module (hand controller is disconnected). My test setup is with the mount in EQ North configuration.
2 years 4 months ago #78053
The topic has been locked.
Time to create page: 1.484 seconds