Advanced Search

Again, something is not OK if you can change values of FFx and get no change in response, so are the drives set in "velocity" or "torque" mode?

The encoder came in and would like to ask what is the best ppr setting to select? I will have max 3600 rpm and i want to do rigid tapping.

rotational speed (at each
resolution)
192, 384, 400, 500, 800, 1000, 1024, 2048 7500 RPM
48, 96, 100, 125, 200, 250, 256, 512 15000 RPM

giaviv wrote:

However I’m a bit limited by the low ram (8GB), low disk space and etc.

8GB should be fine, and how low is "low disk space"? Linux starts complaining only when you get under 1GB of free space, so anything above is fine.

giaviv wrote:

I realize newer models are risky, therefore some of the models I am looking at are far from new generation CPUs (like the Ryzen5 7535U)..

7535U is not "far from new", it is new and still in production, Zen3 with 15W TDP, so it is a laptop CPU and this may be bad for latency, although not always.

giaviv wrote:

Or is CPU not the only potential issue, but also things like the motherboard etc?

CPU's are mostly fine as they can change states and do stuff, mainboards are usually the latency killers depending on quality, BIOS implementation, power saving options, etc, etc, way to many to list here, but mostly bad/weak CPU power stage set to work at the edge and throttling the CPU to save itself from going up in smoke.
-
As a general rule, i would stay away from those small PC's, they are cute and stuff, but way to limited thermally, the xxxxU versions are fine, but a 13900 ... oh hell no, it will be limited thermally to something like a good 4 core CPU when under load, and they fail but being limited will prolong their life a lot so...
There were some NUC's that were OK for LinuxCNC way back.
After all this, there is no way to know for sure if any of those will be OK, short of buying and testing.

I'll try to have a look at the '9D' branch later. Thanks.

which I got not much feedback..

Just as a word of caution from my own experience:
You mustn't expect to much from a forum thread like this. Few people will even read a post that long, fewer still look at the code and hardly anybody will even try to understand it. I know of at least one long time contributor, since retired, who got quite bitter about trying to get sustained and involved feedback here. Even from the very people asking for the specific feature.

Many of us run systems with much lower spec CPUs, like Celeron J1900, i3-6100, N100, N150 with good result. 8GB should be plenty.

What does your latency-plot look like?

This is a good opportunity, but how do I configure these inputs and outputs? I tried different *.xml files, DeASDA and generic. The pins are in the HAL, but the servo drive does not respond to them. ASDA software controls it normally.

i think you mean: 2.9.8

you can try this with running linuxcnc:

halcmd show | grep spindle

and see if there are some spindle pins

Hakan wrote:

38? -3 here.
What made it work?
 

Actually hit 41.8 deg C here today so a bit hotter. (Therefore I did not get that much done!)
I cheated and only moved the one working motor for the video oops!
I saw that: Modes can be switched while the drive is in the "Operation enabled" state
Probing could also be handy.
I'll keep you in the loop

I’m on the latest version 2.8.9

oops 2.9.8, thanks 

Thanks for the reply! I’ve done all that so I believe my G2 is optimized for LinuxCNC.

However I’m a bit limited by the low ram (8GB), low disk space and etc.

I realize newer models are risky, therefore some of the models I am looking at are far from new generation CPUs (like the Ryzen5 7535U).. Or is CPU not the only potential issue, but also things like the motherboard etc?

Sorry for abandon the thread.
Sadly the project/product I had in mind to produce with it turned out to be next to unsaleable, so I had to cut my losses and end.

I think best bet is to keep the G2 and try to optimize it for LinuxCNC.

1.) Disable all power saving options in the BIOS
2.) Update your grub CMD line to include: max_cstate=1 idle=poll isolcpus=(your last CPU core)
3.) Set up IRQ affinity (see below)
4.) Disable IRQ coalescing (see below)

forum.linuxcnc.org/38-general-linuxcnc-questions/47974-grub

forum.linuxcnc.org/38-general-linuxcnc-q...irq-affinity?start=0

forum.linuxcnc.org/38-general-linuxcnc-q...g-for-intel-ethernet

A newer or more modern PC can be sometimes worse and it's a bit of a gamble if it works out of the box.

Once you address 1 - 4 you are in control on how well your PC works with LinuxCNC.

Hi,
For your information.
Stepperonline recommends this noise filter for the A6 servos:
SCHAFFNER FN2090-16-16
 

I’d like to replace my weak HP EliteDesk G2 on which I currently run LinuxCNC. In my setup, the PC drives a Mesa 7i95t over ethernet, and displays a LinuxCNC UI on a monitor. Form factor is important since the PC is only used for LinuxCNC.I’m looking at various options for ~$800 range mini PCs, but am struggling to understand how they will perform in a realtime environment. Some of the options are:

• Beelink EQR7, cpu: AMD Ryzen5 7535U
• Beelink SER9 PRO+, cpu: AMD Ryzen7 H 255
• GEEKOM GT13 Pro, cpu: Intel Core i9-13900HK
• ASUS NUC 14 Pro, cpu: Intel Ultra 7 155H
• MINISFORUM DeskMini UM870, cpu: AMD Ryzen 7 8745H

Could someone please help shed some light on how to evaluate whether these models will perform well running the LinuxCNC realtime environment?

Thanks!

38? -3 here.
What made it work?

Don't know why they don't allow switching between csp and csv.
You switch to homing mode and back, so you do switch modes on the fly.
Had a guy in here that switched modes, although he switched between two cia402 components,
one was Dominik's for CSP and one was mine for PV mode (mostly a quick hack github.com/MetalMusings/cia402pv)

Searched and found many drives that allow dynamic switching while in op-enabled.
That's not a proof it is universally allowed, at least it isn't forbidden.

The current component is quite limited in that respect. It could support CSP, CSV, PV, PP, Homing, maybe also Torque Profile mode.
The main difference is which pins are active as inputs and outputs I guess. Plus the feedback position/velocity/ferror