Advanced Search

I bought that same Hynade 80amp cutter in October '23 and have been running it ever since on my homemade linuxcnc/mesa table, no complaints at all.

I did some research on the torch and found the manuals from Tecmo are the source of the torch or are excellent copies.

www.tecmo.it/wp-content/uploads/2023/02/2022-09-A-PT.pdf

I purchase torch consumables under their part numbers from ebay seller PlasmaDyn www.ebay.com/str/plasmadynplasmaweldingparts

Looking forward to this build.

I see. I'm not very familiar with editing post processors so I have no idea what's possible. I've made a sketch to give you an idea of how Tilted Work Plane (TWP) would work in the example part.

 

What we need is the offset from the current WCS (G54) to the new origin of the TWP. After that we can use regular 3axis gcode to mill the feature on the inclined plane.
Note that the g68.3 command accepts an optional 'R' word to change the direction of the new X axis.

this is the result:

35375     20 -rw-r--r--   1 root     root        20333 Mai  5 16:57 /usr/lib/modules/6.1.0-34-rt-amd64/updates/dkms/ec_generic.ko
  7093046     20 -rw-r--r--   1 root     root        20333 Mai  5 16:55 /usr/lib/modules/6.1.0-30-rt-amd64/updates/dkms/ec_generic.ko
   526822     20 -rw-r--r--   1 root     root        20333 Mai  5 16:57 /var/lib/dkms/ethercat-dkms/1.6.4/6.1.0-34-rt-amd64/x86_64/module/ec_generic.ko
   526812     20 -rw-r--r--   1 root     root        20333 Mai  5 16:55 /var/lib/dkms/ethercat-dkms/1.6.4/6.1.0-30-rt-amd64/x86_64/module/ec_generic.ko

 

Thanks, I will read through that thread to see if it will help, however that thread is for a closed loop drive and mine are open loop. The drives know they are open loop, but I am wondering if linuxcnc knows they are open loop. Where is that set in linuxcnc?

Sorry Chris.
Thank you.

Thanks I got 1 of 3 to work.
So now I know i need new ones.

So I will just order som pnp
And do without extra components.
Make it easy on the "next guy" comming to repair.

Here is what I put in my .Hal file for a standard MPG. This is for EC500 and the switch need to be set to STD MPG on the controller

PS my inputs numbers are not the same as github config.txt, I customize them...

# ###########
# MPG setup # 
# ###########

setp mux4.0.in0 0.0001
setp mux4.0.in1 0.001
setp mux4.0.in2 0.01

# The inputs to the mux4 component
net scale1 mux4.0.sel0 <= remora.input.29 #X10IN
net scale2 mux4.0.sel1 <= remora.input.30 #X100IN

# If your MPG outputs a quadrature signal per click set x4 to 1
# If your MPG puts out 1 pulse per click set x4 to 0

setp encoder.0.x4-mode 0

# For velocity mode, set to 1
# In velocity mode the axis stops when the dial is stopped
# even if that means the commanded motion is not completed,
# For position mode (the default), set to 0
# In position mode the axis will move exactly jog-scale
# units for each count, regardless of how long that might take

setp joint.0.jog-vel-mode 1
setp joint.1.jog-vel-mode 1
setp joint.2.jog-vel-mode 1
setp axis.x.jog-vel-mode 1
setp axis.y.jog-vel-mode 1
setp axis.z.jog-vel-mode 1
#setp joint.3.jog-vel-mode 1
#setp joint.4.jog-vel-mode 1
#setp joint.5.jog-vel-mode 1
setp axis.a.jog-vel-mode 1
setp axis.b.jog-vel-mode 1
setp axis.c.jog-vel-mode 1

# The output from the mux4 is sent to each axis jog scale
net mpg-scale <= mux4.0.out
net mpg-scale => joint.0.jog-scale => axis.x.jog-scale
net mpg-scale => joint.1.jog-scale => axis.y.jog-scale
net mpg-scale => joint.2.jog-scale => axis.z.jog-scale
#net mpg-scale => joint.3.jog-scale => axis.a.jog-scale
#net mpg-scale => joint.4.jog-scale => axis.b.jog-scale
#net mpg-scale => joint.5.jog-scale => axis.c.jog-scale

# The MPG inputs
net mpg-enc-a encoder.0.phase-A <= remora.input.21
net mpg-enc-b encoder.0.phase-B <= remora.input.22

# The Axis select inputs
net mpg-x axis.x.jog-enable <= joint.0.jog-enable <= remora.input.23
net mpg-y axis.y.jog-enable <= joint.1.jog-enable <= remora.input.24
net mpg-z axis.z.jog-enable <= joint.2.jog-enable <= remora.input.25
#net mpg-a axis.a.jog-enable <=  joint.3.jog-enable <= remora.input.26
#net mpg-b axis.b.jog-enable <=  joint.4.jog-enable <= remora.input.27
#net mpg-c axis.c.jog-enable <=  joint.5.jog-enable <= remora.input.28

# The encoder output counts to the axis. Only the selected axis will move.
net encoder-counts  <= encoder.0.counts
net encoder-counts => joint.0.jog-counts => axis.x.jog-counts
net encoder-counts => joint.1.jog-counts => axis.y.jog-counts
net encoder-counts => joint.2.jog-counts => axis.z.jog-counts
#net encoder-counts => joint.3.jog-counts => axis.a.jog-counts
#net encoder-counts => joint.4.jog-counts => axis.b.jog-counts
#net encoder-counts => joint.5.jog-counts => axis.c.jog-counts

"makes me wonder if you can get the CAM so use 'D0':"

Should be no problem.

For now it needs to be done manually. I have a contact at hand who can modify the PP to our preferences. We just need to get the LCNC side going.

I do list all the changes that need to be done to the Doosan PP. My contact will then implement everything.

I think in regards to modifying the PP we are totally free. I've just used to Doosan PP to have something at hand. It definitely needs to be modified and if that includes G17... than that's the way it has to be.

Looking at this:

 

makes me wonder if you can get the CAM so use 'D0':
Instead of 'D1'