I should add... At which point it enables the stepper driver and keeps it enabled from then on.

Kind of feels like feature creep but I have a soft heart for outreach so the beta and master both have code for it. Tested on a Max2 and looks to be working. It turns off the focuser motor at startup

Anything is possible I suppose, but changes between 4.23a and 5.0a didn't have a thing to do aux features. Not one line of code directly related to that was changed.

That dynamic memory estimate isn't a number you look at and say it's < 100%, so I'm good. There is the heap and stack they must have ample room for runtime temporary and not so temporary variables. Ho

If this turns out to be the case perhaps I will merge this new feature back into 4.23, but first I'd like it to be tested on 5 to gain confidence.

And the problem might be something as simple as the Mega2560 reaching the end of its road too (as with the STM32F103C8/CB), RAM (memory) resources specifically. Any other signs of instability on the O

Well version 5 is very experimental. Given that 5.0a doesn't have this new auxiliary feature code it would seem that the problem is elsewhere. I have no plans to incorporate this into the current beta

Rebooting OnStep without rebooting the ESP8266 can do it (which I'm not loosing sleep over) but other than that... never seen it happen.

I added code to set that default intervalometer pin state earlier.

No, likely that is already too high and you haven't taken the steps to make a Vref of 1.4V work (so drivers are overheating and cutting out.) For those motors/drivers try Vref = 1V.

#error

I added this feature to the master branch. Well I think what I added is what you are asking for. That is, the functionality to invert the logic state such that ON is 0V at an output and OFF is 3.3V (o

Stepstick sockets are often designed this way as other drivers need that connection (or other measures taken) to function. Read the Wiki: SilentStepStick TMC2130 or TMC5160 (read about these drivers b

For example this... The shunts/jumpers (under the stepper driver sockets) for a RAMPS 1.4 or MKS Gen-L V1 or RUMBA (AFAIK dip switches) should be REMOVED or OFF for TMC SPI drivers. Some FYSETC TMC's

It's all been proven to work with OnStep. Naturally there can be bad hardware, incorrect hardware, incorrect wiring, misconfiguration, etc. etc. etc. so success is not guaranteed. Things can get compl

There is no hardware listed in the Wiki that "might work".

I don't see that it's "wrong" many use and are perfectly happy with the Mega2560 based OnSteps.

AFAIK you are. There is really no reason the TMC SPI drivers shouldn't work with this. BTW you definitely DON'T need the shunts installed under the drivers for a RUMBA. Those connect the mode control

1. SPI to TMC2130 drivers work for other Mega2560 based boards. 2. Make sure the TMC2130 drivers are SPI enabled, some look like they are (w/ SPI pins up) but are not and operate in TMC2100 compatibil

Download and install the libraries. Once release-4.x hits we'll get serious about bringing the wiki up to date for it.

Basically you can either get support from Instein or become a DIY OnStep user. OnStep has "support" for the Instein Mega2560 hardware AFAIK, use it at your own risk, I think it works. Again, OnStep is