Gscreen - a GTK / Glade / Python based screen

More
13 years 8 months ago - 13 years 8 months ago #29712 by BigJohnT
Replied by BigJohnT on topic Gscreen - a GTK / Glade / Python based screen
That is the way it works for me... T0 at start up. It would be wrong to remember as when it is off it can't tell if I removed the tool or moved the turret or other such silliness that might go on when the computer is off.

John
Last edit: 13 years 8 months ago by BigJohnT.

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

More
13 years 8 months ago #29713 by andypugh
Replied by andypugh on topic Gscreen - a GTK / Glade / Python based screen

BigJohnT wrote: It would be wrong to remember as when it is off it can't tell if I removed the tool or moved the turret or other such silliness that might go on when the computer is off.


Which makes the mechanical barcodes on Skunkwork's machine suddenly look like a really neat idea.

Perhaps a solution would be an RFID chip in every toolholder.

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

More
13 years 8 months ago #29715 by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
@BigJohnT

Ok, your tool changer has an abslout encoder, but most of them don't.
The problem is only if the index tool button results in a change, then it will crash, because you haven't set the tool number bevor.

That is the only reason I use after every start M61Qx to set the mounted tool.

Why do I need ngcgui? It is easy to enter in the MDI window:

T5 M6
G43
G41
G0 X10 Y20
G1 Z-10
G1 X20Y10
G1X50
G3 X50 Y20 I0 J10
G1 X10
G3 X10 Y10 I0 J-10
G1 X22
G1 X50 Y20
G0 Z75

and its done. OK most people will not now the out of memory, but I am used to program line by line Gcode.
Nevertheless I have also written my own cycles for my lathe, so it is even quicker ;-)

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

More
13 years 8 months ago #29716 by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
@Chris,

you are right, forget the H in G43 for normal changes, everybody who need something different will run a programm or he will have to use MDI Comands, my buttons are calles Scripts and are specified in the INI File. You can have until 9 buttons to run 9 different scripts.

And you are right too with your opinion, that I use cutter radius compensation in MDI, not manual mode.
OK so I use MDI to set the compensation, or my own function ;-)

I do use my lath or mill a lot in MDI / Manual mode, on the lateh turning a braking disk down is easely made in manual mode, OK I got a Encoderbox, I hold in my hand.
And on the lathe just making a workpiece 2 mm shorter is also done in manual mode.

Norbert

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

More
13 years 8 months ago #29717 by newbynobi
Replied by newbynobi on topic Gscreen - a GTK / Glade / Python based screen
@andypugh

I thaught also this is wrong, but it seems that other people in this forum think different. So we will have to leave thge desition open or discuss it till finding a solution.

What about adding a checkbox to preferences page "store tool number on shutdown",
if checkt it will be stored and reloaded on the new start of linuxcnc. So everybody is free to choose according to theire needs.

Adding to #5400 and reload it is not selectable, so the user is forced to use it.

Norbert

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

More
13 years 8 months ago #29718 by cmorley
Replied by cmorley on topic Gscreen - a GTK / Glade / Python based screen

andypugh wrote: [quote="newbynobi" post=29705
No, linuxcnc do net remember the tool number. After every reboot the tool is set to "0"


That sounds wrong.

It might be possible to add the tool number (#5400) to the parameter file. I don't know if that would help.[/quote]

This sounds wrong to me too.
Why wouldn't a machine with an auto tool change asumme the tool at shutdown is still there?
I mean yes it's possible to take it out but that would be unusual to do without the rest of the machine running.

I would think it makes sense to assume the tool is the same on start up and if it isn't, the operator must issue the proper command to fix it. (which should be unusual)

and I can't understand why it would crash the tool if you issue a T5 if T5 is already there. waste of time maybe but why crash?
I could also see it get out of sequence if it's a random toolchanger.
Do you have a pic of your toolchanger?

Interesting.

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

Time to create page: 3.767 seconds
Powered by Kunena Forum