- Posts: 101
- Thank you received: 0
LinuxCNC Features - a kind of NGCGUI
-Tom
ps: should add that I am running 2.7.0~pre6
Please Log in to join the conversation.
GLADEVCP = -U --catalog=catalogs/lathe.xml features.ui
Please Log in to join the conversation.
To use it stand alone, you can open a terminal in features directory and type : ./features.py --catalog=catalogs/lathe.xml
You must first make sure that linuxCNC is configured OK for "PROGRAM_PREFIX" and "SUBROUTINE_PATH"
If you plan to always use lathe.xml you can make it the default catalog by changing features.py at line 359
Change
self.catalog_src = "catalogs/mill.xml"
for
self.catalog_src = "catalogs/lathe.xml"
This version does not use a menu and most features in lathe option use milldraw.py. I was never able to make it run neither in my home or work computers. Also there is not much error message, so you do not know much why it is not working. Watch carefully what prints in the terminal window. My lathe is not converted to CNC but I may try to make good ini and ngc files after I release my update for linuncnc-features which is almost a complete rewrite.
Also make sure your mouse double click is set at about 600ms
Good luck
Fern
Please Log in to join the conversation.
FernV wrote: Hi Tom
To use it stand alone, you can open a terminal in features directory and type : ./features.py --catalog=catalogs/lathe.xml
You must first make sure that linuxCNC is configured OK for "PROGRAM_PREFIX" and "SUBROUTINE_PATH"
If you plan to always use lathe.xml you can make it the default catalog by changing features.py at line 359
Change
self.catalog_src = "catalogs/mill.xml"
for
self.catalog_src = "catalogs/lathe.xml"
This version does not use a menu and most features in lathe option use milldraw.py. I was never able to make it run neither in my home or work computers. Also there is not much error message, so you do not know much why it is not working. Watch carefully what prints in the terminal window. My lathe is not converted to CNC but I may try to make good ini and ngc files after I release my update for linuncnc-features which is almost a complete rewrite.
Also make sure your mouse double click is set at about 600ms
Good luck
Fern
Thanks Fern (and Nick)! What should "PROGRAM_PREFIX" and "SUBROUTINE_PATH" be set to? Also I noticed that ../catalogs/lathe.xml is empty (just has a single line in it). Is that normal? I don't know why, I just git cloned the branch but it doesn't look anything like the mill.xml file.... Oh, and how do I set my mouse click speed?
Is your rewrite going to do lathe and mill? Or are you just rewriting the lathe portion?
-Tom
ps: These are the errors I get when I start features.py I set line 359 to point to lathe.xml and I now see the lathe features. The last set of lines was generated when I clicked the refresh button...
Please Log in to join the conversation.
"PROGRAM_PREFIX" should point to the directory that linuxCNC selects when you want to open a file. This is where 'features.ngc' is saved usually when you press on 'Refresh' or it auto-refreshes.
"SUBROUTINE_PATH" should point to the directory where are all required files (*.ngc usually) to execute your lathe job (features.ngc) In your case it should be : '/home/tom/linuxcnc-features/subroutines'. You could have more than 1 path by separating them with ':'.
Those values are stored in '/home/tom/linuxcnc/configs/EMCOturn120p-glade/EMCOturn120pGlade.ini' in your case. It you cannot see them, please post this file so I can help
How do you set your mouse click speed? It is a mouse property you set in the system when you setup the computer. Debian Wheezy had it in the beginning at ~200ms and nothing happenned then when double clicking until I set to ~450ms then later at ~600ms
What is the web address where you git cloned linuxcnc-features?
What I rewrote is the application. I started editing to debug, then added so many options and modified the code so much that Nick will have a hard time to find himself in it. But it is really based on his work.
Is it mill or lathe ? It only depends in the *.ini files that it loads. Linuxcnc-features is just an 'assembler' of what you write in those ini files.
When you read your result in the terminal window, you see that there are still many bugs and the last line shows you why it stopped. I remember I had this message in the beginning but I solved it and I do not remember how. I will see what I can do for you if I can not publish in the next few days.
Regards,
Fern
Please Log in to join the conversation.
FernV wrote: What is the web address where you git cloned linuxcnc-features?
I got the branch from here: github.com/cnc-club/linuxcnc-features
FernV wrote: I will see what I can do for you if I can not publish in the next few days.
Thanks Fern! I look forward to trying out your modifications.
-Tom
Please Log in to join the conversation.
You can now download and test a new advanced version of Linuxcnc-features at
fernv.github.io/linuxcnc-features
Just follow the instruction to use stand alone.
Please report here if you have problems using it.
Some screen shots (stand alone)
Attachment not found
Attachment not found
Attachment not found
Embedded
Attachment not found
Best regards
Fern
Please Log in to join the conversation.
I loaded the new stuff into a Gmoccapy sim and the features did not load. You posted a features_gmoccapy.glade file earlier. Is this still the file to use for gmoccapy?
Regards
Marius
www.bluearccnc.com
Please Log in to join the conversation.
So far I have not found the way to make gmoccapy load a file
I did not have good results with gmoccapy. I postponed the task for a latter date. For now I want to make Features the best it can be and it works well with axis
I have never heard of a features_gmoccapy.glade file before. If I can put my hand on something that works, I will include it.
Please test with axis and comment
Regards
Fern
Please Log in to join the conversation.
Just for completeness here is the error and the glade file.
Attachment not found
Regards
Marius
www.bluearccnc.com
Please Log in to join the conversation.
