Bas de Bruijn

very useful for the following problems too: [external synchronisation of HAL threads not possible #70](https://github.com/machinekit/machinekit-hal/issues/70) [triggered RT execution of HAL function chains missing #63](https://github.com/machinekit/machinekit-hal/issues/63) [HAL lacks filedescriptor-based eventing mechanism #82](https://github.com/machinekit/machinekit-hal/issues/82)

@cerna I have made a component some time ago that encodes pins in a sample protobuf message, and puts that message in a record of a ringbuffer. That ringbuffer you...

@cerna The entire ringbuffer idea was exactly about having communication between realtime and non-realtime. So components are not exclusive here. iirc there's a zero copy mechanism, and the ringbuffer is...

> On 10 Dec 2018, at 18:19, ArcEye wrote: > > The push recently for low latency rt-preempt on amd64 with isolcpus and cpusets, negates multi-core and v2 in favour...

You should first get a debug log by `export DEBUG=5`, restart have a look at `/var/log/linuxcnc.log` as stated in the error message. Then share that sessions output so we can...

I have the same problems, an interactive halrun session, with debug level 5 is unworkable

> On 30 Sep 2019, at 00:51, Michael Brown wrote: > > Playing the ketchup game: (catch up....) > Porting these new hostmot2 SW additions evolvements and bug fixes from...

> On 30 Sep 2019, at 03:29, Michael Brown wrote: > > Well to be totally honest: > I may have startled somewhat when I noticed that the Mesa-dev team...

I will look if this is still needed, since some changes have been made in the past. I know mhaberler made some changes regarding the stepgen, encoder and muxed encoder....

personally I would not remove it since it does not hurt. If you remove it then you will break api heavily for components and existing configurations. is that worth it?