Alec Ari
2018-10-08 02:14:40 UTC
Does anyone have RTAI 5.1 working, besides Paolo? Seb (LinuxCNC) tried getting RTAI 5.0.1 working, but the system would crash upon unloading the modules. I experienced the same issue, and other sporadic crashes, and everyone I know has stopped bothering with it due to instability. With RTAI 5.1, has this issue been fixed? I remember there was talk about violated usage of syscalls or something, could that have been the problem? Something about RTAI_USE_STACK_ARGS?
I'm a bit out of touch with the latest RTAI code, but it'd be nice to switch to RTAI 5 considering RTnet is working again, thank you Paolo for the information. Who did the RTnet update btw? I bet that was a real pain to get working with 4.x kernels.
If anyone can confirm RTAI 5 is working for them, that'd be great. All I'm looking for is just some positive feedback. RTAI 5 has re-worked calibration code (which is where I think this damage occurred) but I am a bit confused as to why RTAI needs to "calibrate" at all since latency is generally under 20 microseconds, under 5 microseconds if you don't use Firefox. Does calibrating RTAI and mucking with those values affect the latency spikes you'll get when watching YouTube videos or is this inevitable? Can anyone guess as to why Firefox causes such a dramatic and nearly instant impact on latency? After your real-time code is loaded and your threads are hard real-time, that shouldn't happen. Browsing YouTube should _always_ be a lower priority to the kernel than your real-time code and should not interfere with those hard real-time threads. If there's a delay, YouTube can wait. The most important and highest priority thread should _always_ be real-time.
Thank you!
Alec
I'm a bit out of touch with the latest RTAI code, but it'd be nice to switch to RTAI 5 considering RTnet is working again, thank you Paolo for the information. Who did the RTnet update btw? I bet that was a real pain to get working with 4.x kernels.
If anyone can confirm RTAI 5 is working for them, that'd be great. All I'm looking for is just some positive feedback. RTAI 5 has re-worked calibration code (which is where I think this damage occurred) but I am a bit confused as to why RTAI needs to "calibrate" at all since latency is generally under 20 microseconds, under 5 microseconds if you don't use Firefox. Does calibrating RTAI and mucking with those values affect the latency spikes you'll get when watching YouTube videos or is this inevitable? Can anyone guess as to why Firefox causes such a dramatic and nearly instant impact on latency? After your real-time code is loaded and your threads are hard real-time, that shouldn't happen. Browsing YouTube should _always_ be a lower priority to the kernel than your real-time code and should not interfere with those hard real-time threads. If there's a delay, YouTube can wait. The most important and highest priority thread should _always_ be real-time.
Thank you!
Alec