Ok, got it now. This is due to the WIndows screen resolution being too low. Even in WIndows 10 which uses scaling, windows does not scale properly but rather trims the window size instead, hence cutting off the buttons at the bottom to make the window fit on the screen.
You need to increase the resolution of the display.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
another issue I have noticed is with the step size. I wasn't able to use it because the stepsize was smaller than 1 and it wasn't accepting any number below zero. now I have changed to half-step instead of microstepping so my step size is "1.754". But still it is not accepting it and changing it to 1(windows app).
the ascom driver setup is not changing it, it justs rounds it to 1.75. however when I ask for the step size in the ascomapp it says "100". I haven't used step size for anything yet including autofocus so it is not critical but I just wanted to let you know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You have both checkboxes on for StepSize?
Enable Step Size
Update on Connect
Without connecting to a controller -
If I open the driver properties - I can type in 0.3 as a step size, then click OK.
When I go back in again , it still says 0.3 as its remembered by Windows.
The best way is to set step size using the windows app. Then in ASCOM no need to specify it at all BUT must have Enable stepsize checkbox checked before connecting.
Hi Robert,
This is not a serious problem but has been bothering me, I'm attaching a screenshot. https://imgur.com/a/iXxA2
I don't know what the problem is?
Ok, got it now. This is due to the WIndows screen resolution being too low. Even in WIndows 10 which uses scaling, windows does not scale properly but rather trims the window size instead, hence cutting off the buttons at the bottom to make the window fit on the screen.
You need to increase the resolution of the display.
try this 243 release
thanks Robert it seems to work fine I'm attaching a screenshot. https://imgur.com/a/iR4dI
another issue I have noticed is with the step size. I wasn't able to use it because the stepsize was smaller than 1 and it wasn't accepting any number below zero. now I have changed to half-step instead of microstepping so my step size is "1.754". But still it is not accepting it and changing it to 1(windows app).
the ascom driver setup is not changing it, it justs rounds it to 1.75. however when I ask for the step size in the ascomapp it says "100". I haven't used step size for anything yet including autofocus so it is not critical but I just wanted to let you know.
You have both checkboxes on for StepSize?
Enable Step Size
Update on Connect
Without connecting to a controller -
If I open the driver properties - I can type in 0.3 as a step size, then click OK.
When I go back in again , it still says 0.3 as its remembered by Windows.
The best way is to set step size using the windows app. Then in ASCOM no need to specify it at all BUT must have Enable stepsize checkbox checked before connecting.
To check what it is in ASCOM, use the ASCOM APP CLIENT
https://sourceforge.net/projects/arduinoascomfocuserpro2diy/files/CODE%20ASCOM%20DRIVER%20TESTER/ASCOM.myFocuserProASCOMApp_1_3_0_2.zip/download
Once connected, use the menu Settings-Get Step size to check the value in the controller.