Startup Error + Axis limit configuration
Error looks like this:
I know it says no input device was detected, but the machine controller was connected to the computer like it always is, any thoughts?
Also I cant seem to get the configuration for the limit switches right.
I have 3axis and 3limit switches, I would like to use the switches as people use their homeing switches, to be able to press `home` and automatically `zero` all the axis, but in the maximum limit mode, how do I do this?
The switches works all the way into the software, all I need to do is to link the signals in the configuration. From what I can understand in the configuration guide, what I need is something like this:
net X-limit parport.0.pin-10-in-not
net Y-limit parport.0.pin-11-in-not
net Z-limit parport.0.pin-12-in-not
my limits are connected like this by the way:
pin 10 = x limit
pin 11 = y limit
pin 12 = z limit
Thanks in advance!
Please Log in or Create an account to join the conversation.
linuxcnc.org/index.php/english/component...iew&catid=9&id=19139
John
Please Log in or Create an account to join the conversation.
I cant try if it works with the joystick connected now but I bet that was the problem.
Thanks John, but do you have any tips regarding my other problem?
Please Log in or Create an account to join the conversation.
linuxcnc.org/docs/html/config/ini_config...d_sub_axis_section_a
start by setting home is shared and the search and latch velocity etc. and leave for last the home sequence once your happy with each axis homing.
John
Please Log in or Create an account to join the conversation.
Also I saw in the new version that you could setup more properties in the wizard, so I thought I'd do that, but it didn't recognize my config file(?) this worked fine before but now I have to make a new configuration? Can't modify the old one? Its not visible when I try to open the file.
Regarding the homeing, dont I have to link the signals in any way (?), will it work after I fill out these values as the site that you linked was about?
I understand I must do it for every axis, but I dont quite understand how to fill everything out:
HOME = 1000 // If my machine is 1000mm on that axis (limit)
HOME_OFFSET = 0.0 // ?
HOME_SEARCH_VEL = any positive value?
HOME_LATCH_VEL = any positive value?
HOME_FINAL_VEL = any positive value?
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = NO
HOME_IS_SHARED = <n>
HOME_SEQUENCE = <n>
VOLATILE_HOME = 0
Please Log in or Create an account to join the conversation.
linuxcnc.org/docs/html/config/ini_homing.html
Did you start with a Stepconf Wizard generated configuration? If so and you picked the inputs then the wizard made the connections for you.
If your manually editing the files then you will have to net the parallel port pin to the home pin for each axis. After starting your config open up Show Hal Configuration and examine the pins to see the names.
John
Please Log in or Create an account to join the conversation.
I get a "RTAPI: ERROR: Unexpected realtime delay on task 1"
And I am unable to move any axis etc!
I have read about the RTAPI error and from what I can understand it has to do with the BASE_PERIOD in the .ini file. But the thing is, I ran the latency test and stressed the CPU etc - still RTAPI error. I also looked in my old .ini file (the one I canĀ“t get to work with the new version) and copied the BASE_PERIOD value to the new .ini - RTAPI error persist! Even though it worked fine before with that value!
For reference wizard put 31250 and my last setup had 25000 both BASE_PERIOD values in the .ini file.
Please Log in or Create an account to join the conversation.
So, perhaps you updated Linux instead?
What does uname -r say?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
I think I made myself unclear, I updated to LinuxCNC 2.5.1 after I took that screenshot, its now definitely 2.5.1 (says so when I start the program even)
I am still curious about your kernel version (uname -r)
If the upgrade to 2.5.1 was associated with a kernel change then it might be that the previous kernel suited your hardware better.
You could try disabling hyperthreading in the BIOS.
Please Log in or Create an account to join the conversation.