Smoothing Out the X Axis Motion | Surface Grinder Automation 7 | Clearpath RAS

[@grantsaviers6557]

A few thoughts about further exploration and tuning of the loop. The cable elasticity is likely the major issue, but the cog belt and table suspension are also in the loop (and variable part mass as others pointed out). One idea is to mount an MEMS 3 axis G sensor (or 6 DOF) to the table and see exactly what is going on there with the tuning. The dynamics may include vertical table motion, as it's unlikely the cable force will be at the center of mass. Then try adding a part to be ground. That is ultimately what matters for grinding to a tolerance & finish. Another perspective on RAS is it controls the frequency spectrum of applied force. Reducing jerk and further derivatives reduces the higher frequency inputs. If you don't put them in, they don't need to be controlled out. Mechanical structures usually have a huge number of resonance modes, and stable control of them is the classic control loop challenge.

[@JustinDavidow]

I expect that RAS setting is going to need to increase once jigs / work is added to the chuck. These will increase the moving mass and thus the "slip" on the spindle + stretch in the cable drive.

[@alexwbakker]

As someone using RAS on a CNC router and a Bed Mill, both required decreasing acceleration and increasing RAS a bit once you mount vises, tools etc.

[@colinrhodes643]

James, you absolutely work and think on another level but provide a wonderfully clear and detailed description even for the complex math and physics behind it. Keep doing what you do

[@MaximilianoKorp]

I don't know if it was intentional but "Something about fitting a fourth order polynomial spline, that sounds great" sounded so saucy and had me rolling

[@patchvonbraun]

We're using ClearPath motors (SC-HP series) on our project (restoring a 12.8m satellite dish for radio astronomy). The API we use (sFoundation) has an API function that lets you query the encoder resolution so you don't have to wire it in to your code. We're taking our project very slowly--the dish weighs in at a svelte 5.6 tonne. We had a crash a few weeks ago--not due to the motors, but due to a failure in our mechanical system design. Kinda scary, but the only thing really damaged was our egos, and the 50+ year-old crash buffer at the bottom of the travel. We're using fairly modest motors (a roughly 3/4HP on azimuth, and 1.3HP on elevation), but with extra gearboxes to boost torque. It's working well, although it will never win any slewing-speed contests :)

[@AnnaVannieuwenhuyse]

Fascinating, thanks for sharing!

[@nathaniellangston5130]

I'm a machinist for a telescope called the GBT, not sure how familiar anyone is with it. But its a pretty big telescope. The large drive motors couldn't be replaced by Clearpath servos but as it has active surface actuators and uses worm driven "servos" from the 1990s to position the subreflector I have always wanted to retrofit. Its pretty awesome that you are actually retrofitting telescopes. We've got three small 85ft scopes that i'd love to swap out the motors for Clearpaths just for a proof of concept.

[@patchvonbraun]

Hah! I've been to visit the GBT 20(?) years ago. This dish started out life as a NATO ground terminal, and hasn't moved under computer control since 1997, with MUCH larger motors. Are you related to Glen Langston?

[@nathaniellangston5130]

@@patchvonbraun I am related to Glen Langston! He is my father! Small world! I'm really glad to hear there is work going on to give the old telescopes new life!

[@patchvonbraun]

@@nathaniellangston5130 I sent you a friend request on FB.

[@jonnafry]

Always enjoy content that leaves me knowing more about a subject than when I started watching. This video was most enjoyable !

[@uncledansworkshop4776]

James - Great video. Your research took me back to when I was 17 and learning basic calculus. "This is hard, where am I actually going to use this?" Then one day we learned the relationship between displacement, velocity and acceleration as derivatives and integrals of each other. Seventeen year old nerd mind blown! Fast forward 41 years and most of an engineering career and at age 61 you point out that there are at least two more useful derivatives to be had when it comes to springy systems. Old nerd mind blown once again! Before you started showing ClearPath's solution to this problem, my mind was running towards a solution in the control software. Since your stops won't be moving during a run, my thought was to run one slow pass at the start of the run to learn the positions of the stops, then use those known positions as part of your control loop and predictively change velocity and acceleration as the movement approaches the stop. Move 95% of the distance at full rates, then reduce acceleration for the last 5%, then same going the other way, something like that. Just check the end stops on each loop to make sure that we didn't miss a count somewhere and as a safety, but since those are servos, the only error might be mechanical slippage. One last thought - the table and vise are fairly massive, but do you think different tuning might be needed with a heavy object added to the system? I'm thinking a large angle plate or sine bar setup plus some heavier part to grind might add enough mass to the far end of the sprung system to mess with the control parameters.

