Minimum uSeconds between motor steps

Cronix, see stepper min_stp and stepper max_stp in Slim for adjusting the value. (Both in 0.82 and nanomoco)

In nanomoco, it had to be set higher, because there were other delays in the the 0.82 engine. The stepping function had a lot of work to do in 0.82, and this time was not accounted for in min_stp/max_stp. In nanomoco, the timing loop is called by MsTimer1 in periods defined by STP_CYCLE (best not to go below 40uS), and then the timing loop simply determines what to do on each timing loop.

The 1000 value? It was just a starting point. The speed at which you are able to move is also relative to your microstep setting (stepper ms [1|2|4|8|16]) - but at very high speeds, you do lose a lot of steps in microstep modes.

Not documented yet in Slim, but if you're using nanomoco, here's the continuous motion mode:

You can call motor cspeed xxx later, and it will change speed on the fly. status home, etc. updates properly.

Here's how you do continuous move interactively:

It's worth noting, the motor I have here can do 1,000 steps per second in full step mode, with no load, before conking out. It can do up to 26,000 16x ms steps per second before conking out - however, it's missing lots of those steps.

!c

They should be arriving next week, they're being printed right now. If they come by next Friday, I'll reflow about ten of them over the weekend, so will have betas to go out.

!c

Good news - the PCBs shipped today, so they should be here by Friday =)

!c

Yeah, I got two done (it takes about 3-5 hours per board to place and reflow everything by hand =) - both had major issues, from the process. I'm presuming the boards are good, mostly because the reflow issues were the ones I expected, (It usually takes 2-3 bad ones to get one good one) and all new changes performed as expected. I'm most likely going to just order a batch assembled, as I don't think I can come up with 60 hours of time just to hand-place ten boards and have most of them fail due to a hacked-up process =) (not with the other design and programming work I have to do).

One change I want to make, however, is to change how I disabled the RS-485 network for programming via the arduino (or just using plain-ol ttl serial) - namely, I put a jumper to bring DE high, and therefore allow the RX and TX pins to operate as normal, when I should've added an (installed by default) jumper to cut the power to the driver.

!c