#linuxcnc-devel | Logs for 2019-03-22
Back
[00:22:32] -!- ve7it has quit [Remote host closed the connection]
[00:23:16] -!- ve7it has joined #linuxcnc-devel
[01:00:10] <linuxcnc-build> build #5879 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org blamelist: Dewey Garrett <dgarrett@panix.com>
[01:00:11] <linuxcnc-build> build forced [ETA 54h34m44s]
[01:00:11] <linuxcnc-build> I'll give a shout when the build finishes
[01:00:24] <linuxcnc-build> build #5880 of 0000.checkin is complete: Failure [4failed fetch branch to local git repo] Build details are at http://buildbot.linuxcnc.org
[01:02:57] -!- ve7it has quit [Remote host closed the connection]
[01:49:02] -!- c-log has quit [Ping timeout: 252 seconds]
[01:51:17] -!- c-log has joined #linuxcnc-devel
[02:28:34] -!- c-log has quit [Ping timeout: 244 seconds]
[02:31:07] -!- c-log has joined #linuxcnc-devel
[07:32:53] -!- c-log has quit [Ping timeout: 244 seconds]
[07:35:04] -!- c-log has joined #linuxcnc-devel
[08:14:34] -!- roguish[m] has quit [*.net *.split]
[08:17:37] -!- mozmck has quit [*.net *.split]
[08:22:12] -!- roguish[m] has joined #linuxcnc-devel
[08:22:21] -!- mozmck has joined #linuxcnc-devel
[14:38:22] -!- ve7it has joined #linuxcnc-devel
[15:27:06] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[15:27:06] -!- JT-Shop has quit [Read error: Connection reset by peer]
[15:27:07] -!- jthornton has quit [Read error: Connection reset by peer]
[15:27:35] -!- jthornton has joined #linuxcnc-devel
[15:27:36] -!- JT-Shop2 has joined #linuxcnc-devel
[15:28:16] -!- JT-Shop has joined #linuxcnc-devel
[16:32:54] -!- JT-Shop has quit [Read error: Connection reset by peer]
[16:32:56] -!- jthornton has quit [Read error: Connection reset by peer]
[16:32:56] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[16:33:22] -!- JT-Shop has joined #linuxcnc-devel
[16:33:50] -!- jthornton has joined #linuxcnc-devel
[16:34:05] -!- JT-Shop2 has joined #linuxcnc-devel
[18:15:39] -!- andypugh has joined #linuxcnc-devel
[19:20:52] <linuxcnc-build> build #3012 of 1903.clang-wheezy-amd64 is complete: Failure [4failed apt-get-update install-missing-build-dependencies configuring] Build details are at http://buildbot.linuxcnc.org blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
[19:21:02] <linuxcnc-build> build #4019 of 1400.rip-wheezy-i386 is complete: Failure [4failed apt-get-update install-missing-build-dependencies configuring] Build details are at http://buildbot.linuxcnc.org blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
[19:21:16] <linuxcnc-build> build #3535 of 1402.rip-wheezy-rtpreempt-i386 is complete: Failure [4failed apt-get-update install-missing-build-dependencies configuring] Build details are at http://buildbot.linuxcnc.org blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
[19:21:34] <linuxcnc-build> build #4020 of 1403.rip-wheezy-amd64 is complete: Failure [4failed apt-get-update install-missing-build-dependencies configuring] Build details are at http://buildbot.linuxcnc.org blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
[19:39:30] <skunkworks> pcw_home: what needs to be set to get DPLL working on 7i92
[19:56:06] <linuxcnc-build> build #5881 of 0000.checkin is complete: Failure [4failed] Build details are at http://buildbot.linuxcnc.org blamelist: Chris Morley <chrisinnanaimo@hotmail.com>
[20:27:38] -!- andypugh has quit [Quit: andypugh]
[21:56:48] <pcw_home> for the stepgen, something like
[21:57:05] <pcw_home> # latch 50 usec before nominal read time:
[21:57:05] <pcw_home> setp hm2_[HOSTMOT2](BOARD).0.dpll.01.timer-us -50
[21:57:05] <pcw_home> setp hm2_[HOSTMOT2](BOARD).0.stepgen.timer-number 1
[22:24:17] <skunkworks> pcw_home: thanks!
[22:41:10] <pcw_home> Ack.. new bug in the TP
[22:43:35] <skunkworks> uh oh.. what?
[22:44:01] <pcw_home> user on forum found it
[22:44:19] <skunkworks> (it really is amazing that there really has only been a handfull of bugs found...)
[22:45:20] <skunkworks> wow - I have to close some browser tabs when I cannot really figure out what I have up..
[22:45:30] <pcw_home> looks like another of those tiny move things (I think Rob E has been working on these but I dont think he's merged any of the work)
[22:47:07] <skunkworks> I could poke him.. he has been really responsive lately..
[22:47:49] <skunkworks> This laptop is at the edge with a 1khz thread.. Darn - other than that it is my perfect laptop
[22:47:50] <pcw_home> I suspect this may have been fixed but not merged in master
[22:48:07] <pcw_home> I have a picture on the forum
[22:48:30] <pcw_home> very short simple gcode triggers it
[22:48:57] <skunkworks> I sent him an email with the forum post..
[22:49:35] <pcw_home> If you dont have high acceleration, a 500 hz servo thread may be OK
[22:51:38] <pcw_home> or set the packet timeout to about 1/2 the period and use the packet error workaround and just let it drop occasional packets if it times out
[22:54:11] <skunkworks> I was letting linuxcnc run 3dchips for a few hours.. It got a realtime delay error - but no following error.. Might be just fine for testing..
[22:54:23] <pcw_home> dpll for the encoder is basically the same, just set the encoder timer number to 1 also
[22:55:11] <skunkworks> no matter what settings I tweek - it seems to have +100us latency.
[22:55:36] <skunkworks> compared to this laptop which peaks around 80us
[22:55:55] <pcw_home> What is your packet timeout setting?
[22:56:56] <skunkworks> 80
[22:57:02] <skunkworks> it looks out
[22:57:07] <skunkworks> *it looks like
[22:57:12] <pcw_home> try 30...
[22:57:25] <skunkworks> thanks
[22:58:52] <pcw_home> you may get following errors unless you add the packet drop workaround
[23:01:16] <pcw_home> This dropping slow to respond packet scheme will only work if the latency is caused the Ethernet access (it often is)
[23:02:50] <pcw_home> I sometimes wish LinuxCNC would have the option to just log a count of latency errors
[23:02:53] <skunkworks> Cool - I will play with it
[23:03:17] <skunkworks> rob says he has a pull request..
[23:04:32] <pcw_home> also following error for warning, and following error for stop
[23:04:44] <skunkworks> that would be cool...
[23:04:58] <skunkworks> your following error is above x.xxx
[23:05:57] <skunkworks> That could be done in hal though.. the stop would be the normal ini setting - the warning could be just a hal trigger
[23:06:08] <pcw_home> also memorize peak following errors
[23:06:58] <pcw_home> yeah most of this could be done in hal but it would be nice if it was always there for debugging
[23:07:04] <skunkworks> sure
[23:10:15] <pcw_home> a pull request means Rob needs a LinuxCNC developer to merge it?
[23:22:54] <skunkworks> yes