Advanced Search

Thank you jjdege.
Schaublin12: du müsstest die xml nur noch etwas anpassen. So in etwa:
Die Pins findest du dann in der Halshow

Doing some work on multiaxis improvements.

github.com/LinuxCNC/linuxcnc/pull/4374

Would love to get some feedback and testers if anyone had time, appreciate it.

Most interesting stuff at this stage might be G53.5, usefull to always lift the Z slide (joint 2) all the way up
G53.5 G0 Z0 (always move joint 2 all the way up regardless of tilt orientation)
and G53.7 Jn=nn
A gcode to move joints instead of axis, for robots and such similar to MOVJ in other controllers.

If you have a 5axis or a robot let me know what you think

Becksvill wrote:

Ecam.it which is another really good turning cam software in my opinion offers the software free for weekends. 

Did you mean e-cam.it ?
I found only 14-day trial and nothing about weekends.

We need to know who still uses the drivers that only work on RTAI kernels. They are all old ISA/PCI/parallel-port cards:

• Servo-to-Go (STG)
• Motenc
• Vigilant VTI
• Siemens EVOREG
• Axiom AX5214H
• Opto22 AC5
• pci_8255
• Advantech PCL720
• Pluto-P (pluto_servo / pluto_step)

If you run any of these cards with LinuxCNC on an RTAI kernel, please post here with the card name.Pluto-P is a special case: its drivers can likely be made to work on regular preempt-rt installs, so if you have one and are willing to test, please say so.Technical background: github.com/LinuxCNC/linuxcnc/issues/4505

Some computers are not suitable for LinuxCNC, not because they are too weak, but because they save energy without taking into account the costs.
If the processor heats up and is turned off for a few milliseconds, you will not be able to control any machine with it.
I like to experiment and although I don't recommend it to anyone, I installed properly working LinuxCNC (2.10 on Debian 13) on Wyse 3040 (Atom X5-Z8350 2 GB RAM and 8 GB "disk"). It lags a bit if you run several programs at the same time, but LinuxCNC with Mesa 7i92 works flawlessly.
For work I use AMD A10, both for Mesa and Ethernet. No problems.
I tried Ryzen 3 2200G and Ryzen 5 3400G, they work better, but they lost compared to AMD A10 in terms of dimensions, because they don't fit in a backpack, and that's what I care about.
So it's more of a lottery, a computer for LinuxCNC doesn't have to be very powerful or very expensive, it just has to fit.

Ok, so for the first test I will use a mesa card, since I don't want to mess with the original motor drives. However if we decide to use Linux CNC multiple machines may be converted, therefore the hassle implementing ethercat is valid. Am I right when looking for a PC that has a Intel nic and 8th gen i5? Is Linux CNC able to do collision detection of the machine gcode?

hey one idea for you that i have seen

Ecam.it which is another really good turning cam software in my opinion offers the software free for weekends.  

can you try a free trial without credit card or anything.  just so i can quickly try it?

cheers

Andrew

You did not give linuxcnc-ethercat version


github.com/linuxcnc-ethercat/ethercat/releases
github.com/linuxcnc-ethercat/linuxcnc-ethercat/releases

I made arm64 debs as well...

syncToRefClock="false" without a refClockSyncCycles means free mode, don't use with axis.

syncToRefClock is going away because it is confusing, use refClockSyncCycles=-1 if you want to test having the pi sync to the clock on the drives, in your case it does not seem to work, should be same as syncToRefClock="true" but test with latest version.

refClockSyncCycles="1" if your latency is decent is a good choice.

5 axis is certainly a bit off the beaten track. You might want to try on the linuxcnc discord server or on a forum that caters more to 5axis machining and CAM applications. I'm afraid I don't have any links for you though.

Here   you have a good example of the xml file for Beckhoff devices
Hi

quark wrote:

 If you know somebody who might be a fit or would be interested yourself, I would love to hear from you. 
 

Contact details?

tommylight wrote:

Not me, despite really needing the money, i never charge for any help here or when initiated from here, and i am of no use for Probe Basic, yet.
For other things related to LinuxCNC, i am here often and daily, so feel free to shoot questions here.
 

You're Mr. Helpful, Tommy - no sarcasm at all.

I suspect the OP has an issue with the Probe Basic ATC control scheme not meshing with their hardware.  Same thing I ran in to when I was setting up my mill - I don't have a 'dumb' on/off motor with geneva drive, so the ATC subroutines aren't gonna work.

I'm betting that as a business they would rather spend money to get things sorted than go back-and-forth over the forum for days/weeks.  Regardless of how awesome the forum members are, sometimes you just want to buy your way out of a jam.

Tinker wrote:

...but it just runs as soon as i enable it.

Does it run slowly or at full speed?
If the drive and motor are a set, do not try to tune them before making sure that is the issue, for this:
-disconnect the analog drive input from Mesa
-connect those two wires together
-power on the drive
-enable the drive
>>>does the motor turn slowly ?
-If yes = move on the drive is fine
-If no = first thing to check is Tacho wiring and brushes, then check motor brushes (if any).
>also check the commutator state for both, if there are signs of sparking on tacho = change tacho and check the drive output to tacho for whatever signal it should output. Rarely an issue, very rarely.
-Use compressed air to blow the brush holes and do not breathe near it
-And VERY important, return the brushes in the same hole you got them from, in the same direction and orientation.

I think i might have a drive issue, the encoder counts are working but it just runs as soon as i enable it. The drive for the 4th is from another machine and i thing i need to break my oscilliscope out and actually tune it per their directions. Im going to get that squared away and then start messing with the software side of it.
Thank you again for all your help!!!!

Looks OK, but i have not used it.
I did use PyCAM several years back, it was terribly slow to generate code but easy to use.
I wonder how fast is this at generating code...