Advanced Search

If I set like the table in your posts, it still moves and slams the axis into the end stops.
If I set homing sequence to -1 it flickers the drive.

I do not want any internal homing on the drive. I want no motion whatsoever.

What "normally" works is not here.

The docs at linuxcnc.org/docs/html/config/ini-homing.html says it
 

The cia402 component says

 For using the servo drives internal homing procedure configure your
joint homing to Home on Index Pulse only and connect the components
home Input to the index-enable Pin:

I don't see you have connected that pin.

To debug, use halscope and record controlword and statusword to and from the drive.

Later I will summarize and correct the first message of the topic.
First, it turned out that it was pointless to consider the topic without taking into account the electrical component and connection diagram.
Then it turned out that neither the Snnnnn parameter nor the M68 Qnnn control the laser power as it should (the hypothesis from the message www.forum.linuxcnc.org/10-advanced-confi...-laser?start=0#92752 is not correct in part 50%).

Colleagues, here we are trying to use the Snnnnn or M68 E0 Q 0.nn commands to turn the laser on and off.

What is known about the time of their execution and delays? What is the point of using M68?

Yeah the thread is long and full of failed attempts and iterations.
That's my development cycle, sadly.
The last post summarizes it. And this post show the performance forum.linuxcnc.org/show-your-stuff/56269...m-60?start=20#336805 It keeps performing like that even on water and rusty pieces.

Because the torch is the way it is, the ground leads in the torch, used during the arc start, needs to be cut and a small voltage applied which one measure to detect contact with the material. The rest is implementation and packaging in a nice format.
If you are willing to do surgery on the long cable to the torch you can cut it open and access the ground leads in there.
Instead, I made a short extension cable where all modifications were done.

I also used two separate voltage readers but I don't think that is necessary.
One uses the built-in voltage port, one measures directly between material ground and torch tip.
I will cut some parts later today so I can compare the voltage output of the two.
Of course, Mesa's THCAD cards can be used, the full voltage version.

Ok, so I sorta understand what is going on. searchvel set to 0 is supposed to work. It was in my file before, HOWEVER it causes my ethercat drives to reset repeatedly, apparently cause the home routine toggles enable. This is basically what was happing with the M3 pins, some manner of conflict.

So how do we get around this?

config files

hrm...

So i have no limit switches yet. i with the old servos and with these id just move the machine to the home position, then press the home all button in axis, and it would mark everything 0 and call it homed.

Now, I pressed home and the machine moved, at full rapid, into the end stops....

Because I didn't change anything at all in the ini since last time, I am confused.

What is the correct way to have the machine home without actually moving?

Also the machine z home offset is set to 110 at the top of the axis, but it slams down into the table. It also goes full rapid even if the rapid overide is 1% and the home approach speed is 1mm/m.

Clearly something is screwwy but i cant see it. I will add my INI and hall files in a moment.

You have a probe diameter set in the tool table?

Does your probe calibration correctly measure the calibration ring/pin used?

Are you correctly setting up your cam post processor?

Have you verified using mdi commanded moves to rule out based cam settings?

Is your axis calibration correct?

Perhaps this is the wrong place to post this but I am doing so incase someone thinks it may be within probe basic as the issue.

Problem: When I probe a corner of my 6-sided precision ground stock, and then run the tool path, the cuts are offset. At the probed Y side, the endmill is a few mm AWAY from the side not cutting and on the opposite side it is digging in a few mm causing a crash. It appears something similar is happening on the X side as well.

Machine: Taig CNC with linuxcnc 2.9.4 using probe-basic

Here is what I have done to debug:
1. Indicated my vise jaws, confirmed vise is in line with X and Y
2. Indicated my probe tip, made sure it is straight
3. redid probe basic probe tip calibration which results in a number in line with my other machines (I use the same aliexpress 3 axis probe)
4. confirmed the table is trammed, column is perpendicular to the table
5. Tested axis travel with a dial indicator mounted in-line with each axis. When I command movement of 12.7mm the indicator reads 0.5 inches so it appears the axis are travelling the correct amount (both X and Y)
6. Using fusion360, verified my endmill dimensions are correct (9.525mm), toolpath seems as usual, simulation looks correct

Additional information:
1. I added a screenshot of my 3/8 endmill on the side I probed, it is hard to tell but the endmill is about 2mm away from actually touching the side whereas it should be digging in 0.2mm into the side and cutting
2. added the start of my gcode file

Question: Do you all have any other suggestions on what I can try to do to debug the issue further? This is the only machine I have issues with. I have a linuxcnc lathe and tormach mill with pathpilot and both work correctly.

thank you. sorry don't see this thread. too difficult for me but i will try

What are the following error limits set for?

Do you lose packets?

That is, what is hm2_7i76e.0.packet-error-total?

Can you post your hal / ini files?

Do you have the usual optimizations:

isolcpus = last cpu in grub (isocpus=3 for a 4 core CPU for example)

IRQ coalescing off with Intel MACS

DKMS driver installed with RealTek MACs

Ethernet IRQ pinned to last processor
 

Can you try removing the "0x" part from the pdo entries in the xml file?

For example
"<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>"
is working for my A6 servo driver

I reinstalled the full Linux, because I probably already messed everything up.
Now the configuration wizard worked right away and everything works fine.
Thanks again for your help.

I agree, but pretty good, non the less.
I am adding this one from our forum by Mozmck as i looked for it several times and could not find it, i am thinking this should be in the "computers and hardware" section, not in the "general LinuxCNC questions".
forum.linuxcnc.org/38-general-linuxcnc-q...ead-and-irq-affinity