Gmoccapy - A new screen for linuxcnc
- mariusl
- Offline
- Platinum Member
-
Less
More
12 years 7 months ago #44686
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Norbert
I would forget about the probe button but as I am using a 1,6mm thick touch off plate I have to be able to manipulate the result first in order to get the true block height. So I have to use a sub routine to do the touch-off on the block. After that, I dont have to use it again. I am asking how to get my result (that is not in #5063), into your routine. Alternatively, is what I am doing in the routine OK for gmoccapy as it is?
I would forget about the probe button but as I am using a 1,6mm thick touch off plate I have to be able to manipulate the result first in order to get the true block height. So I have to use a sub routine to do the touch-off on the block. After that, I dont have to use it again. I am asking how to get my result (that is not in #5063), into your routine. Alternatively, is what I am doing in the routine OK for gmoccapy as it is?
Code:
O<probe_material> sub
G49
G91
G38.2 Z-90 F100 (down to the touch plate)
G0 Z1 ( back off from the touch plate)
G38.2 Z-10 F10 ( back down slowly to the plate)
#<_material_ref> = #5063 (result of the touch off)
#1000 = [#5063 - 1.6] (result less the plate size)
(#5422 = 0)
(G10 L2 P0 Z0)
G91
G92 Z1.8
G90 ( absolute mode)
G0 Z30 ( return to safe level)
O<probe_material> endsub
%
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
12 years 7 months ago #44696
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Sorry Marius,
I can't follow you.
Please take a look at configs/sim/gmoccapy/macros/change.ngc and see if you can add your file, or just subtract the 1.6 mm from the reslult in the mentioned file.
As your way is completely different from mine, you will have to figure it out. I can not give any recommendation. Gmoccapy will handle every remap function you declare.
Norbert
I can't follow you.
Please take a look at configs/sim/gmoccapy/macros/change.ngc and see if you can add your file, or just subtract the 1.6 mm from the reslult in the mentioned file.
As your way is completely different from mine, you will have to figure it out. I can not give any recommendation. Gmoccapy will handle every remap function you declare.
Norbert
Please Log in or Create an account to join the conversation.
- mariusl
- Offline
- Platinum Member
-
12 years 7 months ago #44722
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Hi Norbert
I did look at the change.ngc file. I cannot see a way to do what I am looking for.
There are two ways to get the block height.
1: By making a manual measurement ( as you do )
2: By probing the top of the block or anywhere on a complex part with G38.x (most common way of doing - for me at least )
What I am looking for is a way to get the block height into "gmoccapy.blockheight" from the probed result. It is not always practical to measure a part or block height form the base of the machine so we probe the height. For instance, if I want to machine inside a cavity of an already made part, it could be very difficult to measure the exact height. But if it is probed, you can get the correct measurement.
This is the usual way of getting the job Z zero position for every job that I do. So it serves a dual purpose.
NOTE: This method is done before the gcode is run at all.
To provide a solution for this way of usage;
If the "gmoccapy.blockheight" was R/W or a parameter, then we could write the result to that instead of pushing the "Block Height" button manually. Also we dont have the probe result on display to enter it easily.
I understand that you cannot spend time on support for the usage of the screen but I do think this is a very needed feature. Without that the Automatic tool change function will be limit.
Any suggestions will be welcome
P.S. What is Luminos?
I did look at the change.ngc file. I cannot see a way to do what I am looking for.
There are two ways to get the block height.
1: By making a manual measurement ( as you do )
2: By probing the top of the block or anywhere on a complex part with G38.x (most common way of doing - for me at least )
What I am looking for is a way to get the block height into "gmoccapy.blockheight" from the probed result. It is not always practical to measure a part or block height form the base of the machine so we probe the height. For instance, if I want to machine inside a cavity of an already made part, it could be very difficult to measure the exact height. But if it is probed, you can get the correct measurement.
This is the usual way of getting the job Z zero position for every job that I do. So it serves a dual purpose.
NOTE: This method is done before the gcode is run at all.
To provide a solution for this way of usage;
If the "gmoccapy.blockheight" was R/W or a parameter, then we could write the result to that instead of pushing the "Block Height" button manually. Also we dont have the probe result on display to enter it easily.
I understand that you cannot spend time on support for the usage of the screen but I do think this is a very needed feature. Without that the Automatic tool change function will be limit.
Any suggestions will be welcome
P.S. What is Luminos?
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
- mariusl
- Offline
- Platinum Member
-
12 years 7 months ago #44724
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Hi Norbert
Just noticed something. You can please change the header comment of the gmoccapy script. It is not a "Try of a new GUI" it is a new GUI and a damn good one man.
Give yourself some credit.
Just noticed something. You can please change the header comment of the gmoccapy script. It is not a "Try of a new GUI" it is a new GUI and a damn good one man.
Give yourself some credit.
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
12 years 7 months ago #44725
by newbynobi
I did not change the header, but someoen did
May be the admin of this thread like gmoccapy too 
Norbert
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Hi Norbert
Just noticed something. You can please change the header comment of the gmoccapy script. It is not a "Try of a new GUI" it is a new GUI and a damn good one man.
I did not change the header, but someoen did
Norbert
Please Log in or Create an account to join the conversation.
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
12 years 7 months ago - 12 years 7 months ago #44726
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
ToolChange:
The toolchange of gmoccapy is nothing more than a remap function with the special case of block height.
If you do want to modify it, you only have to modify the change.ngc file.
Marius the way you want to do it, do requiere a reference tool! Exactly this is what I wanted to avoid. There is an example of touching off the workpiece with a reference tool in sim/axis/remap called manual-tool-change-with-tool-length-switch.
Please take that one as starting point. You will not need than the blockheight button or pin from gmoccapy.
Norbert
luminos = Linux User Machine Inetrface NOrbert Sch.
Will be the very industrial version of gmoccapy. It will require basic hardware as ESTOP Button ON-Switch, Jogwhell, Axis selection switch, mode selection switch, keyboard and some more. It will offer the "gmoccapy layout", the sidebutton handling, much more pin than gmoccapy to connect hardware and in the final version it will contain an integrated gcode generator similar to the ShopMill and ShopTurn. so you will be able to produce most 2.5D parts without the need of a CAM. But if you want not only basic stuff, like drill, facing and so on, you will be forced to spend a little money to get contour pocketing with island and atomatic selection of entry and leaving moves, trochiodal slotting and so on...
Be surprised, I will open an own thread for that as soon as the first moves can be done, but that will still take a while.
The toolchange of gmoccapy is nothing more than a remap function with the special case of block height.
If you do want to modify it, you only have to modify the change.ngc file.
Marius the way you want to do it, do requiere a reference tool! Exactly this is what I wanted to avoid. There is an example of touching off the workpiece with a reference tool in sim/axis/remap called manual-tool-change-with-tool-length-switch.
Please take that one as starting point. You will not need than the blockheight button or pin from gmoccapy.
Norbert
luminos = Linux User Machine Inetrface NOrbert Sch.
Will be the very industrial version of gmoccapy. It will require basic hardware as ESTOP Button ON-Switch, Jogwhell, Axis selection switch, mode selection switch, keyboard and some more. It will offer the "gmoccapy layout", the sidebutton handling, much more pin than gmoccapy to connect hardware and in the final version it will contain an integrated gcode generator similar to the ShopMill and ShopTurn. so you will be able to produce most 2.5D parts without the need of a CAM. But if you want not only basic stuff, like drill, facing and so on, you will be forced to spend a little money to get contour pocketing with island and atomatic selection of entry and leaving moves, trochiodal slotting and so on...
Be surprised, I will open an own thread for that as soon as the first moves can be done, but that will still take a while.
Last edit: 12 years 7 months ago by newbynobi.
Please Log in or Create an account to join the conversation.
Moderators: newbynobi, HansU
Time to create page: 1.934 seconds