Lathe Macros
28 Feb 2016 23:22 #70778
by cmorley
Replied by cmorley on topic Lathe Macros
The BBB is a little under powered in the graphics department.
Try tabbing the plot to not show or pick a GUI that doesn't have a plot.
BBB is really a machinekit option, so they may have other/better ideas
Chris M
Try tabbing the plot to not show or pick a GUI that doesn't have a plot.
BBB is really a machinekit option, so they may have other/better ideas
Chris M
The following user(s) said Thank You: f1oat
Please Log in or Create an account to join the conversation.
28 Feb 2016 23:38 #70782
by andypugh
I have to confess, I don't actually know.
There is no polling loop in the code, any polling is standard Glade stuff.
Maybe some clues here? developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html
Replied by andypugh on topic Lathe Macros
I am using LatheMacro-3.zip on a Beaglebone Black.
I see the related gladevcp is eating a lot of CPU (15 to 25%).
I have to confess, I don't actually know.
There is no polling loop in the code, any polling is standard Glade stuff.
Maybe some clues here? developer.gnome.org/glib/stable/glib-The-Main-Event-Loop.html
The following user(s) said Thank You: f1oat
Please Log in or Create an account to join the conversation.
28 Feb 2016 23:39 #70783
by f1oat
Replied by f1oat on topic Lathe Macros
Thanks.
Gmoccapy is running quite well on my BBB with 38% CPU consumption.
The gladevcp add 29% more. Strange, because it does not have to do much as this is only a pyngcui like panel.
I have another gladevcp panel running with 5 widgets and it eats less than 1%.
So, there is something wrong only with lathemacro.ui
I suspect some useless widget refresh somewhere.
Will ask on machinekit forum.
This is for an Emco Turn 120P retrofit: blog.f1oat.org/2016/02/20/emco-turn-120p-retrofit/
Frederic.
Gmoccapy is running quite well on my BBB with 38% CPU consumption.
The gladevcp add 29% more. Strange, because it does not have to do much as this is only a pyngcui like panel.
I have another gladevcp panel running with 5 widgets and it eats less than 1%.
So, there is something wrong only with lathemacro.ui
I suspect some useless widget refresh somewhere.
Will ask on machinekit forum.
This is for an Emco Turn 120P retrofit: blog.f1oat.org/2016/02/20/emco-turn-120p-retrofit/
Frederic.
Please Log in or Create an account to join the conversation.
03 Jun 2016 16:57 #75444
by RotarySMP
Replied by RotarySMP on topic Lathe Macros
This interface looks great. Exactly right for the way I tend to use my lathe. Thanks for sharing this Andy.
I downloaded the files to the folder with the edited machine ini per your readme file. The interface loads correctly, but once I have entered the parameters into a cycle tab and hit the arrow button, I get an Error "Unable to open file <boring>."
Same behaviour for all tabs. The boring.ngc and all other cycle files are in the same folder as the machines INI.
Any help in getting this running would be greatly appreciated.
Mark
I downloaded the files to the folder with the edited machine ini per your readme file. The interface loads correctly, but once I have entered the parameters into a cycle tab and hit the arrow button, I get an Error "Unable to open file <boring>."
Same behaviour for all tabs. The boring.ngc and all other cycle files are in the same folder as the machines INI.
Any help in getting this running would be greatly appreciated.
Mark
Please Log in or Create an account to join the conversation.
03 Jun 2016 17:20 #75447
by andypugh
Replied by andypugh on topic Lathe Macros
In the [RS274NGC] section of the INI file make sure that ./ appears in the SUBROUTINE_PATH
It should look something like:
It should look something like:
[RS274NGC]
...
SUBROUTINE_PATH = ~/nc_files/gladevcp_lib:./Please Log in or Create an account to join the conversation.
03 Jun 2016 17:46 #75452
by RotarySMP
Replied by RotarySMP on topic Lathe Macros
Thanks for the prompt response Andy. That was it.
Mark
Mark
Please Log in or Create an account to join the conversation.
03 Jun 2016 19:12 #75457
by RotarySMP
Replied by RotarySMP on topic Lathe Macros
Just playing around with it, I noticed the following feature.
When you set the macro parameters and hit go, the pop up wndow for the tool change appears. At that point, rather than aknowledging the tool change, I clicked on the Preview tab. Result was the pop up window disappearing into the background, but still being active, so nothing else could be done till I minimised axis and aknowledge the pop up.
I tried a simple turning cycle. in G18, started at X30 Z10. Set the macro for a shaft diameter of 20, 1.5mm per pass, cut to Z-10.
At the end, the lathe ends up at G17 X50.4? Is this due to the retract logic?
Is there any way to use the back plotter with the macros?
Mark
When you set the macro parameters and hit go, the pop up wndow for the tool change appears. At that point, rather than aknowledging the tool change, I clicked on the Preview tab. Result was the pop up window disappearing into the background, but still being active, so nothing else could be done till I minimised axis and aknowledge the pop up.
I tried a simple turning cycle. in G18, started at X30 Z10. Set the macro for a shaft diameter of 20, 1.5mm per pass, cut to Z-10.
At the end, the lathe ends up at G17 X50.4? Is this due to the retract logic?
Is there any way to use the back plotter with the macros?
Mark
Please Log in or Create an account to join the conversation.
03 Jun 2016 19:30 #75460
by andypugh
Typically I use the "load tool" button to tell the machine which tool is loaded (the button is an M61 command).
Replied by andypugh on topic Lathe Macros
You should be able to get the dialog to the top by clicking its button in the task bar.When you set the macro parameters and hit go, the pop up wndow for the tool change appears. At that point, rather than aknowledging the tool change, I clicked on the Preview tab. Result was the pop up window disappearing into the background, but still being active, so nothing else could be done till I minimised axis and aknowledge the pop up.
Typically I use the "load tool" button to tell the machine which tool is loaded (the button is an M61 command).
No, the tool should end at the programmed diameter (or length for facing). This is to make touching-off easier. (ie, you just need to enter the measured dimension). Is it possible that you have an offset active, or something is a bit awry in the tool table?I tried a simple turning cycle. in G18, started at X30 Z10. Set the macro for a shaft diameter of 20, 1.5mm per pass, cut to Z-10.
At the end, the lathe ends up at G17 X50.4? Is this due to the retract logic?
Sadly not, the G-code is not really loaded in the normal way.Is there any way to use the back plotter with the macros?
Please Log in or Create an account to join the conversation.
03 Jun 2016 20:01 #75464
by RotarySMP
Replied by RotarySMP on topic Lathe Macros
Good point, I am just playing around with a sample config, so the sample tool table might have some offsets in it.
I zeroed everything in the tool table for tool 1 and 2 (except type 2 RH turning tool.
Still start diameter X30 (G8 mode)
1.5mm cuts, end diameter 20mm, Z-10
Are the numbers top LH in your turning window a DRO?, the only move is to D50.8, Z-10. Then it stops, but with the program run - Paused state, displaying -10DTG.
Only hint I can see is that I had set F200, the macro set F0.1
I zeroed everything in the tool table for tool 1 and 2 (except type 2 RH turning tool.
Still start diameter X30 (G8 mode)
1.5mm cuts, end diameter 20mm, Z-10
Are the numbers top LH in your turning window a DRO?, the only move is to D50.8, Z-10. Then it stops, but with the program run - Paused state, displaying -10DTG.
Only hint I can see is that I had set F200, the macro set F0.1
Please Log in or Create an account to join the conversation.
03 Jun 2016 20:28 #75466
by andypugh
Replied by andypugh on topic Lathe Macros
It will be waiting for the spindle to start, probably. All the macros run CSS and feed-per rev mode.
Please Log in or Create an account to join the conversation.
Time to create page: 0.117 seconds