Thank you for your reply.
I will check again when it is up.

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.

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
THEN, we apply degrees offsets:
Now I have might made an assumption which may be incorrect (1 encoder revolution = 1 mount revolution). I will know from the table values.

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.

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)

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

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.

I found out!
approved.

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.

Thank you as always
I will confirm it at night.

私はいつもあなたの助けに感謝しています。
私は更新されたDSCドライバをチェックしました。

私はそれを長い文章にするので3つに分けます。

エンコーダのステップは4096、AltAZ Mountです。
（前回と同じ山です。）

About setting in half step
 
  It is from the Axis Settings tab.
 I tried the newly added Half button.
 
 # 1 Ticks Scale 0.087890625
 # 1 Ticks Offset -180
 # 2 Ticks Scale 0.087890625
 # 2 Ticks Offset -180
 
 With this setting, both Axis 1 and 2 become 0 and 0. (Azimuth angle 0 degree, altitude angle 0 degree)
 However, moving the azimuth angle from north to west will result in a negative angle.
 Both axes will be advanced from -180 ← 0 → 180.
 
 this
 
  # 1 Ticks Scale 0.087890625
 # 1 Ticks Offset 0
 # 2 Ticks Scale 0.087890625
 # 2 Ticks Offset 0
 
 If you do, Axis 1 and 2 will be both 180 and 180. (Azimuth angle 180 degrees, altitude angle 180 degrees)
 However, in this setting, both the azimuth angle and the altitude angle are displayed from 0 ° → 360 ° → 0 °,
 With this setting, if the initial value of Axis 1 and 2 becomes 0,0, it will be in the correct motion.
 
 # 1 Degrees Offset, # 2 Degrees Offset changes to Axis 1, 2 even if the value is changed
 It does not seem to work because it is not there.