Advanced Search

tommylight wrote:

Or on weak machines where any motor can do damage.  I had an accidental "hard stop homing" on my old wooden CNC.  The limit switch failed and the motors ripped the end off the gantry before I could stop it.
 

I should probably mention how it's set up.  You will have a spinbox for Slat Height in the Probing section, and a spinbox for Thickness in the Material section of the Parameters tab.  If you set BOTH the Slat Height AND the Material Thickness, then the probe start height will change based on the material thickness. 

If either Slat Height OR Material Thickness are 0, then it will default to Probe Height.  A high level recommendation I have (I have not tested this in practice, yet) would be to set Probe Height to 0.  When Probe Height is 0, the probe movement will begin at probe speed from the current Z position.  In most, if not all, cases while running a program, this would start a 5mm (0.197") below Z maximum height, as the g-code filter automagically adds these moves by default.  That means that if you forgot to set a material thickness, your probe would start from the highest point possible, and it would probably be obvious that you need to fix it, and it would be the "safest" option.  

 

Sorry, for some reason it wouldn't upload some of my pictures.

I found a Hypertherm PDF on grounding. My conclusion is that I need a grounding rod in the ground. I do not currently have one. I will start there. And I will go through my shielding grounding to make sure that is good.

Ah thanks that might be a better option!

The smart serial error was likely due to a bad cable connection which has been fixed, but my main concern was ensuring motion could stop if something happens to the smart serial connection.

The run pin didn't seem to clear. It makes sense that the 7i84 I/O pins stop updating but I didn't think the smart serial run pin changed either. I'll double check and post back, but it didn't look like the run pin went low when smart serial was interrupted.

Thanks again for the quick reply! Merry Christmas!

Thank you for the explanation.
Just for a short conclusion in other words. LinxCNC "works" together with mesa HW like a "closed loop regulator". Linux "controlles" the executed steps donbe by mesa in the servo thread and corrects if necassary?
If this is the case I can estimate the error during milling and probing.

Line 24, replace this:

with this:
works for me on 2.10:

 

UH, too hard to me, not understand anythink this all code, but need use touch probe tool height setting only.

how install and use if not newer before has understand code, or hal or ini or what all this need and what all have. and were have. not understand code.

It looks like you are still running the old version of ethercat master.
I look at this message in syslogThis means the EoE code is still active in the ethercat master.
When EoE is removed from the master, all messaged with EoE will disappear.

Make sure to remove the debian/apt installed version of the ethercat masterThen re-compile and re-install the new version of ethercat master.
Also, the configure statement I told you was wrong (sorry about that), it should beand continue to install according to INSTALL.md.

When you have the ethercat master up and running again, check the syslog. There should be no EOE mentioned.
This must work, it is all dependent on that EoE is removed.

i used hard stop homing on many machines with mitsubishi/yaskawa servo drives. all of them have a "torque limit" input and a "torque clamped" output. so just connecting

joint.*.homing => servo-*.limit-torque
joint.*.home-sw-in <= servo-*.torque-clamped

does the trick.

and here's the video when i'm using "torque-clamped" for motion.probe-input. with z axis driven by 2mm pitch sync belt on 20 teeth pulley it is able to resolve silkscreen paint thickness on a PCB...

Oh no, something else not quite right with my build. The halrun binary seems to be missing. I will try to find out how that dropped out. I will need it for the project where I plan to use this pi3.

Another latency test. The previous one I shared was run a couple minutes with nothing else running. This time I gave it the works. How about 10mS latency.

Here are the error reports I get trying to wake QtDragon. seems to be a complaint about the ngc path. I'm using run-in-place. I've got to look at this again. Just writing it up gave me more ideas.

Wow, I can hardly believe I did this to a pi 3. The simulation is running. Next I want to check if gpio and a couple other basics work. The latency numbers look a bit sad.
Still no luck starting QtDragon.

Sorry to hear about the accident. That work you shared looks nice. Someone had it about all figured out. Wish I could help out. Dunno, my own wiring schematics are just scribbles on paper.