I spent some time working on my machine's fault handling, and in the end all I had to add to get it to do what I wanted (stop machine on fault) is to add these (in addition to the configs I posted earlier):
  net x-fault      => joint.0.amp-fault-in
for each joint.  I also set VOLATILE_HOME for each joint in the *.ini but it didn't do exactly what I wanted.
Given that I use joint.N.amp-enable-out (aka x-enable, set in MACHINE.hal automatically) to enable the clearpaths, as soon as a fault comes in, it posts a warning and shuts the machine off, which disables the clearpaths, which clears the fault.

My ESC TEST VALUE reading is fine...
i tried a lot of things but dont know why i cant get the eeprom correctly set up. Maybe its something with the board I dont know

I tried changing the naming, but had to use different name because was already assigned to pin.I get joint fault as soon as i try to enable I did try changing delay thinking that was it but no luck.  Unless I still having a naming issue with the pins unfortunately I still don't understand this part yet.

Did anybody get it to run with Rods guide??

E.

I think they all describe steps to bring data in and out of the drive, steps that are missing in the lcec case. SOEM mentions fragmentation/defragmentation. Not more complex than that. I haven't found out if the hardware I have can be used for a prototype.
I'll keep searching.

Thanks for the reply. I've been busy with roofing, plumbing, parquet flooring etc but managed to sneak out to the workshop finally.

I've managed to get the spin boxes to appear in an otherwise blank macro screen, which is some form of progress. This was by removing the "notouch=1 -U norun=0 -u" switches from the EMBED_TAB_COMMAND line.

However, the gmoccapy screen is now bigger than the primary display once gladevcp starts up. That doesn't seem to prevent anything new from working otherwise. Presumably I need to correct the screen resolution, possibly by installing better video drivers? It used to fit the screen.
EDIT: the native resolution of the Hanspree HT225 is 1920x1080, same as the second display. No end of playing with display seems to prevent the GUI spilling over beyond the extents of the display(s), other than commenting out the EMBED_TAB line.

My path statement looks like this but perhaps I need to read up on linux path syntax:SUBROUTINE_PATH = ~/nc_files:~/lathe_macros:~/subroutines:~/python
...where those subfolders are in the folder where the INI file is held.
EDIT: I now see I should use the dot character rather than tilde in linux to denote a relative path. I will try that...
Beyond that, when I run linuxcnc from the command prompt, it reveals a royal mess. Clearly gladevcp isn't happy (see attached log file).

I tried installing python-rsvg but it didn't like that:
murray@LinuxCNC:~$ sudo apt-get install python-rsvg
[sudo] password for murray:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package python-rsvg

There are a few things going on here, to say the least - could you suggest what I focus on in the first instance?
 

The 7I76EU inputs have a threshold of 60% of VFIELD when going positive and 40% of VFIELD when going negative.
This means with 24V VFIELD, a voltage below 9.6V is read as low and a voltage above 14.4V is read as high.
This  is called hysteresis, and is deliberate behaviour for noise immunity. With a 10 K pullup you end up just in the middle
of this input threshold range, You need a stiffer pullup resistor (say 2.2K) so that you have a valid input to the 7I76EU.

Thank you. I'll learn. And ask there if don't catch something.

Thank you very much MaHa!

This worked. Initially with (debug,#5230) I got -0.012195. After G10 L2 P1 R0 it was reset to 0. Perfect. So there was a rotation active? Maybe a leftover from when I probed rotation of a workpiece?

PDI = that parallel communication mode? Noone uses it. Everyone uses SPI.
The last few lines in the xml file should look similar to this. The first "80" means spi, then there
is polarity and other settings.  Read out the eeprom from the board and verify that is says "80" in the first byte.
I have had my fair share of problems with SPI so I think you again should verify that you can get past the ESC_init() function.
Use the debugger and verify that you read 0x87654321 from LAN9252 on line 445 in the figure
 
You may need to power cycle the LAN9252, it only reads eeprom after power down.
 

I am pretty sure that you are correct, at least in the part about the inputs being reversed between the two boards.
But it is my understanding that this is why the pull-up resistor is needed, so that the input at idle is 12v and then when activated goes to 0. So to get the correct logic in linuxcnc I use the xxx-not input signal.

But I don't understand why the hal state doesn't change after the first trigger, even though I can see the voltage change on the input pin.

I managed to get spi working but I might have an issue with the eeprom. Apparently I'm stuck in PDI mode and lan9252 is not communicating through spi

I asked Grok:
the official linuxcnc Ethercat driver at github.com/linuxcnc-ethercat/linuxcnc-ethercat does not currently support EoE (Ethernet over Ethercat) drives such as the SV660N drive. Can you suggest modifications to the code to enable EoE support?
And he gave a very comprehensive answer.

Its far to comprehsensive to share on the forum due to formatting but I saved hos answer to markdown and converted to pdf which is attached

 

Sorry to bust you AI bubble but

1. where is  eoe_running defined?
2. where is *arg used?
3. the for statement seems invalid.

I find Grok lies less than ChatGPT but still gives me wrong code sometimes.
 

I spent some time with ChatGpt and I'm of course super skeptical to those tools.
Chatgpt says the likely reason for EoE drives to hang is that the EoE mailbox isn't serviced/emptied.
Yes, it isn't. Maybe one can try that, it doesn't have to be more advanced. A code snippet that does that
There is that ecrt_master_send kworm talked about. It's about principles at this point.
I would need a slave with EoE. I don't have that. Maybe maybe I can make one, there
is an example in SOES with lwip. Or anyone know of a not too pricey servo drive with EoE?