Error Recovery

snowgoer540 wrote:

snowgoer540 wrote:

phillc54 wrote:

I probably shouldn't have put that in, you only need to do that if you have switched branches etc, not on the first build

EDIT: I should have added "sudo make setuid" at the end...

Easy enough to fix. So I have it all loaded up, running. But the Cut Recovery button stays greyed out now...any ideas why?

Do I need to run the configurator from the new linuxcnc-dev folder to change my links?

nevermind, needed to run configurator from the -dev folder. All better!

Back to testing... finally on 2.8. I'm not sure I see a reason to keep the buildbot version?

snowgoer540 wrote:

On to testing...

Linuxcnc freaks out if you click the X on the window rather than click cancel (is there a window option that doesnt allow closing it>)

The bumps X- and X+ etc, are they happening at max velocity? Those tiny .070" movements seem like they're going to beat my table apart. Turning down all the regular sliders had no effect (though I'm sure you knew that), and the movement speed slider for the FWD and REV is greyed out after you hit your first X+ movement, so I couldnt tell if that slider had any effect on the speed.

snowgoer540 wrote:

phillc54 wrote:

Its a personal choice I guess. It really depends on how often you update you Linux system. I do it once a week so I choose to use Buildbot for LinuxCNC then everything updates at the same time. If you don't want to update Linux often then use RIP for LinuxCNC and just update that.

RIP updates come faster than the buildbot ones, right? So if I had an issue and you quickly pushed a fix (because you're usually on it ), I may have to wait a day or two for the build bot to decide to get to work... where as the RIP would update pretty instantly, correct?

I dont really update linux ever, though maybe I should...

Last question, are you pushing your updates to your cut-recovery branch? It says V.138, and before I switched to your branch it said V.139?