Gmoccapy - A new screen for linuxcnc

More
11 years 7 months ago #56876 by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
NO_FORCE_HOMING has to be in the TRAJ section

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

More
11 years 7 months ago - 11 years 7 months ago #56878 by Clive S
Replied by Clive S on topic Gmoccapy - A new screen for linuxcnc

newbynobi wrote: NO_FORCE_HOMING has to be in the TRAJ section


Nobert

Thanks I will try that tomorrow and report back.

Edit Tested out Ok. cut my first part with the new screen :whistle:


Clive
Last edit: 11 years 7 months ago by Clive S. Reason: added text

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

More
11 years 7 months ago #57029 by jbunch
Replied by jbunch on topic Gmoccapy - A new screen for linuxcnc
Norbert,

Here is my estop out of my Hal File:
Code:
# ---digital in / out signals--- # ---estop signals--- net estop-out <= iocontrol.0.user-enable-out net estop-ext => iocontrol.0.emc-enable-in # ---manual tool change signals--- # ---manual tool change signals---



Jim

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

More
11 years 7 months ago #57045 by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@Jim

As you told, that you use a harware emergency estop, there must be more hal connections.

Norbert

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

More
11 years 7 months ago #57280 by mr_deimos
Replied by mr_deimos on topic Gmoccapy - A new screen for linuxcnc
Hi.
I've been using gmoccapy for a while now, and it works great for me so far.
However i have a little feature request.
A few versions back feed override and max velocity sliders got linked. So when i change the feed override to 50%, max velocity also changes to half of its original value. Normally it's ok, especially for testing a new program since it also scales down rapid movements speed.
However sometimes i need to temporarily limit the max velocity (without editing the ini file): for example when my mill runs for a long time, one axis tends to get blocked at high speeds. I know that it means that i really need to fix the mill and i'm working on it, but in the meantime i'm simply using the max velocity slider to keep it from reaching too high speeds.
But as soon as i touch the feedrate knob or use the '100% feed' button, max velocity is also changed, usually to something much higher than i want it to be.
So my question is this, Norbert: could you add an option to unlink these sliders? I guess it could be useful in cases other than crappy threaded nuts and too weak motors, for example when using heavier than usual tool.

And one more question: I noticed that when using a jog wheel (so far only the emulated one, from example gmoccapy configs) the machine always travels at maximum velocity, ignoring both jog speed and max velocity sliders. Is this the intended behavior?

RafaƂ

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

More
11 years 7 months ago #57302 by ssalrin
Replied by ssalrin on topic Gmoccapy - A new screen for linuxcnc

Swapper wrote:

mariusl wrote: Hi Norbert

I agree that we need some better touch off features. If you want to go that route with touch off then you might as well look at a lot more options like circle centres and many more.
IMHO we need a tab with touch off features and leave the run of the mill stuff as it is. Once you start down this road you will find that even the space at the bottom is not enough for what can be done.

The attached file shows what is a good set of touch off functions. That is why I think we need a tab for this.

You must also consider lathe users.



Would it be hard to dock this probe gui in gmoccapy?

linuxcnc.org/index.php/english/forum/40-...gcgui?start=30#37039
github.com/cnc-club/linuxcnc-features

Then all the "hard" probe stuff is done already.



Hello All,

Oh yes please, I vote for the probing!

Scott

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

Moderators: newbynobi, HansU
Time to create page: 0.272 seconds
Powered by Kunena Forum