×

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

Bi-monthly release with minor bug fixes and improvements

I would like support of Digital Setting Circles.

  • Posts: 447
  • Thank you received: 30
Hello
I upgraded to the latest state and checked the DSC driver.

Explain the results and measures.
(Please also check the description of attached data)

1. Since it is set to the hour angle, it does not match the movement of the star map.
(Setting of azimuth angle and altitude angle is required, the unit is angle).

Encoder resolution can not be set. There is no place to enter.

3. A check box is required to change the polarity of the encoder.


The procedure up to the above observation is as follows.

1. Point the telescope to the south or south of the south.

2. Connect the INDI driver.

Enter the direction of the telescope set in 3.1.
(North: azimuth angle 0 degree, altitude angle 0 degree,
South: in the case of an azimuth angle of 180 degrees, altitude of 0 degree)

4. Point the telescope to the reference star, introduce it to the center, right click on the star chart software to display the menu and synchronize.
(Make sure that the azimuth and elevation angle of the star's current time are set from the star chart software)

Example: When starting at local time 170 degrees azimuth, elevation angle 45 degrees, encoder step 4096 (both axes) polarity +, south direction, altitude angle 0 degrees.

The encoder count of the azimuth angle of 170 degrees is as follows.
2048 - ((180-170) * 4096/360) = about 1934

The altitude angle is 45 degrees or less
2048 - (45 * 4096/360) = about 1536

When synchronizing on the star chart software, if there is a deviation from the above values, it is input as an offset value.

PS.LNMOJB - Z.TXT is a log file. The file name changed as you brought the data to Mac.

that's all.
7 years 1 week ago #15330
Attachments:

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

  • Posts: 447
  • Thank you received: 30
P. S.
There were some missing items in the mentioned item.

1. Offset + scale of RAW encoder value. → Present
2. Axis resolution → Absent
3. Axis offset → current
4. Axis reversal → Absent
5. Mount type → None
7 years 1 week ago #15331

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

yeah PPA is not updated yet, I'll make another PPA build now.
7 years 1 week ago #15335

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

  • Posts: 447
  • Thank you received: 30
Thank you for your reply.
I will check again when it is up.
7 years 1 week ago #15340

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

  • Posts: 447
  • Thank you received: 30
I am always grateful for your help.
I have installed a new version so I will report it.

My environment is
I checked at 4096 on both axes.

Initial setting "Axis Settings" tab of the INDI driver

# 1 scale, # 2 scale to 0.087890625
(Value of 360/4096)
I set # 1Offset, # 2Offset to 180.

By setting this, Axis 1 (possibly azimuth) in the "Main Control" tab,
Axis 2 (probably the altitude angle) became 0 respectively, and when you moved the telescope, the numbers of Axis 1 and Axis 2 changed normally.
(0-360

However, unfortunately it did not work properly for the following reasons.

1. The numerical values ​​of Axis 1 and Axis 2 are not accurately reflected in Kstars, and the movement of the pointer indicating the position of the telescope is strange. (Proceed extremely or step in the opposite direction.)

2. The "Sync" command is not functioning for both Kstars and INDI drivers.

3. When checking the inversion of polarity in the "Axis Settings" tab of the INDI driver,
The numerical values ​​of Axis 1 and Axis 2 are strange.
(In the above setting, check Axis 1, Axis 2 0,0 (range 0 to 360), check it, it will be 720, 720)

that's all.

Please confirm when you have time.
7 years 1 week ago #15374
Attachments:

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

I think there is a confusion here. Before we discuss this, can you please provide me with a table of raw Axis1/Axis2 encoders values from your BBox and the corresponding Az/Alt that you expect? I think this would be a good starting point. Now to you points:

1. I think there is confusion for "offsets". There are TICKS offsets, and DEGREES offsets. I moved the degrees offsets into the same group as the rest of the offsets now to avoid this confusion. However, the equation used is this:

First, we apply raw TICKS offsets to what we read:

// Apply raw offsets
    Axis1 = (Axis1 * EncoderOffsetN[OFFSET_AXIS1_SCALE].value + EncoderOffsetN[OFFSET_AXIS1_OFFSET].value);
    Axis2 = (Axis2 * EncoderOffsetN[OFFSET_AXIS2_SCALE].value + EncoderOffsetN[OFFSET_AXIS2_OFFSET].value);

THEN, we apply degrees offsets:
double Axis1Degrees = (Axis1 / AxisSettingsN[AXIS1_TICKS].value * 360.0) + EncoderOffsetN[AXIS1_DEGREE_OFFSET].value;
double Axis2Degrees = (Axis2 / AxisSettingsN[AXIS2_TICKS].value * 360.0) + EncoderOffsetN[AXIS2_DEGREE_OFFSET].value;

Now I have might made an assumption which may be incorrect (1 encoder revolution = 1 mount revolution). I will know from the table values.
7 years 1 week ago #15381

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

Ok so after a little research it seems my assumption above is valid. So I updated the driver as well to include INDI Alignment Subsystem so you can do syncing, but do not use that yet. Let's get the basic stuff done. Now the important part is table of Encoders #1 & #2 along with Alt/Az, and also RA/DE if you can all. 12 points would be OK.
7 years 1 week ago #15385

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

  • Posts: 447
  • Thank you received: 30
Thank you for your reply.
It seems that it is not listed in the debug log, so I annotated the photo for clarity.

If the numbers of Axis 1 and 2 are treated as they are in Kstar, I think they will synchronize with the position of the star map.

I think that it is necessary to adjust 2 and 3 described last time.

2. The "Sync" command is not functioning for both Kstars and INDI drivers.

3. When checking the inversion of polarity in the "Axis Settings" tab of the INDI driver,
The numerical values ​​of Axis 1 and Axis 2 are strange.
(In the above setting, check Axis 1, Axis 2 0,0 (range 0 to 360), check it, it will be 720, 720)
7 years 1 week ago #15403
Attachments:

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

Ok there is still some confusion. I sent you Google chat/hangout invitation, please accept. Or you can come to KStars channel on Matrix: riot.im/app/#/room/#kstars:matrix.org
7 years 1 week ago #15407

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

  • Posts: 447
  • Thank you received: 30
Links can not be opened with errors.
Did you invite a chat for an address registered in the forum?
I examined it, but it was not there.
7 years 1 week ago #15421

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

  • Posts: 447
  • Thank you received: 30
I found out!
approved.
7 years 1 week ago #15422

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

Ok so I added "Axis Range" property with "Full Step" and "Half Step" options. For full step, the range goes from 0 to max (0 to 4096 in your case). For half step, is goes from -0.5*MAX to 0.5 MAX (-2048 to +2048), so please select Half Step for your BBox and try again tomorrow.
7 years 1 week ago #15435

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

Time to create page: 0.359 seconds