Advanced Search

Dear Hakan, thank you for your reply.
Could you please give me hal and ini?
If you could, I would be the happiest person in the world.

 
It should have said you can not control. Sorry.

if Mesa or ethercat,  disable energy efficient Ethernet with commands for your NIC (Intel/Realtek) and consider adjusting IRQ for the network card to prefer the core the servo thread is running one. There is a script somewhere on the forum here.

andypugh wrote:

I really thought we had a newer version than that on Bookworm, but the package lists suggest otherwise. 

[/quote]
You do. Looks like the OP is using the version included in bookworm and has not used the 2.94 ISO
But that's not an issue. Just follow the instructions in the 2.94 docs under getting Linxucnc, section 7.

But also Debian Trixie should be released in the next couple of days. Once that happens an early adopter can do a
sudo apt dist-upgrade
should install Trixie and upgrade to 2.9.4

Its quite possible to get linuxcnc and Ethercat working with secure boot. The instructions you followed have a spoiler to open  explaining how to do it. The method came from the ethercat guys and I have tested it as working.

@Rüdiger
May this be a result of the missing (?, the screenshot is hard to read) Q parameter? From the   readme :

Important Runtime NotesWhen using the S-curve trajectory planner, always use the 

G64 P[x] Q[x]

 command combination. If 

Q[x]

 is not specified, the interpreter may:

1. Remove or filter out small segments.
2. Convert arc segments into line segments.

A standard input should look like this:

G64 P0.01 Q0.0

You can do it! It will depend on you GUI. some may even have the ability to program a slider. Have a browse in the linuxcnc docs as its all documented
 

joshualee777 wrote:

Hello, I reset the device to factory defaults as you advised, but the "Amplifier Fault" error still persists. Is it because the DC setting is not set correctly? I'm wondering if you have any other advice.

The only Amplifier faults I have seen with steppers is when the drive or the motor overheats (Non-ethercat).
With Ethercat it could be a following error reported by the drive throwing this. There is a Fault code for the ETC60 so bring that out in your xml file. It can take  a bit to decode as it is a bitmapped field. Display the field in halshow. Convert it to hex or binary which Google will do for you and refer to the docs.

Hello Andy,

Thanks again for your support.
Inputting "halcmd setp stepgen.4.velocity-cmd 40" from the terminal, while a session of LinuxCNC is cutting metal, works well and is so easy to do.
Now I can adjust (and optimise) the MQL flow rate on the fly, It also allows me to easily use different flow rates for both neat synthetic fluids and also water soluble coolant.

It would be cool to control the flow rate from a virtual slider pot on the AXIS virtual control panel, but I suspect that would be well above my 'pay scale'

Thanks again

Mike

I have an INVT EtherCAT servo that can operate in DC (Distributed Clock) mode or free-run mode. Could anyone explain the differences in performance between these two modes? Specifically, is DC mode more accurate than free-run mode in terms of reducing following error (ferror)?

youre right.
I just looked at gmoccapy_tool_sensor.ini
and it should be like
SUBROUTINE_PATH = macros
the instructions website did not mention anything for subroutine path
Now it works.
Thanks

In ini file is comented:
#SUBROUTINE_PATH = ./
Why?

i have the folder macros with change.ngc and on_abort.ngc

The most important information is:

NGC file not found: ngc=change - 51:REMAP = M6 modalgroup=6 prolog=change_prolog ngc=change epilog=change_epilog

Bei den SINO-Glasmaßstäben ist die gleiche Pinbelegung wie bei den Ditron angegeben, sollte also so passen.
In der Bedienungsanleitung steht "Nullpunkt-Position: eine alle 500 mm" - weißt du, wo die auf deinen Maßstäben liegen?