Gmoccapy - A new screen for linuxcnc

@Marius and the other plasmas

Wouldn't it be a good idea to make an own thread for plasma?
It is mixing the gmoccapy questions a little bit up.

Admin: could you please move the plasma stuff to an own thread?

Hope you plasma people don't mind.

Norbert

LAIR82 wrote:
CSS in Gmoccapy does not function correctly from MDI

What I found is, if you try to invoke G96D800S450M3, from MDI, it starts at 800 and stays there, at the cap speed, regardless of where the X axis is at, if and when you go back to MDI, and enter g92x.....z....., ( whatever the DRO says for its current position) then it will automatically kick the spindle down to whatever RPM it should be at for the given diameter is, it is sitting at, then speed up and slow down accordingly.

Apparently it is not looking at, or taking into account its position, to set it at the correct speed. So you cannot start in CSS from MDI to make a manual cut, or run from line with the spindle started correctly for the cut.

I verified this using the Axis GUI, and in Axis the machine will start off at the correct rpm for the given size in MDI, and go up and down accordingly.

I submitted a bug report for this.

Let me know if I can be of any help in troubleshooting Norbert.

Thanks

Rick


Hello Norbert,

Just wondering if you had a chance to look at this, or if you maybe had an idea of what may be causing it?

Thanks

Rick

Hallo Rick,

sorry for missing your question.

I just took a closer look at that one. I am able to reproduce the behavior, but I am not able to solve that one right now.
I am using the corresponding gladevcp widgets and I do not modify the commands, so it is not an gmoccapy isue, but an gladevcp one.

As a work around I found:
First do the M3
then the G96 D6000 S250

and it will work as expected.

As the components are written by Pawel Shramov, we will have to ask him for help, or may be Chris is able to give us a hand.

Norbert

newbynobi wrote: @Marius and the other plasmas

Wouldn't it be a good idea to make an own thread for plasma?
It is mixing the gmoccapy questions a little bit up.

Admin: could you please move the plasma stuff to an own thread?

Hope you plasma people don't mind.

Norbert

Good idea and no problem we dont mind.

newbynobi wrote:

LAIR82 wrote:
CSS in Gmoccapy does not function correctly from MDI

What I found is, if you try to invoke G96D800S450M3, from MDI, it starts at 800 and stays there, at the cap speed, regardless of where the X axis is at, if and when you go back to MDI, and enter g92x.....z....., ( whatever the DRO says for its current position) then it will automatically kick the spindle down to whatever RPM it should be at for the given diameter is, it is sitting at, then speed up and slow down accordingly.

Apparently it is not looking at, or taking into account its position, to set it at the correct speed. So you cannot start in CSS from MDI to make a manual cut, or run from line with the spindle started correctly for the cut.

I verified this using the Axis GUI, and in Axis the machine will start off at the correct rpm for the given size in MDI, and go up and down accordingly.

I submitted a bug report for this.

Let me know if I can be of any help in troubleshooting Norbert.

Thanks

Rick


Hello Norbert,

Just wondering if you had a chance to look at this, or if you maybe had an idea of what may be causing it?

Thanks

Rick

Hallo Rick,

sorry for missing your question.

I just took a closer look at that one. I am able to reproduce the behavior, but I am not able to solve that one right now.
I am using the corresponding gladevcp widgets and I do not modify the commands, so it is not an gmoccapy isue, but an gladevcp one.

As a work around I found:
First do the M3
then the G96 D6000 S250

and it will work as expected.

As the components are written by Pawel Shramov, we will have to ask him for help, or may be Chris is able to give us a hand.

Norbert

No Problem Norbert, I just wondered if you had a look.

Thanks and Happy Holidays

Rick

I just pushed gmoccapy 1.3.5.1

I did find a way to show possible gcode errors while loading the gcode file.
I think with this we solved one big issue!

The error will be shown in an Warning window. It is modal and will requiere the user to push OK to continue.
Would it be better to make the message as a small gmoccapy pop-up message?

It is in 2.6, 2.7 and master branch, not jet in the deb packages.

Norbert

Hi guys

At the risk of having me head bitten clean off, i need to know what i am missing? Just did a new clean instal of 2.6, updated, added the master repo, updated to 2.8. I then followed the details in the wiki and changed settings in my .ini file but still cannot get gmocappy to run? I'm not a developer so what am i missing please?

thanks