So spindle-at-speed definately works (i made a led in pyvcp) but when the spindle stalls, the program won´t stop. I have a pin spindle-at-speed-detect.scale 1.2 for filtering (i guess it is filtering, or is it spindle-rpm-filter.gain 0.01?)
Is my deadband from the PID too high with the value 5 if my encoder has 512ppr? (i dont understand the sentence from the documentary "...the deadband should be set slightly more than one-half count..." that would be 0.6 for example) i now got myself a indexed encoder and i want my spindle to reverse (for rigid tapping) so i added: net spindle-rev motion.spindle-reverse => bb_gpio .p9.out-28 and it kinda works but as soon as i turn the spindle on, it accelerates to maximum rpm (had to disable PID minimum output 0 to make the PID work in CCW mode) also the spindle stutters sometimes, even with the new encoder. It does not stutter with pwm only. i would be happpy if someone could give me some tips Am Donnerstag, 13. Oktober 2016 10:27:44 UTC+2 schrieb Schooner: > > > On 12/10/16 22:30, Sag ich Dir nich wrote: > > is there a way to tell the program to automatically stop feed(or the > program) if the spindle stalls? (or if it is a specific value rpm under > target RPM) > When the PSU is overloaded, it shuts off for a second and that could cost > me an endmill > > also: > > is there a PID value/pin i can send to a pyvcp module to create a spindle > load meter? > > > The commonly used solution is the 'spindle-at-speed' one > > https://github.com/machinekit/machinekit/search?utf8=%E2%9C%93&q=spindle-at-speed&type=Code > > It has some problems if your spindle only has a crude Z index, > fluctuations in the read speed can cause it to > remain untriggered unless you use a large margin value, but even then it > would protect against a stall. > > Make sure the output is filtered and averaged as far as possible to remove > the spikes > > The xml files will show examples of the speed meter and spindle-at-speed > LED commonly used in pyVCP panels > (especially on lathes) > > > Am Sonntag, 9. Oktober 2016 19:07:54 UTC+2 schrieb Sag ich Dir nich: >> >> thank you, that worked :) >> >> Am Samstag, 8. Oktober 2016 14:01:07 UTC+2 schrieb Sag ich Dir nich: >>> >>> 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 >>>> cha...@steinkuehler.net >>>> >>> -- > 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 machinekit+...@googlegroups.com <javascript:>. > Visit this group at https://groups.google.com/group/machinekit. > For more options, visit https://groups.google.com/d/optout. > > > -- 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 machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
CRAMPS.hal
Description: Binary data
CRAMPS.ini
Description: Binary data
