Advanced Search

unknown wrote:

The thing is a newer kernel will only have better performance if there has been significant changes in the area that are being used in your application. Changes to filesystems you don't use, drivers you don't or in architectures you don't use don't expect any improvements.
To be really sure you have to read change logs and stuff like that to be sure. Newer may very well be the same as what was supplied with the Linuxcnc ISO.
Oh and don't run any other network services that you use for your motion controller, in your case you should have a dedicated NIC for Remora and another for everything else.
I still don't know why people insist on using 3rd party remote desktop clients when X is actually was designed from networking from the beginning and there are plenty of available clients and servers in the distro repos that have been time tested.
Running a CNC machine remotely is a another kettle of fish. If you need to do remote admin use SSH and learn to get comfortable with the command line.

tommylight wrote:

Yes that is the correct place to put it.
While testing this, no stress test, no glxgears, no video, no youtube.

# load the Remora real-time component

    loadrt remora-eth-3.0 PRU_base_freq=500000
    loadrt base_period_nsec=100000

Debug file information:
Note: Using POSIX realtime
base_period_nsec=100000: dlopen: /usr/lib/linuxcnc/modules/base_period_nsec=100000.so: cannot open shared object file: No such file or directory
./nvem-rt1052.hal:10: waitpid failed /usr/bin/rtapi_app base_period_nsec=100000
./nvem-rt1052.hal:10: /usr/bin/rtapi_app exited without becoming ready
./nvem-rt1052.hal:10: insmod for base_period_nsec=100000 failed, returned -1
35117
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime