#linuxcnc-devel Logs

Dec 25 2017

09:34 AM pcw_home: Entertaining TP bug: if you set G64 P very small the TP goes bonkers (I made the mistake because if was in mm mode and was thinking inches )
09:45 AM skunkworks: I don't see it in sim
09:45 AM skunkworks: G64p.0000001
09:45 AM skunkworks: 1000% override
09:45 AM skunkworks: splash gcode
09:51 AM pcw_home: I just changed the P value and G21 in 3D_Chips and blam
09:52 AM pcw_home: ( trying to duplicate the forum error with g64 )
09:53 AM pcw_home: try on 3d chips with g21 and g64 p .0003
10:12 AM pcw_home: sim loops back command to position so wont generate a following error
10:12 AM pcw_home: command to feedback I mean
10:26 AM skunkworks: hmm
10:26 AM skunkworks: really?
10:34 AM pcw_home: if you set the following error limits up, you can see where it goes wrong (about line 939)
10:35 AM pcw_home: it takes a shortcut across the cusp
10:39 AM skunkworks: uh - look at that
10:41 AM skunkworks: .003 is fine
10:44 AM skunkworks: http://electronicsam.com/images/KandT/testing/error.png
10:44 AM skunkworks: .0003
10:44 AM skunkworks: (400in/s^2 is the axis setting)
10:52 AM pcw_home: The error is small (< .1 but greater than .01 mm)
10:56 AM pcw_home: its not an serious error if it only happens with crazy G64 P values but its surprising
11:04 AM skunkworks: yes - suprised it never showed up until now
11:11 AM pcw_home: Kinda wish linuxcnc would keep track of the peak following error
11:15 AM skunkworks: pretty easy to do with hal.
11:16 AM skunkworks: That is how I display the peak ddt'ed vel and acc
11:16 AM pcw_home: Yeah but if you have rare/flakey bugs it would be better if the peak error detection was always there
11:51 AM seb_kuzminsky: pcw_home: goood idea on the max ferror tracking
11:53 AM skunkworks: and a way to reset it
12:02 PM seb_kuzminsky: reboot? :-P
12:03 PM pcw_home: it its a pin/parameter you can just setp it like the tmax parameters
03:07 PM skunkworks: anyone around that can kick someone on linuxcnc?
03:22 PM skunkworks: thank you
03:52 PM Tom_L: freenode took care of it
03:52 PM Tom_L: it was on many channels
03:53 PM skunkworks: ha
03:53 PM skunkworks: ha
03:53 PM skunkworks: ha
03:54 PM skunkworks: ah!
03:54 PM Tom_L: it's the same guy every year
03:54 PM Tom_L: he has a beef with freenode
03:59 PM Tom_L: forever removed from the logs :)
04:02 PM Tom_L: he hit 2-3 other channels i log too
04:03 PM Tom_itx: https://encyclopediadramatica.rs/Rucas
04:03 PM Tom_L: if you really care who he is
04:24 PM linuxcnc-build_: build #4478 of 1301.rip-precise-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1301.rip-precise-rtai-i386/builds/4478 blamelist: andypugh <andy@bodgesoc.org>, joseph calderon <calderon.joe@gmail.com>
04:34 PM linuxcnc-build_: build #3092 of 1401.rip-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1401.rip-wheezy-rtai-i386/builds/3092 blamelist: andypugh <andy@bodgesoc.org>, joseph calderon <calderon.joe@gmail.com>
04:37 PM linuxcnc-build_: build #2417 of 1902.clang-wheezy-rtai-i386 is complete: Failure [4failed compile] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/1902.clang-wheezy-rtai-i386/builds/2417 blamelist: andypugh <andy@bodgesoc.org>, joseph calderon <calderon.joe@gmail.com>
05:08 PM linuxcnc-build_: build #5285 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/0000.checkin/builds/5285 blamelist: andypugh <andy@bodgesoc.org>, joseph calderon <calderon.joe@gmail.com>