Stepper online A6 Servo motor as Spindle motor

Big thanks for your help Hakan

I have retyped a few of the lines in  the Hal file and 

LINUX NOW OPENS AND THE SPINDLE RUNS !!! 

Next issues to solve 
Correct spindle speed ratio
When assigning the spindle to run at a certain speed the scaling is definitely off and is very slow . 
the belt setup is 2:1 how do I configure to this ? 

The spindle also does display that actual speed via the encoder signal any tips on how to change this ? 

Main issue: 
In getting the spindle to run it has caused the rest of the machine to jitter and run what seems like out of sync again 
changing the following " refClockSyncCycles="-5">" fixed the issue last time 
what else could now be causing the issue ? 
Many thanks 
Will 

Phuu, I have no idea why it didn't work right away. I am happy that some patience paid off.

You have some settings in the example hal filequickstop isn't used (yet), but the other values you need to adapt to your liking.
velo-scale is how many steps there are per revolution. It is probably the encoder resolution for you.
Gearing goes into that number as well.
That number also affects the velocity feedback.
Accelerations are revs/s^2. Easiest is maybe to use halshow and set different values while testing start and stop.
 

And btw there may be an error in your ethercat-conf.xml file. Two slave lines for idx=3.
 

would you be able to point to where the issue is in the .xml file ?


<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="-5">

<!-- X axis EL8 Servo Drive -->
<slave idx="0" type="generic" vid="00004321" pid="0000d0" configPdos="true">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<syncManager idx="2" dir="out">
<pdo idx="1601">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="opmode" halType="s32"/>
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32"/>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1a00">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="cia-statusword" halType="u32"/>
<pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="opmode-display" halType="s32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="actual-position" halType="s32"/>
<pdoEntry idx="606C" subIdx="00" bitLen="32" halPin="actual-velocity" halType="s32"/>
<pdoEntry idx="6077" subIdx="00" bitLen="16" halPin="actual-torque" halType="s32"/>
</pdo>
</syncManager>
</slave>

<!-- Y0 axis EL8 Servo Drive -->
<slave idx="1" type="generic" vid="00004321" pid="0000d0" configPdos="true">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<syncManager idx="2" dir="out">
<pdo idx="1601">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="opmode" halType="s32"/>
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32"/>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1a00">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="cia-statusword" halType="u32"/>
<pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="opmode-display" halType="s32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="actual-position" halType="s32"/>
<pdoEntry idx="606C" subIdx="00" bitLen="32" halPin="actual-velocity" halType="s32"/>
<pdoEntry idx="6077" subIdx="00" bitLen="16" halPin="actual-torque" halType="s32"/>
</pdo>
</syncManager>
</slave>

<!-- Z axis EL8 Servo Drive -->
<slave idx="2" type="generic" vid="00004321" pid="000010c2" configPdos="true">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<syncManager idx="2" dir="out">
<pdo idx="1601">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="opmode" halType="s32"/>
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32"/>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1a00">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="cia-statusword" halType="u32"/>
<pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="opmode-display" halType="s32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="actual-position" halType="s32"/>
<pdoEntry idx="606C" subIdx="00" bitLen="32" halPin="actual-velocity" halType="s32"/>
<pdoEntry idx="6077" subIdx="00" bitLen="16" halPin="actual-torque" halType="s32"/>
</pdo>
</syncManager>
</slave>

<!-- Spindle Servo Drive -->
<slave idx="3" name="Spindle" type="generic" vid="00400000" pid="00000715" configPdos="true">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<syncManager idx="2" dir="out">
<pdo idx="1600">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="cia-controlword" halType="u32"/>
<pdoEntry idx="6060" subIdx="00" bitLen="8" halPin="opmode" halType="s32"/>
<pdoEntry idx="60FF" subIdx="00" bitLen="32" halPin="target-velocity" halType="s32"/>
<pdoEntry idx="6083" subIdx="00" bitLen="32" halPin="acceleration" halType="s32"/>
<pdoEntry idx="6084" subIdx="00" bitLen="32" halPin="deceleration" halType="s32"/>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1a00">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="cia-statusword" halType="u32"/>
<pdoEntry idx="6061" subIdx="00" bitLen="8" halPin="opmode-display" halType="s32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="actual-position" halType="s32"/>
<pdoEntry idx="606C" subIdx="00" bitLen="32" halPin="actual-velocity" halType="s32"/>
<pdoEntry idx="6077" subIdx="00" bitLen="32" halPin="actual-torque" halType="s32"/>
</pdo>
</syncManager>
</slave>

