Not really enough information to know for sure but I can state that with Arduino 1.8.15 and STM32duino version 1.9.0 (etc. per the Wiki) OnStep release-4.24 compiles successfully for me (with a run of

That reminds me, I still needed to update the README for that Main branch SHC to describe the standard use of branches in my repositories... https://github.com/hjd1964/SmartHandController/blob/main/RE

No. I'm setting the default to the release as I feel it should be stable enough, if not will patch as needed. It has all issues I know of patched, well there is the change to U8G2 breaking things but

Ok, a little faster than that, the main branch SHC has the fix now. I didn't test (as I don't have an ESP32 SHC nor any SHC wired into OnStep that way) but the code is there and it should work. It lea

On Sun, Sep 12, 2021 at 02:32 AM, Ken Hunter wrote: First let me say this looks like a nice design, I like that you "thinned it out". If it is not removed, the resistor will "Pullup" the signal lines

#wemos #esp32

No problem, concept is the same, but if you don't have the option you don't.

#define GENERIC 12 // alias for GENERIC1 #define GENERIC1 12 // step/dir stepper driver with EN LOW, allows for 1x,2x,4x,8x,16x,32x,64x,128x,256x (no mode switching) #define GENERIC2 13 // step/dir st

#mount #mks

Especially for a device like a "smart switch".

I noted the same exact thing many years ago, just thought modern stuff had the polarization if it mattered.

I don't understand how you can connect it wrong, standard plugs/sockets don't allow you to plug in backwards for this exact reason.

A nice write up, I really enjoyed reading it Ken, good ideas in there.

Keep in mind can get away with wiring STEP/DIR/EN directly into the DM556 like this since the Mega2560 has 5V levels. All other OnStep MCU's are 3.3V and technically would require using some level con

#mount #mks

There's a lot involved in supporting "any motor". Much simpler (for me) to just lean on the step/dir interface and let the motor driver take care of the details. That said, OnStepX already has a gener

Which means at that moment there was no error so perhaps the error doesn't persist for long enough to easily see this way. Check those connections, motors and SPI. Turning off one axis status or the o

It's a bug. There are #define strings that get sent to start/stop the guide motion... those are special 1-char commands in SerialST4 (for speed) and need to revert to the standard commands when a norm

If setting current in Config.h the Vref should be as high as it can go ~2.5V, there is no point in using anything else. And 800mA is well within the drivers capabilities. This problem is due to a faul

I would be surprised if a TMC5160 behaved differently in an S6 vs. any other board that supports it.

#mount #mks

I could consistently do better than that with 40# payload and NEMA17 60 oz-in motors direct into the G11 worms (helical couplings.) My current setup (NEMA17 116 oz-in) is easily twice as accurate at m

A typical 0.9A 400 step NEMA17 pullout torque drops significantly at 180 RPM. Probably ~1/3 of it's pullout in this case. Then there's mid-band resonance which changes once the motors are mounted. And

I've used both too, I find the joystick clumsy and prefer the buttons. Everyone should make their own call.