Hi Daren, > On 24 Jul 2017, at 07:35, Daren Schwenke <darenschwe...@gmail.com> wrote: > > > For kicks I tried some of the other machinekoder variants. > The watchdog errors appear to be specific to the Rostock, which appears to > re-define some of the fdm stuff. > This one starts fine: > https://github.com/machinekoder/Fabrikator-Mini-CRAMPS.git > But of course is missing lineardeltakins which is the reason I tried the > Rostock variant first. > > it's probably easier to go that route as this way I'm starting with a working > config. > If anyone else has been exactly where I am with building a new > lineardeltakins config in the new pythonic world and has it done, feel free > to point me in the right direction.
https://github.com/luminize/machinekit-lineardelta-config/tree/20170326 (branch 20170326) is my working configuration I run it (on my BeBoPr++ with “old” wheezy install) with ./run.py bebopr_pp_lineardelta Maybe this helps? > If not, I'll muddle. > > On Monday, July 24, 2017 at 1:12:14 AM UTC-4, Daren Schwenke wrote: > Pretty good clue in log file, now that I follow the actual directions for > posting an error: > Jul 24 02:02:57 beaglebone rtapi:0: Unknown parameter `num_inputs=1' > > So likely I've just got a mismatched component, which I still don't know how > to fix. > > On Monday, July 24, 2017 at 1:07:51 AM UTC-4, Daren Schwenke wrote: > Building a new printer, starting with 'latest'. > BBG, CRAMPS. > Started with image here: > https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/machinekit/bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz > > <https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/machinekit/bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz> > > Used config from here: > https://github.com/machinekoder/Rostock-CRAMPS > <https://github.com/machinekoder/Rostock-CRAMPS> > Failed. Tried doing apt-get update;apt-get upgrade. Same result. > > Switched back to BBB, CRAMPS. Same result. > > Result: > machinekit@beaglebone:~/Rostock-CRAMPS$ ./run.py > loading cramps2_cape.bbio... cape-universal already loaded > cape-bone-iio already loaded > done > starting mklauncher... done > starting configserver... done > starting machinekit... done > MACHINEKIT - 0.1 > Machine configuration directory is '/home/machinekit/Rostock-CRAMPS' > Machine configuration file is 'rostock.ini' > Starting Machinekit... > io started > halcmd loadusr io started > Traceback (most recent call last): > File "rostock.py", line 20, in <module> > hardware.init_hardware() > File "/home/machinekit/Rostock-CRAMPS/cramps.py", line 45, in init_hardware > errorSignal='watchdog-error') > File "/home/machinekit/Rostock-CRAMPS/fdm/config/base.py", line 34, in > usrcomp_watchdog > watchdog = rt.loadrt('watchdog', num_inputs=count) > File "machinekit/rtapi.pyx", line 219, in > machinekit.rtapi.RTAPIcommand.loadrt (hal/cython/machinekit/rtapi.c:4636) > RuntimeError: rtapi_loadrt '('watchdog', 'num_inputs=1')' failed: Operation > not permitted > Shutting down and cleaning up Machinekit... > exiting HAL component temp > Cleanup done > Machinekit terminated with an error. You can find more information in the > log: > /home/machinekit/linuxcnc_debug.txt > and > /home/machinekit/linuxcnc_print.txt > as well as in the output of the shell command 'dmesg' and in the terminal > stopping mklauncher... done > stopping configserver... done > machinekit@beaglebone:~/Rostock-CRAMPS$ > > Well now I'm in uncharted territory so let the googling commence. > Tried manually loading watchdog. Seems to work fine: > machinekit@beaglebone:~/Rostock-CRAMPS$ realtime restart > machinekit@beaglebone:~/Rostock-CRAMPS$ halcmd newinst watchdog num_inputs=4 > machinekit@beaglebone:~/Rostock-CRAMPS$ halcmd show > HAL Components: > ID Type Flags Inst Name PID State > 66 rHAL i 0 hal_lib 0 > ready, u1:0 u2:0 > 93 uHAL i 0 hal_lib10746 10746 > ready, u1:0 u2:0 > 95 User 0 halcmd10746 10746 > ready, u1:0 u2:0 > 78 RT cd 1 watchdog RT > ready, u1:0 u2:0 > > Instances: > Inst Comp Size Name Owner > 80 78 288 num_inputs=4 watchdog > > > Component Pins: > Comp Inst Type Dir Value Name > Epsilon Flags linked to: > 78 80 bit IN FALSE num_inputs=4.enable-in > --l- > 78 80 bit IN FALSE num_inputs=4.input-00 > --l- > 78 80 bit OUT FALSE num_inputs=4.ok-out > --l- > 78 80 s32 OUT 0 num_inputs=4.process.time > ---- > 78 80 s32 I/O 0 num_inputs=4.process.tmax > ---- > 78 80 bit OUT FALSE num_inputs=4.process.tmax-inc > ---- > 78 80 s32 OUT 0 num_inputs=4.set-timeouts.time > ---- > 78 80 s32 I/O 0 num_inputs=4.set-timeouts.tmax > ---- > 78 80 bit OUT FALSE num_inputs=4.set-timeouts.tmax-inc > ---- > 78 80 float I/O 0 num_inputs=4.timeout-00 > 0.000010 --l- > > Signals: > Type Value flags Name linked to: > > Parameters: > Comp Inst Type Dir Value Name > > Exported Functions: > Comp Inst CodeAddr Arg FP Users Type Name > 66 0000b6678705 000000000000 NO 0 user delinst > 66 0000b66785b5 000000000000 NO 0 user newinst > 78 80 0000b676bd25 0000b666bed8 YES 0 xthread > num_inputs=4.process > 78 80 0000b676be85 0000b666bed8 YES 0 xthread > num_inputs=4.set-timeouts > > Realtime Threads (flavor: xenomai, currently stopped) : > Period FP CPU Name Time > Max-Time util max jitter-95% flags > > > Rings: > ID Name Size Type Rdr Wrt Ref > Flags > > Exported vtables: > ID Name Version Refcnt > Context Owner > > Epsilon Value > 0 0.000010 > 1 0.000000 > 2 0.000000 > 3 0.000000 > 4 0.000000 > > machinekit@beaglebone:~/Rostock-CRAMPS$ > > Remembered that 'building icomp screws up because of posix docker path > thingy'. Tried the sym link: > > sudo ln -s /usr/lib/linuxcnc/xenomai /usr/lib/linuxcnc/posix > > No worky. > > Checked machinekit is indeed in 'xenomai'. > > And..... asking for help. > > -- > website: http://www.machinekit.io <http://www.machinekit.io/> blog: > http://blog.machinekit.io <http://blog.machinekit.io/> github: > https://github.com/machinekit <https://github.com/machinekit> > --- > You received this message because you are subscribed to the Google Groups > "Machinekit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to machinekit+unsubscr...@googlegroups.com > <mailto:machinekit+unsubscr...@googlegroups.com>. > Visit this group at https://groups.google.com/group/machinekit > <https://groups.google.com/group/machinekit>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
