#linuxcnc-devel | Logs for 2018-11-16
Back
[01:02:58] -!- ve7it has quit [Remote host closed the connection]
[01:07:52] -!- c-log has quit [Ping timeout: 264 seconds]
[01:10:01] -!- c-log has joined #linuxcnc-devel
[01:25:47] -!- c-log has quit [Ping timeout: 240 seconds]
[01:27:48] -!- c-log has joined #linuxcnc-devel
[01:40:16] <linuxcnc-build> build #574 of 4031.deb-stretch-rtpreempt-amd64 is complete: Failure [4failed shell_3] Build details are at http://buildbot.linuxcnc.org blamelist: Dewey Garrett <dgarrett@panix.com>
[02:12:04] -!- c-log has quit [Ping timeout: 244 seconds]
[02:13:44] -!- c-log has joined #linuxcnc-devel
[04:50:48] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15rmu75 commented on issue #213: In this case ("a real servo system") jitter of the host clock should not matter that much, because the HW could sample the encoder and latch new velocities at it's own clock ticks. The host just has to do the calculations anytime between these two clock ticks, using the timestamps of the HW. ... 02 https://github.com/LinuxCNC/linuxcnc/issues/213#issuecomment-
[05:00:20] <rmu> is something like this possible / does it make sense with mesa hw: use the dpll to synchronise an internal clock to the servo period, and trigger sampling of the encoders / smart serial write/read, latching of n new velocities etc... from this clock?
[05:07:13] -!- c-log has quit [Ping timeout: 244 seconds]
[05:09:32] -!- c-log has joined #linuxcnc-devel
[07:58:21] <rene_dev_> thats what the dpll does
[08:09:22] <rmu> rene_dev_: you can also use it to latch velocity or other values and trigger sserial?
[08:09:49] <rmu> seems i have to build a 7i90 spi config with dpll enabled ;)
[08:52:28] -!- JT-Shop has quit [Read error: Connection reset by peer]
[08:53:01] -!- JT-Shop has joined #linuxcnc-devel
[08:53:22] -!- JT-Shop2 has quit [Read error: Connection reset by peer]
[08:53:26] <rene_dev_> I dont think so. but at least for the stmbl you dont need that
[08:53:40] -!- JT-Shop2 has joined #linuxcnc-devel
[09:14:22] <rmu> I think current code (stepgen) assumes that new velocities are applied "immediately", not at the end of the servo period.
[09:35:41] <rene_dev_> yes
[09:40:15] -!- JT-Shop has quit [Remote host closed the connection]
[09:41:16] -!- JT-Shop has joined #linuxcnc-devel
[10:48:18] <pcw_home> you can correct for some of the delay between read/write with FF2
[10:51:02] <pcw_home> but for normal systems with moderate acceleration the errors as so small anyway that its probably not worth bothering with
[11:57:55] -!- ve7it has joined #linuxcnc-devel
[14:17:51] -!- jthornton has quit [Read error: Connection reset by peer]
[14:18:17] -!- jthornton has joined #linuxcnc-devel
[15:58:04] -!- andypugh has joined #linuxcnc-devel
[18:12:43] -!- KimK has quit [Quit: Leaving]
[18:49:35] -!- mozmck_lp has joined #linuxcnc-devel
[19:17:24] -!- mozmck_lp has quit [Quit: Leaving.]
[19:58:56] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[20:26:51] -!- andypugh has quit [Quit: andypugh]
[20:43:22] -!- mozmck_lp has joined #linuxcnc-devel
[21:05:12] -!- mozmck_lp has quit [Quit: Leaving.]