Need testers for gmoccapy_5_axis

I have had some time to get everything reloaded from "linuxcnc-dev "and the "checkout gmoccapy_5_axis" from the links supplied. When I load my INI and HAL files with axis 5 items commented out it appears the load and run just fine. When I run a identical set of files with axis 5 items uncommented I get a error that there is s problem enabling axis 5 in gmoccapy.

The two sets of files are the same files I used before on the 5 axis version several weeks ago and worked fine. When gmoccapy tries to run on 5 axis it appears to get in a loop and sluggishly starts displaying its screen partially at times if I wait long enough. When it does show its screen on occasion Axis 4 and 5 dro's are side by side instead of one being below the other. One dro window is split into two parts (left being A and right being U). gmoccapy version 2.0.0 is installed.

hm2/hm2_7i80.0: registered
cant resolve path to 'cant resolve path to '''
emcTrajSetAxes failing: axes=5 axismask=4f
Invalid on color value: greeen
/home/john/cnc-source/linuxcnc-dev/bin/gmoccapy:153: RuntimeWarning: missing handler 'on_btn_load_state_changed'
self.builder.connect_signals( self )
**** GMOCCAPY GETINIINFO ****

When I ran it 10 minutes later after terminating the program.

hm2/hm2_7i80.0: registered
emcTrajSetAxes failing: axes=5 axismask=4f
emcTrajSetAxes failing: axes=5 axismask=4f
Waiting for component 'inihal' to become ready.emcTrajSetAxes failing: axes=5 axismask=4f
..........emcTrajSetAxes failing: axes=5 axismask=4f
..........emcTrajSetAxes failing: axes=5 axismask=4f
..........emcTrajSetAxes failing: axes=5 axismask=4f
..........emcTrajSetAxes failing: axes=5 axismask=4f
..........emcTrajSetAxes failing: axes=5 axismask=4f
..........emcTrajSetAxes failing: axes=5 axismask=4f
..........emcTrajSetAxes failing: axes=5 axismask=4f
..........emc/task/emctaskmain.cc 2986: can't initialize motion
HAL: ERROR: exit called before init
<commandline>:0: waitpid failed milltask inihal
<commandline>:0: milltask exited without becoming ready
Shutting down and cleaning up LinuxCNC...
hm2_eth: HostMot2 ethernet driver unloaded
hm2: unloading
Note: Using POSIX realtime

Hallo fairngs,

The error
emcTrajSetAxes failing: axes=5 axismask=4f
seems not to come from gmoccapy, I am pretty sure, it is your config, please post your configs, so we will be able to try to reproduce the error.

The gmoccapy 5_axis version has axis 4 and 5 side by side, I made that to save some place. Are you sure you had a 5 axis version with the dros placed one under the other? If so, that was a very early development release!

Norbert

Yes before I had the dros below each other. This was with a manual insertion of the modified and commented file for gmoccapy5 that I pulled of the raw file from the repository. I used it as gmoccapy and gmocappy.py. That complete installation has been removed.

My current 5 axis .ini file and .hal file are attached. I still need to add a tool length routine, probing and some spindle functions.

I was not really getting anywhere so I decided to remove all files associated with linuxcnc from my computer since I suspect it was potentially mixing different versions of linuxcnc and thus also gmoccapy. I down loaded the development version again using: "git clone git://git.linuxcnc.org/git/linuxcnc.git linuxcnc-dev" and linked it with "git checkout gmoccapy_5_axis". It compiled with some warnings but completed.

When the compile and rip-environment were finished I ran linuxcnc and it started and I was able the see the new tree menu and selected gmoccapy_XYZAB. It started as "v2.7" and ran but before finishing it failed. What is strange is that when I ran linuxcnc again with the cmd "linuxcnc" in the same 'linuxcnc-dev" folder it started to load as "v2.8" and changed the menu tree in debian jessie to the 2.8 version one. No gmoccapy_XYZAB being possible anymore. Presently I have version 2.8 just parked in a folder downloaded from the jepler repository as a zip file and it has not been compiled. I had removed all linuxcnc files with nautilus while it was running in su mode after its search for linuxcnc files was completed.

Some where there must be a file that is causing this. Perhaps the Debian jessie menu tree retained some info even when there was no visible cnc folder present it its tree. But why would it list a change in versions? I will try the "make install-menus " cmd from the "linuxcnc-dev/src" folder to see if that clears this problem.

Here is the first part of the log from the first start and the second start showing changes in linuxcnc versions during two closely timed program starts from the same directory. A file is attached separately for the first start that is more complete.

First start:
john@cnc1:~/cnc-source/linuxcnc-dev/src$ sudo make setuid
[sudo] password for john:
chown root ../bin/rtapi_app
chmod 4750 ../bin/rtapi_app
john@cnc1:~/cnc-source/linuxcnc-dev/src$ cd ..
john@cnc1:~/cnc-source/linuxcnc-dev$ . ./scripts/rip-environment
john@cnc1:~/cnc-source/linuxcnc-dev$ linuxcnc
LINUXCNC - 2.7.0
Machine configuration directory is '/home/john/cnc-source/linuxcnc-dev/configs/sim/gmoccapy'
Machine configuration file is 'gmoccapy_XYZAB.ini'
Starting LinuxCNC...
Found file(REL): ./core_sim_XYZAB.hal
Note: Using POSIX realtime

Second start:
it pulled up this
john@cnc1:~/cnc-source/linuxcnc-dev$ linuxcnc
LINUXCNC - 2.8.0-pre1-1289-g5f9f789

