Error Recovery
- tommylight
-
- Away
- Moderator
-
- Posts: 19619
- Thank you received: 6614
RIP is for developers, who change a lot of things and test, other than stuff on hal and ini files.
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
- Posts: 2397
- Thank you received: 787
No mistake, buildbot is the same as RIP, give or take a day or two.
RIP is for developers, who change a lot of things and test, other than stuff on hal and ini files.
Right, but earlier in this thread Phill gave me instructions as to how to check out his git with the error recovery... how would I do that with a build bot version?
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
- Posts: 19619
- Thank you received: 6614
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
- Posts: 19619
- Thank you received: 6614
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
- Posts: 2397
- Thank you received: 787
BTW you can have the buildbot and the RIP version on the same computer, just pull with git and follow instructions to build and run.
So, is there a way to do a RIP version of 2.8? I followed the directions below, and it put 2.9 on ...
linuxcnc.org/docs/2.8/html/code/building...cnc.html#Quick-Start
Please Log in or Create an account to join the conversation.
- phillc54
-
Topic Author
- Offline
- Platinum Member
-
- Posts: 5715
- Thank you received: 2091
Yes, it will only reverse up to the start of the current cut but will move forward to the end of the job. PlasmaC has no influence on how that works.Actually, I take that back, it does work, but only between M3 commands. Where I can go forward indefinitely as long as I hold down on forward, Reverse does not work the same way. It will only reverse me to the beginning of the G1 or G0 command. If It gets to the next line, it wont go back further. Is that how it's supposed to work?
For testing it is probably best if you do a RIP build of the phillc54/cut-recovery branch then it won't intefere with your Buildbot install.Sorry to rapid-fire posts. I went to 2.8 so that we can be testing the same version. I wasnt thinking and did the build-bot installation. That was a mistake wasnt it... I need to do the RIP installation to check this back out and keep testing, correct?
You could if you really wanted to use the Buildbot scratch builds but they will overwrite your current Buildbot install and you would need to revert after testing. The Sstretch builds are here
The Stretch buildbot packages are :
2.8
master
Please Log in or Create an account to join the conversation.
- phillc54
-
Topic Author
- Offline
- Platinum Member
-
- Posts: 5715
- Thank you received: 2091
BTW you can have the buildbot and the RIP version on the same computer, just pull with git and follow instructions to build and run.
So, is there a way to do a RIP version of 2.8? I followed the directions below, and it put 2.9 on ...
linuxcnc.org/docs/2.8/html/code/building...cnc.html#Quick-Start
You would need to add a couple of commands:
> git clone git://github.com/linuxcnc/linuxcnc.git linuxcnc-dev
> cd linuxcnc-dev/src
> git checkout phillc54/cut-recovery-28 (or phillc54/cut-recovery-master)
> ./autogen.sh
> ./configure --with-realtime=uspace
> make
> sudo make setuid
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
- Posts: 2397
- Thank you received: 787
> git clone git://github.com/linuxcnc/linuxcnc.git linuxcnc-dev > cd linuxcnc-dev/src > git checkout phillc54/cut-recovery-28 (or phillc54/cut-recovery-master) > make clean > ./autogen.sh > ./configure --with-realtime=uspace > make
I get this error after typing "make clean"
Makefile:71: Makefile.inc: No such file or directory
Makefile:82: *** Makefile.inc must specify RTPREFIX and other variables. Stop.
Please Log in or Create an account to join the conversation.
- phillc54
-
Topic Author
- Offline
- Platinum Member
-
- Posts: 5715
- Thank you received: 2091
EDIT: I should have added "sudo make setuid" at the end...
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
- Posts: 2397
- Thank you received: 787
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?
Please Log in or Create an account to join the conversation.