Gmoccapy - A new screen for linuxcnc

More
12 years 4 weeks ago #51715 by DaBit
Replied by DaBit on topic Gmoccapy - A new screen for linuxcnc

newbynobi wrote: @All,
@DaBit,
If the machine is out of emergency status and the machine is off, the chk_ignore_limits should be checkable. It will be unsensitive if machine is switched on! So check the box, before switching on the machine.


Stays grayed out with machine out of E-stop and not turned on, but on the limit switch. Restarting LinuxCNC does not help.


You will have to edit the combi_dro settings in the gmoccapy.glade file to change the resolution of the DRO. You can do that with the glade editor. If you are on Ubuntu you may need to start glade from a terminal after doing rip-environment. (Ask if you need more info)


Had to install glade-gtk2 to do so (I'm on Ubuntu 12.04), but after that it was a piece of cake. Thanks!

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

  • microsprintbuilder
  • Offline
  • Premium Member
  • Premium Member
More
12 years 4 weeks ago #51765 by microsprintbuilder
Replied by microsprintbuilder on topic Gmoccapy - A new screen for linuxcnc
I love this screen.
That being said I have some issues I'm needing to fix. The first is that the entire screen seems to have a grey haze. almost like a nats or fire fly's running around. If I run it in a demo mode there is no haze. I started with a working axis setup and switched to Gmoccapy using the instructions. I'm running Ubutnu 12.4 with the 2.6
The second thing is that I have a tool change sub that is called when you use M6. It is a remap. When I call the tool change the sub pops up in the g-code display window and the pot disappears but neither return after the tool change is done but the program continues with any problem. Lastly the current codes called don't seem to work.

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

More
12 years 4 weeks ago #51766 by Andreas_S
Replied by Andreas_S on topic Gmoccapy - A new screen for linuxcnc
Hello Norbert

I think it's not necessary to implement a test "ready for MDI or MANUAL Mode. The same tought I had in the beginning, therefore i implementet it like this:
Code:
# Added support for F3 (manual mode) and (mdi mode) if keyname == "F3" and signal: # only change to manual mode if not in auto mode if self.stat.task_mode == linuxcnc.MODE_AUTO: return True self.command.mode(linuxcnc.MODE_MANUAL) return True

Then I tested it without the test for linuxcnc.MODE_AUTO. And then I also tested what happens if a ngc Programm is running. Details see screenshot.

Thanks
Andreas
Attachments:

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

More
12 years 4 weeks ago #51771 by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@microsprintbuilder
What is gray haze? I have never heared about that problem.
The remap problem is known, but i have not been able to solve it.
I will try to get time to work on it.

Norbert

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

More
12 years 4 weeks ago #51772 by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@Andreas,

I did know the error popup, IMHO that should not happen, thatis why i would test the mode.

Norbert

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

  • microsprintbuilder
  • Offline
  • Premium Member
  • Premium Member
More
12 years 4 weeks ago #51776 by microsprintbuilder
Replied by microsprintbuilder on topic Gmoccapy - A new screen for linuxcnc
Hi Norbert:
I"m looking at axis and touchy and the same thing happens so it's not a Gmoccapy issue. It looks like bad TV reception on a analog TV. I'm thinking something to do with graphics.

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

Moderators: newbynobi, HansU
Time to create page: 0.425 seconds
Powered by Kunena Forum