Gscreen - a GTK / Glade / Python based screen

LAIR82 wrote: Hello Chris,

Have a few questions for you,

1. On tuesday, we were running our turning center, and the operator looked up, and realized that the screen had frozen up in the middle of a running program. He hit the feedhold button on the operator console of the machine and came and got me. I it stayed that way for all of the 5 minutes I was trying different things to get it to come back to life, nad nothing worked. I had to press and hold the PC power button to restart the pc. Since then it hasn't done again. I have the refresh rate at 100 in my INI. Any thoughts?

2. Last week the same operator came and got me saying that there was a fault on the display. I looked at it and saved a copy, just in case anything odd were to happen, which today it did. The operator was double checking one of his tools in the machine and went to re-touch off the tool to be sure and after he pressed the tool setting button, entered the value and pressed enter. Then he pressed the Tool Editor button on the top row of buttons and when the tool table came uponly 3 of his 14 tools had any values in them, the rest of his data for the other tools was all zeros. He told me after a short discussion with him that the following fault has came up 3 times in the last 4 weeks, and he has had tool data dissappear 1 other time during the same time period. I attached a screenshot of the fault to see if it may make sense to you, and if what I am experiencing is related.

It has been running fine other than these few things which have come to light in the last couple of days. The operator really like's the feel of the GUI, he's just been getting a little frustrated with me when it throws me a curve ball this.

Thanks

Rick

Rick:

1) I really don't know what would cause this. I'll have to ask one of the other developers about how to diagnosis this.
Thank goodness Linuxcnc uses realtime OS so even if the screen freezes the machine still runs properly.

2) I can get the error code eg type 1.2 3 in. - I can suppress this error so it doesn't pop up.
I do not lose any tool data. Is it possible the operator forgot to hit the apply button after editing the tool file?
This would be easy to do - pressing return updates the screen but does not update linuxcnc until the apply button is pressed.
maybe I should change that behaviour.
If this is not the problem then there must be a special combination that does it - which will be harder to find.

I have fixed the MDI entry problem - update to fix it.

Chris M
Chris M

Chris, is that it is too early but think that you can run run orders, estop, pause, from the keyboard?

Rick.
the problem is in the patch of fanuc.

Rick do the following. Z tool offset # 4, having a wear in 10004, must show up the value of wear. wear off. and returns to compensate. entire table is deleted or does not take the value 0 in the 10004, not replace the previous value

thanks.

I will get that updated monday, and see how it goes. Then I can start to mess around with the tool table issue. I will see if I can replicate what you are saying Jorge, and hopefully get this figured out.

We never noticed any issues like this on the first build using that patch, but I will have to check the interpreter files that are modified for it, to make sure I changed them correctly. Reason I say this is due to me having to hand edit the files because the patch is outdated now against the current interpreter files.

Thanks Again

Rick

jlviloria wrote: Chris, is that it is too early but think that you can run run orders, estop, pause, from the keyboard?

Rick.
the problem is in the patch of fanuc.

Rick do the following. Z tool offset # 4, having a wear in 10004, must show up the value of wear. wear off. and returns to compensate. entire table is deleted or does not take the value 0 in the 10004, not replace the previous value

thanks.

Hmm according to the patch code - 10004 is the geometry and 4 is the wear offset. Is that normal in Fanuc programming?
When tool changing to tool 4 does the pop up say tool 10004?

Jorge could you explain exactly how you get the tool table to delete? is it repeatable?

Chris M

Crhis know the limitation of my English will try my best.

<Tool Editor>

4 = geometry tool = -80.01
10004 = wear tool = 0.6

(I do not use g92 or g54)

1) proceed to "compensate" my tool in Z axis.

2) I press the key "tool-set", digit 0

3) The value of Z in absolute position is 0.6 (take the offset value (10004))

4) delete the offset value (10004) placed him 0, I press apply, reload. back to "compensate"

5) I press key "tool-set" digit 0, and the value returns to 0.6 (the value of wear (10004) is again 0.6)

6) repeat the operation and got it.

7) the third or fourth attempt takes the value 0 at absolute and the wear (10004).

when I try to change the tool, get the message "request not found tool 10004 in tool table".

9) I go to the tool-editor, all erased.


I think that happens when you go to "Compensate" a tool that has already been compensated before.


Thanks,


Jorge

Why is T10004 not wear offset 100 and geometry 04?
I thought that the patch only covered tools up to 99?