twin headed hydro punch how to cnc

jd896 wrote:

the possibility it there then, is there a way to have the file struture/ order its self so that taking into account the punches are 600 appart have the first few holes run on one machine and then invole the second machine without having to run up and down the beam from point to point (not overlapping moves if you like so's to get cycle times down)

i dont know the terminology but could it order the file based on the x position requested ascending/descending

thanks john

Yes you could move the beam and run punch 1 then move the beam and run punch 2 and so on. It just takes a little more up front thinking with your code.

John

jd896 wrote:

is there a difference between using m codes vs oword subs for the punch cycle

eg


inhibit motion moves
turn output 1 on
wait for input 1 (timeout after 10 secs then error, ask is machine pump running? or are limits set correctly?)
turn output 1 off
wait for input 2 (timeout after 10 secs then error , ask are limits set correctly?)
motion moves ok


question is motion paused while in a sub or m code ?

thanks john

The difference between using custom M codes like M100 and subroutines is you can do things outside of LinuxCNC with the custom M codes and subroutines are for doing normal things you do with G code it just adds logic and looping and variables to the G code.

For the pump control I'd use classicladder as it has easy to use timers.

John

This reminds me of the Optimal Golomb Ruler problem (though it is easier)
en.wikipedia.org/wiki/OGR

What form is your input data in?

If you want the pump on when you start punching a beam you could link it to halui.program.running (I think that is correct) so when a program starts it starts the pump then waits for an input that the pump is ready then start running your G code.

John

Subroutines can only see what is available to g code ie M62-M68. M66 is wait on input. All the M I/O must be "connected" in HAL to the I/O pin you wish to use.

linuxcnc.org/docs/html/gcode/m-code.html

A selector switch could be used and you will have to sort out turning on the pump in manual mode.

Just to recap a bit for my understanding... the subroutines are moving the beam with G code and finding the ends as needed with the probe input, the actual punching can be done with M100 user defined codes and the G code program waits for the M100 to complete before the next line. So you define M101 for punch #1 and M102 for punch #2.

So a simplified example subroutine might resemble...

#<num-holes> = 5
#<hole-distance> = 600
#<first-hole> = 257

G0 X#<first-hole>
#<current-x> = #<first-hole>
o100 repeat [#<num-holes>]
M101
#<current-x> = #<current-x> + #<hole-distance>
G0 X#<current-x>
o103 endrepeat

John