Will sure do! Actually, I've been thinking about the best way to put the information about the build together. I used an openbuild bundle for the mechanical part and have been thinking about putting it there, but a description on the software side of things would be nice as well.
On Thursday, July 7, 2016 at 9:32:15 AM UTC+4, Bas de Bruijn wrote: > > > > On 07 Jul 2016, at 07:26, Diego Molina <[email protected] <javascript:>> > wrote: > > > It works beautifully, with metric units, really sweet! > > Now on to the 5th axis design to see if I can get this to full 5 axis. > > > Of course I'm curious, so if you've got pictures/videos when you're done, > please brag about it and show us where to look! > > Bas > > > Cheers! > > > On Wednesday, July 6, 2016 at 4:00:35 PM UTC+4, Bas de Bruijn wrote: >> >> >> >> On 06 Jul 2016, at 13:34, Diego Molina <[email protected]> wrote: >> >> >> Bas, >> >> That's all really clarifying. I'll sit by the machine with all this new >> information and try to sort things out. >> >> >> Good luck, if you run into trouble/strangeness then shout out. >> >> >> In the future I'll follow your advice and try not to pollute the group. >> >> >> Well, it is much easier these days to read the info you can provide from >> the web, where for example you can highlight a specific line of code. If >> you add a lot of text (or some people send file attachments) then the >> thread becomes very hard to read (and attachments are especially horrible >> opening/reading from mobile devices) and difficult to point at lines of >> code for example. >> >> So the better to the point you (or anybody else for that matter) provide >> info, the better the chance for a successful answer. >> >> Cheers >> >> >> Thanks, >> >> >> Diego >> >> On Tuesday, July 5, 2016 at 3:55:30 PM UTC+4, Bas de Bruijn wrote: >>> >>> >>> On 05 Jul 2016, at 13:27, Diego Molina <[email protected]> wrote: >>> >>> >>> >>> On Tuesday, July 5, 2016 at 1:23:35 PM UTC+4, Bas de Bruijn wrote: >>>> >>>> >>>> On 05 Jul 2016, at 10:56, Diego Molina <[email protected]> wrote: >>>> >>>> >>>> Greating to all, >>>> >>>> So I've got a lot of cuts out of my 3 axis machine running on a BBB / >>>> Xylotex configuration, now I added a 4th axis and am having trouble >>>> figuring out the values to calibrate it and make it move as expected. >>>> >>>> I've based my config around Xylotex.ini and Xylotex.hal example >>>> configs, but to arrive at the actual distances on my steppers and lead >>>> screws I had to lower the scale to about 20000. All the axes work as >>>> expected with those settings. >>>> >>>> The thing is, now I've added a 4th axis with a 20-to-1 ratio worm >>>> wheel, and when I issue a G1 A90 F100 code (I'm assuming this is right to >>>> ask for 1/4 turn?) >>>> >>>> >>>> don’t assume, be sure instead. Have a search thru the docs on the >>>> meaning of G1 A90 F100. Find out what units are used. >>>> >>> >>> Is it steps/degrees? You know, I just ask after a lot of searching, >>> which in this case didn't result in any clarification on the matter. >>> >>> >>> look at your configuration for example >>> >>> https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Xylotex/Xylotex.ShuttleXpress.ini#L122 >>> >>> and >>> >>> >>> https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Xylotex/Xylotex.ShuttleXpress.ini#L132-L140 >>> >>> >>>> , for example, with the scale at 20000, it gives me around 10 turns on >>>> the axis. When I try to decrease the scale I get to 400 and it moves about >>>> right, but really slowly. I've tried to increase speeds after that but >>>> without success. >>>> >>>> >>>> it all depends on the settings you use. Don’t upload your ini file >>>> here, but commit you hal and ini file to your repo and provide a link to >>>> that. We can’t see inside your head. read this: >>>> http://www.machinekit.io/docs/getting-help/ >>>> >>>> >>> I've seen people here requesting the ini's, so I just assumed it would >>> be more convenient to just put as text. >>> >>> >>> nope, people specifically ask to give links. >>> >>> >>> >>>> Could somebody please point me on which settings to edit, so my other >>>> axes still work and the 4th can move at a decent speed at the right rate? >>>> >>>> >>>> you need to do some calculating. find out >>>> >>>> - how many steps per revolution your motor uses (200?) >>>> - do you use micro stepping, how much? >>>> - pitch of your leadscrew >>>> - ratio of your worm (1:20) >>>> >>>> >>>> then you need to know the max amount of pulses that you can put out. >>>> find the step length and step time for your drivers and calculate the >>>> max frequency. This should give you an indication of what your motors and >>>> electronics can physically do. >>>> >>>> then look at the settings in your ini file for the 4th axis, and >>>> compare the max_velocity, mac_accelerations, stepgen_max_vel and >>>> stepgen_max_acc settings. >>>> >>>> My driver is 200 steps per revolution, 6400 microstepping (pulses/rev), >>> the pitch is 2mm, but how would I end up knowing the amount of pulses? Step >>> length and step time are both 1500. >>> >>> >>> calculate them. >>> >>> for each mm of movement, there need to be 6400 steps / 2 mm pitch with >>> an extra ratio of your worm of i=20 so you’ll need: >>> >>> (6400/2)*20 steps/mm = 64000 steps/mm >>> >>> both step time and step length define your max frequency. Look at the >>> link above for the example. >>> 3 us (1500ns + 1500ns) means that your max frequency is 1 / 3us = 333.3 >>> kHz >>> >>> 333333 Hz devided by 64000 steps/mm means you have 5.2 mm/sec max speed. >>> But your BBB is probably not set up to use this steprate. This is the >>> physical limit with your settings >>> >>> If you have the standard 10us task period then you’re even limited to >>> 50kHz steprate. which means 50000/64000 = 0.78 mm/sec >>> have a look to the first link in this search >>> >>> https://groups.google.com/forum/#!searchin/machinekit/max$20step$20rate$20beaglebone >>> >>> >>> >>> >>> Thanks, >>> >>> Diego >>> >>> -- >>> 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. >> >> -- > 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] <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 [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