My last idea using "make install-menus " did nothing for me. I decided just to let my present configuration run and have it copy the "gmoccapy_tool_sensor" sim to my desk top and it ran fine from there. It only has three axis. I copied my 5 axis configure files folder into the "/home/john/linuxcnc/configs/" folder and selected it to run from the menu tree. The overall result is listed below. The mention of "Invalid on color value: Green" mentioned below is likely due to file mismatch and data going into the wrong place within gmoccapy during the process handoff due improper version of the gmocappy file that was automatically installed in /usr/bin/.

hm2/hm2_7i80.0: IO Pin 071 (P3-47): IOPort
hm2/hm2_7i80.0: registered
None <<<<<<
Invalid on color value: Green
/usr/bin/gmoccapy:153: RuntimeWarning: missing handler 'on_btn_load_state_changed'
self.builder.connect_signals( self )
/usr/bin/gmoccapy:153: RuntimeWarning: missing handler 'on_gremlin_button_press_event'
self.builder.connect_signals( self )
**** GMOCCAPY GETINIINFO ****
Preference file path: /home/john/linuxcnc/configs/cnc1/cnc1.pref
**** GMOCCAPY ERROR : ******** gmoccapy can only handle 4 axis, ****
**** but you have given 5 through your INI file ****
**** gmoccapy will not start ****

Now in looking at the gmoccapy file in /usr/bin/ it only installed the 4 axis version as show below. I imagine that I will have to manually change this and the .py version of this file at various locations to the 5 axis version. I think that the .glade file may also need to be changed in various locations. From my research these were the files with the most recent changes besides the documentation.

self.axisnumber_four = "" # we use this to get the number of the 4-th axis
self.axisletter_four = None # we use this to get the letter of the 4-th axis
self.hide_axis_4 = False # will hold if the 4'th axis should be hidden

The "gmocappy.py" file in /home/john/cnc-source/linuxcnc-dev/src/emc/usr_intf/gmoccapy/
does appear to be the correct 5 axis version as shown below.

self.dro_size = 28 # The size of the DRO, user may want them bigger on bigger screen
self.axisnumber_four = "" # we use this to get the number of the 4-th axis
self.axisletter_four = None # we use this to get the letter of the 4-th axis
self.axisnumber_five = "" # we use this to get the number of the 5-th axis
self.axisletter_five = None # we use this to get the letter of the 5-th axis
self.hide_axis_4 = False # will hold if the 4'th axis should be hidden

There has to be a reason for this installation error. I don't know what to look for in a simple way to check if the ,glade file is proper in all its locations.

I have duplicated the change in my configration from v2.7 to v2.8 with no v2.8 presently installed. As soon as I open the linuxcnc configuration selector in the jessie desktop application pulldown it calls up a old v.28 configuration and loads that on the next startup of v2.7. This is without selecting anything in the pull down menu that was installed during a prior install of v2.8.

It loaded this three times with sim gmoccapy 5 axis configures but errors caused it to terminate part way during the runs.

john@cnc1:~/cnc-source/linuxcnc-dev$ linuxcnc
LINUXCNC - 2.7.0
Machine configuration directory is '/home/john/cnc-source/linuxcnc-dev/configs/sim/gmoccapy'
Machine configuration file is 'gmoccapy_XYZAB.ini'
Starting LinuxCNC...
Found file(REL): ./core_sim_XYZAB.hal
Note: Using POSIX realtime

Once I opened the Linuxcnc Configuration selector without selecting anything it changed the load to:
john@cnc1:~/cnc-source/linuxcnc-dev$ linuxcnc
LINUXCNC - 2.8.0-pre1-1295-g58ab506


Once it opens with the above and being pointed to the config ini file in the linuxcnc-dev configure folder I get this:

ohn@cnc1:~/cnc-source/linuxcnc-dev$ linuxcnc /home/john/cnc-source/linuxcnc-dev/configs/sim/gmoccapy/gmoccapy_XYZCW.ini
LINUXCNC - 2.8.0-pre1-1295-g58ab506
Machine configuration directory is '/home/john/cnc-source/linuxcnc-dev/configs/sim/gmoccapy'
Machine configuration file is 'gmoccapy_XYZCW.ini'
Starting LinuxCNC...
Found file(REL): ./core_sim_XYZCW.hal
Note: Using POSIX realtime
Found file(REL): ./spindle_sim.hal
Found file(lib): /usr/share/linuxcnc/hallib/simulated_home.hal
None <<<<<<
Invalid on color value: greeen
/usr/bin/gmoccapy:153: RuntimeWarning: missing handler 'on_btn_load_state_changed'
self.builder.connect_signals( self )
/usr/bin/gmoccapy:153: RuntimeWarning: missing handler 'on_gremlin_button_press_event'
self.builder.connect_signals( self )
**** GMOCCAPY GETINIINFO ****
Preference file path: /home/john/cnc-source/linuxcnc-dev/configs/sim/gmoccapy/gmoccapy_XYZAB.pref
No option 'dro_size' in section: 'DEFAULT'
**** GMOCCAPY ERROR : ******** gmoccapy can only handle 4 axis, ****
**** but you have given 5 through your INI file ****
**** gmoccapy will not start ****

It appears that the above loads some old gmoppay files into vital locations from prior memory. It seems logical to assume that old items hanging on in the system are preventing a good install. I think that the culprid is likely the menu configure process due to it saving old unwanted configuration data with no apparent way to purge it. Does this only occur in Debian jessie?