[Emc-users] Homing and restarting Lcnc problem
Suddenly I have problem with homing my z axis, as it reaches switch it back's off as it supposed to, but then it doesn't stop on programmed home offset instead it runs over it and keeps searching with its delatching velocity... Next problem occurred after update to 2.7.0 pre, as when I restart linuxcnc i'm getting error saying: Debug file information:insmod: error inserting '/usr/realtime-2.6.32-122-rtai/modules/linuxcnc/hal_parport.ko': -1 Device or resource busymy5axis_load.hal:25: exit value: 1my5axis_load.hal:25: insmod failed, returned -1See the output of 'dmesg' for more information.2036 -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing and restarting Lcnc problem
Commenting out LP line in modules doesn't help, and also uncommenting install parport_pc /bin/true didn't in /etc/modprobe.d/linuxcnc.conf Next problem occurred after update to 2.7.0 pre, as when I restart linuxcnc i'm getting error saying: Debug file information:insmod: error inserting '/usr/realtime-2.6.32-122-rtai/modules/linuxcnc/hal_parport.ko': -1 Device or resource busymy5axis_load.hal:25: exit value: 1my5axis_load.hal:25: insmod failed, returned -1See the output of 'dmesg' for more information.2036 -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing and restarting Lcnc problem
On Sat, Sep 06, 2014 at 03:12:56PM +, Tomaz T. wrote: Next problem occurred after update to 2.7.0 pre, as when I restart linuxcnc i'm getting error saying: Debug file information:insmod: error inserting '/usr/realtime-2.6.32-122-rtai/modules/linuxcnc/hal_parport.ko': -1 Device or resource busymy5axis_load.hal:25: exit value: 1my5axis_load.hal:25: insmod failed, returned -1See the output of 'dmesg' for more information.2036 Thanks for your report. In master branch, I have made some changes regarding parallel port registration in order to support uspace realtime. I will test later today whether my work caused this problem. If so, I'll fix it. Please remember that the master branch is for new and potentially untested work, so instability like this occurs much more frequently than in our stable release branches such as 2.6.x. Jeff -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing and restarting Lcnc problem
I tested for the hal_parport device or resource busy problem but was unable to reproduce it. I tested on a debian 7 system recently installed from the hybrid.iso. I tested at a master branch revision which describes as v2.6.3-659-gce43af0 (today's master branch) using a standalone test script in the file pp.hal loadrt hal_parport cfg=0 loadrt threads period1=100 loadrt not net x not.0.out = not.0.in parport.0.pin-01-out addf not.0 thread1 addf parport.0.write thread1 start which I ran multiple times in succession with halrun pp.hal I did not receive any errors in the terminal or in dmesg. On my system, the install parport_pc /bin/true line is commented out in /etc/modprobe.d/linuxcnc.conf, so hal_parport is working in cooperatin with the linux parallel port driver. My parallel port is on a PCI card. If you can, please test with the standalone hal script (modifying cfg= if necessary) to see whether that produces the problem for you. But the most basic explanation (that I completely botched the unregistration process for rtai when adding uspace) seems to be discounted at this point. Jeff -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing and restarting Lcnc problem
On Saturday 06 September 2014 12:00:20 Tomaz T. did opine And Gene did reply: Commenting out LP line in modules doesn't help, and also uncommenting install parport_pc /bin/true didn't in /etc/modprobe.d/linuxcnc.conf If the std linux parport driver is available, and udev loads it, the results are similar. So if you have that driver in the /lib/modules/kernel-version tree, nuke it. In the meantime, rmmod it if it shows up in an lsmod listing before you start linuxcnc. This is a rather elderly problem if that is the problem, but it can still bite a new bee. Next problem occurred after update to 2.7.0 pre, as when I restart linuxcnc i'm getting error saying: Debug file information:insmod: error inserting '/usr/realtime-2.6.32-122-rtai/modules/linuxcnc/hal_parport.ko': -1 Device or resource busymy5axis_load.hal:25: exit value: 1my5axis_load.hal:25: insmod failed, returned -1See the output of 'dmesg' for more information.2036 --- --- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] Homing and restarting Lcnc problem
On Sat, Sep 06, 2014 at 03:21:01PM -0400, Gene Heskett wrote: On Saturday 06 September 2014 12:00:20 Tomaz T. did opine And Gene did reply: Commenting out LP line in modules doesn't help, and also uncommenting install parport_pc /bin/true didn't in /etc/modprobe.d/linuxcnc.conf If the std linux parport driver is available, and udev loads it, the results are similar. No, that has not been true for a long time now. Since version 2.4.0 (2010), linuxcnc has by default cooperated with the Linux parallel port drivers, so hal_parport and other parport-using drivers generally do not interfere with or experience interference from the kernel parport_pc driver. For that reason, systems installed since that time have the modprobe.d line that would disable parport_pc commented out by default. One great advantage of this, which we have probably not evangelized hard enough (or scrubbed away all documentation to the contrary), is the ability to refer to parports by their linux numbering, not worrying about I/O port addresses: loadrt hal_parport cfg=0 points at the system's default parallel port, if linux detected one. Super easy, and it even worked on my system where the only parport is a PCI-E one! Some people may still feel more comfortable with parport_pc not loaded. This reduces the risk that some linux software (such as the printing system) will touch the port, causing the attached CNC to do something unexpected. Those people can uncomment the line or take more drastic measures if they prefer. (best possible measure to take: a proper physical estop chain so this doesn't happen even when somebody boots windows 98 from cdrom or whatever crazy thing you might imagine) Jeff -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