[@dynamiteralph]

In college, in a cam design course, we looked at jerk, and its derivative ( we called it jounce) in order to smooth the entry ramp on the cam curve. The goal was to smooth the entry into the cam, reducing the float of the cam follower.

[@Phiz787]

Wow! Just today I auto-tuned some Nema 34 clearpath servos for my CNC milling machine and noticed the RAS 16ms default. Now I know what that's doing! Thanks for the education!

[@rexmyers991]

Hooo - Boy! James, you are really showing me how uneducated I am. I am a retired airline pilot. I was really good at carrying folks safely in really bad weather. That skill now looks like kindergarten level. Thanks for explaining.

[@SimonB6706]

Easter morning and I've learned something!!! Snap, crackle, pop! Fabulous.

[@thetooth]

Motion control is an incredibly cool subject to look into. For a project I have going at the moment I'm using AC servo drives which have absolutely terrifying trapezoid performance due to the winding voltage, instead of doing jerk limiting within the motor PID I'm doing it as part of the trajectory generation, this allows for optimizing within the context of the planned path. So you can have a highly damped control system where you can have the motor track a target of arbitrary error and acceleration and all of the motions between those errors are smooth and jerk free. You can also modify those constraints on the fly, so in the case of your surface grinder you would switch to a dynamics profile optimal for the turnaround point when the limit switch is triggered and then after the velocity is reversed switch to a purely trapezoid profile so that the target velocity is hit much faster, would allow grinding a part at the full width of the table working area without creating hot spots at the edges.

[@JCWren]

You can see that torque in the belt when it reverses. Very impressive. Also, they need to remove the comma after "proprietary" on page 199.

[@joell439]

😂

[@gwharton68]

Always a good day when you learn something.

[@LordSaliss]

You could always design in a 3rd shaft for the X axis pulley drivetrain with the new shaft down below. Make the servo go from its small pulley down to a big one, that big one is on a shaft with a small pulley on the other end, and have that new small one go to the existing X axis large pulley that goes into the machine. This would double your gear ratio which gives you more torque and will let you easier control the motion inertia with a smoother accel/decel curve. You aren't using all the motor RPM right now, so you can afford to cut the max RPM in half to double the ratio. When I did this project I had to use a higher ratio than I thought due to these similar inertia problems of the weight of the table and the springiness of the wire. By doubling the ratio the motor can take more time ramping speed down which does help with the inertia. Eventually you might want to do what I did and replace the wire underneath with a leadscrew and lead nut. The lifetime of the drive wire became too low with a servo due to the higher speeds we tend to run over what you do by hand. The leadscrew fixed this lifetime issue. I first started with a 3/8 screw, because its weight limit was higher than the table. However, the inertia was so high, it overloaded the lead nut too much and caused the nut to fail and strip out after a year of use. I replaced the screw and nut with a 3/4" one and so far (4 years now) I haven't had to replace a single thing again. The lead screw is mounted on each end to the end of the surface grinder table, so it doesn't turn. I have two bronze lead nuts mounted in a timing pulley, with the ends of the nuts sticking out of the pulley. The motor has a pulley on its output shaft that connect to the pulley holding the lead nuts with a timing belt. I have two mounting plates mounted to the table with ball hearings mounted in them, and the ends of the lead nuts are held by the ball bearings. This keeps the lead nuts and pulley centered properly on the lead screw and keeps the pulley from being able to travel left or right, since we want it to stay in place and drive the lead screw through it. I used a 3/4" .250" lead screw, which with my motor (3000RPM max) gives me a 12.5" movement per second on my surface grinder X axis. This was enough for me, but if I was going to do it again I think I would use a 3/4" .333" lead instead to have a but more room to play with things.

