Keyboard Shortcuts in Gmoccapy

More
10 years 5 months ago #74234 by LearningLinuxCNC
Yep, I completely overlooked the hal_input module. I will give that a shot.

Thanks,

Jim

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

More
10 years 5 months ago #75196 by tarasko
Excuse me.
In what version of gmoccapy <F3> and <F5> are works as switching to the manual, mdi mode?

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

More
10 years 5 months ago #75222 by newbynobi
F3 and F5 shortcuts have been introduced with gmoccapy 1.5.5.

You must enable keyboard use in settings to use that feature.

Norbert
The following user(s) said Thank You: tarasko

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

More
10 years 2 months ago #79125 by tarasko

newbynobi wrote: F3 and F5 shortcuts have been introduced with gmoccapy 1.5.5.

You must enable keyboard use in settings to use that feature.

Norbert

newbynobi wrote: F3 and F5 shortcuts have been introduced with gmoccapy 1.5.5.

You must enable keyboard use in settings to use that feature.

Norbert


Well, there is some bug around these shortcuts.
I'm using a touchscreen monitor with hardware keyboard.
I found it more convenient than on-screen keyboard.
So I frequently switching among MANUAL, AUTO, MDI modes.

I think switching from AUTO -> MDI mode not works properly.
(the case when I want directly switch to MDI mode (F5) after program end)

I also reproduced this issue in recent Gmocappy 2.1.0 from master branch

Thanks.

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

More
2 years 5 months ago #300915 by abdulasis12
Hi ,
I try use : loadusr -W hal_input -K +KeyWarrior:0
in my hall, but debug file pop-up
***
Note: Using POSIX realtime
HAL: ERROR: duplicate component name 'iocontrol'
IOCONTROL: ERROR: hal_init() failed
can't initialize the HAL
Waiting for component 'hm2_eth' to become ready.....................
No input devices could be opened. This usually indicates a misconfigured
system. Please read the section 'PERMISSIONS AND UDEV' in the hal_input
manpage
./217-4x.hal:26: waitpid failed hal_input hal_input
./217-4x.hal:26: hal_input exited without becoming ready
1233
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
*
hal_input <<
how to access permission. ?
or more other file to setup before use ?

FYI:
in hall line 26 is : loadusr -W hal_input -K +KeyWarrior:0

Thank you,
Asis

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

More
2 years 5 months ago #300930 by HansU
A similar problem was reported here. Maybe Andys suggestion does help you?

forum.linuxcnc.org/24-hal-components/507...nnected-to-it#286170
The following user(s) said Thank You: abdulasis12

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

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