Advanced Search

Spindles are typically controlled through the NML interface by the GUIs, so if the GUI doesn't support multiple spindles you might have to use MDI to turn on and off the auxilliary spindles.

THat said, flexgui is mane to be flexible, so maybe there is suopport?
I haven't used it yet.

Here are the 2 screenshots of the Pi. One whithout anything but the Desktop running, one with glxgears running (window resized to about the double).

You might have problems with tool radius compensation if you use the orientation, but only if you are doing compensation in the control rather than in the CAM.
So, basically, as a purely graphical fix, it will probably work.
You will need to have different orientations in the CAM tool table and the control tool table, but there is no auto-synching anyway, so that's not a problem.

Hello everyone

I've been working on a web UI for LinuxCNC for my own use and thought I'd share it in case anyone finds it useful. Note that I'm not a professional programmer and this was largely AI-assisted, so take it for what it is.

Greetings

github.com/bildobodo/lcnc-suite.git

       







 

So,

I have a great update. I got the machine working. Using the X-minus hall switch did not do the trick. Testing everything that I already thought was not the problem gave me the solution. The magnetic linear encoder in the X axis was the problem.

I did most of the testing of it at low speeds and short distances, as my indicators obviously cannot measure the length of the full axis. I can remember doing a test running the whole axis at rapid speed for multiple minutes, but I may have done this only on Z, it was two weeks ago. Or it got worse somehow, I don’t know.

In the end, using the motor encoder resolved all the problems.

I also disassembled the X axis to see how the encoder is installed. There is a very small read head in the plate behind the thrust bearing for the ballscrew and a putted scale in the underside of the X-axis slide.

I also made some pictures of the Z-axis encoder.

And then, after I spent all day getting this done, I was able to actually make op 1 on the test parts I wanted to make as test parts.

I've equipped the A6 with a battery-powered encoder cable.
No homing, no problems.
However, I would also recommend the following thread:
forum.linuxcnc.org/ethercat/58103-etherc...fix?start=160#345453

You will need to modify the gearbox comp and recompile it. I didn't write it myself, it was written for me by a friend, so you might need to find someone to do the code changes.

Tested a bit.
I get fairly consistent loading times of lcec's rt_app_main() function of 1.85-1.90 seconds.
But but. In syslog I can see that the initial sync of slaves takes anywhere between zero and
say 3,4,5 seconds. 
To check
ethercat debug 1
start linuxcnc
exit or leave running, doesn't matter.
sudo journalctl --since "2 minutes ago" | grep "Sync after"
and see where it stops for every slave.
I reckon this is the problematic delay time.
Seldom, but it happens, I get "Checking for synchrony" and then it is satisfied directly and moves on.

It seems measuring the time of lcec's rt_app_main is not a good indicator.
Is there a good way of measuring time to OP?

trixie, 
Linux plasma 6.12.69+deb13-rt-amd64 #1 SMP PREEMPT_RT Debian 6.12.69-1 (2026-02-08) x86_64 GNU/Linux
IgH EtherCAT master 1.6.8 1.6.8.g2543cc5-1+27.3  (via apt)
linuxcnc-ethercat, a slightly modified version of commit bf13577ec7b1b54844e07a80d949232e71776b32
linuxcnc 2.9.4 (via apt)

 

I have installed linuxcnc-ethercat...0.9.5-retro1.5.2-rc1, without error, but if coomand ethercat version have reult 1.6.9
But I think, this is not the Igh part, but the lcec driver, right?
I have a version running in place in another directory, do I need to copy or link something to test?
On Debian 10 , in direcory bin the linuxcnc , i have only lcec_conf and not have lcec_coffingen

Syste is debian 10 buster x86_64
Kernel: 4.19.0-27-rt-amd64 #1 SMP PREEEMPT RT Debian 4.19.316-1 (2024-06-25) x86_64 GNU/Linux
Ethercat : IgH ETHERCAT master 1.5.2 unknow
Etherlabmaster-1.5.2+20190904hg33b922p8ea394
LINUXCNC 2.9.0-pre0


When axis opens the gui, the axis dimensions are already present. From tests done, when I had the same problem with debian 12, as soon as it reads the loadrt lcec command, the dimensions appear on the pins in hal, relating to the individual axes.

Update on this:
(a) I have connected 220v power to the machine and have confirmed that the drives and servos all work. I will be able to use this machine in its entirely with 220v single phase input on 12HP spindle (will run it at 4hp max) and run all the drives  (8 of them, XYYZ, AA BB). These old amp drives were set up to run the DC brushed servo at max rpm if the signals (10V,tach,EN) were all OPEN - sort of insane. Thankful I had the foresight to disconnect the ballscrews from the servos. I don't have workspace - working ON the bed of the machine with the controller. See pic. Could have been a final destination sort of outcome. 

