The Config.h matches what is in the spreadsheet. If you will not be using a PEC sensor, then set AXIS1_STEPS_PER_WORMROT to 0. I don't think this is the cause of your issue. Let us know how the mount

#configuration #ci700

I agree with Mike. A bad RJ45 cable cannot harm the microcontroller. It can damage the driver, maybe, but not the MCU. When you insert the Blue Pill into the PCB, and power up, does the PC13 LED light

If someone has the skill and tools to do this replacement, then please don't use any STM32F103 chips at all. Instead, try to located the pin compatible STM32F303CCT6 chip, and use that instead. Why? -

Did you set the location, date, time and UTC Offset properly? You may want to use the Serial Monitor in Arduino IDE's with 9600 baud, and enter the commands at the very bottom of this page, to see if

#configuration #ci700

Yes, it does not do PEC. It only reports whether PEC is active, and whether it is recorded. All that added today by someone who found the API useful. So it can dump PEC, if someone wants to add it. Wr

That is how the 128K sketch works. It does not work at all when flashed to 64K. Basically, the flashing program thinks it successfully flashed the program, but only half of it really go on the chip's

Good point. In fact, for starting out, it is easiest to use the configuration generator. That way, you don't mess default parameters by mistake. From the Android App, set the overhead limit to 90, and

If they work in SPI, then ignore the TMC2100 advice. But, setting them to TMC_SPI has sometimes caused issues for people. Try 900 mA, and set it to OFF on both axes, and see if things are better.

You can try configuring them to TMC2100 instead. That makes the DIY TMC2130 work without SPI. You have to set the Vref using the pots. Also, do you have: #define AXIS1_DRIVER_STATUS OFF #define AXIS2_

Maybe what he is seeing is due to thermal shutdown of the TMCs?

With the maximum current for the NEMA14 being 1.5A, that 1200 mA is excessive. It should be: 1.5A X 1.41 X 0.35 = 730 mA for tracking. Maybe 900 for slewing. But nothing like 1200. I thought it would

Most likely. If you can run the 64k sketch and you do get output, then it is very likely that you have a 64k Blue Pill.

Serge, Yes, having an :STMDFU# command would be helpful. We discussed it in the past, and possible code needed to do it. Can't find the thread now. But there may be another way ... at least for the S6

If the 95 and 97 are from the zenith, then set the horizon limit to -5. OnStep does not have a west horizon and east horizon, so this works for both in your case. Overhead depends on the length of you

That is different than 4.24. In 4.24, starting a slew without starting tracking will make OnStep continue tracking after the slew ends. This is better behaviour than what Vladimir is reporting with On

The ESP32 has an accurate clock, and does not need an external clock source. If you have an RTC or GPS connected then you need something in there, and the OCG sets that correctly if you select one. If

#miniesp3

With the NEMA17, and TMC5160 ... did you set an appropriate IRUN value based on the formula below, or left it as OFF? Maybe you were able to stop it because of that, or because you set a very low IRUN

I can't remember the specifics. I think it compiled, but OnStep did not start at all for some reason. No harm in trying on the Pi. Just don't keep your hopes too high ...

Good strategy. I doubt you will see a marked difference. But let us know what you find. For such a large heavy mount, keeping the speed as low as practical is best. I would shoot for 2.5 or 3 degrees

I agree with Andras here. And just for background, I don't use the ST4 port at all anymore. The overlap of the speed used for autoguiding and manual guiding, and it getting reset when 1X is selected i