Advanced Search

Sounds like it did not get an Arc OK signal.  

The criteria is different depending what Mode you are using:

linuxcnc.org/docs/devel/html/plasma/qtplasmac.html#plasma:modes

Hi .
I'm trying to output an operation with thread milling but the gcode output for z position is static.
Code:
(THM_DRILL.NGC)
( 2-AUG-2025)
N1 
N2 #12=1
N3 #13=0
N4 
N5 #14=1
N6 #15=0

N7  G21 G49 G0 G54 ( ABS mm clr_Z_offset rapid_motion )

(MSG, Óñòàíîâè T1.
N8 M9 (turn all coolant off)

o106 repeat [#14]
o105 repeat [#12]

S3500 M3
G0 X0. Y0. Z25.
N9 M98 P2

N10 g0 x0 y0
N11 g92 x-#13
N12 o105 endrepeat
N13 g92.1
N14 g90
N15 g92 y-#15
N16 o106 endrepeat
N17 g92.1
N18 g90
N19 M30
O2
N20 (

---

)
N21 (THM-DRILL - THREAD)
N22 (

---

)
N23 G0 X0. Y0. Z25.
N24 M98 P3
N25 G0 X0. Y0. Z25.
N26 M99
O3
N27 G91 G0 Z-23.
N28 G1 Z-12. F300
N29 G41 G1 X7.379 Y-1.516 F800
N30 G3 X0.286 Y8.692 Z0.12 R6.15
N31    Z1. I-7.665 J-7.176
N32    Z1. I-7.665 J-7.176
N33    Z1. I-7.665 J-7.176
N34    Z1. I-7.665 J-7.176
N35    Z1. I-7.665 J-7.176
N36    Z1. I-7.665 J-7.176
N37    Z1. I-7.665 J-7.176
N38    Z1. I-7.665 J-7.176
N39    Z1. I-7.665 J-7.176
N40    X2.835 Y-7.176 Z0.88 R-10.5
N41    X-6.15 Y6.15 Z0.12 R6.15
N42 G40 G1 X-4.35 Y-6.15
N43 G0 Z24.88
N44 G90 M99

The Z axis stays at 1 mm.
I did discover if you open the machine editor of youre machine and go to Working Style => General and you put Software Transform to YES , the gcode output gives the corect z output:
Code:
N16 (

---

)
N17 (THM-DRILL - THREAD)
N18 (

---

)
N19    X0. Y0. Z25.
N20    Z2.
N21 
N22 G1 Z-10. F300
N23 G41 
N24 G1 X7.379 Y-1.516 F800
N25 G3 X7.665 Y7.176 Z-9.88 R6.15
N26    Z-8.88 I-7.665 J-7.176
N27    Z-7.88 I-7.665 J-7.176
N28    Z-6.88 I-7.665 J-7.176
N29    Z-5.88 I-7.665 J-7.176
N30    Z-4.88 I-7.665 J-7.176
N31    Z-3.88 I-7.665 J-7.176
N32    Z-2.88 I-7.665 J-7.176
N33    Z-1.88 I-7.665 J-7.176
N34    Z-0.88 I-7.665 J-7.176
N35    X10.5 Y0. Z0. R-10.5
N36    X4.35 Y6.15 Z0.12 R6.15
N37 G40 
N38 G1 X0. Y0.
N39 
N40 G0 Z25.
The problem is there is no more subroutines, the o call does not exist anymore so is M98 , M99.
The post processor is from here: github.com/G-S-E/SolidCAM-postprocessor-for-LinuxCNC
Thanks

Thats what i got so far 

I tried it again without changing anything and the plasmacutter started without firing at startup. Then I loaded the materal and tried to make a cut through 10mm mild steel. The torch fired, but the machine didn't move. And the torch went on and of a few times.
Why does that happen ? And why doesn't the machine move ?

more fun
i think im almost ready to order the atc parts.

 
 
 
 
 

i think i found the correct solution for this problem in the pico examples

Hello

i am trying to setup ethercat on linuxcnc 2.9.4.
I use these instructions

when i want to start the service it gives an error:
 modprobe: ERROR: could not insert 'ec_master': Key was rejected by service

these are the conf params i set:

MASTER0_DEVICE="dc:4a:3e:52:df:de"
DEVICE_MODULES="generic"

i based it on this:
Does anyone know where i went wrong?
I did first install it and find out that i was on a sercure boot, so i disabled it in the bios.

Kind regards,
Andries
 

ok, thanks i check it out.
worked perfectly. 1,5mm difference. Is there a way to compensate for this directly in pncconf. the Y2 sensor is reached 1.5mm faster then Y, so Y2 should move 1.5mm further in the homing sequence?

I was wrong!. It can read rpm in both forward and reverse after watching spindle-vel-fb-rpm in halshow.

I was surprised at how close it was to the set voltage (based on the cut height setting.) Well thought out.

I have not played with this plasma in ages - it was initially setup by me before eoffsets.. It worked good - but this was much easier..

sam

Sounds like you may have the spindle ENA polarity backwards.
 

No, if you setup immediate homing, no home move or sensors are involved,
LinuxCNC simply takes the current position as home.

the problem is i want to be able to jog the gantry before the home all, so i can find out what the physical misalignment of my sensors is. if i home first the homing will force my gantry according the sensors and so misalign my gantry and see it as homed and square

After the last update the formating is fine now.

But the question i have now, about gcode filter. I tried the filter, i am using with axis, but nothing happened.
Is it possible to use a filter and my setup is wrong?

And another problem:
A subroutine for probing is called at program start. To prevent problems with tool not loaded yet and others, i test for #<_task> EQ 0 and return to mainprogram, if 0
But this makes the preview disapear, also after probing is done. until abort or reset the program. only then it comes back.
Is there an alternative probe button for testing?  to load  'simulate_probe &'  doesn't work anymore

edit:
after testing a dummy filterprogram, its definetely not possible.
About the preview, i commented all probing and stuff, just left the bare nc code. When starting the program, preview disapears, on reset it returns. Program is checked in the settings


 

Maybe setup  a test ini file with immediate homing so no
home move is done and then you should be able to jog the
gantry axis after you hit the home-all button.

linuxcnc.org/docs/html/config/ini-homing.html#_configuration