Advanced Search

Is this the original gmoccapy screen?

It stops doing this move.

- XY move (G53 X#1801 Y#1802 )

It has been done before. Ethercat is really just a way of controlling your motors and I/O so it does not change anything or prevent you from building a plasma table.
Choose a plasma cutter with a proper CNC interface and voltage divider that does 20:1 or 30:1 division
You will need an Ethercat I/O module for inputs and outputs.
Torch voltage sensing is something the 7i76e/thcad combo does well. the THCAD has a 0-10 volt range with 500volt overvoltage protection
In an Ethercat environment, I would look for a 0-10 volt Ethercat analog input module that has overvoltage protection to 500 volts.(not hard to find)
To give QTplasmac the voltage output, you should be able to scale the voltage using the QTplasmac voltage scale settings.

Another probably more costly way would be to buy an Ethercat encoder input and attach a thcad to it.

Advanced options would be to home using the drive internals and implement torque mode homing to eliminate the need to wire home switches. This would require a custom homing module in linuxcnc. I am not sure if gantry homing would be supported.

Its working.

how can i turn off.
Beacuse if i press the button its turning green and the output is true. But if i press the button again its not turning off.

stops in the middle of traveling to the probe.

Which move do you mean?
- XY move (G53 X#1801 Y#1802 )
- Z move (G53 Z#1800 )
- the actual probing move (G38.2 Z-60 F500 )

This is awesome! Thank you so much. Who would have thought it would be as easy as adding one character to my INI!

GEOMETRY = ​​​​​​! BXYZ

Thanks again! 

@csurimilan
Your post has been moved to:
forum.linuxcnc.org/qtvcp/54583-call-cust...om-gui-button#315401

- Create a new HAL_COMMAND entry in the [HALUI] section of your ini file:
MDI_COMMAND = M101

- Make sure the [HAL] section of your ini file contains this entry:
HALUI = halui

Then connect the MDI_COMMAND in your hal file:
net coolant-flood => halui.mdi-command-00

Note that this will not work when a program is executing as this requires the controller to execute an MDI command.

Hello,
I have a question about coolant.
Im using costume made M-codes to controll the relays for my collant. (Air,flood,Mist => M100,M101,M102 and M105 turn off all)
I would like to know how can i address in the HAL file that if i press a button in the gui (qtDragon) that is turning on/off my coolant and of course i would like its working autoatically when the cnc is working. (Im using costume M-codes because im controlling more outputs)

net  coolant-flood  <= iocontrol.0.coolant-flood          //here i dont know how can i add the M101

thank you
 

Indeed a python2 vs python3 issue. If you have not customized 'stdglue.py' you can try and replace stdglue.py in your config/python directory with the current file:
'configs/sim/gmoccapy/python/stdglue.py'

There are several EDM machines using LinuxCNC on youtube, BaxEDM is one of them who builds and sells complete machines.
For retrofit, check if the existing drives and motors work and what control signal they accept, usually step/dir or analog +-10V.

Did you ever finish your retrofit? I have a Sodick that needs the same, I made a spark generator that seems to work so I am now ready to start the machine control part. I would benefit from your experience!

Aciera wrote:

Not sure but what you can do is this:1. Open you config the way you are used to.2. Close linuxcnc3. open terminal and run (note the minus letter 'L' which should automatically open the last config you used):

linuxcnc -lPlease see attachment, afterwards, the came out Gmocapy screen still not okay

Start a new topic for that.

Maybe have a look at this:
forum.linuxcnc.org/10-advanced-configura...-axis-display#314070