Advanced Search

It's based on the execution time between two processes which is not guaranteed to align well in all systems, it may be ok on some hardware, very little difference, and completely random on others.

Yup. there's files an info.. somewhere.. in there. haha.
I have not looked at the 229 stuff in 7 years sadly, so its all erased from my brain.

latency is not fine tuned or incredibly stable.

It's actually a realtek interface. I don't think this is luck. I've cycled the machine probably 1000 times and never seen anything of this nature. Literally never even hear of the issue before and I know a number of people on ethercat/linuxcnc (tormach 1500 people included). And this was all news to them.

I've forwarded some info to the people that make the stepperonlione servos to see If they have any thoughts - and one of my customers is setting up their kit at the moment.

I find this all... peculiar to be simply random.

ihavenofish wrote:

What network interface are you using? Beckhoff only really supports a few intel select chips for ethercat. They flat out block realtek in twincat for real time motion.

So I want to know if there is a strong indication people with these issues are on unsupported network interfaces, or it's happening across all of them including the intel 210/211

Thanks.

The real explanation why Beckhoff block Realtek NIC's is they use about 30% more system memory than Intel NIC's which can't be good for real time performance. However, I have never had issues with Realtek NIC's when properly configured regardless if they are driving Ethercat or mesa devices.

Its not enough today to just install linuxcnc and Ethercat and expect things to work. The kernel and NIC has to be tuned for optimum real time performance and that is something of a black art that is not well documented anywhere.

I offer kernel tuning services to manufacturers and have an installer that fully configures ethercat and tunes the kernel. You just need to add your config and plug in your slaves. If interested, reach out here mrrodw.au/ or via the email on my Youtube channel. www.youtube.com/@mrrodw 

Right now the only way to get 2.10 is to build it from source. But later Operating System versions like Trixie need careful tuning to get the kernel running smoothly in a real time environment. This is not easy because there is no single source of information about how to do this.

People definitely need help with this and I have a solution.Today I just completed custom Debian Trixie ISO's for v 2.10 and 2.98 that do something which I never thought was possible. That is to tune and configure the kernel for best real time performance after its up and running on your PC. In other words, install my ISO and you are ready to go with no further effort.

This is a spinoff from my MrRodW Youtube channel which is now a Youtube Partner.. There is a cost for this and it also requires a monthly subscription (which also includes membership to my Discord channel). The subscription is there because I know people will need support. I have some commercial clients who have paid me hundreds of dollars for the same service.

If joining the MrRodW Shop Crew appeals to you, head over to mrrodw.au/ or to my Youtube channel www.youtube.com/@mrrodw, grap some merchandise and a ISO.

I have several projects using LinuxCNC 2.10 on Debian Buster. However, the buildbot.linuxcnc.org site is no longer active. How do I update from LinuxCNC 2.8.4 to 2.10?

The initial resonance could be something with the drivers internal PID unless you are running in torque mode?

If you run in position mode, probably something with the gain of the servos.

If you have not experienced any grinding noise, it maybe that you have incredibly stable latency, or your hardware is incredibly fine tuned, and you have it well dedicated and setup to run only linuxcnc. But there is no question that the original linuxcnc-ethercat, including the last stable release by Scott, has issues, this is confirmed by all core developers, the original code previous my PR to master has random phasing, if your hardware was somehow able to keep the phasing, it was just luck, not because it was setup to be in sync.

I use intel 210

Never experienced looping OP, not sure if it's related, did you give a test to my version?

Did a bit of digging. not related to my issue, but a trend did seem to crop up and Id like to see if it holds as it might start to narrow down the search for a solution.

What network interface are you using? Beckhoff only really supports a few intel select chips for ethercat. They flat out block realtek in twincat for real time motion.

So I want to know if there is a strong indication people with these issues are on unsupported network interfaces, or it's happening across all of them including the intel 210/211

Thanks.

I've never experienced any form of gravelly sound in my servos.

I do get the servos resonating under linuxcnc, when they are stable in the omron software. Is this the same core problem, or is it unrelated (a different bug)? The resonance goes away when moving above a few inches a minute.

My only other issue is sometimes there is a timing issue on start up where the drives will repeatedly cycle op states. happens on in 10 starts maybe.

meister wrote:

I still have to port it to the main branch, but it already works in dev.

www.youtube.com/shorts/7ieYCgcRN9Q
 

Do you have an example config for this setup? I just installed the dev branch and wanted to try out the modbus spindle control with buttons like that video but I wasn't sure what plugin to use and how to connect the hal. Dev branch is looking really good btw, I am really excited to try out the remote devices over rs422, I was thinking of building a plasma controller for a THC to start with
 

Fix was entered into 2.9 and master on Jan 9th

github.com/LinuxCNC/linuxcnc/commit/f0e3...fdb6f4768798b4bf4be2

Chris

I'm just using the default x1 for this but good to know for down the road.

I've finished moving all the other inputs over and they are all working again. Tomorrow I'll get the outputs moved over and then I can work on getting the spindle and it's encoder connected which is what started all of this in the first place.
Simulating a VFD / encoder on the bench is proving to be a lot more work than I originally thought.
M

To get the variable voltage, you set up the TB2 PWM output for spindle use in pncconf
The 7I96S manual shows the TB2 pinout of the analog output

7I96S Spindle + goes to a 10 or 12V supply (on a VFD this comes from the VFD itself)
7I96S Spindle out is the 0--10V analog voltage that goes to the Drives VIN
7I96S Spindle- goes to the drives COM pin and the negative pin of the 10 or 12V supply

Here
forum.linuxcnc.org/30-cnc-machines/32276...29-adventure?start=0
?

unfortunately i dont have that info hand. it is probably in the tc229 thread.