Gmoccapy - A new screen for linuxcnc

Chris,

is there any updated news when 2.6.0. will see the bright of a day?

Thanks,

Hi Norbert

I am busy testing my mill setup and I am using the attached script to replace the hal_manualtoolchange that comes with LCNC. This script works well in Axis but I found some issues with Gmoccapy screen. The script allows you to move the machine during tool change.
The scrip should place the system back to auto mode when the tool change is finished but it somehow does not do so. If I change the mode to auto by hand and vring the popup forward by hand, it all works fine.

Can you please see if we can work with this script with Gmoccapy?

P.S. There is s wiki on this script as well. wiki page

Halo Marius,

I just took a short look on the script, it seems to be very old, as it does import emc, not linuxcnc!
gmoccapy had some problems switching modes from external, but I solved that out with 0.9.9.7
What version do you use actualy?
That could be allready the problem, but.....

I would not suggest to use that script, as it may mess all gmoccapy settings, controls and so on up!
I am just writing an manual tool change with tool measurement remap procedure for gmoccapy, it does run alredy fine, afetr a lot of problems, but I need to include some more stuff to release it.

The user will be asked with the dialog, if he wants to measure the tool or not, (if you switch to a edge finder you surely do not want to measure it's length. also a milling head may not fit to your length probe.

The remap will be done mostly with a gcode subroutine, so it is easy to move to a lool change position etc.

So please understand, that I will not invest time at this development state to include the "patch" you mention here.

Why do you have to move the machine during the tool change? Or what else is needed?
If what you want can be done with gcode, please wait about 2 weeks for me to finish my work.

Unfortunately a German user found a bug, setting the machine in wrong machine units, after a fresh install and with no preference file, so I am forced to do a big rework on the preference and status side of gmoccapy, and this must to be done first, because bugs are more important to solve than features, even if they are only of limited importance. If you do not work this way, we will have to live later with a huge amount of patchwork and work arounds, because we did not solve the real problem.

Unfortunately there are some examples of that also in linuxcnc, as I noticed programming the remap implimentation, like line number handling.

Norbert

Thanks for the reply Norbert. I did not really want you to include this patch just your point of view was good. Thanks. I might have sent you the old version of the script. There is a new one that is redone for LCNC (emc removed). It is working ok for now just the return to auto mode is gone.

The reason that I am going to the script is because I used Gcode to do toolchange and found that if I use a call to a subroutine or a macro, the back plot does not display the job any more. I have a macro on a button that does the tool length measurement.

I will wait for your release before I look at this again.

P.S. If you use a router type of mill then you dont have the luxury of tool holders so the tool table does not work. Every tool must be zeroed at every tool change. For this you may have to move the machine.

The reason that I am going to the script is because I used Gcode to do toolchange and found that if I use a call to a subroutine or a macro, the back plot does not display the job any more. I have a macro on a button that does the tool length measurement.

I am nearly sure, that your sub does end with an M2.
Replace the M2 with a % only at the end!

I do know that that causes an error in the terminal, but in my case that solved the problem of repainting the preview window with nothing.

Please inform if that works for you too.

If you have a tool length probe switch, you do not need to touch off every tool, in gmoccpy it will not even be necessary to have a reference tool.

You measure any tool you want (in coordinate system later be used on the program), and then you enter the workpiece height (measured from the table), that's it.
Start the program, TnM6 will be found the machine moves automatically to the tool length switch and measure the length, G43 will be activated, as the tool switch height and the workpiece height is known, I can calculate the offset to apply to the actual coordinate system
The tool moves to workpiece and does his job, after the next tool change the same happens again, but now the difference between workpiece height and coordinate system is null, the coordinate system will not be moved.

I am on the tests with real machine at the moment.

Norbert

Nortbert
That is exactly what I was trying to achieve with the subs. And yes I do have M2's. I will remove them and check again but I like your way better. No offsets from the job is good for me. I am not a trained machinist and the simpler it is the better form me. I just want to make parts that work and look good. The rest is for much more clever guys.