Gmoccapy - A new screen for linuxcnc
25 Dec 2013 14:36 #42000
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Hi Jim
There is a button on the bottom towards the right hand side that is used to maximize the preview display area. If you press that you will see the whole lot.
If you look at the ngc stuff you will see that there is a header file that is either metric or imperial. You have to setup the ngc to use the correct header file.
There is a button on the bottom towards the right hand side that is used to maximize the preview display area. If you press that you will see the whole lot.
If you look at the ngc stuff you will see that there is a header file that is either metric or imperial. You have to setup the ngc to use the correct header file.
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
26 Dec 2013 02:01 #42004
by jbunch
Replied by jbunch on topic Gmoccapy - A new screen for linuxcnc
Marius,
That is not the problem.
The problem has to do with the popup keypad for editing (pyngcgui_popupkeyboard.ui).
When gmoccapy is in full screen mode if you hit outside the keypad area linux moves the
keypad behind gmoccapy. and you can no longer access it.
Also if you use (pyngcgui.ui) without the popup keyboard the keypad on your keyboard
does not work so you have no way to enter data into the fields. You get an error in the terminal window
that that key has not been implemented yet.
Jim
That is not the problem.
The problem has to do with the popup keypad for editing (pyngcgui_popupkeyboard.ui).
When gmoccapy is in full screen mode if you hit outside the keypad area linux moves the
keypad behind gmoccapy. and you can no longer access it.
Also if you use (pyngcgui.ui) without the popup keyboard the keypad on your keyboard
does not work so you have no way to enter data into the fields. You get an error in the terminal window
that that key has not been implemented yet.
Jim
Please Log in or Create an account to join the conversation.
26 Dec 2013 04:50 #42008
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Jim
I found that problem a long time ago when I first tested pyngcgui. I was under the impression that it was fixed. The keypad is supposed to keep focus until closed.
I am busy implementing Gmoccapy with pyngcgui on my desktop router. I will test it soon as I want to implement a tool change macro.
Can I suggest that you report your problem on the pyngcgui thread. It might help to get it fixed soon.
I found that problem a long time ago when I first tested pyngcgui. I was under the impression that it was fixed. The keypad is supposed to keep focus until closed.
I am busy implementing Gmoccapy with pyngcgui on my desktop router. I will test it soon as I want to implement a tool change macro.
Can I suggest that you report your problem on the pyngcgui thread. It might help to get it fixed soon.
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
26 Dec 2013 15:59 #42024
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Norbert
I seem to have a problem loading any macro file. It works in the sim config but not in any of my live configs.
I tried it on my new desktop mill as well as the plasma config. The error says
I seem to have a problem loading any macro file. It works in the sim config but not in any of my live configs.
I tried it on my new desktop mill as well as the plasma config. The error says
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
27 Dec 2013 02:47 #42039
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Hallo Jim,
I see the problem! It is because you have activated keyboard usage. Please go to the settings page to the hardware tab and see what says keyboard usage, if you uncheck that one, you will be able to enter values.
Pyngcgui is not my work, and as I am going to include a much more profesional gcode generator (Rene is doing that one), I will not invest any work on pyngcgui. I hope to be able to show first results in summer 2014.
Norbert
I see the problem! It is because you have activated keyboard usage. Please go to the settings page to the hardware tab and see what says keyboard usage, if you uncheck that one, you will be able to enter values.
Pyngcgui is not my work, and as I am going to include a much more profesional gcode generator (Rene is doing that one), I will not invest any work on pyngcgui. I hope to be able to show first results in summer 2014.
Norbert
Please Log in or Create an account to join the conversation.
27 Dec 2013 02:50 #42040
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Halo Marius,
have you checked, that there is a file called "helo_world.ngc" in the mentioned folder?
It seems you did not copy the macros folder to your config or your subroutine path from INI point to somewhere else.
Norbert
have you checked, that there is a file called "helo_world.ngc" in the mentioned folder?
It seems you did not copy the macros folder to your config or your subroutine path from INI point to somewhere else.
Norbert
Please Log in or Create an account to join the conversation.
27 Dec 2013 03:59 #42042
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Hi Norbert
As you can see from the picture, the path is set correctly. The macros directory is under my config directory and the files are in there. I have created some of my own files as well. It does not see anything.
Out of desperation I started to write some subs to use with V buttons but I would rather use the macros if I could.
I have set the path up any way possible but it still does not pick up the files.
As you can see from the picture, the path is set correctly. The macros directory is under my config directory and the files are in there. I have created some of my own files as well. It does not see anything.
Out of desperation I started to write some subs to use with V buttons but I would rather use the macros if I could.
I have set the path up any way possible but it still does not pick up the files.
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
27 Dec 2013 04:39 - 27 Dec 2013 04:40 #42043
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Hallo Marius,
check:
- What is in your [MACRO] section?
- What is under [RS274NGC] ; SUBROUTINE_PATH
- What files are in that path?
- do the files fit the following needs?
The name of the file must be exactly the same as the name given in the MACRO line.
So the macro i_am_lost will call the file i_am_lost.ngc.
The macro files must follow some rules:
- the name of the file need to be the same as the name mentioned in the macro line, just with the ngc extension
- The file must contain a subroutine like so: O<i_am_lost> sub, where the name of the sub must match exactly the name of the macro (case sensitive)
- the file must end with an endsub command O<i_am_lost> endsub followed by an M2 command
- the files need to be placed in a folder specified in your INI file in the RS274NGC section (see [RS274NGC]:
I tested that just now on my test machine, and it does work fine.
Norbert
check:
- What is in your [MACRO] section?
- What is under [RS274NGC] ; SUBROUTINE_PATH
- What files are in that path?
- do the files fit the following needs?
The name of the file must be exactly the same as the name given in the MACRO line.
So the macro i_am_lost will call the file i_am_lost.ngc.
The macro files must follow some rules:
- the name of the file need to be the same as the name mentioned in the macro line, just with the ngc extension
- The file must contain a subroutine like so: O<i_am_lost> sub, where the name of the sub must match exactly the name of the macro (case sensitive)
- the file must end with an endsub command O<i_am_lost> endsub followed by an M2 command
- the files need to be placed in a folder specified in your INI file in the RS274NGC section (see [RS274NGC]:
I tested that just now on my test machine, and it does work fine.
Norbert
Last edit: 27 Dec 2013 04:40 by newbynobi.
Please Log in or Create an account to join the conversation.
27 Dec 2013 04:49 #42044
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic Gmoccapy - A new screen for linuxcnc
Norbert
# for details see nc_files/subroutines/maco_instructions.txt
[MACROS]
MACRO = goto_tc
MACRO = halo_world
MACRO = jog_around
MACRO = increment xinc yinc
MACRO = go_to_position X-pos Y-pos Z-pos
MACRO = set_tc
SUBROUTINE_PATH = home/marius/dev/bluearc/configs/bluearc_plasma/macros
As you can see I am using the original files to test with.
- What is in your [MACRO] section?
# for details see nc_files/subroutines/maco_instructions.txt
[MACROS]
MACRO = goto_tc
MACRO = halo_world
MACRO = jog_around
MACRO = increment xinc yinc
MACRO = go_to_position X-pos Y-pos Z-pos
MACRO = set_tc
- What is under [RS274NGC] ; SUBROUTINE_PATH
SUBROUTINE_PATH = home/marius/dev/bluearc/configs/bluearc_plasma/macros
- What files are in that path?
As you can see I am using the original files to test with.
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
27 Dec 2013 05:20 #42046
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Hallo Marius,
I do think the problem is you path:
Try:
SUBROUTINE_PATH = ~/dev/bluearc/configs/bluearc_plasma/macros
or even better try relative path like:
SUBROUTINE_PATH = macros
if your ini file is under: configs/bluearc_plasma/
Norbert
I do think the problem is you path:
Try:
SUBROUTINE_PATH = ~/dev/bluearc/configs/bluearc_plasma/macros
or even better try relative path like:
SUBROUTINE_PATH = macros
if your ini file is under: configs/bluearc_plasma/
Norbert
Please Log in or Create an account to join the conversation.
Time to create page: 0.330 seconds