Looks nice, i have made a small 3d printed mount myself using geared steppers with 1:720 ratio and have been thinking about building something big 3d printed as well. Using a wheel hub is a nice idea.

#diy

Hi there, no need to pay for it, if you like you can contact me i was planning to look at the cnc v3 shield myself so this would be an interesting project to me. So far converted 5 different rigs to a

#cnc

I added it to the config myself, that is what i expected to do from what i read down here. #define MODE_SWITCH_BEFORE_SLEW ON // Experiment to test microstepping rate shift I put it under motion contr

I did some more testing with the new version M. Guiding seems to work fine now while nina is active and doing things, did not have any more weird issues of runaways when starting guiding, i however ha

Miracles happend and i had 2 hours without clouds! I just flashed the latest version and now my RA seems to ignore the reverse parameter. (This is with the MODE_SWITCH_BEFORE_SLEW) set to on. Fixed it

Thanks this gives some insight, i will give it a try with and without. From previous trying i know the exact steps to mess up the guiding so testing it with and without is not really an issue. Will re

One more post then i will shut up :') I see that MODE_SWITCH_BEFORE_SLEW was added since patch E and i see the question down here in the topic to test with it. I am a bit confused if i need to enable

Missed your post :) i was just browsing the GitHub, will flash the new version tomorrow and test as soon as we have clear sky's again (Bought a new camera so slim chance that will be this year :') )

Maybe add a bit more info here: This happens for me when slewing in NINA using NSEW buttons and with the polar alignment plugin, this weirdly also ignores all limits of the mount (have not figured out

if that was directed at me: FysETC S6 v2.0 board with currently 4.24E on it. other data: #define AXIS1_DRIVER_MODEL TMC5160_VQUIET #define AXIS1_DRIVER_MICROSTEPS 32 #define AXIS1_DRIVER_MICROSTEPS_GO

This sounds exactly like the issue i am having, will be following this with a close eye :) (my topic from some time ago: weird_issues_with_phd2 )

I solved my problem by cutting the enable pin of the axis1 driver and jumping it to axis2. Enable pin on Axis 1 was stuck high.

#fysetc #S6 #configuration

Hi there, i received a second Fysetc S6 V2 board today, wanting to replicate my first build with 5160 drivers. Everything went fine till i tried to turn the motors for the first time. Y axis (axis 2)

#fysetc #S6 #configuration

One more update, sorry for spamming inboxes. I just flashed with my new desired slew rate set to 2.5, so i dont have to change to 0.5x every time. Result, no difference whatsoever :) Then i thought we

#S6

Sorry for replying to myself, i can't seem to find any edit button to update my post: so far: > booted up > slewed with stellarium (using the ascom device hub and setting max slew speed in onstep to 0

#S6

On Wed, Aug 11, 2021 at 07:48 PM, Khalid Baheyeldin wrote: Thanks, that explains a bit more, so if i change the Slew speed to 1x the guide speed will also be reset, that is what i get from the answer

#S6

He means the ASCOM device hub (it gets installed with the ascom platform). You then connect PHD2 and stellarium both to the Device hub (which shows up as an ascom device itself). And the device hub is

Hi there, i am new here, hope i am doing this right :') I have recently build two onstep drives, one mks and one Fysetc (for a diy startracker and for my LXD75). This works absolutely brilliant, in co

#S6