SK3 Turnigy 6374 149 / encoder CUI AMT102 => can VESC 4 support position control?

perfect. this limitation is perfectly fine.

unfortunately i do not have my VESC 4 cards nearby, thus vesc_tool wont start its excellent motor config wizard

in previous setup i was using velocity control over UART using hall effect sensors and foc.

here looking i settings windows i see

Motor > General > General > Motor type > FOC (is it ok?)
Motor > General > General > Sensor Port Mode > ABI encoder / AS5047 encoder / AD2S1205 resolver (which one should i choose?) 
Motor > General > General > ABI encoder count > 8192 (looks like a 2048*4 so should be ok, can u confirm?)

Motor > FOC > General > Sensor Mode > Encoder 
Motor > FOC > Encoder > Encoder > Encoder Offset > 180.0 (should i keep this default value?)
Motor > FOC > Encoder > Encoder > Encoder Ratio > 7.0 (what is this?)
Motor > FOC > Encoder > Encoder > Encoder Inverted > False (what is this?)

Motor > PID Controllers > Position Controller > Kp / Ki / Kd / Kd Filter ==> please tell me i do not have to touch this and the wizzard will take care of it???
Motor > PID Controllers > Position Controller > Position Angle Division > 1.0 (what is this?)

in terms of cabling the encoder, is it like hall effect = dont care about how things are connected, because the wizzard will figure it out alone? or do i need to follow a particular convention?

Now for controlling the position, it seems the API is to talk in degrees instead of encoder counts (which is fine). So on principle issuing the following commands :

+360 makes the motor turns one complete revolution in positive direction
-720 makes the turns spin backwards 3 revolutions
0 makes spin forward 2 revolutions
0.5 makes the motor spin forward 0.5/360*8192 = 11 encoder ticks

==> ???

and what is the best way to make that single turn to have the encoder index found? (calibration i suppose)

(ok maybe there are too many questions here... but the i did not find enough explanations in the manual => https://vesc-project.com/node/180)

What???

Limited to single turns??

Can't be. What if there is a 30:1 gear reduction after motor?

We'll see. I'll try and report. Isn't VESC opensource? Maybe if default FW limits absolute positioning to single turn someone can add support for multiple turns?