#linuxcnc-devel | Logs for 2018-12-11
Back
[01:02:06] -!- c-log has quit [Ping timeout: 244 seconds]
[01:03:27] -!- c-log has joined #linuxcnc-devel
[01:07:36] -!- mozmck has quit [Ping timeout: 250 seconds]
[01:23:48] -!- mozmck has joined #linuxcnc-devel
[01:53:23] -!- c-log has quit [Ping timeout: 245 seconds]
[01:55:16] -!- c-log has joined #linuxcnc-devel
[02:20:12] -!- ve7it has quit [Remote host closed the connection]
[02:51:07] -!- c-log has quit [Ping timeout: 244 seconds]
[02:53:53] -!- c-log has joined #linuxcnc-devel
[03:35:34] -!- Robh__ has joined #linuxcnc-devel
[03:51:28] -!- selroc has joined #linuxcnc-devel
[04:49:28] -!- DrippityDrops has quit [Quit: DrippityDrops]
[04:50:00] -!- DrippityDrops has joined #linuxcnc-devel
[05:52:44] -!- Robh__ has quit [Ping timeout: 250 seconds]
[06:18:10] -!- selroc_ has joined #linuxcnc-devel
[06:18:45] -!- selroc has quit [Read error: Connection reset by peer]
[07:13:50] -!- selroc_ has quit [Quit: Leaving]
[07:23:19] -!- selroc has joined #linuxcnc-devel
[07:23:35] -!- selroc has quit [Remote host closed the connection]
[07:38:59] -!- Robh__ has joined #linuxcnc-devel
[08:54:18] -!- Robh__ has quit [Ping timeout: 250 seconds]
[11:38:17] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15andypugh closed pull request #540: add to readme purpose of this software (06master...06readme) 02 https://github.com/LinuxCNC/linuxcnc/pull/540
[11:38:59] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15andypugh commented on issue #540: I think that this makes sense, it does seem the most logical place to look for a "what does this software do" if browsing github. 02 https://github.com/LinuxCNC/linuxcnc/pull/540#issuecomment-446270882
[11:44:34] -!- crazyben has joined #linuxcnc-devel
[11:48:53] <crazyben> rmu, Hello - I tried the to add #include "rtai_mutex" below #include "rtapi_app.h" and build lcec. This did solve the issue with lcec. Thank you very much!! :-)
[11:50:15] <rmu> yw
[11:50:33] <rmu> it would be nice if you could communicate this upstream
[11:50:42] <crazyben> rmu: To get ethercat (build with ec-debianize), I had to add "allow-hotplug eth0 iface eth0 inet dhcp" to my network settings
[11:53:13] <crazyben> rmu: my plan is to do so. Could you tell me what may be "good" Jitter / Latency-Times on a PREEMT-Kernel? AT the moment, I have 178.000 (Servo Thread) and 32.000 (Base Thread). These values look too high for me
[11:56:00] <rmu> you need only the "slow" 1kHz thread. I get max jitter of about 100µs on a raspberry pi 3, a properly configured PC should be (much) better
[11:57:24] <crazyben> This is a HP-Laptop with Core i5 and 8GB RAM
[11:58:59] <crazyben> Don't know how old this is, but are these still realistic references on this page?
[11:59:00] <crazyben> http://wiki.linuxcnc.org
[11:59:57] <rmu> historically laptops were not the best joice for linuxcnc because of somewhat unpredictable power and thermal management causing latencies. don't know about situation now. i would reserve the ethernet interface for ethercat traffic.
[12:01:46] <crazyben> rmu, whats the exact meaning of you last sentence? - Sorry, I am not a native speaker
[12:02:12] <rmu> german?
[12:02:43] <crazyben> Austrian?
[12:02:48] <rmu> s/joice/choice/
[12:02:52] <rmu> oh, nice, i'm from linz ;)
[12:03:06] <crazyben> Karlsruhe :-)
[12:04:33] <rmu> also auf deutsch: Notebooks sind nicht unbedingt die beste Wahl für linuxcnc, weil power- und temperatur-management dazwischenfunken können. Ethernet-Interface für das Realtime-Zeug sollte für nichts anderes verwendet werden.
[12:08:28] <crazyben> Than I already got it. Sure - I am using the LAN-Interface for Ethercat only. Due to the fact that the Ethercat driver will be loaded while Starting LinuxCNC, it seems to be necessary to configure the interface with "Allow-hotplug". Otherwise (at least on this creepy e1000e chipset and debian 9)
[12:10:16] <crazyben> won't start my interface up (Ethercat that protocoll seems to remain then unloaded). If I fon't configure the interface as described, I have to manually start up interface using "if up eth0" manually..
[12:10:40] <pcw_home> crazyben: you will get more realistic latency figures if test with servo thread only (latency-histogram --nobase --sbinsize 1000)
[12:12:53] <crazyben> rmu: regarding the performance, I am running now on powersupply again (has disconnected itselv - yes, my desk is a nightmare at the moment). running "while true ; do echo "nothing" > /dev/null ; done" I am getting now 175.000ns@Servo and 40.500ns@Base
[12:13:29] <rmu> crazyben: i know nothing about ethercat, it seems to include it's own ethernet drivers.
[12:13:59] <rmu> crazyben: try opening a webbrowser and a number of tabs, some opengl app, start a large build, and monitor latency
[12:14:10] <rmu> with latency-histogram --nobase --sbinsize 1000
[12:14:30] <rmu> you don't need the fast base thread
[12:16:21] <crazyben> rmu, indeed - I worked for a company within automation sector a couple years ago. we used the ethercat components to connect field componts of chemical and metal (steel) - industry, as they give the customer better interchange and scaleability (just add a new module if it is needed or remove)
[12:17:19] <rmu> i need to go. will check back later
[12:17:31] <crazyben> rmu, how many gears do we want?
[12:18:19] -!- Robh__ has joined #linuxcnc-devel
[12:19:20] <crazyben> rmu, I have now 4 glxgears and the "while true ; do echo "nothing" > /dev/null ; done" in the background running.
[12:33:24] -!- crazyben has quit [Remote host closed the connection]
[12:37:42] -!- crazyben has joined #linuxcnc-devel
[12:56:06] -!- crazyben has quit [Remote host closed the connection]
[12:57:24] -!- crazyben has joined #linuxcnc-devel
[13:01:44] -!- crazyben has quit [Remote host closed the connection]
[13:04:24] -!- crazyben has joined #linuxcnc-devel
[13:09:53] <crazyben> rmu: I was able to reduce jitter values now down 11145@ServoThread and 12324@Base Thread while running 8glxgears and 4 "gzip -c /dev/urandom > /dev/null"
[13:10:06] -!- crazyben has quit [Remote host closed the connection]
[13:12:20] <rmu> nochmal: der base thread ist nicht notwendig wenn der servo am ethernet hängt
[13:20:18] -!- crazyben has joined #linuxcnc-devel
[13:40:30] -!- crazyben has quit [Remote host closed the connection]
[14:23:26] -!- ve7it has joined #linuxcnc-devel
[15:37:28] -!- Robh__ has quit [Quit: Leaving]
[15:37:54] -!- rob_h has joined #linuxcnc-devel
[17:38:27] -!- c-log has quit [Ping timeout: 240 seconds]
[17:39:53] -!- c-log has joined #linuxcnc-devel
[19:50:58] -!- rob_h has quit [Ping timeout: 272 seconds]
[21:25:49] -!- Tom_itx has joined #linuxcnc-devel
[21:34:41] -!- Tom_itx has quit [Quit: Leaving]
[22:08:01] -!- gambakufu has quit []
[23:58:57] -!- ve7it has quit [Remote host closed the connection]