Yes, replace axis in the .ini file with mkwrapper in the [DISPLAY] section.
The msgd errors usually appear when a previous session wasn't cleaned up correctly. Make sure to run realtime stop before you try to realtime start again. Am Donnerstag, 17. Oktober 2019 23:20:00 UTC+2 schrieb mlampert: > > don't you also need to use `mkwrapper` as the UI, otherwise you're not > getting the UI services published? > > > On Thu, 17 Oct 2019 21:49:26 +0200 > Bas de Bruijn <[email protected]> wrote: > > > > On 17 Oct 2019, at 21:35, auto-mation-assist <[email protected]> > > > wrote: > > > > > > I can try the 4.9 kernel. Right now I have 4.4.190 loaded. > > > > > > What I have found is that whenever I enter anything into 'bind' in > > > file /etc/linuxcnc/machinekit.ini I get the errors listed below. If > > > I just leave it blank it runs machinekit with no gui just fine but > > > does not appear to output anything on a tcp connection. > > > > > > halcmd: the rtapi:0 RT demon is not running - please > > > investigate /var/log/linuxcnc.log halcmd: the msgd:0 logger demon > > > is not running - please investigate /var/log/linuxcnc.log halcmd: > > > cant connect to rtapi_app: -1 (uri= > > > uuid=3c6b50af-0fe2-4929-b0bf-0cd4b6b6c327): rtapi_rpc(): reply > > > timeout > > > > > > So my problem could be that the below is instructions are not clear > > > to me an that I don't know what to type in there yet. Im trying to > > > bind to my network card with address 10.10.20.2. > > > > > > This is the part I'm having trouble with understanding of just what > > > bind is and how to make it happy. These feel that these > > > instructions could be revised to help by giving an example of what > > > is expected and a links to the documents mentioned. > > > > > > "# -------------- interface and protocol selection ----------------- > > > # > > > # binding zeroMQ sockets and mDNS announcements are conceptually > > > separate, # but of course better add up. > > > # the default is to bind on in6addr_any (ipv4 and mapped ipv6 on > > > Linux). # see the zeromq docs - zmq_tcp(7) and the ZMQ_IPV6 option. > > > # > > > # The binding algorithm is as follows: > > > # > > > # Bind any addresses or interfaces in the BIND_IPV4 list (none if > > > empty). # if a port number was explicitly specified above, use that > > > port # else bind as ephemeral port, retrieve that assigned port > > > number, and use # that port in subsequent bind operations." > > > > > > So "Bind any addresses' > > > > > > BIND_IPV4=10.10.20.2 would seem like it should be ok but its not > > > according to the errors. > > > > I have no specific knowledge about what you should do. > > The only thing is that when I used a remote GUI, I only built with > > the configure flag for the RT-PREEMPT kernel; - -with-rt-preempt And > > change in machinekit.ini so that REMOTE=1 Never changed anything else. > > I can’t help you with more info that this :( > > > > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/75d2309a-3b3a-430c-99d1-f4b16494ddbc%40googlegroups.com.
