GUI Discussion
... the labels you are referring to are part of a gladeVCP widget so I cannot change them unless I commit code to EMC (which I might later)
Chris,
I'm not entirely sure this is the case.
I would think that it is possible to import the widgets and customize them by defining a subclass and redefining as needed them before they are displayed. I havent tried this though.
Where's Pavel when we need him
- Michael
Please Log in or Create an account to join the conversation.
I guess some experiments then some added docs are in order.
There are a couple other things I have come across for instance LEDs
In Gscreen I'd like to use LEDs as indicators but without HAL pins - I want to set and unset them in the program.
Thinking further I could see a want of LEDs that one can change in the program but wish that they export a HAL pin that follows the LED state.
adding HAL pins as an option: in / out / or none should not be that hard...
gladeVCP is so powerful now - it has grown farther then I imagined when I started it - I'm so glad You guys took it and ran !!
Please Log in or Create an account to join the conversation.
This is why for instance EMC has a non standard threading behavior. ( you must calculate the hypotenuse on tapers )
While technically if gives more feature , no machinist is going to think that way !
I am not sure if this is true only of G33 or G76 too. However, I think it is correct behaviour, as G33 is "spindle synchronised motion" not "threading".
One advantage is that you can use it equally well for a scroll as for a thread.
G33.1 is a dedicated threading operation, but in that case it is again a useful feature as (I think) it allows rigid tapping of angled holes. In that situation slaving the feed to the Z axis only could get very expensive.
Please Log in or Create an account to join the conversation.
<rant on>
but you prove my point not many machinists think of threading as 'spindle sync motion' it's threading!
On the Okuma I used it could thread longitudinally, scroll or taper wit G33 ( or was it G32?)
It had a few other threading g codes such as variable pitch etc.
I will look it up in the manual when I get time...
ridged tapping is of course different hence the different g code. I've never used a 5 axis machine.
What would have made more sense is have g33 work as standard and have the current behavior as a different g code such as g33.2
Wouldn't it make sense to have the 99% common behavior standard and the 1 % an option?
I can think of little reason one would need the pitch to be parallel to an angle. Parallel to X or Z you bet.
your argument that EMC is correct because we call it 'spindle sync motion" not threading is a programmer or engineers view.
Your not wrong but why would we do that ?
<Rant off>
I hope i have not offended any programmers or engineers.
Tradesmen and engineers seldom see exactly eye to eye! Which is probably not all bad..
Chris m
Please Log in or Create an account to join the conversation.
I'm not sure why you would want to use G33.1 for threading unless your doing a taper thread or a fusee or something unusual. I use G76 for threading on the lathe.
John
Please Log in or Create an account to join the conversation.
To add to the fire, I wish the G54 canned cycle was official
?
Please Log in or Create an account to join the conversation.
This code is currently unimplemented in EMC2. It is accepted, but the behavior is undefined.
John
Please Log in or Create an account to join the conversation.
OK, I was confused by the way you called it G54 (which I do recall some recent debate about, but works as far as I know)According to the manual entry for G84 tapping...
This code is currently unimplemented in EMC2. It is accepted, but the behavior is undefined.
Please Log in or Create an account to join the conversation.
John
Please Log in or Create an account to join the conversation.
Odd:According to the manual entry for G84 tapping...
This code is currently unimplemented in EMC2. It is accepted, but the behavior is undefined.
git.linuxcnc.org/gitweb?p=emc2.git;a=blo...9e2294d91f28;hb=HEAD
Line 236.
The code seems to all be there.
Please Log in or Create an account to join the conversation.