Kedar, That is by design. When you park your mount it saves the current focuser position in the eeprom.

#features #wemos #cnc #esp32

Peter, Try checking Reverse Dec output after meridian flip in Advanced settings in PHD2. https://openphdguiding.org/man-dev/Advanced_settings.htm There is a test in the documentation to see if it is n

Peter, I haven't tested extensively, but I successfully unparked from the sequencer last weekend. Lloyd

If your equipment will allow, try increasing the minutes after meridian in NINA to a number >8. Flipping right at the meridian can be problematic.

The difference I see from my config and Hendrick's is he is using 5160_VQUIET and I am using 5160_QUIET. Could this make a difference? I can try V_QUIET (I thought I read somewhere it shouldn't be use

The above message was for Eric.

Do you plate solve in NINA? This is where I always see the error crop up. Standard goto has not been an issue for me and Howard fixed the issues with guiding/PhD. I can reproducibly make the tracking

Unfortunately this did not work. No issues during the initial slews or guiding. During the plate solving slews, the rate would speed up.

Howard, I will give that a try. The other thing I may do to test Andras's suggestion is turning of the microstepping switch on 1 axis at a time to isolate the problem (I don't have any extra 5160s at

I was able to get out tonight to test. Unfortunately, the change to the guide time limit did not work. The problem was intermittent but would usually appear (tracking too fast). However, I thought I w

I made the change to config.h and checked the box in the driver. Unfortunately, it looks like I will be clouded in for the next few days.

Well Howard, I think 4.24m was a partial success. While it seems the guide rate may no longer be an issue (yay!), now the tracking rate is being set too high. After an initial slew in NINA, everything

Great news Howard. If the clouds cooperate I'll give it a go tonight. Thanks!

My discord post on the NINA forum: I did some more testing on this last night. I connected my mount to cdc and performed a slew. Turned on PHD and the mount tracked and guided fine. Repeated the same

I am still having issues with tracking rate and guide rate. After a slew in NINA the tracking rate is too fast. I pushed the manual move axis buttons in NINA to get the mount to track at the proper ra

I can say that this also happened when I was using 1.0x as well. What makes me think that this isn't the issue is that I can hear the motors "rev" like it is slewing. I would expect to not hear them a

Update: I first had to press the proper guide rate (for me 0.5x) then tap the directional buttons. The it switched to the correct rate.

Just the direction buttons. I tapped on all 4, in no specific order.

This is the same behavior that I observe as well and mentioned here: https://onstep.groups.io/g/main/message/36837 You may be onto something about the microstep switching. I never observed this with m

I purchased a Losmandy G11 with a 492 clock drive in December last year with the intent to convert it to goto with OnStep. My Vixen SP build was a fun project, but I had already nearly maxxed out the