thanks ill try that Make sure none of the motor drivers are enabled until the software is > configured and running. There is an ESTOP chain and machine power > output available on the CRAMPS board already, and you can use any of the > available GPIO to drive an enable output wired to the appropriate axis > enable pin in HAL.
no i mean when the spindle is running it stutters sometimes, i think it may be because the encoder is not 100% working or some electrical interferences. the real problem is when i power the machine on, the spindle is at maximum speed until i start the software (i am going to solve this with a relay board and gpio pins) Am Samstag, 8. Oktober 2016 13:18:16 UTC+2 schrieb Charles Steinkuehler: > > > > On 10/7/2016 2:35 PM, Sag ich Dir nich wrote: > > Hello, > > > > i got my closed loop spindle kinda working but everytime i start the > machine i > > have to re-set the pins to input and qep, how do i better start > optimizing P,I > > and D? > > I usually make a shell script to configure pin modes (setup.sh) , and > call it early on in the HAL file. > > > Also sometimes the motor stutters for a split second > > Make sure none of the motor drivers are enabled until the software is > configured and running. There is an ESTOP chain and machine power > output available on the CRAMPS board already, and you can use any of the > available GPIO to drive an enable output wired to the appropriate axis > enable pin in HAL. > > -- > Charles Steinkuehler > [email protected] <javascript:> > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
