CNC plazma Microstep - retrofit
25 Mar 2018 13:33 #107812
by r4cv
Replied by r4cv on topic CNC plazma Microstep - retrofit
I did a simple test:
G53 G0 Z0
G92 Z0
M64 P0
M66 P0 L1 Q5
G38.2 Z-90 F500
G0 Z[#5063 + 0.5]
G92 Z40
M65 P0
M66 P1 L1 Q5
G1 Z#1
M2
inputs and output works well. if everything works, the probing is fine. But if the compressed air is absent, Z drops down with a retracted probe and a torch crash.
I have to write a subroutine if I want to interrupt probing when signal do not be true (M66P0 L1 Q5)? Now is waiting for signal or time.
how to set the variable from pin plasma.pierce-gap to #1? Now is Z#1=0 (default). Z[#5063 + 0.5] works.
G53 G0 Z0
G92 Z0
M64 P0
M66 P0 L1 Q5
G38.2 Z-90 F500
G0 Z[#5063 + 0.5]
G92 Z40
M65 P0
M66 P1 L1 Q5
G1 Z#1
M2
inputs and output works well. if everything works, the probing is fine. But if the compressed air is absent, Z drops down with a retracted probe and a torch crash.
I have to write a subroutine if I want to interrupt probing when signal do not be true (M66P0 L1 Q5)? Now is waiting for signal or time.
how to set the variable from pin plasma.pierce-gap to #1? Now is Z#1=0 (default). Z[#5063 + 0.5] works.
Please Log in or Create an account to join the conversation.
25 Mar 2018 13:35 - 25 Mar 2018 13:36 #107813
by r4cv
Replied by r4cv on topic CNC plazma Microstep - retrofit
islander261
Can you send me your GUI files? they are very interesting.
Can you send me your GUI files? they are very interesting.
Last edit: 25 Mar 2018 13:36 by r4cv.
Please Log in or Create an account to join the conversation.
- Mike_Eitel
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1159
- Thank you received: 185
25 Mar 2018 14:56 #107816
by Mike_Eitel
Replied by Mike_Eitel on topic CNC plazma Microstep - retrofit
I have no glue of plasma, but if compressed air is so importand, why not include in e-stop?
m5c
Mike
m5c
Mike
Please Log in or Create an account to join the conversation.
- islander261
- Offline
- Platinum Member
-
Less
More
- Posts: 757
- Thank you received: 216
25 Mar 2018 14:57 #107817
by islander261
Replied by islander261 on topic CNC plazma Microstep - retrofit
r4cv
Ok, I will upload an archive of the files some time today.
First you need to study the docs about Gmoccapy and using Glade to edit the GUI parts and the python handlers that go with the tabs. I am sorry my code will be very confusing because I used a mix of HAL widgets and regular GTK2 widgets. I also have a very clumsy method of running widgets across tabs that I hope doesn't cause any problems.
John
Ok, I will upload an archive of the files some time today.
First you need to study the docs about Gmoccapy and using Glade to edit the GUI parts and the python handlers that go with the tabs. I am sorry my code will be very confusing because I used a mix of HAL widgets and regular GTK2 widgets. I also have a very clumsy method of running widgets across tabs that I hope doesn't cause any problems.
John
Please Log in or Create an account to join the conversation.
25 Mar 2018 16:01 #107825
by r4cv
Replied by r4cv on topic CNC plazma Microstep - retrofit
Mike_Eitel
there are more reasons to check probeON. compressed air is one of them.
it is better not to touch the sheet for a longer lifetime of consumable parts.
for this reason I want this probe, but maybe you have another idea.
there are more reasons to check probeON. compressed air is one of them.
it is better not to touch the sheet for a longer lifetime of consumable parts.
for this reason I want this probe, but maybe you have another idea.
Please Log in or Create an account to join the conversation.
- Mike_Eitel
-
- Offline
- Platinum Member
-
Less
More
- Posts: 1159
- Thank you received: 185
25 Mar 2018 17:04 #107828
by Mike_Eitel
Replied by Mike_Eitel on topic CNC plazma Microstep - retrofit
Not realy, as i do not know plasma. But you can always use ladderlogic and make combinations with f.x. motor enable Signals. Or i would even do that with a direction signal of an axis motor.
Please Log in or Create an account to join the conversation.
25 Mar 2018 17:49 #107830
by r4cv
Replied by r4cv on topic CNC plazma Microstep - retrofit
checking the probe is not a big problem. I can make it later, so far I will use the HAL to create a pause signal for MOTION and continue when the signal probe-is-ON go TRUE.
The bigger problem is I can not find how to set the value from pin plasma.pierce-gap to #1 .
After probing I have torch on 0 (zero) height instead of pierce height.
The bigger problem is I can not find how to set the value from pin plasma.pierce-gap to #1 .
After probing I have torch on 0 (zero) height instead of pierce height.
Please Log in or Create an account to join the conversation.
25 Mar 2018 19:47 #107839
by r4cv
Replied by r4cv on topic CNC plazma Microstep - retrofit
I found an older topic
Reading Hal pins from Gcode [SOLVED]
I tried the MDI command
#1 = #<_hal[plasma.pierce-gap]>
the result is a error
Named parameter #<_hal[plasma.pierce-gap]> not defined.
how to create this parameter?
plasma.pierce-gap is pin conected to signal gap-p.
I tried the MDI command
#1 = #<_hal[plasma.pierce-gap]>
the result is a error
Named parameter #<_hal[plasma.pierce-gap]> not defined.
how to create this parameter?
plasma.pierce-gap is pin conected to signal gap-p.
Please Log in or Create an account to join the conversation.
- islander261
- Offline
- Platinum Member
-
Less
More
- Posts: 757
- Thank you received: 216
25 Mar 2018 20:58 #107843
by islander261
Replied by islander261 on topic CNC plazma Microstep - retrofit
r4cv
You need to define that pin to connect your label widget displaying the pierce gap to the HAL. You normally do this in the python handler file associated with the tab (Gmoccapy tab) that the label is defined in. Look and read here:
linuxcnc.org/docs/devel/html/gui/gladevcp.html
Jon T. has a good tutorial on this as well.
Study how all the parts fit together in the Gmoccapy plasma example.
John
You need to define that pin to connect your label widget displaying the pierce gap to the HAL. You normally do this in the python handler file associated with the tab (Gmoccapy tab) that the label is defined in. Look and read here:
linuxcnc.org/docs/devel/html/gui/gladevcp.html
Jon T. has a good tutorial on this as well.
Study how all the parts fit together in the Gmoccapy plasma example.
John
Please Log in or Create an account to join the conversation.
25 Mar 2018 21:23 #107849
by rodw
Replied by rodw on topic CNC plazma Microstep - retrofit
John (Islander261) has a very good tutorial in this thread that allows setting a gmocappy plasma screen variable from gcode
forum.linuxcnc.org/plasma-laser/32691-settings-from-g-code-file
As he's just said, its done in plasma.py which is the screen handler for python.glade which defines the gmocappy plasma screen layout.
From gcode you use M67/M68 to change the screen variables.
You can probably limit the probe movement by changing the -90 in this line so the torch cannot crash
G38.2 Z-90 F500
That way the probe process will error out and prevent the crash.
forum.linuxcnc.org/plasma-laser/32691-settings-from-g-code-file
As he's just said, its done in plasma.py which is the screen handler for python.glade which defines the gmocappy plasma screen layout.
From gcode you use M67/M68 to change the screen variables.
You can probably limit the probe movement by changing the -90 in this line so the torch cannot crash
G38.2 Z-90 F500
That way the probe process will error out and prevent the crash.
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.232 seconds