gmoccapy 2.1.0 has been released

More
01 Sep 2016 13:03 - 01 Sep 2016 13:05 #79828 by tarasko

This ??

3. How to update gmoccapy

3.1. For users
Just do an update using your deb package tool like synaptic.


Well as user you'll get new gmocappy 2.1.0 when linuxcnc 2.8.0 will be released. Current release version is 2.7.6 and it doesn't include new gmocappy. So as user you'll need to wait some time when linuxcncn 2.8.0 will be releaed (I don't know release schedule)

So you need to use 'For developers' way. Manually compile master branch and use compiled version of linuxcnc
Last edit: 01 Sep 2016 13:05 by tarasko.
The following user(s) said Thank You: dinkata

Please Log in or Create an account to join the conversation.

More
01 Sep 2016 18:30 - 01 Sep 2016 19:14 #79862 by newbynobi

I want to report a few bugs.

1. Spindle speed is reporting 0 when I'm running a g-code program with command 's12000 m3'
2. Transition from AUTO -> MDI doesn't work when I'm pressing F3 key after program finish.


To item 1: Did you connect the corresponding gmoccapy hal pin in your postgui hal file?
I understand you are referring to the feedback bar, or do you thing the active gcode?
I see, the label besides the 100 % button is not updated as expected, I will check that.
I have an idea, but no time actually, so please stay tuned;-)

To item 2: I checked that, after running a program, pressing F3 brings me back to manual, and pressing F5 to MDI mode, so here everything is fine.

Norbert
Last edit: 01 Sep 2016 19:14 by newbynobi.

Please Log in or Create an account to join the conversation.

More
01 Sep 2016 18:39 #79864 by newbynobi
@All

There is ctually no documentation for gmoccapy 2.1.0 !!!

And please do not use the WIKI, It is not up to date:

For 2.7.6 branch the documentation is here:
gmoccapy documentation for 2.7

Master is on this page:
gmoccapy documentation for master
but I have not updated the master stuff to be actual with gmoccapy 2.1.xx

If you use master branch, be aware, that that one is the developers branch, you should know how to compile stuff and how to fix small hal issues, as in that branch a change may happen changing names or complete behavior!!

If you want to use that please do:
sudo apt-get install git-core gitk git-gui
git config --global user.name "Your full name"
git config --global user.email "you@example.com"
git clone git://git.linuxcnc.org/git/linuxcnc.git linuxcnc-dev
sudo apt-get install libboost-python1.49-dev libmodbus-dev libusb-1.0-0-dev libxmu-dev libglu1-mesa-dev libgl1-mesa-dev libreadline-dev tcl8.5-dev tk8.5-dev  
cd linuxcnc-dev
cd src
./autogen.sh
./configure
make
sudo make setuid
cd ..
. ./scripts/rip-environment
linuxcnc

Norbert

Please Log in or Create an account to join the conversation.

More
01 Sep 2016 19:19 #79865 by tarasko

To item 1: Did you connect the corresponding gmoccapy hal pin in your postgui hal file?

Well no. In gmocappy of linuxcnc 2.6.7 all works out of the box.

I understand you are referring to the feedback bar, or do you thing the active gcode?

Feedback bar works properly when I manually increase/decrease spindle speed, but If I call
the MDI command like 's6000m3' feedback bar shows '0'

Please Log in or Create an account to join the conversation.

More
01 Sep 2016 19:32 #79867 by newbynobi
Please check the hal connections, as some hal pin names has been renamed!

I just pushed the fix to update the label besides the 100 % spindle button.

Feedback bar should work, if you have the feedback pins connected.
Please test with sim config and report steps to reproduce the error.

Norbert
The following user(s) said Thank You: tarasko

Please Log in or Create an account to join the conversation.

More
01 Sep 2016 20:30 - 01 Sep 2016 20:37 #79877 by tarasko
I verified on latest master, all works like charm!

Please check the hal connections, as some hal pin names has been renamed!

I didn't change any configuration files. Besides in my custom_postgui.hal file there are no any gmocappy pin connections

Please test with sim config and report steps to reproduce the error.
Norbert

I verified on my real harware config.

Thanks.

Back to other little bug. "Shorctuts mode switching problem"

Reproduce steps:
1. Switch to the AUTO mode.
2. Switch to the MDI mode with 'F5' shortcut.
3. Switch back to the AUTO mode.
4. Switch againt to MDI mode with 'F5' ---> oops. It doesn't switch.
5. Switch to the MANUAL mode by F3.
6. goto step 1

Other little issue is labels on macro buttons, and their alignment.
As you can see on the attached picture. The macro names are not full.

full names are "1_measure_and_change", "2_tool_change", "3_tool_measure"
Attachments:
Last edit: 01 Sep 2016 20:37 by tarasko.

Please Log in or Create an account to join the conversation.

More
02 Sep 2016 08:14 - 02 Sep 2016 08:16 #79892 by dinkata

Well as user you'll get new gmocappy 2.1.0 when linuxcnc 2.8.0 will be released.

I update to 2.8 gmoccapy 2.1.2 a pleasant surprise ,
please note DRO axis Z remains in red after homing ..I use sim_hardware.hal .

Attachments:
Last edit: 02 Sep 2016 08:16 by dinkata.

Please Log in or Create an account to join the conversation.

More
03 Sep 2016 08:53 #79960 by newbynobi

Back to other little bug. "Shorctuts mode switching problem"

Reproduce steps:
1. Switch to the AUTO mode.
2. Switch to the MDI mode with 'F5' shortcut.
3. Switch back to the AUTO mode.
4. Switch againt to MDI mode with 'F5' ---> oops. It doesn't switch.
5. Switch to the MANUAL mode by F3.
6. goto step 1


Fixed with 2.1.3
it was caused, because we do record the last key event, to avoid that a action is excecuted several times with one push of the button. Now the button push event reset the key event and so it does work fine.

I also corrected another bug, Pressing F3 or F5 while running a program leaded to a short time of no reaction of the GUI.
Now a error message will be trhrown.

Norbert

Please Log in or Create an account to join the conversation.

More
03 Sep 2016 08:58 #79961 by newbynobi

Other little issue is labels on macro buttons, and their alignment.
As you can see on the attached picture. The macro names are not full.

full names are "1_measure_and_change", "2_tool_change", "3_tool_measure"


That is caused due to space reasons, I will check, if there is a possibility to line brake them automatically on the button.

Norbert
The following user(s) said Thank You: tarasko

Please Log in or Create an account to join the conversation.

More
03 Sep 2016 09:02 #79962 by newbynobi

I update to 2.8 gmoccapy 2.1.2 a pleasant surprise ,
please note DRO axis Z remains in red after homing ..I use sim_hardware.hal .


If the DRO does not get green, it is not homed. I am not able to reproduce that, because I do not know the content of sim_hardware.hal.
I am convinced, that the home switch of Z is not connected, or you did not home that joint.

Please try with configs/sim/gmoccapy/gmoccapy_lathe.ini

Norbert

Please Log in or Create an account to join the conversation.

Moderators: newbynobiHansU
Time to create page: 0.289 seconds
Powered by Kunena Forum