Gmoccapy - A new screen for linuxcnc

More
12 years 1 month ago #50610 by newbynobi
@Rick,
Let me see if i can implement that, as it isn't at the moment.
But only if you do the documentation on the WIKI:-)

@sliptonic,
Could you please post your config files?
Does the sim config gmoccapy.ini work like expected?

Norbert

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

More
12 years 1 month ago - 12 years 1 month ago #50611 by DaBit

sliptonic wrote: If I run a program, it just hangs at a line like T3 M06 G43. Again, no dialog.
Thoughts?


Yes, I had that too. Snippet from my (postgui) HAL file:

# Use gmoccapy toolchanger..
net tool-change gmoccapy.toolchange-change <= iocontrol.0.tool-change
net tool-changed gmoccapy.toolchange-changed <= iocontrol.0.tool-changed
net tool-prep-number gmoccapy.toolchange-number <= iocontrol.0.tool-prep-number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

The last line is what I added; LinuxCNC is indeed waiting until the tool is prepared but without above line (or more complex logic) that will never happen. This is not gmoccapy specific.
Last edit: 12 years 1 month ago by DaBit.

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

More
12 years 1 month ago #50612 by sliptonic
I think I got it. The sim file worked fine so I started backtracking. I guess I was confused by this comment in the postgui file:

# the unlink pin commands are only used, because they are connected
# in core_sim.hal and we use this file to simulate
unlinkp iocontrol.0.tool-change
unlinkp iocontrol.0.tool-changed

I assumed that meant they shouldn't be unlinked in a non-simulation config.

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

More
12 years 1 month ago - 12 years 1 month ago #50613 by DaBit
Just copy the four (!) lines in my post, and you should be fine. It is the 'iocontrol.0.tool-prepare => iocontrol.0.tool-prepared' you are missing.
Works for me at least.
Last edit: 12 years 1 month ago by DaBit.

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

More
12 years 1 month ago #50614 by LAIR82

newbynobi wrote: @Rick,
Let me see if i can implement that, as it isn't at the moment.
But only if you do the documentation on the WIKI:-)


Norbert


Sounds Fair enough :)

Rick

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

More
12 years 1 month ago #50781 by newbynobi
Hallo LAIR,

no it's your turn ;) B)

I just pushed gmoccapy 1.2.0 to 2.6 branch, will push to master in a few minutes.

There are now:

3 message types that support pango markup language
this is a part copy from the new config gmoccapy_messages.ini
Code:
# set up 3 user popup message dialogs # the messages support pango markup language # detailed information about the markup language can be found at # https://developer.gnome.org/pango/stable/PangoMarkupFormat.html # MESSAGE_TEXT = The text to be displayed, may be pango markup formated # MESSAGE_TYPE = one of "status" , "okdialog" , "yesnodialog" # status : Will just display a message as popup window, using the messsaging system of gmoccapy # okdialog : Will hold focus on the message dialog and will activate a "-waiting" Hal_Pin OUT. # Closing the message will reset the waiting pin # yesnodialog : Will hold focus on the message dialog and will activate a "-waiting" Hal_Pin bit OUT # it will also give access to an "-responce" Hal_Pin Bit Out, this pin will hold 1 if the # user klicks OK, and in all other states it will be 0 # Closing the message will reset the waiting pin # The responce Hal Pin will remain 1 until the dialog is called again # MESSAGE_PINNAME = is the name of the hal pin group to be created MESSAGE_TEXT = This is a <span background="#ff0000" foreground="#ffffff">info message</span> test MESSAGE_TYPE = status MESSAGE_PINNAME = statustest MESSAGE_TEXT = This is a yes no dialog test MESSAGE_TYPE = yesnodialog MESSAGE_PINNAME = yesnodialog MESSAGE_TEXT = Text can be <small>small</small>, <big>big</big>, <b>bold</b>, <i>italic</i> and even be <span color="red">colored</span>. MESSAGE_TYPE = okdialog MESSAGE_PINNAME = okdialog

So please get the branch gmoccapy 1.2.0

and inform, if it is what you expected?

Norbert

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

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