Advanced Search

Hi Scotta!

This is the error we get:

"command (EMC_JOG_CONT) cannot be executed until the machine is out of E-stop and turned on"

but when we disconnect the E-stop it recognizes that it is connected, we also sometimes get the Joint X following error.

Can you post your hal and ini files?
 

Hello everyone,
I am also trying to connect the Mesa7i96s card to a Y620-A VFD.
I connected the pins as mentioned in the post above
22 - SPINDLE- to COM
23 - SPINDLE OUT to AI1
24 - SPINDLE+ to +10 V
S1 --> OUT4A
OUT4B --> COM
S2 --> OUT5A
OUT5B --> COM
The M3, M4 and M5 commands work, but I can't control the speed.
Any ideas?
Thanks
Milko

Great to hear you are making progress.

No need for the SPI_clk_div=32 in the loadrt command line, that is for the RPi4/3.

What fault / error is generated when the machine stops? I've still got the Octopus and RPi setup on the bench, will look to try your config again over the weekend.

Today, after updates, i am not able to start any flexgui ui .  Error: No module named 'psutil'

Wasn't exactly sure where to put this question. But this is like the third time it happened to me. Upon the initial startup I'll home out the axis, go to MEM, select a g-code file, then I hit start. And it'll race through the g code like the entire program was full of G0 commands. If I had a part in the machine it would have crashed.  It's like it ignored every G1 command. Once the cycle is done, If I hit start cycle again, it'll go through like it's supposed to. The strange part is, it does not do it every time. Is this a configuration issue or a G-Code issue or a Linux issue? 

It's also known as chip breaking in mill G-Code. G83 and G73
The cycle sets final depth (X), retract position (R), peck depth (Q), and feed rate (F) normally used for drilling process. It's also handy for breaking stainless steel instead of getting birds nests or for live lathe tooling. Since my setup utilizes a grinder, without a pecking cycle it can stall the grinder out.
Right now I have to program a "peck" cycle manually. An example of this is:
G1 X2.02 F1
G0 X2.01
G1 X2.03 F1
G0 X2.02
G1 X2.04 F1
G0 X2.03

More pictures.

I have a simmilar 15k rpm Kessler spindle on a DMC 100 V.

I have attached the datasheet pictures.

Thanks for your quick reply.
Unfortunately the slots I need are open lines.
So no lead ins.
What I tried is using the puddle jump at Pearce hight. No pierce delay but a puddle delay. It seems to work well. But you don’t really have much control over plunge rate.
Is there a better way of doing this?

How do I fire the torch while the gantry is moving?

You need "lead in" for plasma cutting, you have that option in the included wizards for stuff you draw in LinuxCNC, and you will need a CAM software for other stuff to add those, probably SheetCAM.
BTW, you can start the torch while moving, but that will leave uncut sections on thin material and not cut at all on thicker material, but it will ruin the nozzle really quickly.

I must make changes to in jogscale..
Working setup
######################################################
#Jog Pendant
######################################################

loadrt mux4 count=1
loadrt ilowpass

setp ilowpass.0.scale 100
setp ilowpass.0.gain 0.01

addf mux4.0 servo-thread
addf ilowpass.0 servo-thread

net x-jog-select joint.0.jog-enable axis.x.jog-enable <= hm2_5i25.0.7i77.0.0.input-10
net y-jog-select joint.1.jog-enable axis.y.jog-enable <= hm2_5i25.0.7i77.0.0.input-11
net z-jog-select joint.2.jog-enable axis.z.jog-enable <= hm2_5i25.0.7i77.0.0.input-12
net a-jog-select joint.3.jog-enable axis.a.jog-enable <= hm2_5i25.0.7i77.0.0.input-13

net x10 hm2_5i25.0.7i77.0.0.input-14 => mux4.0.sel0
net x100 hm2_5i25.0.7i77.0.0.input-15 => mux4.0.sel1
setp mux4.0.in0 .0000025
setp mux4.0.in1 .000025
setp mux4.0.in2 .00025
setp mux4.0.in3 .0

net jogscale mux4.0.out => joint.0.jog-scale axis.x.jog-scale
net jogscale => joint.1.jog-scale axis.y.jog-scale
net jogscale => joint.2.jog-scale axis.z.jog-scale
net jogscale => joint.3.jog-scale axis.a.jog-scale

net mpg-out hm2_5i25.0.encoder.05.rawcounts => ilowpass.0.in

net jogcounts ilowpass.0.out => joint.0.jog-counts axis.x.jog-counts
net jogcounts => joint.1.jog-counts axis.y.jog-counts
net jogcounts => joint.2.jog-counts axis.z.jog-counts
net jogcounts => joint.3.jog-counts axis.a.jog-counts

I am experimenting with cutting straight lines for a screen.
Problem is this. On start and end of a line there is a hole that is bigger than the rest of the line. 
So I figured out how to edit a cut file by hand so it does stop the torch while the torch moves. So I get a perfect ending on the line I cut. 
Question is there a way I can get the torch to probe the metal, then accelerate to cutting speed for say 10 mm then turn the torch on at pierce height. 
And pierce while the torch is moving. Start point of cutting is not crucial but cut width at the beginning of the cut should be as close to the rest of the cut as possible.

Yes, Debian deserves some kind of prize for the dumbest login screen possible.

In addition to the jog enables, you need to do a similar change with the mpg count pins
that is, for example both joint.0.jog-counts axis.x.jog-counts must connect to the mpg count.