Computer total freezes only during jogging

More
12 Aug 2015 15:07 - 12 Aug 2015 15:09 #61315 by emcPT

I would use the USB keyboard and mouse through USB to PS2 converters as first choice.


So, if I understood correctly you recommend to use the existing keyboard and mouse (USB), then at the motherboard transform them to PS2 through a simple USB -> PS2 adapter, yes?
This is the simplest thing to do, so it would be great :) , because one of the machines is at a customer and having to change the keyboard would be a mess, as the keyboard is placed on a nice panel, so any change on the panel size/geometry would be bad.

Thanks.
Last edit: 12 Aug 2015 15:09 by emcPT.

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

More
12 Aug 2015 15:16 - 12 Aug 2015 15:37 #61316 by ArcEye
As far as I am aware, PS2 is just a 2 wire serial bus, same as USB, so the conversion is just a matter of the plug shape.

The difference is which motherboard bus it is connected to and that does seem to make a difference.





Got to be worth a try

regards
Attachments:
Last edit: 12 Aug 2015 15:37 by ArcEye.
The following user(s) said Thank You: emcPT

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

More
12 Aug 2015 16:04 #61318 by emcPT
The web site from where that image was taken out says it all! ;)

I will post back with more info, as I have a few of those in house.

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

More
19 Aug 2015 23:55 #61560 by emcPT
Well, I was not able to place the keyboard working with the PS2->USB adapter. I tested 4, but with no luck so I quited.

I will place physical buttons to jog as it is the correct way to do it.

However I would like to ask if there is any way to disable the jog though the keyboard.

This will force the user to use the new placed keys.
Thank you

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

More
20 Aug 2015 00:10 #61561 by andypugh

However I would like to ask if there is any way to disable the jog though the keyboard.


One way would be to put the following in a .axisrc file. That would only apply to one user, though (I think)
root_window.unbind("<KeyPress-Left>")
root_window.unbind("<KeyPress-Right>")
root_window.unbind("<KeyPress-Up>")
root_window.unbind("<KeyPress-Down>")
The following user(s) said Thank You: emcPT, jtc

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

More
20 Aug 2015 00:23 #61562 by emcPT
One user is totally ok.
Thank you!

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

More
20 Aug 2015 14:52 #61570 by ArcEye
If you want to look at a permanent all user solution, lines 2740 and 3099 in axis (at least in 2.8~ but won't be far out)

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

More
20 Aug 2015 16:22 #61571 by andypugh

If you want to look at a permanent all user solution, lines 2740 and 3099 in axis (at least in 2.8~ but won't be far out)


That will bring it back if the LinuxCNC version is upgraded (probably, it might depend on the way that apt does deltas)
I guess the way to be absolutely sure is to do both.

I should probably add jog-wheels to my lathe, for the opposite reason. It is very annoying that I can't jog when the pointer is over a GladeVCP tab. Also, the GladeVCP action-buttons now put Axis in MDI mode, which also prevents jogging.

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

More
07 Sep 2015 22:07 #62198 by jtc

However I would like to ask if there is any way to disable the jog though the keyboard.


One way would be to put the following in a .axisrc file. That would only apply to one user, though (I think)
root_window.unbind("<KeyPress-Left>")
root_window.unbind("<KeyPress-Right>")
root_window.unbind("<KeyPress-Up>")
root_window.unbind("<KeyPress-Down>")


I tried to implement this way and it didn't work.

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

More
08 Sep 2015 00:20 #62208 by dgarrett
Edit the inifile to add this line to the [DISPLAY] stanza:
USER_COMMAND_FILE = unbind.py

Create a new file named unbind.py in the same directory as the
inifile with the following contents:
root_window.tk.call("bind",".","<KeyPress-Left>","")   # Left arrow
root_window.tk.call("bind",".","<KeyPress-Right>","")  # Right arrow
root_window.tk.call("bind",".","<KeyPress-Up>","")     # Up arrow
root_window.tk.call("bind",".","<KeyPress-Down>","")   # Down arrow
root_window.tk.call("bind",".","<KeyPress-Prior>","")  # PgUp
root_window.tk.call("bind",".","<KeyPress-Next>","")   # PgDn

root_window.tk.call("bind",".","<KeyRelease-Left>","")   # Left arrow
root_window.tk.call("bind",".","<KeyRelease-Right>","")  # Right arrow
root_window.tk.call("bind",".","<KeyRelease-Up>","")     # Up arrow
root_window.tk.call("bind",".","<KeyRelease-Down>","")   # Down arrow
root_window.tk.call("bind",".","<KeyRelease-Prior>","")  # PgUp
root_window.tk.call("bind",".","<KeyRelease-Next>","")   # PgDn

You can do this in a ~/.axisrc file as well (for each user); using [DISPLAY]USER_COMMAND_FILE applys to any use of the modified inifile
The following user(s) said Thank You: emcPT, jtc

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

Time to create page: 0.528 seconds
Powered by Kunena Forum