Advanced Search

I would probably use pncconfs discovery option so pncconf knows about the
additional stepgens so you can configure the B axis.
 

You should be able to use pncconf to setup your spindle
The firmware does not affect the spindle setup as the analog
spindle setup would be the same regardless of firmware.

A possible exception would be if you used the breakout board
to generate the analog spindle control voltage, but this would
really only make sense if you needed two analog outputs.
 

Hi everyone, I hope you’re doing well.

While going through the electrical diagrams of my machine, I noticed something I don’t fully understand. The schematics show a clutch on each axis. Could someone explain what exactly this means and what role the clutch plays? Is it connecting or disconnecting the motor from the ballscrew, or something else?

I’ll attach the diagrams for reference.

The spindle part I’ve already figured out, since I found out how the connections and control signals are set up. Right now, I’m working on counting all the inputs I will need to make sure the Mesa board I choose has enough capacity. Fortunately, the linear scales output 5V signals, so that part looks straightforward too.

Thanks a lot in advance — I’d really appreciate your input and experience on this.
 
 
 
 
 
 
 
 

This is the output of ip a

cnc@linuxcnc1:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2c:cf:67:3a:15:bb brd ff:ff:ff:ff:ff:ff
    altname end0
    inet 192.168.0.153/24 brd 192.168.0.255 scope global dynamic eth0
       valid_lft 799842sec preferred_lft 799842sec
    inet6 fdce:a2be:2d61:0:2ecf:67ff:fe3a:15bb/64 scope global dynamic mngtmpaddr
       valid_lft 7124sec preferred_lft 3524sec
    inet6 2003:e4:9741:1e00:2ecf:67ff:fe3a:15bb/64 scope global dynamic mngtmpaddr
       valid_lft 7124sec preferred_lft 1191sec
    inet6 fe80::2ecf:67ff:fe3a:15bb/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether aa:57:f1:85:a9:88 brd ff:ff:ff:ff:ff:ff
    altname enp1s0
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 2c:cf:67:3a:15:bc brd ff:ff:ff:ff:ff:ff

When connecting the eth1 port to my network switch I got an information from my router, that it assigned a new IP adress to the ethernet card with the MAC adress of eth1. So I assumed that it should be possible to reach that port via ping. This ping was done from a windows PC in my network. All four tries timed out. But looking to the result of ip a above, the IP adress is not shown on Linux side. This I did not see before.

The reason why I would like to use this second ethernet is because my workshop is in the basement of my house and the RaspberryPi is in a metal housing within a metal cabinet. Finally I like to use my devices hardwired instead of using WIFI. I thought it would be straight forward to put in an additional ethernet card, activate PCIe and then be able to use it.

Unfortunatelly I am not an Linux expert and I am not a native english speaker, so if I miss something from your advices please give me a hint. I will try to make it. 

I throw this here because someone will need it, they removed it from the product page: software stepperonline OMC A6 help.stepperonline.com/en/article/how-to...series-servo-edqavw/

I've already mentioned that Realtek NICs can cause latency issues and the dkms package may need installing.
I kind of the OP skipped over that part or just ignored it. Anyways I think the issue at hand is to get the interface up and running and cross the Realtek driver later.
As it was the OP was claiming the Linuxcnc image was not recognising the interface and after digging that was found not to be the case.
To tell the truth the wifi adaptor of the RPi5 is quite good, even within the confines of a metal case, and is more than enough for transferring files via samba, nfs or sftp (which is my preferred method). Ssh sessions are a non issue as well.
Given the choice of Nvme or a second NIC, Nvme will win, if a second wired network interface is needed a usb3 one will be fine, probably better if you can find one that isn't Realtek based.