Debian packages search says its there in trixie if I correct your spelling error
packages.debian.org/trixie/python3-distro
try: sudo apt install python3-distro

I would try the realtek dkms driver and the additional RT kennel tuning tweaks in my YouTube guide and I think you will have good performance


If you do buy a new NIC card.definitely get  an Intel card preferably one that supports time sensitive networking (TSN) Eg i210 series en.wikipedia.org/wiki/Time-Sensitive_Networking this gives real time network performance (finally) and is supported by ethercat. Take care as some of the intel cards have different versions and the entry level card for that model does not support TSN. Not sure if this will require slave level support.

First off, I'm not a computer expert. I've followed all the steps on the website step by step. I've attached a few screenshots. Can anyone tell me how to solve this problem?

Can anyone give me full detail intruction for the INOVANCE SERVO SV635N. I have try many hal and xml file but still not working. I have test all the servo in twincat everything OK. 


jakelong@JLCNC:~/linuxcnc/configs/ethercat-test$ linuxcnc test.ini LINUXCNC - 2.9.8 Machine configuration directory is '/home/jakelong/linuxcnc/configs/ethercat-test' Machine configuration file is 'test.ini' Starting LinuxCNC... linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod Note: Using POSIX realtime Found file(REL): ./core.hal HAL: ERROR: function 'motion-command-handler' not found ./core.hal:3: addf failed Shutting down and cleaning up LinuxCNC... Note: Using POSIX realtime LinuxCNC terminated with an error. You can find more information in the log: /home/jakelong/linuxcnc_debug.txt and /home/jakelong/linuxcnc_print.txt as well as in the output of the shell command 'dmesg' and in the terminal jakelong@JLCNC:~/linuxcnc/configs/ethercat-test$ linuxcnc test.ini LINUXCNC - 2.9.8 Machine configuration directory is '/home/jakelong/linuxcnc/configs/ethercat-test' Machine configuration file is 'test.ini' Starting LinuxCNC... linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod Note: Using POSIX realtime Found file(REL): ./core.hal motmod: dlopen: /usr/lib/linuxcnc/modules/motmod.so: undefined symbol: kinematicsSwitch ./core.hal:1: waitpid failed /usr/bin/rtapi_app motmod ./core.hal:1: /usr/bin/rtapi_app exited without becoming ready ./core.hal:1: insmod for motmod failed, returned -1 Shutting down and cleaning up LinuxCNC... Note: Using POSIX realtime LinuxCNC terminated with an error. You can find more information in the log: /home/jakelong/linuxcnc_debug.txt and /home/jakelong/linuxcnc_print.txt as well as in the output of the shell command 'dmesg' and in the terminal

hey guys i am also about to try scales plus ballscrews and encoders on a larger machine

just posting here to see if Nitram is still online at all?

hoping to make this work and then document it a bit for people and maybe post a config that is working etc

cheers

Andrew

Is their any update, as I am too looking for a Mesa board

Can you show the probe parameters on the versa probe page please.

Lieber Oliver,

vielen Dank, die option rpi5:true hat geholfen, jetzt funktioniert die Axis App!
Nun kann ich mich in die Konfiguration vertiefen.

sei lieb gegruesst,
Robert

Okay , thanks i want to use this board combined with a breakout board where the original flat cable sub d plugs are connected so i want to get +24v input signals and 24v output signals that means i just have to connect field a and b with the +24v from my power supply or do i have to connecht the two a and b with a bridge ?

The 7I84/7I84U has split field power supplies so you can have different
voltages (say 5V and 24V) on the inputs and outputs

You can normally ignore VIN as it powered by field power when W1 is in the default
left position.

Drifting usually indicates that you do not have the drive enables working.

The drives should be disabled until linuxCNC in running and in the machine-on state.
At this point, the encoder feedback and PID loop will prevent drifting.
If you get drift in the machine-on state that indicates a hal, encoder or PID tuning issue.

This is a safety issue, with analog drives, the drive enable is critical.


 

Benutzt du einen RPI5 ?
dann trag mal bitte diese option mit ins json ein:

```
"boardcfg": "Olimex-ICE40HX8K-EVB",
"protocol": "SPI",
"rpi5": true,
"flashcmd": "/home/cnc/prog/olice40prog/spiflash.py -b rio.bin",
```
ansonsten bin ich etwas ratlos.

an welchem CS pin hast du das board ?

per default benutzt RIO CE0 an pin 8:
```
#define SPI_PIN_MOSI 10
#define SPI_PIN_MISO 9
#define SPI_PIN_CLK 11
#define SPI_PIN_CS 8
```

Hello , i had figured out what the mistake was , i think i had taken bad cables because i took other cables and now the connection works and i have made some exercises for myself with a led and some playing with hal commands and now the 7i73 and the 7i84u is connected to the 7i74 per cat 6 cables and with the command " halcmd show pin" i am able to see 7i97t_7i73 and 7i97t_7i84u . Another question , why are there two vfield a and two vfield b screw terminals for the 7i84u for power supply and for what stands VIN ? I couldnt figure that out . Thanks for your answer.