(b) Hunted down faulty monitor display to a few bad connections and once those were fixed, my LCD display is actually perfectly good, this allowed me to actually test out the machine's ability to work. The linuxcnc mindhive (grumpy old dudes who have forgotted more shit than I will ever learn) helped me out immensely like with everything else. Have to look at the fagor 8055 manual to understand what to expect from triggering the limit switches but other than that, I have a big functioning CNC router. There is some weird stuff going on which I do not understand - the servos are not paired corrected, meaning, moving "controller Y" physically turns one X servo and one Y servo. A few wires need to be fixed and I need to make sure stuff turns in the right direct and get synced and what not. Maybe its a controller setting. I have no intention of using the Fagor controller and will likely not waste time on it. 

(c) Mechanically, Y axis is good. Z axis is good. the X-axis is "grinding". Will remove rust with neutralized citric acid and starch to get me a chelating paste. and repack the bearings on the X axis. I hope it is not a bad ball screw. The blocks that glide on the linear rails are these things that have 2 rows of bearings that slide along the groove. I have no experience whatsoever with these. Any and all tips super appreciated.

(d) Ordered my 5in rotaries. Found this design where the 5in chuck is connected to a wormgear with 20:1 reduction. backlash (10arcs) seems acceptable. The reduction gives me holding power that will all but eliminate any issues with holding the word steady. Adding up the 2 chucks, I'll have in the region of 200Nm of torque on my work pieces. Happy about this. 

(e) Gambling that it will be OK to hang 200lbs off the gantry for the swivel head + spindle. Found some implementations of this with older heavier hardware so I'll take my chances. I might have to upgrade the air balancer, or add a counter weight to the gantry. In any case, its too late. Stuff is ordered and they don't do refunds.

(f) Fun times. The entire manual for my spindle contains one single word of English. It says No! on page 19. See attached. Everything else is in Chinese that I can't read. Hopefully AI translation is decent. Same company with spindle and swivel head. Very happy to have found them. Not pushy. Don't give bullshit answers. Take pride in explaining stuff in engineering speak. Feels like a bunch of guys trying to make the best damn product they are capable of making.

Some questions that remain:
I wonder if I can reuse the dynamic brake and reactors. They are rated for the amperage that I will use with my 9kw spindle. I don't see why not, but I do not know for sure. I also don't understand from first principles what a reactor does. I think they are inductors to smooth out ripples in the outgoing current from VFD to spindle.

Grease. What should I use? I wanted to change the color of the grease so I know which lines are blocked, but someone cautioned against mixing stuff.

Ball bearings. Should I just put new ones in while I'm at it, or, do they last a lifetime? Do I caliper them? Is it even meaningful to? Surely the precision needed would be far more than my 0.02mm caliper. 

July 4th. This has to make a chopstick by then.
 

OK I guess I got too swayed by the "homing" in the title when in fact this looks like a C axis
programmed path where the "steps" are real.

It basically looks like  the acceleration is too high to the spindle to follow. This may just be physics
(inertia vs spindle motor torque) or programming (some acceleration limit set in the drive)

@Hakan @papagno-source
I get worse OP times with 1.5.2
Is that the case for you as well?
Do you have a kernel + linuxcnc + linuxcnc-ethercat + ethercat
versions combination that gets everything ready sub 1 sec?
Before axis opens or just as axis UI opens up?

gitlab.com/grandixximo/ethercat/-/jobs/1...ad?file_type=archive

Here have debs of ethercat 1.5.2 compatible with debian 13

github.com/grandixximo/linuxcnc-ethercat...0.9.5-retro1.5.2-rc1

and here a linuxcnc-ethercat compatible with the 1.5.2 retro release

you need to type in the mac address and use generic in the systemconfig/ethercat file, in my test OP is same speed, please test on your end and let me know.

linuxcnc-ehtercat retro version I only tweaked latest version based on Sascha's work, and did minimal changes to be compatible with retro 1.5.2 ethercat

I'm trying to revisit this again. (and still failing)

I am trying to insert the Gladevcp Offsetpage widget into a tab in the Axis user interface. The tab and Offsetpage widget are opening and seem to function (sort of), but it is showing all offsets as zero. I can use the edit button in the widget to set an offset to some value, and that offset is set to that value in Linuxcnc. The problem is that the widget will not see what current offset values are or are set to by other means in Linuxcnc.

What am I missing to make the widget read the current offset values from Linuxcnc?