Advanced Search

I'm interested in this as well.  I have spent many hours trying to get > 11-12 m/min smooth motion on a large format router without joint following errors and/or jerky motion.  Using the old control or TwinCAT CNC with the same servo driver config works fine at 30 m/min.

I'm no expert on LCNC internals but if RTAPI_TASK_PLL_SUPPORT is defined in linuxcnc-ethercat lcec_main.c then it appears that syncronization is attempted between the ethercat application cycle and LCNC with a max error of one app period...maybe this is where Hakan is getting the potential extra cycle delay.

Since you have the ethercat master running outside LCNC it seems like it would be difficult for those to be perfectly syncronized but perhaps that does not matter in application. I know TwinCAT is running in hard realtime on one or more dedicated cpu cores outside of operating system and with their tools you can see how much time is being used in each cycle.  It would be nice if there were a tool for LCNC where you could see that info but I'm not sure it's even possible in the current architecture.

after moving the jumper I was able to get the computer to see the device again and I thought I had it programmed but moving the jumper causes it to be not seen again... Not sure where I am messing this up but I will keep reading forums and manuals

Used old Dell Optiplex 980 in Tower version has a built in parallel port, plenty can be found for very cheap, you can probaly just yank the old hard drive and put it in the new PC and everything should work. Granted the hard drive works.

tommylight wrote:

Topic separated, finally.

... start a new topic next time.

It was for next time, not for this one, this one is fixed already.
Continue here.
Thank you.

Hakan wrote:

Linuxcnc servo cycle is not synchronized with the ethercat cycle. That adds an extra cycle delay.

Okey this is new for me ... why is there the timing setup or else ? Can you explain us more about your knowledge please?

After changes in the master version it does not start, error as in the screenshot. In the compiled version some configurations work and some do not, but maybe it is only my problem. 

I am sending a corrected ui file of qtdragon hd vertical.


I do not know if the new sim directory for vert. I have tested almost all ini configurations and they work with the vert.ui version, so it is probably not necessary.