Juan Menendez replied to the topic '[SOLVED] Calibration problem' in the forum. 11 months ago

I found there is a bug in the celestron driver affecting the pulse guiding commands!
I made a pull request to the main INDI repository a few minutes ago. It should be fixed in the next release.

Read More...

Juan Menendez replied to the topic 'Setting dome parameters' in the forum. 1 year ago

I've been testing the driver and found an error in the code!
I have to test it in the real MaxDomeII board, but I'm quite confident it is the bug that is causing you trouble.
I'm pretty busy this week, but I'll try to fix it as soon as I can.

Read More...

Juan Menendez replied to the topic 'Setting dome parameters' in the forum. 1 year ago

I think a "Park" button and a "Park azimuth" field would be very interesting additions to the MaxDomeII control panel. Also, a self-calibration procedure would be very useful.
I will work on those features as soon as possible. Thank you for your suggestions!

Read More...

Juan Menendez replied to the topic 'Setting dome parameters' in the forum. 1 year ago

There is no autocalibration method implemented in the MaxDomeII driver yet. If you want to figure out the ticks per turn you can use the following procedure:

  • go to the home position
  • put a high number (1000, for example) in "Ticks per turn"
  • move the dome a full turn with the manual buttons and check the angle in "Absolute position"
  • calculate the ticks per turn: 1000*angle/360
You have to choose a high initial value in "Ticks per turn" in order to be sure a full rotation does not exceed 360 degrees.

On the park azimuth question: I don't know what is the best method. I always keep the dome in the home position when unused, which is defined by the physical location of the index mark.

Read More...

Juan Menendez replied to the topic '[SOLVED] Commit (5 and 20) days aago breaks Celestron AVX' in the forum. 1 year ago

It's good to know it!
Thank you for your feedbak

Read More...

Juan Menendez replied to the topic 'indi-web -v --> not starting' in the forum. 1 year ago

Maybe you have a malformed XML file in /usr/share/indi.

You could add a new line to driver.py in order to see what xml file is being processed, like this:

for group in root:
    print(fname)
    family = group.attrib['group']
    ...


Read More...