Annoncing gmoccapy 3.0
10 Feb 2019 12:43 #126139
by Erikcnc
Replied by Erikcnc on topic Annoncing gmoccapy 3.0
I just download the files.
Try to install it my self allso for my new lathe.
There is a file in docs with a installation guide if i'm not wrong.
Try to install it my self allso for my new lathe.
There is a file in docs with a installation guide if i'm not wrong.
Please Log in or Create an account to join the conversation.
24 Feb 2019 13:24 #127053
by newbynobi
Replied by newbynobi on topic Annoncing gmoccapy 3.0
No, no installation doc, as you will need to run it rip-environment.
Just get the mentioned branch and compile as usual.
Norbert
Just get the mentioned branch and compile as usual.
Norbert
Please Log in or Create an account to join the conversation.
- my.cnc.brother
- Offline
- New Member
Less
More
- Posts: 12
- Thank you received: 25
24 Feb 2019 21:07 #127069
by my.cnc.brother
Replied by my.cnc.brother on topic Annoncing gmoccapy 3.0
Dear Norbert,
Refering to issue #330 github.com/LinuxCNC/linuxcnc/issues/330#issuecomment-367805969
I would like to ask if 3.0 has already fixed correct pocket handling?
Right now I am reproducing behaviour exactly as described by you. Pocket number is equal to index line of my tooltable file instead P value. Thus operation of my non-random ATC is very limited and cumbersome. I have 10 pockets but would like to use much more tool than 10.
Glad for your comment.
Refering to issue #330 github.com/LinuxCNC/linuxcnc/issues/330#issuecomment-367805969
I would like to ask if 3.0 has already fixed correct pocket handling?
Right now I am reproducing behaviour exactly as described by you. Pocket number is equal to index line of my tooltable file instead P value. Thus operation of my non-random ATC is very limited and cumbersome. I have 10 pockets but would like to use much more tool than 10.
Glad for your comment.
Please Log in or Create an account to join the conversation.
02 Mar 2019 13:29 #127491
by newbynobi
Replied by newbynobi on topic Annoncing gmoccapy 3.0
Sorry, also gmoccapy3.0 will not solve that very, very old bug. It is not related to the GUI, but to the very strange way to handle tools and pockets. I am testing some code, Rene-Dev made, but there is still a way to go to solve this one.
Norbert
Norbert
Please Log in or Create an account to join the conversation.
- nigel-tufnel
- Offline
- Junior Member
Less
More
- Posts: 35
- Thank you received: 0
11 Mar 2019 17:01 #128355
by nigel-tufnel
Replied by nigel-tufnel on topic Annoncing gmoccapy 3.0
Quick question - if used for an XYZ application, are the jog buttons, dro's, etc shown for the additional axes (A, B, etc)? Is there a way to turn off unused axis buttons to reduce clutter? Thanks
Please Log in or Create an account to join the conversation.
11 Mar 2019 18:16 #128364
by newbynobi
Replied by newbynobi on topic Annoncing gmoccapy 3.0
gmoccapy_3.0 gets the axis from [TRAJ] COORDINATES
For all the AXIS Letters in that entry it will display DRO and jog button, etc.
So if you find a way to not enter the unused axis in that entry, they will not be displayed.
Norbert
For all the AXIS Letters in that entry it will display DRO and jog button, etc.
So if you find a way to not enter the unused axis in that entry, they will not be displayed.
Norbert
Please Log in or Create an account to join the conversation.
11 Mar 2019 19:33 #128375
by newbynobi
Replied by newbynobi on topic Annoncing gmoccapy 3.0
I pushed some minor changes and a very small bug has been solved.
If I do not get negative information, I will push this branch to master in a few days.
So please test that brunch, I made all test I could and from my part it is fine to be merged.
Norbert
If I do not get negative information, I will push this branch to master in a few days.
So please test that brunch, I made all test I could and from my part it is fine to be merged.
Norbert
Please Log in or Create an account to join the conversation.
- Mike_Eitel
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
11 Mar 2019 21:34 #128383
by Mike_Eitel
Replied by Mike_Eitel on topic Annoncing gmoccapy 3.0
Hi Norbert
After you pushed:
If I do nothing but a normal upgrade of LCNC. What will happen?
My version 2 changed to the new 3 and all is done and running?
Or do I have to load manually plus make some modifications of my code?
Mike
After you pushed:
If I do nothing but a normal upgrade of LCNC. What will happen?
My version 2 changed to the new 3 and all is done and running?
Or do I have to load manually plus make some modifications of my code?
Mike
Please Log in or Create an account to join the conversation.
12 Mar 2019 17:14 #128453
by newbynobi
Replied by newbynobi on topic Annoncing gmoccapy 3.0
Yes, you will not even feel the change, except you use a rotary axis.
You may feel a speed increase in gui reaction, as i cleaned up some stuff.
So screen 2 is not availible any more and also the additional DRO button are gone.
Most useres should not get any problem after an update.
Norbert
You may feel a speed increase in gui reaction, as i cleaned up some stuff.
So screen 2 is not availible any more and also the additional DRO button are gone.
Most useres should not get any problem after an update.
Norbert
The following user(s) said Thank You: HalaszAttila
Please Log in or Create an account to join the conversation.
- Mike_Eitel
- Offline
- Platinum Member
Less
More
- Posts: 1150
- Thank you received: 184
12 Mar 2019 18:59 #128464
by Mike_Eitel
Replied by Mike_Eitel on topic Annoncing gmoccapy 3.0
I'm looking forward;-)
Please Log in or Create an account to join the conversation.
Time to create page: 0.087 seconds