[@b2gills]

I would attach a stop for each of your stops. Basically make it so that you don't have to rely on seeing the marks you added, as you would be able to just move your switch stops to a stop that doesn't ever move.

[@danw8404]

James thank you.....I learn so much from you.

[@francisrampen9099]

I have been thinking of doing the same thing with my Landis 618. Thank you so much James - you probably saved me weeks of faffing about when I finally get around to it. I will only likely do the x axis. Awesome channel.

[@mattholden5]

So much insight into the black art of motion control tuning. Teknic's videos makes it look unbelievably easy, your explanation makes their results understandable. Now I know specifically what I'm trying to affect with RAS/jerk/jerk derivative. Thanks James.

[@TerryGaskett]

Thx James, I did my Uni in Logistics not Engineering, you are filling in mind holes , making the new life easier 😅👏👏👏

[@garnergc]

I’m quite spoiled using Kinetix motion servos as a System Integrator. Do a Motion Axis Move to a position in x amount of time, set it to S-curve and let it rip. A the hiperface absolute encoder makes indexing bulletproof. Throwing excessive acceleration at a wet noodle axis doesn’t always work, but it’ll be interesting to see how the dynamics of the system changes when a workpiece is added and the wheel is engaged because the resonance frequency shifts. Also the forward and back directions will see different forces because of the grinding wheel engagement. Will be great to see the final results

[@seabreezecoffeeroasters7994]

I am having flashbacks to Mech Eng and Mechanics of Machines and Engineering Calculus from nearly 40 years ago. Lucky I am old and have forgotten most of the horror 🤣

[@akr1865]

Another great video James. Something to be aware of at that fast of a speed on the X-axis is the speed of the grinding wheel vs longitudinal movement. If it's too fast you will not leave enough time for the wheel to do its work. Think of climb cutting on a mill at a rapid feed rate. Every "automatic" grinder I've ever used had a much slower x- axis feed rate. Also, as you may already know, things can go wrong in a hurry when surface grinding, so an external control outside of the e-stop would be helpful to vary the speed.

[@davidblumer6509]

Thanks for the educational video today. It occurs to me that the surface grinder presents a special case where the motion is repetitive for each job, so after the initial (or a few) traverses are made, you could take advantage of that by allowing the motor to learn when it needs to slow down prior to the reversals to prevent the torque excursions by using an algorithm in your code. Here is what I'm thinking: Sum the number of motor steps for each motion for the first, say 5 cycles to take advantage of statistics, and calculate the average for each direction. Then, following the 80/20 rule, start ramping the velocity down at the 80% of the full average number of steps (for that direction) to some chosen velocity that the motor can accurately accommodate with minimal excursions. I think that would allow both a faster velocity and acceleration while maintaining good torque profiles and reducing the stress on the motor. Just a thought.

[@ftownroe]

I don’t own a surface grinder but if I ever decide (and have the Benjamin’s) I would consider this model because you have already worked out all the bugs to automate its function. Another fantastic video.

[@johnmerrill6999]

If you're writing in C++, you might also mark the external state variables as volatile. Otherwise, the optimizer might make assumptions, which could lead to odd (and potentially dangerous) bugs.

[@PeregrineBF]

Like infinite loops being undefined behavior if the don't have side effects. Writes to non-volatile variables are not side effects.

[@arimadx]

As someone who knows almost nothing about physics, you did a really great job of explaining everything. I think im actually on the same page as you on all this haha.

[@davidawaters]

Nice! I wish I had this info a couple of years ago when I built a couple of machines for a local manufacturer. It had a springy x axis (6’ of 0.25” wide timing belt). It had very little mass/speed/force but I had a lot of problems with resonance. A combination of a much stiffer belt and auto tuning finally took care of it, but I would have much rather just swapped to a RAS-able motor if I knew about it.

[@mr.b6034]

Would be interesting to see if there will be any difference in thr torque oscillations when you put some weight on the bed...

