I noted the GS server using Moveaxis property behaves different then for example EQMOD and Telescope Simulator.NET.
The sky moves with 0.004178075 degrees/sec in RA. If I set using ASCOM the property moveaxis(0,0.004178075) then both EQMOD and Telescope Simulator.NET are steady in RA. But via GS Server the mount is moving at double rate sidereal rate. So GS server is adding the value to the sidereal rate and EQMOD and Telescope Simulator.NET are not.
ASCOM_DeviceInterface_ITelescopeV3_AxisRates.htm) are absolute, unsigned values and apply to both directions, determined by the sign used in this command.
Not very clear but it looks like the rate is absolute and not relative to the sidereal rate. It would be better to adapt GS Sever to this or ask for more clarity from ASCOM developers.
I noted the GS server using Moveaxis property behaves different then for example EQMOD and Telescope Simulator.NET.
The sky moves with 0.004178075 degrees/sec in RA. If I set using ASCOM the property moveaxis(0,0.004178075) then both EQMOD and Telescope Simulator.NET are steady in RA. But via GS Server the mount is moving at double rate sidereal rate. So GS server is adding the value to the sidereal rate and EQMOD and Telescope Simulator.NET are not.
The property is described at: https://ascom-standards.org/Help/Platform/html/M_ASCOM_DeviceInterface_ITelescopeV3_MoveAxis.htm
There is stated:
Not very clear but it looks like the rate is absolute and not relative to the sidereal rate. It would be better to adapt GS Sever to this or ask for more clarity from ASCOM developers.
Han