Got my first cuts made with it today, took a while to get the gcode to work correctly with qt plasma c
We also added a image to dxf function, still needs some work but its a start. 
I added a kerf width calculation wizard... cut out a test piece input the actual cut size vs the wanted cut size and it calculates what your kerf width is spoused to be. I did a install on a friends computer and some of the install seems broken, need to make it more shareable if anyone else wants to easily use it. Not to shabby tho for only being 2 weeks into the project part time.  

Reading something today. Maybe try using smp affinity to lock the USB interrupt to  Core1 (away from core 0 housekeeping) and assuming > 2 cores. You can find the interrupt by
cat /proc/interrupts | grep -i usb

Then follow one of the many posts about cpu affinity for networking. Just remember you need to reset this on every boot.

Tommy are you talking about the engravertest.zip?

Ich habe keine Add-ons installiert und das Design nicht verändert. 

Firefox und Microsoft Edge haben beide den gleichen Fehler. 

Was meinst du? 

Okay, so maybe we can conclude that somehow the hardware is not 100% suitable on your "real" setup?

If you still test on the N100, I believe you could force the setupAsyncTransfer error by putting the loops back to original values (or even higher), and jogging while a program is running.

Thanks for the very quick help. Fabex is BlenderCam renamed because of a naming dispute between blender and the author(s) of the CAM add on. 1 week ago I installed the latest Blender 5.0.1 and the latest Fabex 3.0.1 from their official repositories. Due to the famously complex non standard Blender GUI I am not sure I have all the configuration and settings correct. That is why I am looking for a simple .blend file for CNC machining which ALREADY is fully set up to generate GCode.( the resultant Gcode would probably be handy too ). That way I can back check where I might be making a mistake. If you or others have already run BlenderCAM I think any simple/ non confidential file would do the trick.
Cheers and again thanks.
Alan J

In your archive there are many files, but I can see (as ncam xml files) only the default tamplate.
Please, in ncam, use the menu "Project->Save as..." to save your ncam project as xml and post here.
Are you using a milling machine or a lathe?

Regards
Giovanni

I should have stated - the limit / homing, picked off machine, home axis - trying to home one at a time, the axis moves to the limit switch and locks, need to over ride limits, move axis off limits - all axis

Eisbaeeer wrote:

Hi David
Did you get running the 2A?
Im own the version with 4 axis and trying to get the right ethercat config.
The name of driver is CL57E-4A.
I will try to expand your example to 4 axis.
Perhaps you can told me, if you get it running?
Greets Lars

I have a second driver from Lichuan called OLC-E57H. I will also try to get it running. I think this should work all in same structure (hopefully).

Its critical with multi axis slaves that the xml exactly matches the pdo structure. fire up linuxcnc and in another window, type halcmd show pin cia402* Look for the status word. (or use halshow) They all should have the same value. If they don't your xml is wrong (ask me how I learnt this)