[@Clough42]

Very little, in my testing. The table and chuck are already very heavy.

[@nf4x]

But your torque ripple and ringing will reduce when you grind. The drag will dampen the system. With the better profiling (planned jerk and snap) you might try reducing the integrator gain and / or increasing the proportional gain slightly. If they have a Bode plot feature in their software, run it and show us next time. Then you can tune it as well as PI will ever get you. :)

[@steveh8724]

@@nf4x damp

[@AmateurRedneckWorkshop]

Success always feels good. Thanks for the video keep on keeping on.

[@Hossimo]

Im honestly supprised you didn't add a jerk paramiter to your code so you could tune it on your own. On one of my 3D printers I compiled my own marlin firmware and apent some time messing with the jerk setrings and it was easier then i thought it would have been

[@carlholmberg1576]

Weirdly enough, the definition of the jerk parameter in marlin is not the same as jerk in physics. In marlin, jerk is defined as the "maximum instantaneous change in velocity" instead of the rate of change of acceleration. Seems to be from an early misapropritation of the term which has then stuck around.

[@Hossimo]

@@carlholmberg1576 great to know thanks for that.

[@jhbonarius]

Very nice! I understand that some professional cnc machines use the linear scale to determine the position of the axis, instead of closed loop servos. That might also help in this situation?

[@DanBowkley]

How hard would it be to get a DRO scale feeding back into the servo control? Move the feedback out to the end of the line and you can easily tune a PID for the springiness.

[@marclevitt8191]

I don't know, sometimes more data is not better. Perhaps only using glass scales and bypassing the motor's internal ones? Is that what you meant? I believe that Leadshine’s latest hotness EtherCAT servo can take both inputs.

[@DanBowkley]

@@marclevitt8191 Pretty much yeah. Even the optical encoder strip from a printer (if it were long enough) would be plenty. Just enough to tell the brains where the table is. I just suggested a DRO because there's probably one readily available inside a machine shop and it's probably meant for that role. Interfacing it shouldn't be too hard.

[@macaroniandtuna]

I looked into this question several years ago, and the consensus seemed to be that it's technically possible, but not a good idea for some reason i couldn't figure out (maybe related to position hunting), which is why basically no motion controllers below and up to light industrial usage support it.

[@kashifkhan3040]

perfect job for a viscous coupling :)

[@shaun9054]

It will be interesting to see how much the scope curves change as you place different mass on the chuck to grind

[@merlinmagnus873]

Definitely worth the extra money. I guess another option would be mechanically damping the torque spikes with a hydraulic torque limiter. One out of the cooling fan on an engine could be retrofitted to work. The damping effect is mechanically variable and controlled by a bimetallic thermostat which could be replace with a lockable thumbscrew adjustment. For extra credit, you could use a centrifugal actuator to mechanically emulate those rounded corners on your torque graph making it a purely electromechanical system with no controller.

[@jhbonarius]

Adding mechanical solutions will probably not work with these closed loop servos. You would have to do the calibration fully manually. I mean the software solution is the whole reason to use these expensive clearpaths.

[@โนรีคอกเบิร์น]

This is a great tutorial, great understanding, great tenacity & great outcome. What would be the icing on the cake is a test piece, that has an area (strip) of grind at same depth etc but with different motors and RAS settings to see if the quality of traverse actually shows or is measurable in the real world or if the mass of the table hides it. Thanks James, this is perhaps the best (most revealing) project you have done.

[@vandyFixer]

Interesting viseo as always but I did have look at the wikipedia page to understand what, Snap, Crackle and pop were all about. 😊

[@MartLeib]

Couple more notes regarding the ClearPath: * If not, then run auto-tune again with the new motor, and see, if it finishes. There have been instances when the auto-tune has "gotten stuck" at certain percentages, in such cases I have just applied some force to the mechanics to allow it to overcome it * Try fine tuning. You can find it under Setup -> Tuning -> Fine Tune. There you have a slider which you may try moving to either side to see how it affects your use case. * Use higher input resolution. You have set it to 800 in the MSP software, but the motor's native resolution is 6400 which would result in (a little) better movement since the RAS algorithm has a higher input frequency. CleraCore can handle such high output frequency very well thanks to the clever internal "clock"

