hi,
is it possible to use the jog controls in sharpcap to control a planewave mount connected thru PWI4 mount controller software .
I am able to connect to the mount and also use the goto features.
However when i want to jog the mount as i search for framing lunar features, the up/down/left/right arrows dont work ?
is there a solution for this ?
Vikas Chander
Planewave PWI 4 jog
-
admin
- Site Admin
- Posts: 17342
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Planewave PWI 4 jog
Hi,
there are two possibilities here
1) The PWI ASCOM driver does not support the 'MoveAxis' command that SharpCap needs to move the mount using the arrow keys - in this case the buttons will be fully disabled and there isn't anything that can be done unless PlaneWave make a new version of their ASCOM driver that does support 'MoveAxis'.
2) The buttons are enabled but the default movement rate is really slow - if this is the case there will be different speeds available in the movement rate dropdown (to the right of the up button). Select a higher movement rate like a high multiple of sidereal rate or something shown in degrees per second. If this rate dropdown isn't available then the problem is very likely the lack of 'MoveAxis' as mentioned above.
cheers,
Robin
there are two possibilities here
1) The PWI ASCOM driver does not support the 'MoveAxis' command that SharpCap needs to move the mount using the arrow keys - in this case the buttons will be fully disabled and there isn't anything that can be done unless PlaneWave make a new version of their ASCOM driver that does support 'MoveAxis'.
2) The buttons are enabled but the default movement rate is really slow - if this is the case there will be different speeds available in the movement rate dropdown (to the right of the up button). Select a higher movement rate like a high multiple of sidereal rate or something shown in degrees per second. If this rate dropdown isn't available then the problem is very likely the lack of 'MoveAxis' as mentioned above.
cheers,
Robin
-
vikaschander
- Posts: 2
- Joined: Mon Mar 30, 2026 3:14 pm
Re: Planewave PWI 4 jog
hi Robin,
thanks for your reply. So if MoveAxis is not implemented in PWI4, does this also mean the feature tracking will not work. I am asking because when lunar imaging, the feature i am trying to keep centered slow drifts away from center....i am not using any ROI as i am using the full sensor resolution, in this case a ZWO 678 ( 3840 x 2160 ).... TIA ...vikas
thanks for your reply. So if MoveAxis is not implemented in PWI4, does this also mean the feature tracking will not work. I am asking because when lunar imaging, the feature i am trying to keep centered slow drifts away from center....i am not using any ROI as i am using the full sensor resolution, in this case a ZWO 678 ( 3840 x 2160 ).... TIA ...vikas
-
admin
- Site Admin
- Posts: 17342
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Planewave PWI 4 jog
Hi,
Feature tracking can still possibly be used if the ASCOM driver implements pulse guiding instead - in the feature tracking you will find that the only option for the movement rate is the 'guiding rate' if that is the case.
In that scenario, the feature tracking will probably work, but the calibration procedure will be slow. Using the 'continuous movement' option for calibration and setting a smaller number for the required movement of the image during calibration will help a bit with that.
cheers,
Robin
Feature tracking can still possibly be used if the ASCOM driver implements pulse guiding instead - in the feature tracking you will find that the only option for the movement rate is the 'guiding rate' if that is the case.
In that scenario, the feature tracking will probably work, but the calibration procedure will be slow. Using the 'continuous movement' option for calibration and setting a smaller number for the required movement of the image during calibration will help a bit with that.
cheers,
Robin