#linuxcnc-devel Logs

Oct 23 2019

03:34 PM skunkworks: pcw_home: you around?
03:38 PM skunkworks: Huh? Are you?
03:38 PM skunkworks: I finally got a shot of the following error - it seems odd.. You can see the phase error drop and then following error. then phase error turns into a triangle wave..
03:39 PM skunkworks: http://electronicsam.com/images/greenmachine/2019-10-23-152359_1920x1080_scrot.png
03:39 PM skunkworks: there was no packet errors
03:54 PM skunkworks: I disabled the dpll and am running for grins.. following error has leveled out at .0005" so far. Much worse than with DPLL of course..
04:26 PM skunkworks: well - now .0008"
05:53 PM Tom_itx is now known as Tom_L
05:54 PM skunkworks: seems to be maxing out at about .0009
05:54 PM skunkworks: no spikes
06:37 PM skunkworks: I don't understand.. Servo thread doesn't take too long, read/writes seem ok...
06:37 PM skunkworks: http://electronicsam.com/images/greenmachine/2019-10-23-182058_1920x1080_scrot.png
06:37 PM skunkworks: http://electronicsam.com/images/greenmachine/2019-10-23-182801_1920x1080_scrot.png
06:40 PM skunkworks: it is like - when the times go down - there is an increased following error
06:44 PM skunkworks: like this -
06:44 PM skunkworks: http://electronicsam.com/images/greenmachine/2019-10-23-183528_1920x1080_scrot.png
06:44 PM skunkworks: the following error seems to happen when the fuction times are at the minimum
06:45 PM skunkworks: (servo thread, mesa read/write, motion)
06:45 PM skunkworks: it seem odd to me
09:56 PM pcw_home: skunkworks: looks like the DPLL lost sync, might be that there are too fast changes in the average delay so the DPLl time constant needs to be lower
09:58 PM pcw_home: The interesting thing is what happened 1 and 3/4 divisions from the left edge (I suspect a clock adjust )
09:59 PM pcw_home: (TOD clock adjust from the host)
11:21 PM skunkworks: how could i catch that?
11:25 PM skunkworks: I dont really see anyhing that is causing the f error.. (no realtime delays or such)