[@CalMariner]

You could wrap those cams around the sides of the t-track with little a gled pointers, print/glue a tape measure on the top of the t-track

[@mrburns366]

Grinder? Damn near killed 'er!

[@SomeNameGoesHere]

Disney talks about the visual impacts of this if you ever see the behind-the-scenes tours or videos. They refer to it as Audio-Animatronic Compliance in regards to addressing jerky limb movement when trying to make their attractions move faster.

[@JohannSwart_JWS]

Those motors are amazing. Could not help wondering about the peak currents at accel/decel points. Must be quite a bit, for a short while.

[@charleskeller4288]

How about a dial indicator on the surface of the table to quantify any bounce better than eyeball?

[@philareilly]

@patchvonbraun now that’s a series of videos I would love to watch

[@LetsRogerThat]

That's an impressive improvement James. My Rockwell Delta bed sits on ball bearings and there's nothing preventing the bed from lifting as it changes direction. I wonder if your grinder is subject to any mechanical lift during the directional change. If there is, it would affect you surface finish. You might want to check that out. Gilles

[@KPNH]

Excellent work, sir! 👍👍

[@Skyliner_369]

hilariously, I would have coded the RAS myself in the controller. not too hard to implement. especially if the accel can be directly coltrolled by code and not just constants

[@marclevitt8191]

He let Teknik program it in-a better solution and cheaper.

[@rogertrett406]

I learnt a lot from this video. Many thanks.

[@davekellogg6819]

It would be very revealing to compare the motor’s encoder position to the table’s position as determined by a linear encoder scale on the table. However, to do so would rapidly degenerate into a research project. As it stands, James has enlightened most of us with the novel RAS solution. From a design standpoint, it is a great solution because it avoids the expense of a linear encoder and it’s mounting. If this was a ground-up design (vs James’ retrofit) the better approach would be to replace the cable drive with a ball screw. But even then, this is a surface grinder’s X axis: It doesn’t need precise positioning, only smooth velocity.

[@LyallPearce]

I was only half way through watching and my first thought was you need to provide a delay between direction changes to allow the system to settle. It will be interesting to see what you did...

[@jackpledger8118]

This went way over my head.

[@โนรีคอกเบิร์น]

So, Buy thicker sole shoes. It wont help because the knowledge will go straight through your head like a Quark. Dont worry, you wont feel a thing.

[@the_rad_Panda]

Great Video! Have you tried a belt tensioner? Looks like some of the inertia springiness might come from the belt tensioning. Maybe even the wrap angle on the driven wheel? Just food for thought - really enjoying this series and your way of going about things 😊

[@hasanzakeri8708]

Nice! Have you thought about using dro-style linear scales for feedback and having a real closed loop position system?

[@PlovsLV]

Make 2 stop sensors on each end, one for slowing down table and second one for dead stop. With this setup, table/motors/belts etc. at the moment, is going under a very heavy load because there is a high speed and a rapid change of direction. Just make it that table slows down gradually before changing directions.

[@algotn]

Is there any reason to not do the jerk limiting in software? It would require more programming yes, but it also seems like you would have better control over it.

[@marclevitt8191]

To save approximately $500? Doing the jerk limiting in software is precisely what James’s doing; it's just Teknic’s software. Right? It seems like a bargain for who knows how many engineering hours it took to develop this feature. But I agree that if one wanted to control more parameters or had a good reason to do it higher up the control chain, now that we think we know the problem and how to fix it, one could provide rounded velocity curves. But then what does Techik’s servos now think of our input? Just thinking out loud here, but now maybe we would want a dumber motor so we don't get rounding on top rounding.

[@josephmacey8512]

nice work James, is there a line of code to make it stop at the end ( Left or Right) and not on the job your grinding

[@larrybud]

Great call!

[@johnblazeindetroit]

Hey James, not sure if you considered this...Maybe an initialization routine that first determines the locations of the left and right stop, then you could ramp up and 'brake' between the two locations. My intuition is telling me that you would have to ramp up before making contact with the part and brake after leaving the part to maximize surface quality uniformity.

