Gmoccapy - A new screen for linuxcnc

Hallo Marius,

the signal panel is not the problem, as it must have certain width. If you make only the signals widget smaller, than some of the gcode info will be hidden.

I was thinking in placing the most important button on the right side in between the right button and the main frame as right panel, but as I do not know what are the important and have to be changed during machine run and what are only used some time, I will not decide the changes jet.

I would prefer also to move the limit LED to the signals panel, but we got a place problem also on that side.




Norbert

@All:

is someone still using the gscreen error system? showing the errors in the status bar? If not, I am thinking about removing the status bar completely, iMHO it only waste space.

I would like to include button for spindle speed increase and degrease as well as for feed speed.
So pushing the buttons will not increase the override, it will increase the programed speeds.

Till now it is only a idea, as I am still busy with tool measurement.

Norbert

Hi Norbert
I agree with changing the actual requested feed rate rather than the machine rate. You can have a parameter in the INI file to say by what percentage you can override the program feed ate. So if the max is 100% and the feed rate was F1000 then we will end up with F2000.

Please confirm that we are not running the gmoccapy_plasma.glade skin. I make changes to that and it does not appear anywhere.

Hallo Marius,

after a fresh pull, there shouldn't be any more files called gmoccapy_plasma in the directory you specified.

All relevant files are located now in:

/configs/sim/gmoccapy/gmoccapy_plasma

and the main screen is located in :

/share/gscreen/skins/gmoccapy

If you want to work on the real machine, please copy the relevant files from the sim directory to you config folder and edit the files there.

I am sorry for the mess with the file locations, but it seems that Garret has reworked the complete config picker and that made the relocation necessary.

If you want to modify label of the main screen like getting rit of the % of speed, make sure you do not use a translated version, because the label will be overwritten with the content of the locale file.


Norbert

If you want to modify label of the main screen like getting rit of the % of speed, make sure you do not use a translated version, because the label will be overwritten with the content of the locale file.

I am not sure what this entails but I am just using the screen as is in the directory. If we have to change the locale files you will have to direct me.

Please see the commit message of:
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...4fba80d75855bddfa38e

The goal here is to simplify the presentation of configs by the configuration picker AND to make sim configs run both in a RIP build and in an install from a deb.

Installing from a buildbot deb is much simpler for users who don't want to learn how to build a system from scratch, install all the dev packages, learn the intricacies of commandline autogen.sh, configure, and make, etc.

Norbert
I see that the MDI interface is not available if not homed. If the FORCE_NO_HOMING option is set, then one should have MDI available.

As far as I know, all functions should work as if homed if the NO_FORCE_HOMING option is set.

dgarrett wrote:

Please see the commit message of:
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...4fba80d75855bddfa38e

The goal here is to simplify the presentation of configs by the configuration picker AND to make sim configs run both in a RIP build and in an install from a deb.

Installing from a buildbot deb is much simpler for users who don't want to learn how to build a system from scratch, install all the dev packages, learn the intricacies of commandline autogen.sh, configure, and make, etc.

Thanks Garret, it makes sense. Just confused me for a while. Not so difficult to these days

Norbert
I see that the MDI interface is not available if not homed. If the FORCE_NO_HOMING option is set, then one should have MDI available.

As far as I know, all functions should work as if homed if the NO_FORCE_HOMING option is set.

Let me check that tomorrow, I just shut down my dev-computer.
It should work if the NO_FORCE_HOMING is set in the INI. I corrected that long time ago, but Chris just change some homing options in gscreen, so this may affect my settings.

Chris,

if you are still awake, could you check that?

Norbert

Ok Norbert fixed

Chris M