That error is just "noise", no effect on how the things work. Only happens when the default is active, I patched to fix it (not tested.) You can only switch using the command line then: For GEM: :SXEM

Anywhere in Config.h is fine, I'd put in just below the other serial port settings.

This setting is on the "WiFi" page.

When the release-4.23 arrives and we document everything I'll add a note to the MKS Gen-L Wiki letting users know. Sorry you had to be the user who reached this level. Thinking about it, if it were me

Separate but integrated. Read the Wiki, Encoder section: Control

I don't understand what the goal is here. It's been a while but from what I recall I didn't need to do much of anything other than installing the Cube Programmer and changing that address per the Wiki

Encoder support exists in OnStep, with the help of its WiFi and Ethernet addons.

If it were me I'd add the #define if hand soldering the chip, it makes the circuit easier. Pins 1,2,3,4 and 7 all to ground. Connect VCC to 8. Then you just need the I2C. Probably put the resistors ne

I didn't study this chips address scheme but it might very well not be compatible with the EEPROM library we use. Use an AT24C32 since that's a really good bet for working. On the other hand, changing

If you're a little adventurous you could definitely use just the EEPROM chip. If motivated, get yourself a breadboard (if you don't already have one) and some cheap jumper leads and an AT24C32 chip (f

It would be nice to see a breakdown of both Axis1 (RA) and Axis2 (Dec) drive design otherwise we are still guessing; but based on what I see... The Mega2560 will limit slew speeds likely below what th

0x57 is the (ZS-04) EEPROM address. 0x68 is the DS3231 RTC.

Those pads on the bottom of an WeAct Blackpill STM32F401 or F411 are for an SPI interface flash chip AFAIK. It's called "U3" and on the lower left of the schematic here you can see those pins are SPI

Exactly.

Not listed in the newer OnStep Config.h files and the compiler warns the user.

Well, it's of basically no use for visual observing since the rate corrections are so small you'd never notice them. That leaves imaging, and for that it (dual axis) can interfere with autoguiding, es

No. Adding the feature would be too likely to cause trouble for novice users "wanting it all", but not understanding the implications.

Note that the usb/serial chipset(s) in question here might be CP2102's. It would be informative and useful as an aid in isolating the issue to know which usb/serial chipsets the two ESP32's have. If b

During these experiments be sure to take note of the ESP32/OnStep state during the connect attempt. If it's being reset (rebooted) by the RTS (or DTR) line activity the connection attempt can fail sin

Another point that would be interesting to hear a comment on: If uploading OnStep to the ESP32 by the Arduino IDE (and not disconnecting USB) allows my ASCOM driver to connect. Does instead simply con