2015-05-17 22:00 GMT-03:00 andy pugh <[email protected]>: > Yes. In case the Hostmot2 driver will only be limited by the stepgen > limits. All LinuxCNC limits are ignored. >
I guess I should study more the dinamics of what I need to do. Anyway for rough cuts I guess to vary the speed is not that necessary. But for grinding cams It should be considered. > I use a custom component, but I wrote that before I wrote Lincurve. > > Setting the values from G-code just seems horribly clunky. > Setting the values of a lincurve from Python sounds like an afternoon > of fiddling to end up with a better solution. > Even with a custom component, I would skip the G-code idea. I assume > you plan on sending angle and amplitude data on analogue outputs and > clocking it through with a digital? > It seems much easier to write a script that can parse spreadsheet > data. (CSV, for example) even if you do use a custom component. You > will need some sort of script anyway to create your crazy G-code. > Indeed, I was planning to use digital outputs as clocking and then feed the values through analog outputs. It was just an idea and I never did it but I guess it's a little clunky haha. About making a script, well yes, the idea is to either capture the lobes with an arduino using an encoder and a LVDT to get the diferrent lobe shapes, or by hand for testing purposes (which I did by 5 degreees increments). I have a lot of work to do with that but for testing I should use the hand method at the moment. Then after the lobe is captured, my idea is to load all the data into two vectors (one for the rotary data and the other for the lift data) in the component to calculate the offsets. I tested that part and it semeed to work ok but never tested it on a machine. Also the component calculated the radius of the cutter to make the compensation in the case of a rotary tool. > A custom component would cope better with wrap, possibly. Also it > might be better with variable curve resolution. The only way to change > the size of a lincurve would be to unloadrt it, then loadrt it at a > differenct size. And then re-make the connections. > > Even for a custom comp would suggest starting with lincurve.comp. > It's already nearly there. > I'm going to take at look at that! I should modify it a little bit but I guess It's going to help me to build something that fits my needs. -- *Leonardo Marsaglia*. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
