Advanced Search

The problem is this:

Region 0: Memory at fce00000 (32-bit, non-prefetchable) [disabled] [size=64K]

Which is likely something the BIOS did so may be fixable if you have access to BIOS PCI settings
I will take a look into what is needed to get mesaflash to re-enable the memory region (lLinuxCNC does this)

BryceJ wrote:

Ran into an issue with IRQ balance after updating to trixie
 

Late to the party but currently best practice is not to use irqbalance. the balancing is now managed internally in the kernel so adding a second balancer can confuse things.... but it worked here....

Here we are! I super appreciate it...so does my wife   Ive been trying to make this work all day

I once set a digital input in my probing sequence that was and2'd to the probe signal to stop this.
I think a better way would be to use motion.motion-type = 5 to signify probing was in use and disable the signal if this is false.

andrax wrote:

and even professionals sometimes find it frustrating.

Sometimes????? More often than that! 

why jog before homing? I always disable it.

Can you do a

lspci -vv  | grep -A 10 2718 > pci.txt

and post pci,txt here?

 

I tried to follow your instructions, and it works ok for me.
I suspect it maybe something with the custom tool table which is missing from default, could you share that?

Linuxcnc Version?
IMO this is a bug in the source code, i have this error disabled in the codebase I use for work

I understand your concern now. I only use probing to find my Z height. X/Y is handled by a crosshair laser. Once centered on the starting position of the cut, a button attached to g-code computes the actual position by applying offsets for both X and Y to the current location of the laser. Offsets are stored in my INI file and can be changed if needed without touching the code.

Er, no. It’s not that simple; LinuxCNC isn’t plug-and-play. If you don’t have any prior knowledge, you should put the A6 aside for now and start with simple stepper motors. You’ll first need to learn how the system works and what each component does. With EtherCAT, you’re moving beyond the hobbyist level, and even professionals sometimes find it frustrating.

Hakan wrote:

In what way do you see 2x50k as a better way than 1x100k?

 

Keeps the high power stuff more isolated in case of wire break/short, making it much safer.
I always put those 3 resistors on the plasma source of in a box behind it.

yes, mesaflash still says 5i25 not found

 

Did you try running mesaflash after running LinuxCNC?
 

The problem isn't the 50ms, it's that during that time the machine is *moving*. I.e. where you home depends on the bouncing of the sensor, which means it's unpredictable, which means every other position is also unreliable.
If you "hit" on the first contact, instead of waiting for the physics to settle down, you get a more predictable "moment" when the machine is in the known state.
You'd think it wouldn't matter, but I've seen my probe go measurably past the right spot before it "hits", and my probing routines actually probe in both directions (G38.2 then G38.4, and take the average) to try to eliminate this overshoot.
With a "first hit" debouncer, you could set the debounce time to 3 seconds and still get the right value.