> On 28 Dec 2018, at 05:27, Matthew <[email protected]> wrote: > > I increased the P term to 1000 with no change. I'd like to try to plot the > error with halscope... any idea how to do that? :-) I looked at halscope > and googled a bit... is there a good tutorial somewhere?
Yes there is. One of the very first links that showed up in my Google search. Remember that you have to click on the link ;) http://linuxcnc.org/docs/html/hal/tutorial.html#_halscope Or if you search the machinekit docs http://www.machinekit.io/docs/index-HAL/ See section “Halscope” http://www.machinekit.io/docs/hal/tutorial/#halscope-a-id-sec-tutorial-halscope-a > > Thanks! > > >> On Thursday, December 27, 2018 at 7:37:17 AM UTC-8, pcwcol wrote: >> >> >>> On Tuesday, December 25, 2018 at 4:42:28 PM UTC-8, Matthew wrote: >>> The error I usually get is: joint 1 following error >>> >>> >>>> On Tuesday, December 25, 2018 at 3:14:55 PM UTC-8, Matthew wrote: >>>> I recently finished putting together my CNC router using the Beaglebone >>>> Black, a 5 axis breakout board, HY-268-N6 drivers, and NEMA23 steppers. >>>> Since I received assistance with getting my steppers moving in the correct >>>> directions (my earlier post on this forum), everything works great for >>>> jogs. I can jog any axis at 120 in/min without problems. The issues come >>>> when I try to run a gcode file through it. No matter how slow I set the >>>> feeds, it seems like I get following errors. I've googled the issue and >>>> tried: >>>> >>>> 1. Increasing the min_ferror and ferror values (up to 0.5/1). >>>> >>>> 2. Decreasing the pru_period to 5000. >>>> >>>> 3. Increasing or decreasing the DEFAULT_VELOCITY and MAX_LINEAR_VELOCITY >>>> values. Goal is for a max of 120 in/min but plan to run around 25-50% >>>> depending on what I'm working on. >>>> >>>> 4. Increasing or decreasing the MAX_VELOCITY and MAX_ACCELERATION for each >>>> axis (although it seems like the y-axis is usually the one giving me >>>> errors). I've been keeping the stepgen values 20-25% higher than the max >>>> velocity/acceleration values. >>>> >>>> 5. I adjusted the microstepping to lower the steps per inch scale value. >>>> Didn't seem to make any difference. I'm currently at 1/2 stepping I >>>> believe. >>>> >>>> 6. I've played with the driver timings (DIRSTEP, DIRHOLD, STEPLEN, >>>> STEPSPACE) but they didn't seem to change much. The values are high due >>>> to the cheap drivers I'm using but they work just fine when jogging... >>>> >>>> Any thoughts? I've still got my configuration files at the following >>>> links (ignore the hal_bb_gpio values - I've corrected the pins since >>>> posting the files): >>>> >>>> Xylotex.hal: https://pastebin.com/UNtgPpyx >>>> Xylotex-axis.ini: https://pastebin.com/u5Ba6ULH >>>> Xylotex.postgui.hal: https://pastebin.com/NFHf6Px9 >>>> >>>> Thanks for looking! >>>> >>>> ~Matthew >> >> >> You might try increasing the P term to 1000 >> >> The current P term of 50 with a maxerror setting of .001 means the maximum >> correction >> applied to velocity is .050 IPS which may not be sufficient >> >> Another thing to try is plotting the following error with halscope to see >> whats going wrong > > -- > 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. -- 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.
