#linuxcnc-devel Logs

Apr 12 2018

10:46 AM seb_kuzminsky: the wheezy-rtai-i386 buildslave locked up (kernel backtrace shows it was in ipipe...)
10:49 AM seb_kuzminsky: i rebooted it and now the buildbot is making progress again
10:54 AM rene-dev: whats the best way to auto-restart a program? I need some test setup, where I can run a program in a infinite loop
10:54 AM seb_kuzminsky: i like this:
10:54 AM rene-dev: preferably in hal, so I can just click a checkbox
10:54 AM seb_kuzminsky: while true; do run-my-program; done
10:54 AM seb_kuzminsky: oh, you mean a g-code program, heh
10:54 AM rene-dev: yes :D
10:54 AM seb_kuzminsky: err
10:54 AM rene-dev: cant do it in gcode...
10:55 AM seb_kuzminsky: well you could write a python program that connects to linuxcnc as a UI, monitors the status buffer for the completion of the program (idle interpreter maybe? i'm not sure), and re-starts it
10:56 AM seb_kuzminsky: you could look at tests/motion-logger/basic/test-ui.py for inspiration
10:56 AM rene-dev: maybe halui.program.is−idle -> halui.program.run
10:57 AM seb_kuzminsky: your solution sounds a lot simpler
10:58 AM rene-dev: BTW, I think you can crash the interpreter with a infinite loop
10:59 AM seb_kuzminsky: that wouldn't surprise me
10:59 AM rene-dev: I remember trying this a few years ago from gcode, and it would lock up
11:00 AM rene-dev: and when you only repeat a few 1000 times, it would take ages to load
11:59 AM Tom_L: run it in a subroutine and loop alot of times
03:39 PM alex_joni: cradek: I saw some comments on joint vels and traj vels
03:39 PM alex_joni: (couple days ago, but was traveling)
03:40 PM alex_joni: I think fixing that involves having jacobian functions in kins, then you might be able to calculate in advance what the joint velocities will be, and adjust accordingly
03:42 PM alex_joni: and as an off-topic note, on robots these days we do predictive dynamics to figure out what the load on joints will be and how fast we can drive them (that involves a model of the robot,payload,friction,etc)