Because duet has working wifi,telnet, easily configurable, has 5 stepper drivers (i may need more than 2 steppers), inexpensive, does not require soldering it yourself, allows rather fast step rates?
On second thought, sending multiple move commands is not acceptable at all, because axes must move as smooth as possible (stops between commands will cause too much vibration). So i must generate the full trajectory file. I've forgot about the baby stepping. This might be the best solution for me.
Best posts made by dascvcsadc
-
RE: Following a trajectory
Latest posts made by dascvcsadc
-
RE: Can't get stall detection to work on my delta.
@phaedrux
Thanks, will try that later.
I'm running 24v. -
Can't get stall detection to work on my delta.
I cannot find a proper S value for my steppers on a delta printer for M915 command. I've tried to lower both acceleration and jerk values to quite low values(400-500 mm*s2). If I use S3 and H400, I get a lot of false positive alarms. If I use S4-5, then i still get false positive alarms occasionally, but never get an alarm if I hold any axis by hand, so it would really skip steps. I don't get any alarms with S6. I use low inductance high current motors - 2.4A, inductance 1.8mH/phase, resistance 0.8Ohm/phase. Is it possible at all to calibrate stall detection with these motors?
-
RE: Following a trajectory
Thanks, i guess sending a short queue of moves should work. Maybe I don't even need real time, just keep the time one move would take below 1 second.
-
RE: Following a trajectory
Because duet has working wifi,telnet, easily configurable, has 5 stepper drivers (i may need more than 2 steppers), inexpensive, does not require soldering it yourself, allows rather fast step rates?
On second thought, sending multiple move commands is not acceptable at all, because axes must move as smooth as possible (stops between commands will cause too much vibration). So i must generate the full trajectory file. I've forgot about the baby stepping. This might be the best solution for me. -
RE: Following a trajectory
And maybe there is a possibility to modify current move parameters without a stop? Or instantly execute a new move command?
-
RE: Following a trajectory
Alright, but can I interrupt any current move in real time (or within a second)? Sending move commands every second does not seem as a practical way.
-
Following a trajectory
I would like to try to use a 3d printer controller for a home built motorized telescope mount.
If I want to track a satellite with it, i need to set up a trajectory in gcode for a controller(say, a list of G moves sent every 30 seconds with specified speed for two axes, a gcode file, maybe). If the satelite tries to escape my field of view, I need to adjust the trajectory. How can i interrupt a move instantly? What is the fastest way to handle the list of moves after the interrupt (modify it, upload again, maybe)? Maybe it is better to send commands string by string?