[@zaprodk]

Fascinating to see how the RAS fixed up the oscillation. I wonder what the difference in the actual servos are - I suspect it is just a software difference - The hardware is identical.

[@marclevitt8191]

The new one has a higher resolution. Perhaps a different encoder?

[@jlkainz]

Very nice video James! If you are programming the motor movement in C++, it seems you could have programmed in the control system for the motor to control the jerk/snap/... instead of purchasing the enhanced version. Just a thought from another controls guy.

[@jeffholden4600]

Will resistance, introduced by griding wheel and object friction, affect the smoothness of the x axis?

[@RossReedstrom]

How much will this tuning be affected by the mass of your vise and part? It is the table significantly more massive than anything you'd clamp onto it?

[@pbkobold]

Clearpath, if you're reading this, not having a 90 day return/swap exemption when a support engineer says "you need this other thing" is a little lame. I'm happy to pay a premium for a nice product with nice support, but I'm also the kind of person who will order motors months before I can start on a project (and discover I bought the wrong ones).

[@janoahuerta]

Snap Crackle Pop! Gotta love nerds naming terms 😄

[@Icaros03677]

Thank you very much for this video!

[@ita-1245]

Great mod, is there a failsafe if the limit switch fails or cams break and the bed progresses infinitely?

[@paullewis6612]

James, Have you considered the torque load on the teeth of the drive belt ? Is there a High Torque option available? Yes, there are many teeth engaged, there are also ‘many torques’ ! Regards, love the show, Paul

[@gravydog51]

All this math is over my head, but in the manual (at 11:25) is the term "forth-order" actually correct as opposed to "fourth-order"? Googling the first spelling does get a lot of hits, so I just don't know.

[@BigJonYT]

I know it's a personal preference, but I would have made the limit switches virtual. Leave one physical switch at the far end of travel to home, then set start and length parameters in the SW. You could also build a cool interface like the lead screw controller with speed, start and stop displayed. That way you can dynamically control it during the job without have to stop and physically adjust the end stops. Then as the controller knows where the two points are, it can accelerate and decelerate in SW to the exact positions. You don't need the more expensive servo, and you can stop on a dime without any overshoot. You could even leave the two physical end stops at the two extreme positions as estops too late now. You bought the expensive servo. But you have to live with the overshoot... Nice project, though. :-) I'm still jealous ... :-)

[@johnirvine3346]

Great video! You may have covered this but do you have a plan to stop the motor if (when) a limit switch fails?

[@qwertyboguss]

Not sure of its possible but I'd look into defining the limit switch state changes as interrupts. If you complicate the code more, or the controller is busy otherwise you may miss the trigger. Unlikely with this setup but I'd feel safer with hardware interrupts.

[@HangarQueen]

Great video. I came into it frankly thinking that it would likely be boring. I mean, how entertaining could 26 minutes of smoothing X-axis motion be? But it was! And very educational too! (Now I know about "jounce", as just one takeaway.) I'm wondering why you decided on the mechanical lever switches rather than the proximity switches. From your earlier video comparing the two, I really thought the proximity switches would be the winner. Heck, if you switched to using the proximity switches, you could add the mechanical switches as WAY-overkill to trigger eStop if the table went beyond limits.

[@jimsvideos7201]

What if you put a bellcrank at each end of travel to lift a weight up against gravity? That might soften the stop and help with the acceleration.

[@rvamerongen]

Always impressed with the details. Jusr curious; Did you test it with a heavy weight on the bed?

[@ianmoone2359]

Perhaps if you replace the wire cable with spectra dyneema which has less than 1% stretch and more strength than steel, you might also help smooth out the change of direction even more.

[@marclevitt8191]

My thoughts as well. Or a drive chain?

[@ianmoone2359]

@@marclevitt8191 now that’s also a good idea, chain might work. I’m guessing it might have more mass hence more inertia to overcome each change of direction than dyneema spectra tho.

[@carlhitchon1009]

