You can do it both way. NINA's automatic meridian flip works on her own and have nothing to do with settings in the controller, if you're doing imaging sequence you should configure NINA to do flips.

#bluepill

I think you should uploaad your Config.h and someone may help

#EQ5 #mks #tmc2208 #tmc2103

Idk about SP, but ASCOM driver can sync time properly, (same as Android App). First you need to setup location and tick "Set Date/Time on connect" then apply and reconnect.

Afaik there is no such thing as TMC2103. There is TMC2130 but it's different and that pinmap will not work for TMC2208/TMC2209 (or vice versa) as they have different type of interface. For MKS Gen L v

#EQ5 #mks #tmc2208 #tmc2103

First time use Android App to set location and UTC offset automatically by using phone location services to avoid confusing it with timezones. Then you can read the data, remember for future use... Un

Actually it does. In NINA 2.0 there is new plugin called Scope Control which can be installed easily from NINA plugin manager. This is not the same as one in equipment manager.

Can you elaborate what actually happens when it "hangs"? Is it stall or restarts? Is this happening right after USB is connected to PC or when ASCOM driver is connected (in that case, did you unchecke

I am not sure about this. Reference design didn't took into account TMCs in all axis. Protection diodes are present in 1&2 only and nowadays there are standalone TMCs (with same limitation) which can

Maybe try to remove power from your USB cable: cut out 5V wire (red) and leave other three wires intact: D+, D- and GND (green/white/black) and try that way? I read about similar issues with R32 board

Then you are on wrong place friend, go for AstroEQ instead. It is limited to legacy drivers and EQ mounts only. And let me correct myself, EQMOD have optionally custom horizon data (defined in json fo

Erything EQMOD can do, can also be done with OnStep via Android App, SHC or SWS. Only thing present in EQMOD and missing in OnStep is custom horizon, which I never found particularly useful.

No. EQMOD communicates on Synta protocol, while OnStep works with classic LX200, from command perspective these are two different languages. Any LX200 compliant client should work and for minimal inve

First, check battery voltage and check if battery is properly inserted (it can be shorted if inserted inproperty by accidentally bending contact plates). Then connect RTC module to other device (i.e a

#rtc #blackpill #maxstm3 #ds3231 #pps

Long answer (also no): DRV8825 (typicall generic driver) by default operates in dynammic decay mode (starts with 75% in fast then switch to slow decay in last 25% of each duty cycle), because pin 19 o

And one more thing, since you're using Android app. My way of choice for connecting Android App is Bluetooth. Because only this way I can connect to both OnStep on remote dark site and have mobile dat

I am not sure I fully understood the problem here. However, take this into account: Initial fixed IP addresses or DHCP are set in Extended.config.h and afterwards you can change them from inside SWS (

For which build? Usually DRV8825, TMC2208, TMC2209, LV8729, S109, TMC2130 DIY are considered as drop-in replacement but some may have some specific requirement. Have a look at this page: https://onste

Since starting of this thread, I added an acitive buzzer, leds and BME280 weather aensor to this build. I want to share first light photos as a proof of successful conversation: This is M42, 50.mimute

For a week I was unable to connect Android App via bluetooth to OnStep controller which uses HC-05 module, that used to work just fine until recently. After night spent on debugging and checking all w

I had issue with one which wouldn't work with 5V but worked well with 4.96V, but it was based on ESP32. I had it connected to XL4015 buck converter with both voltage and current adjustment and there w

#wmosd1 #wemos