</master>
</masters>

Here it looks fine. Saw it in the first ethercat-conf.xml you attached.

There is no reason the PV mode should cause problems with other drives.
Check the output of "sudo dmesg" the last say 20 lines are of interest.

here is the result of running sudo dmesg


[ 4.057274] Bluetooth: HCI UART protocol Broadcom registered
[ 4.083683] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 4.087327] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 4.087734] usbcore: registered new interface driver brcmfmac
[ 4.291603] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[ 4.291861] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2
[ 4.393502] Bluetooth: hci0: BCM: chip id 107
[ 4.393719] Bluetooth: hci0: BCM: features 0x2f
[ 4.394870] Bluetooth: hci0: BCM4345C0
[ 4.394873] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
[ 4.426812] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.hcd' Patch
[ 4.462459] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)
[ 4.462471] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode
[ 4.469213] pps pps0: new PPS source ptp0
[ 4.469263] macb 1f00100000.ethernet: gem-ptp-timer ptp clock registered.
[ 4.470153] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[ 4.470300] ec_master: loading out-of-tree module taints kernel.
[ 4.470306] ec_master: module verification failed: signature and/or required key missing - tainting kernel
[ 4.475936] EtherCAT: Master driver 1.6.8 1.6.8.g2543cc5-1+27.1
[ 4.476617] EtherCAT: 1 master waiting for devices.
[ 4.490862] zram: Added device: zram0
[ 4.628070] ec_generic: EtherCAT master generic Ethernet device module 1.6.8 1.6.8.g2543cc5-1+27.1
[ 4.628086] EtherCAT: Accepting 2C:CF:67:24:E6:CD as main device for master 0.
[ 4.628096] ec_generic: Binding socket to interface 2 (eth0).
[ 4.645137] EtherCAT 0: Starting EtherCAT-IDLE thread.
[ 4.747291] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.747296] Bluetooth: BNEP filters: protocol multicast
[ 4.747300] Bluetooth: BNEP socket layer initialized
[ 4.752789] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 5.129671] Bluetooth: hci0: BCM: features 0x2f
[ 5.131033] Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+
[ 5.131037] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0342
[ 5.131328] Bluetooth: hci0: BCM: Using default device address (43:45:c0:00:1f:ac)
[ 5.150144] Bluetooth: MGMT ver 1.23
[ 5.155700] NET: Registered PF_ALG protocol family
[ 6.530993] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
[ 6.537016] EtherCAT 0: Link state of ecm0 changed to UP.
[ 6.545022] EtherCAT 0: 4 slave(s) responding on main device. Re-scanning on next possibility.
[ 6.545024] EtherCAT 0: Slave states on main device: PREOP.
[ 6.545025] EtherCAT 0: Re-scanning now.
[ 6.545194] EtherCAT 0: Scanning bus.
[ 7.356283] EtherCAT 0: Bus scanning completed in 808 ms.
[ 7.356289] EtherCAT 0: Using slave 0 as DC reference clock.

Looks fine so far.
Can you start linuxcnc to see if any useful message comes out to explain jerkiness.
You can also try to temporarily remove/comment out the dcconf line for the spindle driver only in the ethercat.conf.

Having tested the machine this morning , the Juddering on the servo drives appears too of stopped for the time being?

Could it be due to the pi not being powerful enough and having bad latency? Yesterday I had a few windows open running whilst running linux .

If this is the issue is it worth upgrading from the pi5 to something with more powerful ? .
Any suggestions on reasonable priced upgrade options

Sounds good. Let's hope it keeps that way.

I ran the RPi4 for some time and it was ok, so the Rpi5 should be ok too?
Latency isn't so much of an issue now with the "-" sign.
That "should" keep it on track (sync).
You can check if it isn't doing so great with the value of the pin lcec.0.pll-reset-count
If that is way above 1 there may be a problem.
First thing to do then is to increase lcec.0.pll-step to 10000 which is max, or something in between say 5000,
setp lcec.0.pll-step 10000
If pll-reset-count then keeps increasing you need to work on the latency.

The main reason I switched to Intel-based is that the gui became more and more
sophisticated and needed more and more processing power to function smoothly.
I am hesitant to recommend a setup, there are many that works fine.
For ethercat I would definitely look for an Intel network adapter,
the rest is more form factor, power draw, cpu performance.
I have had good luck with the N100/N150 mini pcs. Intel network adapter though.