Dyneema is slippery stuff, might be a problem.

[@ianmoone2359]

@@carlhitchon1009 Indeed it is very slippery, no denying that. 👍

[@mfx1]

Estops should always control things physically by cutting power (or a controlled stop through a safety rated system) with software being a secondary thing.

[@tonyr3352]

Very nice work! I'd be interested how it's going to change with a increase load on the table. Have you run experiments loading the table?

[@nf4x]

Your software could start each run by identifying where the limit switches are located, then just run back and forth within them, to get highly precise travel without worry of overrunning the stops. If you start hitting the limit switches, you know your cable is stretching, has slipped, or has loosened. Better performance and extra safety - win-win.

[@edwardaloftis6705]

Cool project.

[@anniebooo]

Thanks for a very interesting video. Appreciated. What happens when you put the force of the surface grinding wheel on a metal surface on top of the table? Best, Annie

[@Moinois]

Looks good, I am curious though what happens when you introduce a 10kg piece to surface grind and the grinder running as it will change the dynamics of the table. I'm guessing there might be a need for a new session of tuning when that happens.

[@the1maxb]

Could the progressive acceleration (anti-jerk) required not have been implemented in controller software? Along with anticipation of travel limits, based on tracking of the most recent limit switch triggers?

[@CalMariner]

Any safeties/backups for end of travel? If one of the control switches fails...

[@MachinedComponents]

Awesome video and great project. Can the Clear Core controler be programed in a language other than C++? I haven't used C++ and it's appears daunting to learn.

[@MacLocky]

Could the Clear Core controller be used with all of your CNC projects to date and if so with hindsight, would you just use this controller?

[@jbrownson]

Very interesting

[@rickswanberg4995]

The RAS enabled motor has clearly worked. Would you be able to program different acceleration and deceleration values to smooth out the start of motion if RAS did not work?

[@urbanawoodproject3123]

I was hoping to see you add some weight to the table and then observe the changes.

[@joopterwijn]

I don’t know if a different cable type (table movement cable) could reduce the “stretching”.

[@DavidSchmitt]

It's nice what values you put into the code, but what acceleration is the table actually experiencing?

[@swp466]

I'm curious -- if the settings are dialed in for the machine with an empty table, what will happen when you have a 20 pound chunk of steel on the chuck? Will the extra mass cause issues?

[@motorcoach123]

2 tens of a second stop on the clear path code when at the reverse cycle cuts the jerk acceleration

[@turbotona25]

How does it handle the stops real close together for grinding small parts?

[@seancollins9745]

Big Brushed DC servo would be ideal for the X axis, nice big heavy rotor, hard switching, loads of grunt particularly near shaft stall.

[@criggie]

Possibly a newbie question - how much does the table/object speed matter when surface-grinding? The wheel's surface speed is far higher so does it matter if the part is moving slow or fast ?

[@keithmonarch447]

James. In many PAST videos you made. I'm now retired from my career in Michigan. I was very involved in automation with huge transfer system, cycling. On and on! What / why are you planning a surface grinder for, production??

[@seapy2398]

I don't think James has any leanings towards production, merely to remove the tedium of manually cranking a handle back and forth when he knows a better way.

[@davefilicicchia6341]

James, I'm curious if you think the tuning issue was more about the 'squishiness ' of the cable drive on the table or an inertial mismatch?

[@alp763]

I did not get this part at the beginning of the video where you increase speed but also acceleration. I mean, if you put like velocity=600 and accel=2400 - you get 250ms for motor to speed up / slow down. Why crank accel and then buy motor with RAS to fix this? What do I miss?

[@georgescott6967]

I'm surprised that you don't have "stopped" as a third state in your finite state machine. I'm also wondering about "accelerate left", "decelerate left", "accel right", "decel right" but haven't thought long enough about it yet!

[@ligius3]

I would want to add some soft limit swiches to the software. As an anecdote, my sliding gate sometimes goes crazy and keeps going past the limit switch, chewing the rack and pinion in the process. It then thinks it has travelled far to the other side and doesn't want to fully return, so there is some soft limit, just probably badly implemented.