Work with probe

More
14 May 2015 20:13 - 14 May 2015 22:01 #58685 by verser
verser replied the topic: Work with probe

mariusl wrote: What is the other piece of software next to you probing stuff on your picture a couple of posts back?

This is Features for linuxcnc from Nick (cnc-club.ru) - construction of g-code directly from linuxcnc
Attachments:
Last Edit: 14 May 2015 22:01 by verser.
More
14 May 2015 20:20 - 14 May 2015 20:21 #58686 by verser
verser replied the topic: Work with probe

mariusl wrote: Hi
Gmoccapy loads with the probing stuff loaded in the usertab but when I run it the system goes to MDI mode and nothing further happens. Is there some other stuff that must be installed or not?

I'm a little touched up installation instructions.

Check at this part

1. .ini
...
[RS274NGC]

FEATURES=30
SUBROUTINE_PATH = your_subroutine_path
...

2. The following files from the archive placed in:
....
your-folder-configuration/your_subroutine_path
all from folder "macros"
...
Last Edit: 14 May 2015 20:21 by verser.
More
15 May 2015 00:07 #58694 by mariusl
mariusl replied the topic: Work with probe
I have those settings in the .ini file.
I see that your version of Gmoccapy is a bit old and not standard any more. Did you make a lot of changes to gmoccapy?
More
15 May 2015 01:12 #58698 by verser
verser replied the topic: Work with probe

mariusl wrote: I have those settings in the .ini file.
I see that your version of Gmoccapy is a bit old and not standard any more. Did you make a lot of changes to gmoccapy?

Just a bit old screenshot. No any changes to gmoccapy, only custom additional panels.
More
15 May 2015 01:17 #58699 by mariusl
mariusl replied the topic: Work with probe
I cannot get the code to work but something else might be the problem. I have Ngcgui loaded as well and for some reason when ngcgui is loaded the Gmoccapy cannot find any files that are in the macro directory. I have this on my lathe and on my mill.
I cannot get Andy's Lathemacro to work when I have ngcgui either.


Would you mind sharing how you got Nick's Features to load and work with Gmoccapy?
More
15 May 2015 02:01 - 15 May 2015 11:30 #58701 by verser
verser replied the topic: Work with probe

mariusl wrote: I
Would you mind sharing how you got Nick's Features to load and work with Gmoccapy?

My translation :) from this (for sim gmoccapy)

Installation:
features.zip unzip to ~/linuxcnc-dev/lib/python/gladevcp/
features_gmoccapy.zip unzip to ~/linuxcnc-dev/configs/sim/gmoccapy/
In file ~/linuxcnc-dev/configs/sim/gmoccapy/gmoccapy_4_axis.ini (or your-config.ini) in section [DISPLAY] add:
EMBED_TAB_NAME = features
EMBED_TAB_LOCATION = box_right
EMBED_TAB_COMMAND = gladevcp -x {XID} features_gmoccapy.glade
Do:
sudo apt-get install python-lxml 
cd /usr/lib/pymodules/python2.6/gladevcp
ln ~/linuxcnc-dev/lib/python/gladevcp/features.py -s
ln ~/linuxcnc-dev/lib/python/gladevcp/features.glade -s
ln ~/linuxcnc-dev/lib/python/gladevcp/subroutines -s
Insert in ~/linuxcnc-dev/lib/python/gladevcp/hal_pythonplugin.py, after "calculator" :
from features import Features
Insert in ~/linuxcnc-dev/lib/python/gladevcp/hal_python.xml
after first "calculator"
<glade-widget-class name="Features" generic-name="features" title="features">
        <properties>
            <property id="size" query="False" default="1" visible="False"/>
            <property id="spacing" query="False" default="0" visible="False"/>
            <property id="homogeneous" query="False" default="0" visible="False"/>
        </properties>
    </glade-widget-class>
after second "calculator":
<glade-widget-class-ref name="Features"/>

Then, update only folder ~/linuxcnc-dev/lib/python/gladevcp/subroutines from github

File Attachment:

File Name: features_gmoccapy.zip
File Size:1 KB


File Attachment:

File Name: features.zip
File Size:1,319 KB
Attachments:
Last Edit: 15 May 2015 11:30 by verser.
The following user(s) said Thank You: nilsht
More
17 May 2015 05:44 #58768 by elf
elf replied the topic: Work with probe
Inside circle routine isn't working for me. The first -X move is executing twice, once in the python code(line 975) and once in the macro xminus_in.ngc (line 10).

LinuxCNC version is 2.6.4.
The following user(s) said Thank You: verser
More
17 May 2015 12:28 #58773 by verser
verser replied the topic: Work with probe

elf wrote: Inside circle routine isn't working for me. The first -X move is executing twice, once in the python code(line 975) and once in the macro xminus_in.ngc (line 10).

This is bug. It's corrected. Thank you for accurate description.
More
17 May 2015 14:56 #58776 by elf
elf replied the topic: Work with probe
The updated code fixes the double move bug. There is another bug in the python code where the program assumes both probed positions have the same sign [line 1028: cxres=0.5*(xres+xres1)] Note: the docs don't say if the probed_position is relative or absolute: linuxcnc.org/docs/html/common/python-interface.html

The home position on my machine is in the center for all three axes so when the circle is centered on the home position, I'm getting wildly different results. When I move the circle to +X and +Y, the code works as expected.

A minor issue is xplus.ngc and yplus.ngc contain Z axis moves. I think these should be moved to the python code.
The following user(s) said Thank You: verser
More
17 May 2015 16:22 - 20 May 2015 14:24 #58779 by verser
verser replied the topic: Work with probe

elf wrote: The updated code fixes the double move bug. There is another bug in the python code where the program assumes both probed positions have the same sign [line 1028: cxres=0.5*(xres+xres1)] Note: the docs don't say if the probed_position is relative or absolute: linuxcnc.org/docs/html/common/python-interface.html

The home position on my machine is in the center for all three axes so when the circle is centered on the home position, I'm getting wildly different results. When I move the circle to +X and +Y, the code works as expected.


Screenshot in the header of this topic by the way shows the result of measurement of hole. We see that true equality "Xc"=0.5*("X+" + "X-"). In Probe Screen application probed_position matches with absolute coordinates . I do not quite understand why it is wrong.

elf wrote: A minor issue is xplus.ngc and yplus.ngc contain Z axis moves. I think these should be moved to the python code.


Now I think so too :)
Last Edit: 20 May 2015 14:24 by verser.
Moderators: Rick G
Time to create page: 0.113 seconds
Powered by Kunena Forum