Advanced Search

If you edit the tool table, save the changes, re-load the tool table in the GUI and then issue a G43 in MDI then the tool diameter really should change.

Maybe it's the "reload tool table" step that is missing?

Is the Z limit switch also a home switch?

halshow (in Axis menu - Machine - Show Hal Configuration) will let you explore whether joint.2.*-lim-sw-in is not working properly.

When i start this pendant must push continuous mode button for jogging with
wheel is not press continuous it changes feedrate override.
How can fix this ?

Been getting this error a lot, and again, the machine will not home.

I was not awere of this working mode, it can be useful because you can use  sheetcam drawings or generate in QTplasmaC.
but still need change pierce delay in tool.

Turn off eoe

I am unable to get the motors to move, they are open loop steppers.  This is my first use of linuxcnc so I don't know much, but I tried power on, then home and got the following:

phil@SodickA:~/linuxcnc/configs/sim.axis$ linuxcnc lathe.ini
LINUXCNC - 2.9.3
Machine configuration directory is '/home/phil/linuxcnc/configs/sim.axis'
Machine configuration file is 'lathe.ini'
Starting LinuxCNC...
libnml/buffer/shmem.cc 320: Shared memory buffers toolCmd and toolCmd may conflict. (key=1004(0x3EC))
libnml/buffer/shmem.cc 320: Shared memory buffers toolSts and toolSts may conflict. (key=1005(0x3ED))
libnml/buffer/shmem.cc 320: Shared memory buffers emcError and emcError may conflict. (key=1003(0x3EB))
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./ethercat.hal
note: MAXV max: 3.333 units/sec 200.000 units/min
note: LJOG max: 3.333 units/sec 200.000 units/min
note: LJOG default: 1.000 units/sec 60.000 units/min
note: jog_order='ZX'
note: jog_invert={'X'}
task: main loop took 0.059970 seconds
task: main loop took 0.075473 seconds
task: main loop took 0.050344 seconds
Can't run a program when not homed
task: main loop took 0.019042 seconds
task: main loop took 0.052011 seconds
joint 0 following error
emc/task/taskintf.cc 976: Error on joint 0, command number 110
task: main loop took 0.036446 seconds
task: main loop took 0.045782 seconds
task: main loop took 0.078341 seconds
task: main loop took 0.050362 seconds
Can't issue MDI command when not homed
task: main loop took 0.018336 seconds
Shutting down and cleaning up LinuxCNC...
task: 746110 cycles, min=0.000007, max=0.078341, avg=0.001059, 14 latency excursions (> 10x expected cycle time of 0.001000s)
Note: Using POSIX realtime


Were can I get a definition of command number 110?

I’ll try to take a peek after work today

Hi, that looks like a lot of network problems to me. I don't actually know what the problem is, it's a guess.
First, check this one out

which uses a different dcconf statement and a watchdog statement. It's worthwhile to try.

If that doesn't work.
What computer and network card do you have? Can you post the output of the commands "uname -a" and  "lshw -C network"?
Have you tried changing to other network cables?
Tested with only one drive attached?
Tested with another ethernet card. Intel cards works the best for me. If you have a free pci-e slot it's easy to test with a Intel i226 card.

Hello , its been a while but did you succeed in running the simodrive ?

I have the same setup on an Eumach 1050 Heidenhein TNC 407

Nice to know it works for you before I embark on the same mission

What's the application of EtherCAT PWM output? ie, where would you use that rather than analogue output?

Basically, I agree with you. Specifying some basic settings at the start of the program makes sense and is done that way. However, it's confusing when the machine is always in different states during different phases, such as after the control system starts, during program execution, after a program abort, after a tool change, and so on. For me it's not clear why the tool length should disappear when a program is aborted? I can't see the reason or the rationale for this.

But I have a solution for this.

However, we're getting away from the actual question:

How can I ensure that the radius is updated in the tool info window when applying the tool table after editing? Are incorrect half pins connected here, or where are the functions triggered by the "Apply" button controlled? When milling with radius compensation, the value from the info field is used. G41/42 accesses this value.
When programming, I use radius compensation (finishing, fits, etc.) whenever possible and sensible. This allows for easy adjustment of the dimensions without having to change with the CAD program.

I'm still working on it.
Having the tool pointing in the x direction instead of the z direction in the home position has turned out to be a bit more of a headache as Linuxcnc applies the tool offsets internally.
TCP with xyz tool offset and tool spindle orientation is done. The kinematic for Tilted work plane also works but the transformation of the work offset still needs some work.

Let me figure this out first and I'll post a new sim config so you can have a look at it. Then we can have a look at customizing the gcodes for your specific needs.
 
 

first thing i went to google and searched for this:
Google help me  
I didn't find anything to configure the steps, I attach my configuration. After the modification the stepper doesn't move anymore I also tried to give it this combination:I attached the txt file I sent to NVEM
 

I've always felt it was best to always explicitly set G43 Hn in the g-code program, but I came from a back round of programming primarily for Fanuc controlled machines before using Linuxcnc. Never assume the state of the machine. Inserting a handful of g-codes at the start (preamble) or every tool change is cheap insurance.

Are you using the diameter offsets (G41/G42)? If not, I'm not sure that the tool diameters are really used for much of anything unless G41 or G42 is active. If you are using the diameter offsets, generally you would be turning them on and off in your code for different situations and the new offset would be activated at the next G41/G42 call. Myself I almost never use them, and program from the tool center with the CAM program. About the only time I use them is for compensating for resharpened tools (which I rarely use.)